[X] I am using a supported browser or the Desktop Client.
[X] I am not using anything that modifies game code (e.g. TETR.IO PLUS).
[X] I am certain this is a bug, not a feature request.
OS and Version
Linux Mint 21.3 x86_64
Browser and version
Firefox 126.0.1 and TETR.IO Desktop v9
Describe the bug/issue
There's a very rare Game Over condition called "Top Out" which occurs when the stack gets pushed by garbage into the vanish zone (above row 40 on the standard board size).
However, TETR.IO doesn't do that.
Instead, the lose condition seems to be when the active piece gets dragged by garbage into the vanish zone.
Reproducing
There are various methods of testing this behavior:
In a PvP:
Set the garbage multiplier to something absurd (like 100), garbage cap 100, and continuous garbage spawn.
Shrink one of the windows, so that the entire buffer zone is visible.
First test whether the player dies because of the active piece getting dragged into the vanish zone
Use an anonymous account to send garbage to you.
Place a piece to tank the garbage.
Watch your active piece getting dragged with the garbage.
You should be Spike KO'd.
Second test whether the player dies because of the active piece getting dragged into the vanish zone
Make sure you have an I-piece early. If not, place some pieces, so that only 1 column gets blocked.
Use an anonymous account to send garbage to you.
Place a piece to tank the garbage, and hope that the garbage doesn't spawn in the column on which the piece was placed.
Insert an I-piece into the hole in the rising garbage.
Notice that only 40 lines of garbage got inserted, and no Top Out occured despite the stack being pushed into the buffer zone.
In singleplayer:
Zen test
Set the Cheese messiness to 0 and turn on the cheese timer.
Insert an I-piece into the hole in the rising garbage.
Notice that the cheese won't stop rising even when the garbage reaches row 40.
Expected behavior
An instant Game Over if addition of garbage would push the stack into the vanish zone (above row 40 on the standard board size).
Screenshots
(Change the extension from .json to .ttrm)
First test whether the player dies because of the active piece getting dragged into the vanish zone
piece_gets_dragged.json
Second test whether the player dies because of the active piece getting dragged into the vanish zone
long_bar_in_hole.json
Checklist
OS and Version
Linux Mint 21.3 x86_64
Browser and version
Firefox 126.0.1 and TETR.IO Desktop v9
Describe the bug/issue
There's a very rare Game Over condition called "Top Out" which occurs when the stack gets pushed by garbage into the vanish zone (above row 40 on the standard board size).
However, TETR.IO doesn't do that.
Instead, the lose condition seems to be when the active piece gets dragged by garbage into the vanish zone.
Reproducing
There are various methods of testing this behavior:
In a PvP:
Set the garbage multiplier to something absurd (like 100), garbage cap 100, and continuous garbage spawn. Shrink one of the windows, so that the entire buffer zone is visible.
In singleplayer:
Expected behavior
An instant Game Over if addition of garbage would push the stack into the vanish zone (above row 40 on the standard board size).
Screenshots
(Change the extension from
.jsonto.ttrm)https://github.com/tetrio/issues/assets/125081901/6795b3a0-d550-483d-898b-f68258b42672
An extra: Delayed piece spawn kills the player if garbage reaches the vanish zone. delayed_piece_spawn.json
Console logs
No response
Additional context
This behavior may be intended, because of an issue with loud garbage addition sound in Zen, which I can't seem to find.