Closed whty541 closed 6 years ago
If i manually close the bot with one second left there will be no queue.
Try one of the *.dbj files "D2BotLeader.dbj or D2Botfollow.dbj" or whatever file it is
On Feb 5, 2018 9:40 AM, "whty541" notifications@github.com wrote:
If i manually close the bot with one second left there will be no queue.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/kolton/d2bot-with-kolbot/issues/339#issuecomment-363142323, or mute the thread https://github.com/notifications/unsubscribe-auth/AIrd05fFNMmRZkGpnfq_NvJLpy2SZ9zEks5tRy72gaJpZM4R5rvB .
im not sure what im looking for i use D2botlead.dbj but is there a setting in there that needs changed?
Well in D2Botleader.dbj it has lots of that might help u out. Turn of all wait times or lessen them
On Feb 5, 2018 10:44 AM, "whty541" notifications@github.com wrote:
im not sure what im looking for i use D2botlead.dbj but is there a setting in there that needs changed?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/kolton/d2bot-with-kolbot/issues/339#issuecomment-363162100, or mute the thread https://github.com/notifications/unsubscribe-auth/AIrd09AQc0csd1DnbS6rv1JfAgUUhK1-ks5tRz3igaJpZM4R5rvB .
took all the wait times off and i still go back to the login screen after a run
I have same issue. I have used all the .dbj files during troubleshooting. It appears to be an issue with d2bs core and the way it handles logins / game creations / leaving a game. Mule, Blank, Lead, Follow all have the same issue. Legit D2 loaded does not produce a queue, but a blank bot loaded, create one game, leave, next game is queued 600s. Bot is working, but not at optimal speed. Currently just maxing every script i can to get max monsters killed/hour due to this queue issue.
V1.14d legit version, no VH, no extrawork etc. just basic d2bs + kolbot
However, vampirewolve on BH has a 1.6xxx version of d2bs, we have 1.5.x.. he may have fixed that core issue ;)
I'm getting the exact same issue, bot logs after every run then I have to wait in queue. Nothing that I found could fix it either, I've looked through all the .dbj files and still no solution.
Its definately in the way d2bs leaves the game. If you force close manually before the run is finished, there is no queue on relog. That really narrows it down quite a bit.
This problem also happens if your bot chickens.
Removed due to snitching on blizz forums ;p
200+ runs no issues since that fix
Works, no queue.
you deleted the fix, how can i fix it now?
Toolsthread.js this.exit = function () { this.stopDefault(); //quit(); quitGame(); // used to prevent 600 game queue after every run, this will close and reload d2 after each run. Not ideal, but works. };
Bot runs and works fine I have the games set to 10 minutes, so after the wait time is up it exits game and instead of making a new game it seems he logs out and logs back in resulting in a queue, I only have 1 key and one account running so im not sure if its trying to switch to a key or what. Ive looked through the leader file and i cant see any setting in there that i could change, There was a user on here that posted the same issue as me but then he closed it and said fixed without giving the solution. Any help would be great thanks.