Issue with kolbot config (some options do not work)

[azur3wrath]

Hey! Ive been trying to use kolbot for couple of days however discovered some major problems during setting up. The bot in general works however it seems that some functions are not working or are limited

1. The bot runs, executes the script however if I don’t set up max time per game it stays in the game forever

2. The auto pot seems to not work at all - health and mana just keep dropping until I run out of it and die (if mana, character waits until mana replenishes to attack/tele). It doesnt heal the merc as well, if thats important

3. Chicken is not working either, character simply does not leave the game - not talking about being one shot, when he is out of mana he will simply wait until mobs kill him

4.* (bonus question): I have been trying to use kolbot to join public diabaal runs in order to exp using D2BotPubJoin but regardless what I put in the filter it just doesn’t want to join any game. Would anyone have any working script here?

Many thanks in advance.

[DarkHorseDre]

1-3 are all covered in your config file - ensure you are using the latest and the correct folder (if you have more than one repo of kolbot) and are editing the correct config file. read the comment text that describes how to set each option (maxgame time, pot & bely config, chicken and also useraddon) and how to correctly have a new config generated for a character.

I'd also search open & closed issues here to see if people have already asked and answered your questions as a lot of this sounds familiar.

[azur3wrath]

The point is, I tried to recreate the character config file from scratch, didn't help. I am pretty sure I am using the correct config, as every other change is simply visible (e.g. particular farming route, maximum game length, cain identifying, etc). I can live with 2&3 but my main problem is that if I put it like this:

// General config Config.AutoMap = false; // Set to true to open automap at the beginning of the game. Config.LastMessage = ""; // Message or array of messages to say at the end of the run. Use $nextgame to say next game - "Next game: $nextgame" (works with lead entry point) Config.MinGameTime = 300; // Min game time in seconds. Bot will TP to town and stay in game if the run is completed before. Config.MaxGameTime = 0; // Maximum game time in seconds. Quit game when limit is reached. Config.TeleSwitch = false; // Switch to secondary (non-primary) slot when teleporting more than 5 nodes. Config.OpenChests = false; // Open chests. Controls key buying. Config.MiniShopBot = false; // Scan items in NPC shops. Config.PacketShopping = true; // Use packets to shop. Improves shopping speed. Config.TownCheck = true; // Go to town if out of potions Config.LogExperience = true; // Print experience statistics in the manager. Config.PingQuit = [{Ping: 0, Duration: 0}]; // Quit if ping is over the given value for over the given time period in seconds. Config.Silence = false; // Make the bot not say a word. Do not use in combination with LocalChat

my game will last forever despite the fact game time exceeds minimum game time.

[azur3wrath]

Also, to make sure, my D2BotLead.dbj looks as following:

var StarterConfig = { MinGameTime: 300, // Minimum game length in seconds. If a game is ended too soon, the rest of the time is waited in the lobby PingQuitDelay: 30, // Time in seconds to wait in lobby after quitting due to high ping CreateGameDelay: 23, // Seconds to wait before creating a new game ResetCount: 999, // Reset game count back to 1 every X games. CharacterDifference: 99, // Character level difference. Set to false to disable character difference. ChatActionsDelay: 2, // Seconds to wait in lobby before entering a channel

[DarkHorseDre]

Zero as a value sets this (and many others) as infinite (or disabled?)

set it to a value greater than zero/min gametime - you don't want a game that has a max of zero, you want a game that is greater than mingametime but not infinite no?

[azur3wrath]

Every tutorial on youtube mentions 0 as number where whenever all scripts are finished, the bot resets the loop. Sometimes it is hard to evaluate the full time of the run (if I set it as 12 minutes and bot stucks somewhere for a bit longer time, it doesn't finish the loop)

[DarkHorseDre]

Finishing the loop isn't the goal if you are MF'ing/xp'ing - you want to maximise xp/mf over time, so getting stuck or wasting time is to be avoided. you want the game to end and restart.

you should time an average run and set your end time to that/just after that. any "stuck" points or errors should be investigated and solved or avoided (e.g. stop running certain bosses etc)