Kolbot not waiting long enough when creating games

Support
1

Hello, sorry to bother you guys but while running my bot i noticed it throwing “failed to create game” multiple times and when i watched the process the que would start around 800 for a position in line then when it drops to around 24 it cancels and attempts to create another game starting over again and throws the failed to create game. Im in USEast and have updated kolbot via tortisesvn as well. Was wondering if there was a way to increase the time between pressing the create game button and checking to see if game was created . Thanks in advance

1 Like
2

WaitInLineTimeout: 60, // Seconds to wait before cancelling the ‘Waiting in Line…’ screen

This is in the lead.dbj

1 Like
3

if waiting in line appears, the better choice will be to stop for some hours.

if you wanna randomize the timers from D2BotLead, check - https://github.com/blizzhackers/documentation/blob/master/kolbot/MultiBotting.md/#randomize-the-timers

in D2BotLead you have in default line 4

	CreateGameDelay: 10, // Seconds to wait before creating a new game

increase that value, and also increase the value from line 16 up to 120

	CrashDelay: 5, // Seconds to wait after a d2 window crash

otherwise you could try https://github.com/blizzhackers/documentation/blob/master/kolbot/MiscellaneousOptions.md/#staggered-delays-for-creating-games

2 Likes
4

These last two replies don’t address the actual issue. Seems to be another setting or issue with kolbot. I have my wait in line set to over 900 seconds which should be 15mins and frequently kolbot will randomly cancel the game and create a new one about 3-4 minutes into the wait. Eventually it will fully wait for the game creating queue but it’s definitely frustrating to have to sit through the queue 3-4 times before the bot actually creates the game. I have it running right now and even though my delay is 900 seconds, it cancels about one minute in. I doubt kolbot programmers expected to have to deal with 5-10 min game creation waits.

1 Like
5

@kadoobiedo @Lucifersfire
Hi!
The two responses, one from @InterestingIndeed and from @mf22 do point us in the right direction.
From what I can understand from your explanation, this is what you are experiencing:

  • start around 800 for a position in line, then
  • when it drops to around 24 it cancels, and then
  • attempts to create another game starting over again and throws the failed to create game

Within the D2BotLead.dbj file, you may need to make these changes:
(Note: all of the following values are what I use and which work well with these darn queues)

  • CreateGameDelay: rand(120,180),
  • CrashDelay: 480,
  • FTJDelay: 480,
  • RealmDownDelay: 15,
  • PleaseWaitTimeout: 30,
  • WaitInLineTimeout: 1200, < this one is the one which you may need to reduce/increase/tweak as this is my setting for a ~2700 queue wait in line. If it leaves the waiting in line too soon, increase it
  • GameDoesNotExistTimeout: 60,

It may be best to start with a large value for your: WaitInLineTimeout: 1200, and then to reduce by a little at a time.

The fact that your bot is ending its wait as soon as it does is odd as its code can hangle pretty much any length of delay.

Please, plug in the values that I use and see if it continues to do that.
If you can, please time the length of an 800 queue. I have had only 2700 to 4000 queue line waits. Those are very long queues.

Hope these help! And, welcome to the two of you to the forum!

1 Like