QuestBot Guide/Support/Discussion

[roneo1]

Bot gets stuck on essence mobs in fetid pool/daresso's dream if monoliths plugin is disabled, it relogs after stuck timeout etc and keeps getting stuck again in endless loop. I suspect its cuz of track mob task active there, the bots are already leveled and ive deleted logs but I remembered this issue happening so I thought I'd give a heads up. I dont keep monolith enabled in cruel/merc as those mobs can be quite OP and I dont want to risk the bot dying and losing xp.

 

[widds]

Yeah for some reason sometimes it thinks the frozen essence mob is "alive" and just stays there. Haven't had it happen enough to pin down the cause, thinking maybe if it accidentally clicks it once it "wakes" up the mob partially and so EB thinks it's an active mob, but won't click it to finish unfreezing because monolith is disabled.

 

[yfbd]

The frozen mobs are considered .IsInvincible, therefore trackmoremobs do have the .IsInvincible property check, unless you are using an outdated one.

 

[Darox]

My bot for some reason doesn't get scrolls to TP out after quest. I do not have auto log on enabled but shouldn't it hold some scrolls for after quests?

 

[tak0312]

For some reason my bot doesn't have Questbot, Please help

 

[toNyx]

For some reason my bot doesn't have Questbot, Please help

thanks for joining a log, we'll come to you once we've reviewed it.

 

[ErzaScarlet]

thanks for joining a log, we'll come to you once we've reviewed it.

They never learn

 

[a4tech111]

Please correct the quest bot as it tries to reward non-existent. so almost all quests


[OpenRewardPanel] "Medicine Chest Reward" has need successfully opened.
[ReactionWait] Now sleeping 290 ms.
[TakeReward] Fail to find "Eternal Life Flask" in reward inventory.
[CRITICAL ERROR] Now requesting bot to stop.
[Stop] Now requesting the BotThread to stop.
[Tick] Exception #4 during execution:Buddy.Coroutines.CoroutineUnhandledException: Exception was thrown by coroutine ---> System.Exception: CRITICAL_ERROR
at EXtensions.ErrorManager.ReportCriticalError() in E:\Games\dsg57ujyki870o98\3rdParty\_CONFIGS_\marader_gs\EXtensions\Content-18294611\ErrorManager.cs:line 44
at EXtensions.TownNpcs.TownNpc.<TakeReward>d__10.MoveNext() in E:\Games\dsg57ujyki870o98\3rdParty\_CONFIGS_\marader_gs\EXtensions\Content-18294611\TownNpcs.cs:line 216
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
at QuestBot.QuestHandlers.A1_Q2_MercyMission.<TakeReward>d__8.MoveNext() in E:\Games\dsg57ujyki870o98\3rdParty\_CONFIGS_\marader_gs\QuestBot\Content-18302006\QuestHandlers\A1_Q2_MercyMission.cs:line 66
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
at QuestBot.QuestTask.<Logic>d__2.MoveNext() in E:\Games\dsg57ujyki870o98\3rdParty\_CONFIGS_\marader_gs\QuestBot\Content-18302006\QuestTask.cs:line 18
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Loki.Bot.TaskManager.F_^c "Nw5\\%-Ai)`Rfo-);A9#.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
at QuestBot.QuestBot.<MainCoroutine>d__13.MoveNext() in E:\Games\dsg57ujyki870o98\3rdParty\_CONFIGS_\marader_gs\QuestBot\Content-18302006\QuestBot.cs:line 211
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Buddy.Coroutines.Coroutine.6Z\,273Iq'lm2~hsweBtclpL\.(.fJ$J~=2bbS"0EkRn(EOPBP"I\*.MoveNext()
--- End of inner exception stack trace ---
at Buddy.Coroutines.Coroutine.‫​‏‏‪‫​*‏​*‬‎‎‫‎​‪*‏‪*‪*‏*(Boolean )
at Buddy.Coroutines.Coroutine.*​​*‫*​‫‎***​*​​​*‎‪**‬​*(Boolean )
at Buddy.Coroutines.Coroutine.Resume()
at QuestBot.QuestBot.Tick() in E:\Games\dsg57ujyki870o98\3rdParty\_CONFIGS_\marader_gs\QuestBot\Content-18302006\QuestBot.cs:line 142
at Loki.Bot.BotManager.*‫‫*‪*‪‫‪**‪‬**‎‏‪**​*‬*‪‬‪‎**(IBot )

 

[widds]

