-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: No Escape - stun effect removed #131
Comments
Just happened again no_escape_stun_2.mp4 |
Hey @kissiga, thanks for reporting The removed stun appears to occur because the minimum turn TU (3TU) for the victim was not exceeded prior to the stun being inflicted. So, when the victim ended their turn, and the minimum turn TU cost kicked in, this advancement in TU caused the stun to expire (since the stun only lasts .5 TU for the victim). Alternatively, if the minimum turn TU is exceeded prior to triggering stun, it will last until their next turn as expected. 2023-03-13.12-37-06.mp4 |
Hey @XQAMike, thanks for the explanation. I recently played a game where my opponent's ZZoo moved 5 fields (that's all he did), which cost him slightly less than 2 UT (ZZoo had a 99% INI). He triggered my No Escape, and the stun remained. This is what confuses me now. :) https://www.dropbox.com/s/qvls3gqrr5e2mn8/noescape_stun.mp4?dl=0 |
@kissiga Upon further discussion with the designer, cleansing stun on the same turn that it was applied is not intended. We'll be filing an issue for this. Thanks again for the detailed reports :) |
@XQAMike Thank you too :WassieDab: :WassieDab: |
Contact Details
Simi
What happened?
The No Escape stuns the opponent but as seen in the video, the effect disappeared for some reason.
Steps to reproduce
as in the video
Expected Behavior
AFAIK the opponent's ZZoo should have remained stunned.
Which browsers are you seeing the problem on?
No response
Which wallet are you using?
No response
Screenshots / Videos capture / Attachments
no_escape_stun.mp4
Code of Conduct
The text was updated successfully, but these errors were encountered: