What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

QuestBot 2.0 Guide/Support/Discussion

E

ExVault

Active Member
Joined
Oct 23, 2013
Messages
748
Reaction score
57
QuestBot is a bot-base for progressing through the game, up to the maps.
It also can used to grind regular non-map areas.

QuestBot supports complete game playthrough from Act 1 to Act 10.

Settings description
Current quest
Shows you what QuestBot is currently doing.

Grinding
Rule

Quest - bot will grind selected areas after specified quest.

Level cap - bot will grind selected areas until specified level is reached. When level is reached bot will return to questing.

Areas - list of areas to grind. Multiple area grinding is supported. To add more areas click on corresponding button, to remove an area - right click on it. Please keep in mind that bot will not do quests to reach specified areas, you must select areas that are accessible in that point of the game. For instance: if you set grinding Submerged Passage after "Enemy at the Gate" quest, bot will not be able to do that. That area becomes accessible only after "Breaking some Eggs" quest.

Pool - bot selects an area to grind randomly, but list of possible areas is predetermined. This value represents a total number of specified area in the list. Bot endlessly cycles through the list, each time it begins anew bot shuffles the list (more explanation)
Examples
Example 1:
Quest: Enemy at the Gate
Level cap: 5
Area: Coast, Pool: 1.
Area: Tidal Island, Pool: 1.

Result: After "Enemy at the Gate" bot will grind Coast and Tidal Island till level 5. Areas in pool: 1 Coast, 1 Tidal Island. Total area count in pool: 2. Bot will spend 50% of it's time in Coast and another 50% in Tidal Island.


Example 2:
Quest: Sharp and Cruel
Level cap: 18
Area: Western Forest, Pool: 5.
Area: Wetlands, Pool: 3.
Area: Riverways, Pool: 2.

Result: After "Sharp and Cruel" bot will grind Western Forest, Wetlands and Riverways till level 18. Areas in pool: 5 Western Forest, 3 Wetlands, 2 Riverways. Total area count in pool: 10. Bot will spend 50% of it's time in Western Forest, 30% in Wetlands, 20% in Riverways.

Example 3:
Quest: Fiery Dust
Level cap: 30
Area: Docks, Pool: 1.

Result: After "Fiery Dust" bot will grind Docks till level 30. Areas in pool: 1 Docks. Total area count in pool: 1. Bot will spend 100% of it's time in Docks.

Settings

Exploration percent - bot will finish current area beforehand if exploration percent is equal or greater than specified value.

Max deaths - bot will finish current area beforehand if death count in this area is equal or greater than specified value.

Monster tracking - bot will memorize all seen monsters and return to them if they move outside of combat range.

Manual bosses
Contains a list of bosses that pose a threat to the bot. When bot comes to a selected boss, it will stop and do nothing, waiting for you to handle the boss fight manually.

Please note that currently bot does not have any dodging logic and will face-tank everything. It is recommended to manually kill bosses unless you are leveling with a good twink gear.

GGG do count your deaths and use that value in their ban estimation algorithms, especially on new accounts.

Optional quests
Here you can select what optional quests bot will do.

Quest Rewards
Here you can select what quest rewards bot will take.

Misc
Enter corrupted side areas - bot will enter corrupted areas during questing or grinding.

Talk to all quest givers in town - usually bot interacts with NPCs in town only when its necessary. With this option enabled bot will always interact with all NPCs that have exclamation mark. This feature was made only to make bot act more like average new player and is completely optional.

Known issues
- Problems and issues caused by high latency and/or desync. All of those can screw the bot up unpredictably.

- Bot can fail to pick up an item if its on the other side of some big object (Strongbox, Tribal Chest). This is more related to the game itself which does not automatically pathfind around such objects.

- Bot can stuck while grinding the Ruined Square (Act 5) near "red wall" that blocks an entrance to Cathedral Rooftops. This is true only for grinding and has nothing to do with questing.

- User intervention can mess up navigation through multilevel areas (Vaal Pyramid, Sceptre of God). Do not stop the bot on one level and then start on another.

