Bot literally afk's out of every game now

[danyo]

So I've been botting since release of this bot and I've been having no problems what so ever until the recent patch hit. Now the bot doesn't even play a full game. It'll join a game no problem, but then I noticed after returning after several hours I'm flagged for doing QM after leaving games (or getting afk'd out from what I've been seeing). SO I started the bot, and watched it queue up just fine and after about level 4 it literally STOPS doing anything and just afks in lane. I've reinstalled the bot completely which it tends to fix the problem for a few hours but then I noticed it breaks again after only barely half a night of botting. This happens on any character that the bot "supports".

Anybody else having this problem now? I can't even bot a single game anymore without afking out of the game.

Here is the log I saved during this game.

Settings saved
Run started
Selected hero : Nazeebo
Start Game - Searching for players
Map Modus - Dragon Shire
Wait for loading screen
Game is ready !
Level 4
Bot is dead - Waiting for respawn
Try rejoin
Try Debug Step 01
Bot sleeps for 45 sec
Game is ready !


Here is the log I saved the night prior

Settings saved
Settings saved
Run started
Selected hero : Nazeebo
Start Game - Searching for players
Unknown Error @ w8 timer mapmodus
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Try Debug Step 03
Try Debug Step 01
Game

 

[serg312]

i have same problem.

 

[madeinchina85]

the afk kick timer is quite unforgiving once you afk out for the first time during a match. The bot is very insistent on only contributing when minion waves are available. This typically leads to repeated kicks which the bot response poorly or not at all to.

I seem to see this happen more frequently with some heroes than others. For example, from my experience falstad will time out maybe every 2-3 games, where azmodan will time out maybe once every 8-9 games. Hope this gets fixed soon.

 

[NoExcuses]

Does the bot go afk during the game and you get disconnect for afk
or
lose the connection to the game and the debugger did not find back into the game ?

 

[danyo]

Does the bot go afk during the game and you get disconnect for afk
or
lose the connection to the game and the debugger did not find back into the game ?

The bot appears to go afk during the game and I get disconnected for being afk. Once I get disconnected for being afk the bot is unable to "rejoin".

 

[NoExcuses]

Is it possible that the bot stuck in skilling talents, bacause the talent window stays open?

 

[danyo]

Is it possible that the bot stuck in skilling talents, bacause the talent window stays open?

Hmm that could be possible actually. I had noticed that a few times it could not (for whatever reason) select a talent but then I intervened and chose one for it and it continued to derp that game unable to select any talents. I'll do a thorough test tonight when I get home.

 

[danyo]

Looks like the bot is working as normal now. The only change I had made was setting the graphics to ULTRA instead of HIGH and it didn't have any issues through out the whole night playing various characters.