[Beta] QuestBot

lol, thats your fix?

so if the duck can't swim, its the waters fault?

rekt

 

He said "for now" which means it's not a permanent solution. He's also not blaming anything unlike you.

 

yay its no solution at all, so ofc not permanent. its just, its been like 1.5 weeks now, at least, so im wondering if it has any priority.

 

try makeing your own quest plugin/routine. I'll see you in never.

 

Bot is working by reading your in game memory. If that memory does not contain a valid data - bot is screwed. Workaround must be made and it will be made, no worries.
Additional problems in this particular case:
- Only small portion of users have encountered such poe memory behavior.
- Neither me nor Pushedx can reproduce it on our machines.

 

ty for the answer sir, really appreciate it!
will try to build a working level vm on my side.

 

ok i menage to fix my latest problems but now i have sth diffrent error looks like this:
2016-08-08 09:35:07,959 [22] DEBUG Logger - [OpenInventoryPanel]
2016-08-08 09:35:07,962 [22] DEBUG Logger - [OpenInventoryPanel] The InventoryUi is not opened. Now opening it.
2016-08-08 09:35:07,975 [22] INFO Logger - [ReactionWait] Now sleeping 293 ms.
2016-08-08 09:35:08,282 [22] DEBUG Logger - [CloseBlockingWindows] LokiPoe.Gui.IsLeftPanelShown || LokiPoe.Gui.IsRightPanelShown. Closing them.
2016-08-08 09:35:08,328 [22] INFO Logger - [SellTask] No items to sell.
2016-08-08 09:35:08,330 [22] INFO Logger - [StashTask] No items to stash.
2016-08-08 09:35:08,343 [22] ERROR Logger - [DefaultPlayerMover::MoveTowards] ExilePather.FindPath failed from {205, 306} to {2208, 184}.
2016-08-08 09:35:08,344 [22] ERROR Logger - [MoveTowards] Fail to move towards Waypoint at {2208, 184}
2016-08-08 09:35:08,345 [22] ERROR Logger - [MoveTowardsWalkable] Unexpected error. Fail to move towards Waypoint at {2208, 184}
2016-08-08 09:35:08,346 [22] ERROR Logger - [ErrorManager] Error count: 10/10.
2016-08-08 09:35:08,346 [22] ERROR Logger - [ErrorManager] Errors threshold has been reached. Now requesting bot to stop.
2016-08-08 09:35:08,347 [22] INFO BotManager - [Stop] Now requesting the BotThread to stop.
2016-08-08 09:35:08,353 [22] ERROR BotManager - [Tick] Exception #1 during execution:
Buddy.Coroutines.CoroutineUnhandledException: Exception was thrown by coroutine ---> System.Exception: MAX_ERRORS
at EXtensions.ErrorManager.ReportError() in C:\Users\Buddy\Desktop\nvnbnvhg\3rdParty\_CONFIGS_\Default\EXtensions\Content-33209929\ErrorManager.cs:line 36
at EXtensions.Move.TowardsWalkable(Vector2i pos, String destionation) in C:\Users\Buddy\Desktop\nvnbnvhg\3rdParty\_CONFIGS_\Default\EXtensions\Content-33209929\Move.cs:line 32
at EXtensions.Positions.WalkablePosition.Come() in C:\Users\Buddy\Desktop\nvnbnvhg\3rdParty\_CONFIGS_\Default\EXtensions\Content-33209929\Positions\WalkablePosition.cs:line 32
at QuestBot.OpenWaypointTask.<Logic>d__8.MoveNext() in C:\Users\Buddy\Desktop\nvnbnvhg\3rdParty\_CONFIGS_\Default\QuestBot\Content-33216169\OpenWaypointTask.cs:line 68
--- 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._{O!x4`|Lol0Z?o=@BFWg'^B).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 C:\Users\Buddy\Desktop\nvnbnvhg\3rdParty\_CONFIGS_\Default\QuestBot\Content-33216169\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.Ddg`t\*2;{G<'hDo2Iv3h\&2iK8.RS\[lc%I6\[\\;}\[KZ#Kk'Q`d2\\$.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 C:\Users\Buddy\Desktop\nvnbnvhg\3rdParty\_CONFIGS_\Default\QuestBot\Content-33216169\QuestBot.cs:line 142
at Loki.Bot.BotManager.?????????????????????????????????????????(IBot )
2016-08-08 09:35:08,361 [22] DEBUG Logger - [QuestBot] Stop
2016-08-08 09:35:08,361 [22] DEBUG Logger - [CommonEvents] Stop
2016-08-08 09:35:08,362 [22] DEBUG Logger - [AdvancedItemFilter] Stop
2016-08-08 09:35:08,363 [22] DEBUG Logger - [AutoFlask] Stop
2016-08-08 09:35:08,363 [22] DEBUG Logger - [AutoLogin] Stop
2016-08-08 09:35:08,364 [22] DEBUG Logger - [CommunityLib] Stopped
2016-08-08 09:35:08,365 [22] DEBUG Logger - [DevTab] Stop
2016-08-08 09:35:08,365 [22] DEBUG Logger - [EquipPlugin] Stop
2016-08-08 09:35:08,366 [22] DEBUG Logger - [EXtensions] Stop
2016-08-08 09:35:08,366 [22] DEBUG Logger - [GemLeveler] Stop
2016-08-08 09:35:08,367 [22] DEBUG Logger - [Idler] Stop
2016-08-08 09:35:08,368 [22] DEBUG Logger - [ObjectExplorer] Stop
2016-08-08 09:35:08,368 [22] DEBUG Logger - [Stats] Stop
2016-08-08 09:35:08,368 [22] DEBUG Logger - [OldRoutine] Stop


http://www.filedropper.com/exilebuddy12482016-08-072351

 

havent seen a guy with more problems and errors than you lol...

 

Not sure if anyone else is having this problem, but bot occasionally gets stuck after killing Vaal in A2. Essentially, the bot just sits at the bottom left of the stairs leading to the City of Sarn. This is too far to trigger the "opening" of the door to the outside, and the bot will just sit there forever.

I don't have a log on hand, but its just basically spamming "Waiting for area change/transition" or whatever non stop and nothing else of interest. If I see it again, I'll grab the log.

 

Had it about 1 min ago

 

had it too, many times, also bot somtimes don't rescue clarissa in act 3 and then he stuck coz there is no clarissa in town ...

 

emdok
Thanks for the log. That issue will be fixed in next version.

skyllynt
I need a log to tell you more, but I am pretty sure that was a Vaal's corpse absence. I experienced that error a couple of times myself. Basically, after Vaal's death, his corpse sometimes does not spawn (I dunno why, say thanks to GGG). Bot moves to pyramid's exit only when Vaal is dead, and without a corpse bot assumes he is alive. Ill add some more checks that hopefully will fix it.

As for Clarissa. Do you interfere the bot? Its a really low chance that bot can miss her by itself. She is right on the way to Sarn. I will also add Guard Captain tracking, maybe that will help.

 

Hi, I have attached the log. It seems to still occur with the new version of QuestBot. I found the bot waiting at the bottom of the stairs to City of Sarn once again (after have killed Vaal).
View attachment vaal_stuck_log.txt

 

According to log everything went fine. Bot registered Vaal's death and moved to the Sarn area transition. If transition did not activate - thats a game problem, not bot's. After Vaal's death everything bot can do is move to area transition and wait endlessly until its become active.
How long did you wait? You know sometimes Sarn area transition activation can take like 3-4 minutes, thats an old and known poe bug.

 

it doesnt walk close enough to the door to proc the transition

 

i keep getting some weird... thing where it says there is a issue with something in my invetory.

 

Consider linking a full log, tyvm

 

Is there a way to stop the bot opening all the strong boxes? Makes HC unviable (I am happy to edit the code if necessary)

 

In /EXtensions/CommonTasks/OpenChestTask.cs
Comment all code from line 68 to 75

 

As another user mentioned, it's not because the game bugs out. It's because the bot is too far away from the area transition(and thus never triggers the event which opens the City of Sarn). The wait spot for the tombs opening needs to be changed (or added).