hugomg
commented
10 years ago The problem with the old method is that the only way to know what the real slowmode time limit is is to try to send a message and get it rejected. Because of this, in the old version the slowmode timer was hardcoded to the script and would never decrease if it were too high. In the new version, if the script thinks the slowmode is longer than it really is you can bypass it. If it succeeds, good for you. If it fails twitch sends an error message back and we can update the timer.
I don't know how to get the best of the both worlds though. One possibility is adding back the sent message to the chat box if it gets rejected by slowmode. Another one is going back to fixed slowmode timers (and let them be controlled via settings?)
Alright so here's the problem:
You input something. Say you press A. Now the timer is activated (3-4 seconds after inputting a command). In the old script, you could have a new A (or any other command really) in the message bar and spam ENTER without it inputting. But now, with the new script/twitch chat, even if the timer is still counting down/active, if you press enter with a command in chat, it'll send it BUT it won't be counted as the timer was still active. Same problem with touch screen. In the old script I was able to spam click the touch screen and it wouldn't input my commands until the 3 second timer was over. But now it just spams the chat regardless if the timer is up or not.