I'm not sure if this has been posted before, but I can't find any reports on this so I figured I'd add it:
Using:
"/roll xdy!>0" (Specifically, the one tested that resulted in the worst slowdown, was "/roll 50d20!>0")
Causes dice to roll infinitely, as a dice roll is never going to be a 0 (Obviously), and this constant rolling slows down the game room unbearably (Typing has close to a 20 second delay, dragging map is impossible, even trying to click the settings tab is borderline impossible) effectively making the command an exploit to make a room unusable.
I was testing out dice mechanics and for the heck of it I tried the "!>0" part (I figured it would throw an error) however it did not, and therefore became an easily exploitable bug to stop a game entirely. Additionally, as of 3 days later, said game is still unbearably slow, and does not appear to have any end in sight.
I would suggest adding a simple check to ensure that rolls' stop conditions are actually possible to occur, to prevent exploitation.
Using:
"/roll xdy!>0" (Specifically, the one tested that resulted in the worst slowdown, was "/roll 50d20!>0")
Causes dice to roll infinitely, as a dice roll is never going to be a 0 (Obviously), and this constant rolling slows down the game room unbearably (Typing has close to a 20 second delay, dragging map is impossible, even trying to click the settings tab is borderline impossible) effectively making the command an exploit to make a room unusable.
I was testing out dice mechanics and for the heck of it I tried the "!>0" part (I figured it would throw an error) however it did not, and therefore became an easily exploitable bug to stop a game entirely. Additionally, as of 3 days later, said game is still unbearably slow, and does not appear to have any end in sight.
I would suggest adding a simple check to ensure that rolls' stop conditions are actually possible to occur, to prevent exploitation.
