Deepbot stops responding every now and then (every few minutes it will stop responding for very few minutes, making it unresponsive towards commands and working with the bot impossible,)
after its done having its phase (after chosing to wait for the program to respond again instead of shutting it down) it acts like nothing happened and just spams out all the commands and everything else that has happened while it wasnt responding.
It sometimes gets stuck in a loop though, aspamming (literally spamming) through all my timed messages without mercy until i reconnect the bot
While it doesnt sound like much of a big deal (since the commands just respond VERY late, its really annoying for my stream since i work with a lot with viewer queues and many people dont bother joining until my match is over and i invite a new batch of viewers to my party.
people wanting to join while the bot isnt responding wont get into the queue in time and i have trouble operating the bot and drawing the viewers since its not responding.
problem has been there the past few days...
I've had this problem before and also made a post on it, all the suggestions at that point did not fix my issue.
the problem just randomly disappeared after i gave up on deepbot and called it a day, then at some later point (DAYS later) i opened it and everything was just fixed?
it responded just fine, several hours a day, every day, for months.
now the problem appeared again and its really frustrating.. i need this bot to work properly as soon as possible..
I tried: reinstalling, switching ports, disabling scanning the chat for mods, running deepbot on its own so no program interferes with it, firewall is not blocking deepbot, running deepbot a few hours before stream starts to see if the problem fixes itsself, disabling any other features of deepbot ( timed messages etc. and as said, i used a completely new version of deepbot and the problem still persisted) claims its up to date (which makes sense since i just downloaded it again)
please help me find a solution to this..
win 10
(freshly installed OS, the problem still persists)