[Beta] QuestBot

With the Vaal Overseer the bot walks to the left of the stairs and gets stuck in the corner between the wall and the stairs, so it is kind of underneath the portal and too far away to click the transition (in the screenshot it worked correctly, it is just for position reference).

Clarissa doesn't get interacted with when the bot gets dragged out of range by the mobs.

There is also the well known Docks bug, which only occurs when the bot runs around to the back of the Cart thing to click on it instead of running straight up to it - then the Thaumatic thing drop on the other side of the cart and the bot gets stuck trying to go straight over the cart to get to it. I can post logs, but they will just show bot was at x,y and not any actual errors.

 

If you die during the Daresso fight or chicken it breaks the bot:

2016-08-16 21:35:00,897 [30] ERROR Logger - [KillDaresso] ArenaExplorer has finished, but we do not have an Eye of Desire.
2016-08-16 21:35:00,898 [30] ERROR Logger - [CRITICAL ERROR] Now requesting bot to stop.
2016-08-16 21:35:00,898 [30] INFO BotManager - [Stop] Now requesting the BotThread to stop.
2016-08-16 21:35:00,899 [30] ERROR BotManager - [Tick] Exception #2 during execution:
Buddy.Coroutines.CoroutineUnhandledException: Exception was thrown by coroutine ---> System.Exception: CRITICAL_ERROR
at EXtensions.ErrorManager.ReportCriticalError() in xxx\3rdParty\_CONFIGS_\Default\EXtensions\Content-608551875\ErrorManager.cs:line 44
at QuestBot.QuestHandlers.A4_Q4_KingOfDesire.<KillDaresso>d__5.MoveNext() in xxx\3rdParty\_CONFIGS_\Default\QuestBot\Content-608554234\QuestHandlers\A4_Q4_KingOfDesire.cs:line 59
--- 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)

 

WiN
- You should not stand exactly near the exit to trigger the activation. That distance (on your screenshot) is enough. Just wait more, as I said before it can take 3-4 minutes.
- Clarissa was fixed in recent patch (13 August).
- I'll look into that Daresso problem, thanks for the report.

 

Thanks for the feedback - the Sarn Exit - I have left the bot for 30+ mins and it never completes. Looking at it more carefully, you can see from this latest attempt (where the bot is stuck for real in the image) that the bot doesn't get close enough to the exit to trigger the door to become interactive.



