BotsHub

Thorulf · 01/12/2026, 21:17

First: great work on the updates!

I don't know exactly why but since the Hub 2.0 update it is getting repeating disconnects (code 007) after exactly one run. The log always looks the same.
When finally managing to reconnected (normally after 30+ manual attempts), the inventory is not full (10+ free slots). It is very odd that the inv full+pause message appears after the sell message. Apparently it starts a new run but a crash/dc occurs. Manual human runs do not cause this.

What could the reason and solution be?
Any insight is highly appreciated.

Code:

19:38:02 - Map has been fully vanquished.
19:38:02 - Travelling to House Zu Heltzer (Outpost)
19:38:09 - Run Successful after: 47min 46s
19:38:10 - Travelling to Eye of The North Default (Outpost)
19:38:17 - Identifying items
19:38:23 - Salvaging items
19:38:32 - No space in inventory to move the items out of the equipment bag
19:38:32 - Moving to merchant to sell items
19:38:39 - Selling items
19:38:39 - Inventory full, pausing.
19:38:39 - Starting run 2
19:38:39 - Travelling to House Zu Heltzer (Outpost)

PS
I have a local git branch and am working on adding more useful into to the logs. E.g. how many free slots are considered "full inv", how many item are actually sold, etc.
DS

Kronos8 · 01/12/2026, 21:43

I have no plans for a bandit raid bot but I'll add it to the wishlist.

@

I don't know, I'm not running UW bot very much. Is the whole team dying in the traps ? Maybe bringing some whole team healing/regen like Together_as_One could help but honestly it's a shot in the dark.

For Tasca I think you can look into the related file to find more details about team builds.

@

I had some disconnections today too. I think not all bots are equal for that though.

Quote:

It is very odd that the inv full+pause message appears after the sell message.

I wouldn't bother too much with this, if game disconnects, bot reads **** from memory and anything can happen. The real question is what was the bot doing right before crash that could have lead to it, and is there something we can do to reconnect and continue business as usual.

Thorulf · 01/12/2026, 22:10

Quote:

Originally Posted by Kronos8

I wouldn't bother too much with this, if game disconnects, bot reads crap from memory and anything can happen. The real question is what was the bot doing right before crash that could have lead to it, and is there something we can do to reconnect and continue business as usual.

I fully agree. Have been monitoring it manually, simply never timed it in order to see exactly what happens (40+ min runs, 1s crash/dc = the odds are very low).

For the Record: I am getting very strong Deja Vu about this! I know there where code 007 disconnects a long time ago, but don't recall if I did a specific fix, or if it simply went away by itself. Never made a note about it since I trusted it was gone for good. Bugging me like crazy! xD

Predictions are very hard, especially about the future.

PS
I just have to ask: did anything special in the combat change with version 2.0? I notice alot more skill usage with "not enough energy" and "not enough adrenaline". It's so bloody annoying I cannot even have the sound on (not a fan of high pitch, much prefer base). A setting to relax this overzealousness would be super! Just chill 2 seconds between skill use would be enough. ^^
DS

It consistently happened again, dc crash with code 007.
Missed the exact moment. Log below.

Code:

22:59:02 - Travelling to House Zu Heltzer (Outpost)
22:59:09 - Run failed after: 28min 47s
22:59:10 - Travelling to Eye of The North Default (Outpost)
22:59:17 - Identifying items
22:59:20 - Salvaging items
22:59:25 - No space in inventory to move the items out of the equipment bag
22:59:25 - Moving to merchant to sell items
22:59:31 - Selling items
22:59:31 - Inventory full, pausing.
22:59:31 - Starting run 2
22:59:31 - Travelling to House Zu Heltzer (Outpost)

Interesting fact: after spamming login and dismissing all code 007 errors, it actually continues the run, but fails/forgets to set HM so its not a real vq now. The reason is most likely that it does not recognise the DC and mode reset.

Exact continuation of the log:

Code:

