5 ms·
I don't believe this is the case, as OpenAI was able to hex (an immediate disable) Earthshaker before he got off Echoslam (a spell with no cast delay except the
by larkeith 8y ago
I don't believe this is the case, as OpenAI was able to hex (an immediate disable) Earthshaker before he got off Echoslam (a spell with no cast delay except the time to click the key).
- def_true_false 8y agoThe ES player didn't queue his abilities so there was delay between blinking and casting echo. Someone counted the frames and it was well over the 200ms minimum.
- el_devo 8y agoHere is a post from the Dota 2 subreddit discussing the timing with proof that OpenAI's reaction was over the 200ms minimum: https://www.reddit.com/r/DotA2/comments/94vdpm/openai_hex_was_within_the_200ms_response_time/ https://www.reddit.com/r/DotA2/comments/94vdpm/openai_hex_wa...
- Q6T46nT668w6i3m 8y agoYeah. I agree. It was over the 200ms minimum but it was artificial. No human could reasonably perform that type of action as relilably. And that has nothing to do with learning performance.
- eptcyka 8y agoYou can queue abilities to instantly cast them after the previous one finishes, so it is actually quite reasonable for a human to perform that type of action quite reliably.
- def_true_false 8y agoThey probably meant the reaction, not the blink and echoslam.
- StavrosK 8y agoDid he blink in? Is there a delay there?
- dx87 8y agoThere's no delay, but when people looked at the replay, Earth Shaker was actually visible when he thought he wasn't. The AI that disabled him had precast his spell on the out of range Earth Shaker, so when Earth Shaker blinked in to range, the precast spell went off in the following server tick.
- StavrosK 8y agoThat makes sense, thanks.
- Strom 8y agoThat's not what happened. The 200ms delay worked as intended. The reddit thread counting the frames can be seen here: https://www.reddit.com/r/DotA2/comments/94vdpm/openai_hex_was_within_the_200ms_response_time/ https://www.reddit.com/r/DotA2/comments/94vdpm/openai_hex_wa...