Rewards seem to have been messed up. I'd just manually select each one (even for the ones you don't care about) just so it picks an actual reward. Like the pulldown offered a choice of Fingerless Silk Gloves from the A1 Normal Hillcock quest as a Ranger... obviously not a choice, but if the bot thinks it's a choice and randomly selects it (and it's not there) it could error out.

 

[ExVault]

Bot reads rewards from game files. It seems like some patch changed certain internal structures. Pushedx will release a fix soon.

 

[Darox]

Bot reads rewards from game files. It seems like some patch changed certain internal structures. Pushedx will release a fix soon.

When 2.4 was released, there was an issue with POE skipping the quest reward box auto pop up, was automatically closing. Had to talk again to NPC. They patched it a few patches later (if I remember correctly) this might have caused the change. The issue I facaed with quest bot last night, was it trying to select a reward, that was already chosen, erroring out after 10 failed attempts. This wasn't for all quests either, it happedn to me on the blocked passage & the act 3 one before the general.

 

[ExVault]

That's gonna be fixed in next version.

 

[widds]

In the next version can you add in keeping a stack of scrolls in the inventory? Thanks

 

[ExVault]

In the next version can you add in keeping a stack of scrolls in the inventory? Thanks

What scrolls? Bot stashes only excess wisdoms and portals, i.e it always keeps 1 big stack of them in player's inventory.

 

[widds]

What scrolls? Bot stashes only excess wisdoms and portals, i.e it always keeps 1 big stack of them in player's inventory.

It really doesn't, at least not at the start. I think it's a weird interaction with AIF. QB wouldn't take them out of the currency tab, and it wasn't until I dropped below the AIF threshold for scrolls in stash that it started keeping them in the inventory.

But starting QB up with a level 1 in town and thousands of portal scrolls in the currency tab it won't pull them out and fill the inventory like OGB does.

 

[ExVault]

QB does not have any portals stash taking logic because its just redundant.

First of all, bot can have problems with portals only in like first 4 areas on Normal, while getting out of Tidal Island and Fetid Pool. After that bot usually finds some portals and does not have any problems with them ever. While out of portals, bot will use logout instead, which is completely fine, all speedrunners have been using it for ages.
Secondly, if you wanna "help" your bot and give it some starting portal amount - just put them in player's inventory, 10 scrolls are more than enough.

If you have any external logic that forces bot to stash ALL portals from player's inventory or you have disabled portals pick up in item filter - none of the above will work. And thats not a QB fault.

 

[widds]

I wasn't trying to get you heated lol. I just notice OldGrindBot has zero issues with even starting at level 1 and keeping scrolls in the inventory (as there's a selection to force it in settings). QB doesn't seem to have the same sort of logic starting out. I just assumed the logical approach would be to copy over whatever code is working in OGB and apply it to QB, it's not like having a stack of portal/wisdom scrolls is going to cause any sort of issues with questing. I realize 99% of the time it's not an issue due to /logout at WP when the bot wants to grab rewards it can pick right up at the WP... but there are situations when the bot would need to visit town and is in the middle of an exploration/quest task and /logout would cause it to start back at the WP regardless of how far it has progressed through the zone.

 

[toNyx]

I wasn't trying to get you heated lol. I just notice OldGrindBot has zero issues with even starting at level 1 and keeping scrolls in the inventory (as there's a selection to force it in settings). QB doesn't seem to have the same sort of logic starting out. I just assumed the logical approach would be to copy over whatever code is working in OGB and apply it to QB, it's not like having a stack of portal/wisdom scrolls is going to cause any sort of issues with questing. I realize 99% of the time it's not an issue due to /logout at WP when the bot wants to grab rewards it can pick right up at the WP... but there are situations when the bot would need to visit town and is in the middle of an exploration/quest task and /logout would cause it to start back at the WP regardless of how far it has progressed through the zone.

^ This, + it could avoid multiple logouts and could speed up execution. In addition to this, equipper loves identifying stuff on the fly to evaluate them. Hurray for wisdom/portals in inventory !

 

[ExVault]

QB has logic for wisdom taking from stash. It was there since the first beta.
For portals, as I said, give the bot some small starting amount and be good. I don't know how portal taking from stash will help you, considering 1 stack in inventory is more than enough for the entire Act 1 Normal - Act 4 Merciless walkthough.

 

[54sgdg4d6s]

I never had any problems with portals. Early on bot does a couple of logouts to come to town, but then he starts to find portals on himself and self-sustains them till end.