23:14:07 - Moving to Ferndale
23:14:50 - Taking blessing
23:14:57 - Buffing party
23:14:57 - Consumable used successfully: ID = 37810
23:14:57 - Consumable used successfully: ID = 26784
23:14:57 - Consumable used successfully: ID = 22269
23:14:57 - Consumable used successfully: ID = 28436
23:14:58 - Mantis Group 1
23:15:42 - Mantis Group 2
23:15:46 - Mantis Group 3

Update:
* Without toolbox the DC happens after 2 runs instead of one. Don't know if this is relevant.
* Regardless: there is pausing without the inventory being full. Concretely with 10+ free slots. Is this a known issue or something I can fix with my config? I have set to use the max 5 bags.
* I have a clear memory of adjusting the amount of free inv space limit b4 pausing (which minimized pauses). This must have been overwritten with the Hub 2.0 updates. Will find and adjust it again to see if it makes a difference.

kawembe · 01/12/2026, 23:55

Regarding Tasca: looked into the file and got all I needed, thanks! Now getting the Error

"Line 135 LocationOfBotHub
SetupTeamUsingGUISettings()
^ ERROR

Error: Unknown function name."

While sort of understanding what this means, I have no idea whether this is a bot issue or a me-issue.

LandonCarter7 · 01/13/2026, 01:04

My disconnects are happening right after travel to EotN and ID all inventory, does not get the point of sale. Unfortunately, it crashes while I am away so I can't entirely catch what it is doing during the crash

Quote:

Originally Posted by kawembe

I'm not. I thought since the bot sets it up automatically I need the ones it wants to use for it to run properly... Which builds do you use and what classes etc? My discord so we maybe don't spam here... wilson1861
Only if you want to of course, thanks for your reply in any case!

and I use my own Esurge mesmer build

eskel2 · 01/13/2026, 12:29

I am getting the same disconnects, bot travels to EoTN, ID-s the inventory, starts salvaging and the disconnects happen, error 007.

This is what I get from the logs:
11:32:38 - Run Successful after: 22min 43s
11:32:39 - Travelling to Eye of The North Default (Outpost)
11:32:45 - Identifying items
11:32:49 - Salvaging items
11:32:52 - Moving to merchant to buy items
11:32:59 - Not enough space in inventory and storage to buy anything
11:32:59 - No space in inventory to move the items out of the equipment bag
11:32:59 - Moving to merchant to sell items
11:33:06 - Selling items
11:33:06 - Balancing character's gold
11:33:06 - Not enough gold in chest, get some.
11:33:06 - Inventory full, pausing.

I have enough gold and actually the bot purchased like 10 salvage kits.

Boytae6969 · 01/13/2026, 15:50

do you happen to have the heroes ascent bot as well in the mix?

Dogi06 · 01/13/2026, 17:11

Hi everyone.
i have a question about Mantids farm.
I'm having trouble with the hero; I'm using Hayda with me. I selected her in the code as instructed.
But nothing works; the bot kicks Hayda out and tells me "Could not set up party correctly. Team size different than 2." I've tried to understand and solve the problem myself, without success... So I'm sorry to ask for your help once again...
PS: I've downloaded the latest version of the hub and Mantrids.

Kronos8 · 01/13/2026, 20:13

@

For Mantids, if you want to use Hayda, you need to update the code. For now, the team configuration from the interface does not override the individual configuration from the bots, but I think I will change this behaviour.
So, for code, it means go into the Mantids.au3 file, and replace:

Code:

Global Const $MANTIDS_HERO_PARTY_ID = $ID_GENERAL_MORGAHN
;Global Const $MANTIDS_HERO_PARTY_ID = $ID_KEIRAN_THACKERAY
;Global Const $MANTIDS_HERO_PARTY_ID = $ID_HAYDA

By:

Code:

;Global Const $MANTIDS_HERO_PARTY_ID = $ID_GENERAL_MORGAHN
;Global Const $MANTIDS_HERO_PARTY_ID = $ID_KEIRAN_THACKERAY
Global Const $MANTIDS_HERO_PARTY_ID = $ID_HAYDA

@

Please, if you have questions, first read documentation (readme) of the hub. It's clearly stated what bots are availables, and that if a bot is not shown, then I don't have it. No, I do not have HA, and will never do: it's PvP and I don't want to make PvP bots.