When I manually move the bot to the bottom of the stairs it triggers the door to become interactive and the bot clicks no problem (even, as you say, if the bot is standing below and to the left of the portal/stairs it still clicks correctly, so you are right, the bot click range isn't the problem, its physical proximity to the door is causing the stuck):

 

Perhaps now that the awesome new Questbot is up and running very well, the passive tree profiling API calls could be reintroduced? This is pretty much the only thing stopping the bot from being able to auto-level.

 

I doubt GGG made that you literally have to stick your nose into the door to trigger it.
When I was coding Malachai fight I noticed that fight stage change triggers faster when you are constantly moving around instead of standing still far away and waiting.
Maybe they use same (weird ) scripting for this door too. I will try to code some simple movement route in boss room after Vaal is dead.

 

Tested again - if you fight vaal anywhere south on the platform, once he is dead the pathing takes you to the position above and gets stuck. The bots feet literally have to touch the bottom step for the doorway to become active.

 

Keepo

 

I can confirm that. Dunno where char has to stay to enter door, but when he's at that spot next to the step, bot gets stuck until u move him by hand.

 

Not sure if the Clarissa bug is supposed to still exist in in Beta 1384 or if it has been fixed - but either way it still exists. Logs attached: Dropbox - Exilebuddy 104456 2016-08-22 21.00.zip the fight with the guard starts at 2016-08-23 01:11:45,485 (almost at the end ... as shown by the dodge)

I sent the bot back to the start of Sarn to run it again and it ran straight past her again - i think because it had moved onto the next part of the quest. So i manually went back to right beside her and hit go on the bot - still ran away - so then i manually ran back to her to try one last time - changed window to make sure there was a log for you - changed back - and RIP Doggy dinner I hope my HC death wasnt in vain.

 

Did you post the right log? According to it, bot successfully interacted with Clarissa

Also, right after that bot entered town and Clarissa was there. I do not see any problem in log you posted.

 

That was in normal - the cruel log is at the end with no interaction. The log has a run from level 0-45.

016-08-23 01:12:20,136 [93] DEBUG Logger - [MoveAtOnce] Moving to Clarissa at {150, 323} (distance: 286)
2016-08-23 01:12:20,151 [93] INFO Logger - [Alcor75PlayerMover::MoveTowards] Now building TGT info.
2016-08-23 01:12:20,152 [93] INFO Logger - [BeginUseAt] 2 False {302, 91}
2016-08-23 01:12:21,166 [93] DEBUG Logger - [MoveAtOnce] Moving to Clarissa at {150, 323} (distance: 260)
2016-08-23 01:12:22,218 [93] DEBUG Logger - [MoveAtOnce] Moving to Clarissa at {150, 323} (distance: 277)
2016-08-23 01:12:23,266 [93] DEBUG Logger - [MoveAtOnce] Moving to Clarissa at {150, 323} (distance: 279)
2016-08-23 01:12:24,268 [93] DEBUG Logger - [MoveAtOnce] Moving to Clarissa at {150, 323} (distance: 289)
2016-08-23 01:12:25,301 [93] DEBUG Logger - [MoveAtOnce] Moving to Clarissa at {150, 323} (distance: 303)
2016-08-23 01:12:26,317 [93] DEBUG Logger - [MoveAtOnce] Moving to Clarissa at {150, 323} (distance: 318)
2016-08-23 01:12:27,333 [93] DEBUG Logger - [MoveAtOnce] Moving to Clarissa at {150, 323} (distance: 328)
2016-08-23 01:12:28,333 [93] DEBUG Logger - [MoveAtOnce] Moving to Clarissa at {150, 323} (distance: 313)
2016-08-23 01:12:29,333 [93] DEBUG Logger - [MoveAtOnce] Moving to Clarissa at {150, 323} (distance: 297)
2016-08-23 01:12:29,852 [93] INFO Logger - [Alcor75PlayerMover::MoveTowards] Act 3 Town force adjustment being made!
2016-08-23 01:12:30,333 [93] DEBUG Logger - [MoveAtOnce] Moving to Clarissa at {150, 323} (distance: 253)
2016-08-23 01:12:31,385 [93] DEBUG Logger - [MoveAtOnce] Moving to Clarissa at {150, 323} (distance: 203)
2016-08-23 01:12:32,453 [93] DEBUG Logger - [MoveAtOnce] Moving to Clarissa at {150, 323} (distance: 154)
2016-08-23 01:12:33,488 [93] DEBUG Logger - [MoveAtOnce] Moving to Clarissa at {150, 323} (distance: 113)
2016-08-23 01:12:34,520 [93] DEBUG Logger - [MoveAtOnce] Moving to Clarissa at {150, 323} (distance: 81)
2016-08-23 01:12:35,537 [93] DEBUG Logger - [MoveAtOnce] Moving to Clarissa at {150, 323} (distance: 42)
2016-08-23 01:12:36,604 [93] DEBUG Logger - [MoveAtOnce] Moving to Clarissa at {150, 323} (distance: 64)
2016-08-23 01:12:37,621 [93] DEBUG Logger - [MoveAtOnce] Moving to Clarissa at {150, 323} (distance: 47)
2016-08-23 01:12:38,424 [93] INFO Logger - [UseAt] 2 False {143, 303}
2016-08-23 01:12:38,542 [93] INFO Logger - [UseAt] 2 False {141, 314}
2016-08-23 01:12:38,553 [93] INFO Logger - [InjectKeyEvent] 100 ms sleep for 4.
2016-08-23 01:12:38,723 [93] DEBUG Logger - [MoveAtOnce] Moving to Clarissa at {150, 323} (distance: 21)
2016-08-23 01:12:38,741 [93] INFO Logger - [UseAt] 2 False {148, 316}
2016-08-23 01:12:38,754 [93] INFO Logger - [InjectKeyEvent] 116 ms sleep for 4.
2016-08-23 01:12:38,939 [93] DEBUG Logger - [FinishCurrentAction] Waited 0 ms for the action to finish Move.
2016-08-23 01:12:39,054 [93] DEBUG Logger - [FinishCurrentAction] Waited 115 ms for the action to finish Move.
2016-08-23 01:12:39,155 [93] DEBUG Logger - [FinishCurrentAction] Waited 216 ms for the action to finish Move.
2016-08-23 01:12:39,172 [93] ERROR Logger - [Talk] Cannot find NPC with name "Clarissa".

 

Thats more interesting. Thanks for the log, Ill look into that.
edit: found the error, will be fixed in next version

 

Nice on the Clarissa Next up Vaal Overseer - still a problem in 1384 - not sure if it was supposed to be fixed. I waited for 10 mins of logs in the stuck:

Dropbox - Exilebuddy 113216 2016-08-23 16.53.zip

Same as before - bot doesnt get close enough

Video demo here: Dropbox - vaal.wmv

Still shot here:

 

I've already replied to that. In next version bot will do some patrolling route between exit door and dark altar.

 

Ah sorry i thought it might be in the update - no notes about the questbot in it.
The final Malachai boss fight the bot tends to ignore the 3rd tree until it has to chicken and reset and come back in. Most noticeable on Cruel and Merciless as it takes a long time to kill malachite with occasional hits on the third tree to kill it. Big log file attached - scroll to the very end:

Dropbox - Exilebuddy 97056 2016-08-23 21.36.zip

3 or 4 chickens later it still isnt trying to kill the third tree - so i stopped it and killed it myself (HC lev53 takes a while and I didnt want to die to a 10 minute Malachai fight).

 

There is a weird stuck that keeps happening when doing the Captain Arteri kill - the bot gets stuck in the tent and can't get out - because he is moving all the time it doesnt timeout either. End of the log:

Dropbox - Exilebuddy 73340 2016-08-27 17.08.zip

 

QuestBot only directs your character where to go. The actual fight is handled by Combat Routine. There is not much I can do to improve Malachai fight from within QB.
Stuck issues are the exact same situation, QB directs your character to go somewhere, but Pathfinding system fails to do that.

 

Is there any way to skip some quests? It is not too human-like to complete all the quests

 

Yes, I am working on that feature.