So here is my latest log, bot has been running since I last posted. I watched it quit and remake the game 4 times with the quests : "Sceptre of God " ~ Talk to Grigor "Piety's Pets " ~ Talk to Grigor Sever The Right Hand ~ Talk to Maramoa for your reward. It quit the game three times and started again by going back to The Ebony Baracks without talking to anyone, I have attatched my log. I will not turn the bot back or turn in quests until I get further instruction. View attachment Exilebuddy 4152 2015-01-11 11.09.txt
Hey Yori, Oh.. Um it doesn't talk to anyone at all, it just goes and does the quest. The only Npc it talks to is, Act 2, Eramir, The bandits Act 3, Clarissa, Lost in Love So it is working as intended. It shouldn't quit and remake any instances, unless you set it to make a new instance on death. By default, it chooses Take Last Checkpoint on death. Also, Code: 2015-01-11 18:14:00,923 [23] DEBUG Logger (null) - [StuckDetection] {756, 1236} => 3 2015-01-11 18:14:00,924 [23] DEBUG Logger (null) - [StuckDetection] {628, 1258} => 5 2015-01-11 18:14:00,924 [23] DEBUG Logger (null) - [StuckDetection] {631, 1258} => 6 2015-01-11 18:14:00,924 [23] DEBUG Logger (null) - [StuckDetection] {487, 1257} => 2 2015-01-11 18:14:00,925 [23] DEBUG Logger (null) - [StuckDetection] {491, 1257} => 3 2015-01-11 18:14:00,925 [23] DEBUG Logger (null) - [StuckDetection] bounds: {281, 45} 2015-01-11 18:14:30,959 [23] DEBUG Logger (null) - [StuckDetection] {491, 1257} => 28 2015-01-11 18:14:30,960 [23] INFO Logger (null) - [StuckDetection] We have been at the position {491, 1257} 28 times. We are most likely stuck! 2015-01-11 18:14:30,961 [23] DEBUG Logger (null) - [StuckDetection] bounds: {0, 0} 2015-01-11 18:14:30,984 [23] INFO Logger (null) - [SetNewInstanceOverride] 1_3_13 = True 2015-01-11 18:14:30,986 [23] DEBUG Logger (null) - [ActivateEscapeState] !IsEscapeStateActive. Attempting to open it. 2015-01-11 18:14:32,309 [23] DEBUG Logger (null) - [AutoSelectCharacter] DelayBeforeSelectingCharacter | SelectCharacterDelay: 00:00:04. 2015-01-11 18:14:32,309 [23] DEBUG Logger (null) - [AutoSelectCharacter] The bot will wait 00:00:04.9600000 before selecting a character. Your stuck detection is triggering new area overrides. That's probably what's causing it to log out and back in. Therefore, while trying to do quests, it's getting reseted due to the stuck detection kicking in and re-logging. Can you try it without stuck detection and see for yourself? Edit, Oh and don't worry about any tick issue errors, it's my plugin trying to get GUI data when in character select screen and other things. I'll have that fixed soon. Code: 2015-01-11 19:10:02,864 [23] ERROR Logger (null) - [Tick] Exception during execution: Buddy.Coroutines.CoroutineUnhandledException: Exception was thrown by coroutine ---> System.Exception: Only part of a ReadProcessMemory or WriteProcessMemory request was completed, at addr: 00000000, Size: 2128 at GreyMagic.ExternalProcessMemory.ReadByteBuffer(IntPtr addr, Void* buffer, Int32 count) at GreyMagic.MemoryBase.ReadBytes(IntPtr addr, Int32 count) at Loki.Game.LokiPoe.LocalData.() at Loki.Game.Utilities.PerCachedValue`1.get_Value() at Loki.Game.LokiPoe.LocalData.() at Loki.Game.LokiPoe.LocalData.get_TileHash() at Loki.Game.Utilities.PerAreaCachedValue`1.ShouldUpdateCache(Boolean force) at Loki.Game.Utilities.PerCachedValue`1.get_Value() at Loki.Game.LokiPoe.ObjectManager.() at Loki.Game.LokiPoe.ObjectManager.() at Loki.Game.Utilities.PerCachedValue`1.get_Value() at Loki.Game.LokiPoe.ObjectManager.get_Objects() at Loki.Game.LokiPoe..() at Loki.Game.LokiPoe.InGameState.get_CurrentTarget() at Loki.Bot.v3.Coroutines.?.() --- 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.v3.Coroutines.?.() --- 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.ValidateEnd(Task task) at Loki.Bot.Logic.Bots.BasicGrindBot.LootItemsTask..() --- 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.v3.TaskManager..() --- 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.Logic.Bots.BasicGrindBot.BasicGrindBot..() --- 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...() --- End of inner exception stack trace --- at Buddy.Coroutines.Coroutine.(Boolean ) at Buddy.Coroutines.Coroutine.(Boolean ) at Buddy.Coroutines.Coroutine.Resume() at Loki.Bot.Logic.Bots.BasicGrindBot.BasicGrindBot.Tick() at Loki.Bot.BotManager.(IBot )
I do believe it was the stuck detection and not your bot now... just wasn't letting it get far enough due to being "stuck" when it wasn't at times.. , I think that's silly... Not a very good stuck detection lol. I do apologize for not being able to identify that myself.
Hey Yori, The stuck detection is actually working as intended, but it's very, very sensitive. So you have to play around with it. And no worries on troubleshooting, I rather very much enjoy it, as it gives me reasons to probe on what can happen. Therefore sometimes find things that aren't the actual cause but solves another issue. Anyhow, glad to see it resolved =).
Hi Yori, I actually don't even use the plugin lol. Movement skills to move resolves most stuck issues, and you can add more then one movement skill, like leapslam, or lightning warp together.
Hey ExVault, Thanks dude!!! Took a lot of reconfiguring and etc. Word is Pushedx has some sweet GUI features coming in the near future, so it will look even better then mine.
I am looking forward to the new look. I like the current one but always nice to have somehing maybe a bit easier to use. Or view various stats
Hey thetestdummy, Thanks! I just did some more work on it, act 1 optional quests done, adding options to choose which one, and randomizers for them. Also found a way to get the bots to go to bandits right away, so there's an option for that.
Hey I just downloaded the Beta Exilebuddy and this plugin. I can't seem to get it to work at all, is there a profile or something that i'm missing? I have used the d3 bot many times in the past but i'm new to exilebuddy
I did, it just stands around not moving. Here is a log of what it shows: [QuestPlugin] Start, we're doing Quests Primary = True, Secondary = False [QuestPlugin] UPDATING QUEST [QuestPlugin] UPDATING QUEST COMPLETE [QuestPlugin] We're in Act 1 [QuestPlugin] Is In Correct Area, Proceeding with Primary "Tasks" [QuestPlugin] We're in Act 1, adding tasks for that act only [AddAtFront] Now adding [HandleAct1Progress] This task helps BasicGrindBot stay in the Vaal boss fight area, resetting exploration to keep the bot moving around to trigger different phases.. [HandleAct1Progress] AddAtFront Success. [AddAtFront] Now adding [HandleGlyphWall] This task helps BasicGrindBot stay in the HandleAliraKill boss fight area, resetting exploration to keep the bot moving around to trigger different phases.. [HandleGlyphWall] AddAtFront Success. [HandleMerveilArea] AddAfter ExploreTask Success. [QuestPlugin] Primary Tasks Added, Proceeding [ExampleRoutine] Start [Start] Please configure the ExampleRoutine settings (Settings -> ExampleRoutine) before starting! [Stop] Now requesting the BotThread to stop. [HandleGlyphWall] Task Loaded. [HandleAct1Progress] Task Loaded. [HandleBlockingChestsTask] Now resetting task state. [IdTask] Now resetting task state. [SellTask] Now resetting task state. [WithdrawTask] Now resetting task state. [ReturnToGrindZoneTask] Now resetting task state. [TagWaypointTask] Now resetting task state. [UseLooseCandleTask] Now resetting task state. [UnblockCorruptedAreaTransitionTask] Now resetting task state. [TravelToGrindZoneTask] Now resetting task state. [TravelThroughBossAreasTask] Now resetting task state. [TravelThroughBossAreasTask] Now resetting task state. [HandleMerveilArea] Task Loaded. [Start] The plugin AutoFlask is enabled. [Start] The plugin QuestPlugin is enabled. [Start] PlayerMover.Instance: Loki.Bot.v3.DefaultPlayerMover. [BasicGrindBot] OnStop [AutoFlask] Stop [QuestPlugin] Stop [RemoveAllTasks] Starting [Remove] Now removing [HandleAct1Progress]. [RemoveAllTasks] HandleAct1Progress Remove Success [Remove] Now removing [HandleGlyphWall]. [RemoveAllTasks] HandleGlyphWall Remove Success [Remove] Now removing [HandleMerveilArea]. [RemoveAllTasks] HandleMerveilArea Remove Success [RemoveAllTasks] Finished [ExampleRoutine] Stop [QuestPlugin] CLEARING GUI
Hey Rafreak, You have to set the settings for it, go here and read it all. https://www.thebuddyforum.com/exilebuddy-forum/exilebuddy-guides/178296-exilebuddy-users-guide.html
hey darkbluefirefly, Ive been using this and i'm up to act 2 cruel now, its great but theres a couple problems i found. Act 1 works perfect, act 2 99% works, but at act 3 once it joins most zones, the bot will stop and i have to press start again. Im not complaining just wanted to let you know, maybe its just me? Anyway thanks its a time saver!
Hey thetestdummy, Thanks for the feedback, did you check the zoneoverlevel? The text box on the top right. That's the amount you are allowed to be over leveled before it stops the bot. Also, if you set it to 0, it totally ignores this option. If that's not the case, can you click "zip" on the ExileBuddy when it's having this issue, read what the log says, and post that file here. Thanks.
Err... yes i noticed that behavior badly too. But the bot stop after reach an area. So times later some mobs kill my char because i wasnt near computer. I play hardcore only and loose some char because of that. No offence about the zoneoverlevel.... it's a great idea but if trigger that the bot should go back town first . Next Idea will be a parameter (Boolean) like "autoExp". So it take automatically a Zone wich is in Levelrange and Exp there as long as the next Questzone is possible?! Sorry for this kiddy imaginations but i am badly new in coding here....