my bot “Lootboxbot” is a nice little interactionbait bot that is currently on the maximum amount of channels allowed for a non verified bot.
I am currently in the middle of writing a website for my bot to make it easier for streamers to edit their settings and everything and even wanted to make the invite (and kick) for them fully automated (currently I had to to run one chatcommand to add or remove it from a channel) and also for users to be able to see their items from the bots. (The bot generates random loot for users which land in an inventory)
But then I suddenly got hit by my bot being down and it took me a bit to realize that my bot is being killed by twitch because it joins “too many channels”. So I checked around and saw that the documentation officially states that no bots are being verified anymore. This technically means that it is impossible ever to establish a new bot unless it runs on the streamers end like with “streamerbot”.
Since the bot verification formular is still available I just filled it out just in case but generally I opened a ticket and explained what the bot is but the support agent only read the word “drop” in my explanation and instantly sent me the text template for twitch drops.
Then I fully explained the bot again with all commands (as it is requested for bot verification) and I got another reply “Oh you like bots, then try nightbot or stream elements and if you wanna ever try to make your own bot then read the documentation”… Again my text was not read. The bot is running for almost a year now, flawlessly, no errors, crashes ro anything. The only downtime the bot ever had was twitches fault or server/bot updates.
Am I really at a wall and am not allowed to let the bot grow further? Is this really the end? Or is there any way to get a real human to read my ticket and maybe help me?
I am sad, angry and desperate. I don’t want to have my bot just sitting on this few channels, I want to see it grow, where many people can enjoy the silly stuff.
You don’t need bot verification at all for growth, you just need the appropriate permissions from the channels using your bot.
For example if you look at the Channel Chat Message EventSub topic, you can use an App token if you have the user:bot scope from the chatting user (ie, your bot account), and the channel:bot scope or be a mod in the broadcasters channel. With those permissions your bot will show up as a channel bot in chat and will have an EventSub cost of 0, meaning that your bot can grow to listen to as many channels as needed, the streamer just needs to auth with the appropriate permissions.
So it seems like you’re attempting to use the wrong tools for what you’re trying to achieve here as all of this is entirely possible without needing verification or any special status from Twitch, and even brand new bots can still grow.
thanks for the reply, which is the first real reply to this topic I ever get in a twitch environment.
So far, if a user wants to use my bot I let the bot just simply join the irc channel for them with a simple /join. But how would I else join a channel and how would my bot “get” the invite? I am a bit confused. I always make my local bots use mostly IRC unless I need infos I only get from helix, so I never run into any ratelimits. My Lootboxbot is the fist public bot I have, so I might miss some things here that I never needed to use.
If you could maybe point me to that I’d be really happy.
Currently my bot uses a simple oauth token (read/write) for the IRC and a Client & Secret from my corresponding app from the twitch dashboard.
Then they return to your site and then you know it’s time to create the eventsub subscription for the channel.chat.message and thats the IRC “/join” equivalent
Alternatively a subscription to user.authorization.grant will tell you when people auth to attempt creation/joins
I never knew that. Hmm that looks kinda overcomplicated for what it does and I’d honestly rather want to stick to IRC. It’s so much easier to handle, responds much faster than api…
So I gotta full convert to helix for that. rip… I wish I could stick to irc
But big thanks for the reply! Finally I know what I can do.
Seeing that nightbot and streamelements take sometimes 2-3 seconds to reply and often just fully ignore commands that are not on cooldown in bigger channels where my IRC bot always flawlessly answered in subseconds…
That is my only metric I can see live, I sadly can’t look whats causing this but that always made me wanna stick to irc as much as I can. (tbf: Me working with IRC for 30 years might also have a tiiiiiiiiny little point in that argument too)
IRC has it’s own set of issues, such as when you grow to larger number of channels you have to distribute them over multiple connections, and if one goes down you have to slowly rejoin each and every channel it was joined on which takes time due to the join channel rate limit. With EventSub Conduits if there’s an outage you just start up a websocket, attach it to the conduit, and all of your EventSub subscriptions will be ready to go without you need to subscribe to each one again.
I’d recommend actually trying EventSub before just dismissing it outright, as if you wish to grow your bot then this is the most appropriate way for your bot to scale.
The bot now is fully on helix and the conversion took like 40 years off of my lifespan, me being over 40 doesn’t make that a good thing lol but it works.
I found something I don’t like but I hope it has a simple solution. Someone that has their chat in follower/subscriber only and my invited bot, marked as channelbot can not reply. Is giving the bot mod/vip a MUST for this or should bots be automatically bypass this?
Because it makes no sense to me that I invite a bot to my channel, to talk in my channel to have to “waste” a VIP/Mod Slot on them?
Bots cannot bypass this restriction (IRC or otherwise), would be nice though, on follower mode at least since doing oAuth to grant access to be present
Okay so I added the mod scope and see that THIS is the reason even the smallest toy bot always asks for mod.
A bot invited by the channel owner should honestly have no restrictions in when it comes to chatoutput. As giving every bot that doesn’t even have mod commands or features, rights to do bad things if the dev suddenly wants to is actually a security risk and giving bots just the rights of a VIP without wasting a VIP or Modslot should be the standard.