mat1jaczyyy

https://github.com/tetrjs/tetr.js/assets/13300194/237d0e19-20a3-4b3a-a89e-90e66effc715

do you expect the newly implemented err/kick/nope handling to handle this case, allowing us to log the error and only taking down that client instead of the entire process?

> the newly implemented err/kick/nope only emits the respective events that are sent from the server can you pls try catch this somehow and stall for a second or two...

big if true, is he right

well it didnt happen last month but it just happened again right now, luckily it's stream room so no big deal but if this were to happen mid tournament we...

how different is the new one, at a glance

@Mistera91 this project definitely will not support new ribbon.

Sure, not sure when I'll find free time, but this sounds reasonable. What behavior do you expect when the "held down" pads are re-pressed again betwen steps 3 and 4?

i will add this but not soon, there are lots of things that are higher priority unfortunately

specifically which t-spin would not count for b2b? that sounds like a bug in tetrio honestly