@

I will test the salvage more in detail. I've been running bots today for hours on end (though, without salvaging) and had 0 disconnections. So maybe it comes from salvage, I will try that.

@

That issue is fixed in latest version.

@

- Are you salvaging by any chance ? Maybe that's one big source of crashes. I will have to try this more in details.
- Yes, lots of things changed with 2.0 so it's likely why skill usage changed.
- Don't use toolbox at the same time as bots if possible. It's triggering crashes very easily (access to the same memory)
- Not sure about the bot pausing with lots of inventory space, I still have commendations bot running for 3 hours and it didn't stop once.

Dogi06 · 01/13/2026, 21:14

Thanks for your quick reply. I just made the change, but the problem persists... I'm completely lost.
Maybe it's my fault

Boytae6969 · 01/14/2026, 00:23

Quote:
Originally Posted by Kronos8
@
For Mantids, if you want to use Hayda, you need to update the code. For now, the team configuration from the interface does not override the individual configuration from the bots, but I think I will change this behaviour.
So, for code, it means go into the Mantids.au3 file, and replace:
Code:
Global Const $MANTIDS_HERO_PARTY_ID = $ID_GENERAL_MORGAHN
;Global Const $MANTIDS_HERO_PARTY_ID = $ID_KEIRAN_THACKERAY
;Global Const $MANTIDS_HERO_PARTY_ID = $ID_HAYDA
By:
Code:
;Global Const $MANTIDS_HERO_PARTY_ID = $ID_GENERAL_MORGAHN
;Global Const $MANTIDS_HERO_PARTY_ID = $ID_KEIRAN_THACKERAY
Global Const $MANTIDS_HERO_PARTY_ID = $ID_HAYDA
@
Please, if you have questions, first read documentation (readme) of the hub. It's clearly stated what bots are availables, and that if a bot is not shown, then I don't have it. No, I do not have HA, and will never do: it's PvP and I don't want to make PvP bots.

@
I will test the salvage more in detail. I've been running bots today for hours on end (though, without salvaging) and had 0 disconnections. So maybe it comes from salvage, I will try that.

@
That issue is fixed in latest version.

@
- Are you salvaging by any chance ? Maybe that's one big source of crashes. I will have to try this more in details.
- Yes, lots of things changed with 2.0 so it's likely why skill usage changed.
- Don't use toolbox at the same time as bots if possible. It's triggering crashes very easily (access to the same memory)
- Not sure about the bot pausing with lots of inventory space, I still have commendations bot running for 3 hours and it didn't stop once.

thanks! very clear now, i read them and I was just hopeful you will also support pvp. thank you for all your hard work!

LandonCarter7 · 01/14/2026, 04:56

TravelToOutpost(ID_GADDS_ENCAMPMENT, $district_name)
TravelToOutpos(^ ERROR

this is popping up for me now trying to start Froggy

Thorulf · 01/14/2026, 09:06

Quote:

Originally Posted by Kronos8

@
- Are you salvaging by any chance ? Maybe that's one big source of crashes. I will have to try this more in details.
- Yes, lots of things changed with 2.0 so it's likely why skill usage changed.
- Don't use toolbox at the same time as bots if possible. It's triggering crashes very easily (access to the same memory)
- Not sure about the bot pausing with lots of inventory space, I still have commendations bot running for 3 hours and it didn't stop once.

@

thanks for the feedback.

Answers:

Salvaging: no, only config to pickup - keep a very small and specific set of mods - and store alt. sell the rest.
BotsHub 2.0 changes: ok good to know. Any pointers to where the combat overzealousness is so I can relax it?
Toolbox: really? this is new info to me. It normally has worked fine, and it is such HUGE QoL! Not really a healthy option to live without it. I for one am def. NOT wasting valuable and limited lifetime salvaging 100+ items one-by-one. However, given what you are saying now, I will ignore tb for the runs. Thanks for the heads up.
Unmotivated pauses: I agree, this is still unknown to some degree. I did find where the threshold specification for what is considered a "full inventory" is: it's the big switch-case in BotsHub.au3 for all the different runs which sets $inventory_space_needed depending on the specfic run (default = 5).
This was hardcoded to a whopping 15 free inventory slots for the Kurzick VQ run. This explains some of the pauses. However not all: I have also seen "Pausing" without any previous "inventory full" message, and after restoring the client from the DC the nr of free spaces are > $inventory_space_needed
The key problem seems to be not actually selling items. See notes below.

Noted the following:

Inventory management is actually not selling anything. Expected: sell all per the config.
NOT selling salvage items which have only non-interesting mods on it, per the config. Expected: sell these to free up space.
NOT storing traded rare mats, amber chunks etc. Keeping and Starting the run instead. Expected: store in material storage to free up space (mat.storage is almost empty).
NOT storing found rare mats, fur squares etc. Keeping in inventory instead. Expected: store in material storage to free up space (mat.storage is almost empty).
After restoring the client I notice the inventory has a mix of salvage items with mods the config says to keep and to sell respectively.
DC with code 007 always seems to happen right at the start of the run. The exact reason is still unknown. Have not been able to recreate this manually. Given that the last log is travel to HzH, my intuition is that it crashes on entering the instance map (Ferndale, the next logical step). Any further insight is highly appreciated.
DC happens with or without Toolbox. Without TB it manages 0-2 more runs b4 DC. If this is random or a pattern I honestly don't know yet. Simply need more data.

DC (code 007) after 4 kurz runs (without toolbox). Log:

Code:

00:27:33 - Travelling to Eye of The North Default (Outpost)
00:27:41 - Identifying items
00:27:52 - Salvaging items
00:27:58 - Moving to merchant to buy items
00:28:08 - No space in inventory to move the items out of the equipment bag
00:28:08 - Moving to merchant to sell items
00:28:15 - Selling items
00:28:15 - Sold 0 items to merchant
00:28:15 - Inventory considered full given 4 slots needed! Pausing.
00:28:15 - Starting run 5
00:28:15 - Travelling to House Zu Heltzer (Outpost)

DC (no code this time) after 1 kurz run (without toolbox). Log:

Code:

18:44:26 - Dredge Patrol 54
18:45:20 - Dredge Patrol 55
18:46:15 - Dredge Patrol 56
18:47:10 - Map has been fully vanquished.
18:47:10 - Travelling to House Zu Heltzer (Outpost)

Update 2026-01-17:
DC after SoO 1st run (always without tb now). Insights and log:
* The fail to sell items is consistent, regardless of run. Config is set to sell blue+purple+gold items given that they do not have a mod which is set to keep. This last part I trust is the behaviour. Pls confirm.
* The DC seems to happen ON the travel to the relevant outpost. The log message happens b4 the actual action, which is good for debug purposes.
* Some of the log messages are false. Concretely: There is 10+ slots free in inventory to move items out of the equipment bag.
* Even though it says "Pausing", it goes right ahead with the next run.

Code:

14:06:57 - Not enough space in inventory and storage to buy anything
14:06:57 - No space in inventory to move the items out of the equipment bag
14:06:57 - Moving to merchant to sell items
14:07:04 - Selling items
14:07:04 - Sold 0 items to merchant
14:07:04 - Inventory considered full given 15 slots needed! Pausing.
14:07:04 - Starting run 2
14:07:04 - Setting up farm
14:07:04 - Travelling to Vloxs Falls (Outpost)

Insight and answers per above would be super and greatly appreciated.

Cheers!

Staubsauger5 · 01/15/2026, 11:13

JadeQuarry
Can someone insert the JQ Bomber bot?

Thorulf · 01/18/2026, 11:28

SoA seems to have regular issues with becoming stuck. After the pause it looks fine. Party is standing in an open area.
Unwanted: when unpausing it maps out and restarts everything [wasted a couple of consets this way].
Expected: continue from where you at. Ideally sync location and just keep going.

Code:

01:39:39 - Going through portal
01:39:39 - Bot appears to be stuck at: SoO Floor 2 - Opening door. Restarting run.
01:39:39 - Run failed after: 83min 7s
01:39:39 - Paused.