- User intervention can mess up taking a reward for "Deal with the Bandits" quest. Do not stop the bot while it takes the Apex.

- Sometimes bot can have problems moving through:
  • Stairs in Docks and similar tilesets.
  • Stairs in Aqueduct and similar tilesets.
  • Rooftops in City of Sarn and similar tilesets.
  • Ruined church in Fellshrine Ruins

Warning! Using community made routines with QuestBot
Kitava and Arakaali bosses are always located on unwalkable terrain (basically a hole in the floor). It means that bot cannot pathfind to them properly. Adjustments have been made to OldRoutine and now it can correctly handle Kitava and Arakaali.

During Brine King water phase you must stay very close to the boss. QuestBot will modify your combat range for a duration of the fight and then restore it once you are in Act 7. Routine must support "GetCombatRange" and "SetCombatRange" messages for that reason.

Using some old community made routine without those adjustments will result in bot's inability to kill mentioned bosses.

Other adjustments that were made to OldRoutine:
- Routine prioritizes Tukohama totems that give him damage immunity.
- Routine ignores Doedre totems in Act 9 last boss area because they spawn endlessly.

If you want to report a bug/issue, please attach a full log.
 
Last edited:
Hey Exvault, thanks for the update and all the beta acts you managed to include. May I ask for a Rough ETA of act 9 inclusion? No need to be too exact but just an estimation.

Thanks, and keep up the good work :)
 
how does it alternate between pool 1 and 2 in this kind of setup?

Randomly?

LkdrcUj.png
 
roneo1 said:
Hey Exvault, thanks for the update and all the beta acts you managed to include. May I ask for a Rough ETA of act 9 inclusion? No need to be too exact but just an estimation.
Thanks, and keep up the good work :)
Click to expand...
Act 9 and 10 will be added in patch 3.0.1 update.

IeU said:
how does it alternate between pool 1 and 2 in this kind of setup?
Randomly?
Click to expand...
"Pool" number is not "id" or something. There is only 1 pool per rule and that number is the amount of that area in the pool.

Taking your settings as an example:
After quest "Essence of the Hag" bot will create a pool of 7 areas: 1 Chamber of Sins, 1 Crypt, 1 Fellshrine, 2 Ramparts, 2 Grain Gate.
Then bot will shuffle the pool and go to the first area. Then second and so on. When pool ends, bot will re-shuffle it and do again.

The whole point of this system is to eliminate an element of randomness. Imagine we just go easy-mode and you simply assign a % chance to go to a certain area. Lets say 70% chance to Crypt and 30% chance to Grain Gate. Each time bot decides where to go it does a random roll according to percentages you gave. That way you can potentially never visit Grain Gate, just because of bad luck, bot rolled Crypt all the time.

With current system thats not possible. Bot will still visit areas "randomly" because pool is shuffled. But you can be sure that each area you specified will be eventually visited.
 
