You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The default watch mode is "Exit replay after end".
Watch player DERKMEH until the very end. You'll see that their last moves are LEFT and then HARD DROP:
Go back to that match, but change the watch mode to "Pause reply after end".
Again, watch player DERKMEH until the very end. When the player pauses, the game omits the LEFT:
Note that in my reproduction, it's quite obvious why DERKMEH loses regardless of which watch mode you do. But I reckon that in a scenario where the player misdrops an I piece into a 4-wide well that's in the middle of the board, and they watch the replay and reproduce this bug, it will confuse the player as to why they lost.
Expected behavior
When the video pauses when watching in mode "Pause reply after end", it should show the very last move that all players do.
Screenshots
No response
Console logs
Likely not needed.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Checklist
OS and Version
HP Elite Dragonfly 13.5 2022 (16GB) Chromebook
Browser and version
Chrome Version 121.0.6167.212 (Official Build) (64-bit)
Describe the bug/issue
"Pause reply after end" doesn't always show the very last move that a player does, probably because of some timing issue.
Reproducing
Steps to reproduce:
Note that in my reproduction, it's quite obvious why DERKMEH loses regardless of which watch mode you do. But I reckon that in a scenario where the player misdrops an I piece into a 4-wide well that's in the middle of the board, and they watch the replay and reproduce this bug, it will confuse the player as to why they lost.
Expected behavior
When the video pauses when watching in mode "Pause reply after end", it should show the very last move that all players do.
Screenshots
No response
Console logs
Likely not needed.
Additional context
No response
The text was updated successfully, but these errors were encountered: