Bot implementation / command limits

[jip]

Thx for the replies.

@xDemonsxXxSaintx

About once every five minutes, the server will send you a “PING :tmi.twitch.tv”. To ensure that your connection to the server is not prematurely terminated, reply with “PONG :tmi.twitch.tv”.

My bad, i have implemented the PING PONG. I didnt mention it because the error occurs before the first PING arrrives.

@xDemonsxXxSaintx

Twitch also limits the amount of data sent to and from a single address.

You mean other than message/whisper limits? In the test-case the bot sends 100 JOINS and “.mods” commands to get the moderator list of each channel. 245 messages in total.

@3ventic

Once every 300ms amounts to 100 in 30 seconds, which is the current limit for channel moderators. The send limits are per account, so additional connections on the same account having their own independent rate limiting is going to break.

I am really suprised that the message limit is per bot account. I thought it is per connection. How can you handle (even with verified state) a lot of channels (500+) at the same time? Not that I am in that range, I just want to implement it correctly.

@3ventic

You can also only rely on having the mod limits if you 100% trust the broadcaster(s) using your bot not to unmod it while it’s above the non-mod limit.

Currently i am kind of working around this by reacting to

:jtv MODE #channel -o user

message and move (part and rejoin) the channel to a connection with VIEWER iteration and the other way around. But it feels not reliable since the bot might react during the transition time and maybe the MODE message is not received or to late.