Last edited:
After you finish questing the 10th Act and try to setup grinding for a few levels you get a loop (tried with setting the quest to "An End to Hunger" and "Death and Rebirth"

Now reloading the Quest cache.
The Quest cache has been reloaded.
[QuestManager] An End to Hunger - Take reward
[TakeReward] Now going to take "Any" from Lani.
[Interact] Now going to interact with "Lani".
[InteractWith] Now attempting to highlight 258.
[InteractWith] Now attempting to interact with 258.
[LatencyWait] Now sleeping 370 ms.
[Interact] "Lani" has been successfully interacted.
[Converse] Fail to find any dialog with "Kitava Reward" in it.
[ErrorManager] Error count: 1/10.
[CloseBlockingWindows] InstanceInfo.NpcDialogDepth > 0. Closing it.
[LatencyWait] Now sleeping 369 ms.
[ReactionWait] Now sleeping 254 ms.
[IdTask] No items to identify.
[SellTask] No items to sell.
[StashTask] No items to stash.
[VendorTask] No items to vendor.
[QuestManager] An End to Hunger - Take reward
[TakeReward] Now going to take "Any" from Lani.
[Interact] Now going to interact with "Lani".
[InteractWith] Now attempting to highlight 258.
[InteractWith] Now attempting to interact with 258.
[LatencyWait] Now sleeping 364 ms.
[Interact] "Lani" has been successfully interacted.
[Converse] Fail to find any dialog with "Kitava Reward" in it.
[ErrorManager] Error count: 2/10.
 
Harbinger of Lunaris goes out of range quite often if you die during the fight you end up standing on the portal point i.e you don't engage the Harbinger again.
 
WiN
Thanks for the reports. Kitava reward issue will be fixed in next version.
For Dusk I need a full log.
 
Last edited:
Blood Aqueduct Act 9 a common shortcut is to portal to town at the start of it. Can this be added?
 
I cant seem to get my bot to grind any area no matter what I do, I just wanted to grind chambers of innocence before kitava. set the quest to that room and put a 15 lvl cap and 1 pool. what have I missed?
 
Grinding has not worked for me at all. I've done every combination I can think of to try and get it to work. Support section on discord over the last few days, it has been brought up numerous times. No idea what to do to get Grind to work. Can we add a toggle to just tell it to grind instead of this weird Quest initiation thing? I've tried setting up 3 separate groups just to test out if it works. One with a quest I completed. One with a current quest, and one with a future quest. None of them worked. I tried single. I cannot get it to work at all.
 
S
dirin said:
Grinding has not worked for me at all. I've done every combination I can think of to try and get it to work. Support section on discord over the last few days, it has been brought up numerous times. No idea what to do to get Grind to work. Can we add a toggle to just tell it to grind instead of this weird Quest initiation thing? I've tried setting up 3 separate groups just to test out if it works. One with a quest I completed. One with a current quest, and one with a future quest. None of them worked. I tried single. I cannot get it to work at all.
Click to expand...
Same here bruv, I'm on clicking the conclusion that its not operational yet. I feel like there needs to be a toggle button to enable that grind XD

I tried it with a hero that had done all quests, and it sat at the end trying to receive kitava reward..
 
Funny, Grinding is working great for me.

Just finished a 8h+ session now of Grinding, without any hick ups. Setup was easy and did it with 4 areas . . .

You guys def. doing something wrong, post a screen-shot of your Grinding Setup so we may help you guys out . . .

And please, dont change the way it works, this "quest thingy" is great, if you get the idea behind it.

I think you guys are forgetting to set the level above yours, i.e. really high, if you just want to grind endlessly . . .

Try something like this, with a quest you guys already done.

s6KnRrM.png
 
o trueeeeeee! so that lvl cap is based on your actual lvl eg . 15 above the lvl cap o the map which is like lvl 40 XD derp! thanks for pointing that out !

NOTE: use objectExplore and save then try it.
 
Last edited:
After the most recent update to EB, everything is working now. ;)
 
Boltwall said:
o trueeeeeee! so that lvl cap is based on your actual lvl eg . 15 above the lvl cap o the map which is like lvl 40 XD derp! thanks for pointing that out !

NOTE: use objectExplore and save then try it.
Click to expand...

i usually have multiple of those settings for grind. Once i finish one level session, instead of deleting the "filter", i just set the level cap to 1, so from now on, EB will ignore it, since i am over the cap.
 
IeU said:
i usually have multiple of those settings for grind. Once i finish one level session, instead of deleting the "filter", i just set the level cap to 1, so from now on, EB will ignore it, since i am over the cap.
Click to expand...
O true ! mint idea, I've been deleting :D , Cheers for the tip
 
If you die during "the descent" the bot cant click the next descent portal:

MoveTowards] Fail to move towards Next Descent level at {1242, 713}
[MoveTowardsWalkable] Unexpected error. Fail to move towards Next Descent level at {1242, 713}
[ErrorManager] Error count: 10/10.
[ErrorManager] Error threshold has been reached. Now requesting bot to stop.
 
You must log in or register to reply here.
Back
Top