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

Bot leaving game early in 2.250.769 (also 772, 775)

T

thegrimace

New Member
Joined
Jun 13, 2016
Messages
7
Reaction score
0
Last night I updated from 2.250.767 via SVN and observed the bot attempting to leave the game for (what seemed to be) no reason. I tried disabling gold and experience inactivity timers, but that had no effect. The bot would just decide that it was done in the middle of a rift.

I've been running this build and profile mostly successfully on 2.250.767 for the past week or so. I say "mostly" because it will occasionally ignore portals in rifts, leading to running back and forth on an already cleared level. I check SVN daily in hopes that the portal ignore issue has been fixed.

I've attached my log from the session last night, where you'll see several entries that look like this:

Code: 
2017-04-22 05:08:36,897 [Main Bot Thread] INFO  LeaveGameTag (null) - Leaving game, reason: Done

When that log message displays, the bot will immediately try to leave the game.

I reverted back to the previous commit (r320) in SVN and the bot continued working as it had previously.

All Bot Information
DemonBuddy version: 1.1.3154.482
Trinity version: 2.250.769
Other plugins: none
Profile: GreaterRift.xml
External programs: none

Character Information
Class and Build: Impale DH
Routine: https://www.thebuddyforum.com/threa...-build-with-impale-gr70-speed-farming.301357/
 

Attachments

Last edited:
I had this issue as well. For another unrelated reason I decided to do a completely fresh install. Since then, this behavior seems to have stopped. Or it has at least gotten smarter and stopped doing it while I'm at the computer.
 
I tried again with a completely fresh install (other than the custom routine) and I'm experiencing the same behavior. New log file attached.
 

Attachments

Tried again on 2.250.772 with a fresh DB install tonight. As far as I can tell, it's only happening with the DH impale routine. I've tried two different ones:

Both the original and the updated one from this post: https://www.thebuddyforum.com/threa...-build-with-impale-gr70-speed-farming.301357/
Nightbreeze's routine from this post: https://www.thebuddyforum.com/threads/impale-demon-hunter-combat-profile.300108/#post-2399837

Interestingly, the crash does not seem to happen with any other routines - I tried a few different wizard routines and did not experience the same problem.

I'm not super adept at troubleshooting Trinity/DB issues from logs (this is the first major problem I've had over the course of a few years), but it seems like the root cause of the bot leaving the game is this stack trace:

Code: 
2017-04-30 03:27:58,452 [Main Bot Thread] DEBUG DefaultLogger (null) - [Trinity 2.250.772] Exception in NephalemRiftTag: System.Exception: Only part of a ReadProcessMemory or WriteProcessMemory request was completed, at addr: 0000019C, Size: 12
   at GreyMagic.ExternalProcessMemory.ReadByteBuffer(IntPtr addr, Void* buffer, Int32 count)
   at GreyMagic.MemoryBase.Read[T](IntPtr addr)
   at Zeta.Game.Internals.Actors.DiaObject.get_Position()
   at Zeta.Bot.Navigation.DefaultNavigationProvider.?????????????????????????????????????????.?????????????????????????????????????????()
   at System.Threading.Tasks.Task`1.InnerInvoke()
   at System.Threading.Tasks.Task.Execute()
--- 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 ?????????????????????????????????????????.?????????????????????????????????????????.?????????????????????????????????????????(Task , Int32 )
   at Buddy.Coroutines.Coroutine.W\&{\*9OC`}=9M1K3oVZ7POI\\ !.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 Buddy.Coroutines.Coroutine.=F7 YyR:0GSHVm@\]/\\#=3-|Q.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 Buddy.Coroutines.Coroutine.V\,XGkFlU>JXwWJ~YNE%>@tuw#.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 Zeta.Bot.Navigation.DefaultNavigationProvider.hfN=^ATvVe#$<Uz^|P8Xv=9R!.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 Zeta.Bot.Navigation.DefaultNavigationProvider.Cs(:vMo6\& _wTk/4S'}gnn>I.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 Zeta.Bot.Navigation.DefaultNavigationProvider.v=}Fpt\.y:2a}7(pyY"\."Lk;s$.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 Trinity.Components.Adventurer.Coroutines.NavigationCoroutine.<Moving>d__29.MoveNext() in C:\db\Plugins\Trinity\Components\Adventurer\Coroutines\NavigationCoroutine.cs:line 348
--- 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 Trinity.Components.Adventurer.Coroutines.NavigationCoroutine.<GetCoroutine>d__20.MoveNext() in C:\db\Plugins\Trinity\Components\Adventurer\Coroutines\NavigationCoroutine.cs:line 145
--- 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 Trinity.Components.Adventurer.Coroutines.NavigationCoroutine.<MoveTo>d__13.MoveNext() in C:\db\Plugins\Trinity\Components\Adventurer\Coroutines\NavigationCoroutine.cs:line 63
--- 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 Trinity.Components.Adventurer.Coroutines.ExplorationCoroutine.<Exploring>d__18.MoveNext() in C:\db\Plugins\Trinity\Components\Adventurer\Coroutines\ExplorationCoroutine.cs:line 163
--- 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 Trinity.Components.Adventurer.Coroutines.ExplorationCoroutine.<GetCoroutine>d__10.MoveNext() in C:\db\Plugins\Trinity\Components\Adventurer\Coroutines\ExplorationCoroutine.cs:line 81
--- 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 Trinity.Components.Adventurer.Coroutines.ExplorationCoroutine.<Explore>d__2.MoveNext() in C:\db\Plugins\Trinity\Components\Adventurer\Coroutines\ExplorationCoroutine.cs:line 26
--- 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 Trinity.Components.Adventurer.Coroutines.RiftCoroutines.RiftCoroutine.<SearchingForExitPortal>d__57.MoveNext() in C:\db\Plugins\Trinity\Components\Adventurer\Coroutines\RiftCoroutines\RiftCoroutine.cs:line 862
--- 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 Trinity.Components.Adventurer.Coroutines.RiftCoroutines.RiftCoroutine.<GetCoroutine>d__35.MoveNext() in C:\db\Plugins\Trinity\Components\Adventurer\Coroutines\RiftCoroutines\RiftCoroutine.cs:line 210
--- 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 Trinity.ProfileTags.RiftProfileBehavior.<MainTask>d__22.MoveNext() in C:\db\Plugins\Trinity\ProfileTags\RiftTag.cs:line 79
--- 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 Trinity.Components.QuestTools.BaseProfileBehavior.<Run>d__27.MoveNext() in C:\db\Plugins\Trinity\Components\QuestTools\BaseProfileBehavior.cs:line 84
2017-04-30 03:27:58,519 [Main Bot Thread] DEBUG DefaultLogger (null) - [Trinity 2.250.772] Finished Tag: NephalemRiftTag in 37.37 seconds

You can see at the end that the bot thinks that it has finished the rift tag, which (I think) results in leaving the game. The bot leaves the game a few seconds afterwards with this message:

Code: 
2017-04-30 03:28:01,593 [Main Bot Thread] INFO  LeaveGameTag (null) - Leaving game, reason: Done

Would anyone be able to take a look at either of the routines I linked above to see if there's anything out of the ordinary that could be causing this? I looked them over and nothing jumps out at me, but I'm not very familiar with C# and I've never written my own routine before.

Thanks!
 
I'm still seeing it myself on both my wizard and my DH using multiple routines. Very random. Have seen it be in a rift less than a minute and decide it was done. Have seen it almost be complete and decide it was done. I'll grab logs and post them here whenever I see it happening.

Code: 
2017-04-30 05:58:27,455 [Main Bot Thread] DEBUG DefaultLogger (null) - [Trinity 2.250.775] Exception in GreaterRiftTag: System.Exception: Only part of a ReadProcessMemory or WriteProcessMemory request was completed, at addr: 0000019C, Size: 12
   at GreyMagic.ExternalProcessMemory.ReadByteBuffer(IntPtr addr, Void* buffer, Int32 count)
   at GreyMagic.MemoryBase.Read[T](IntPtr addr)
   at Zeta.Game.Internals.Actors.DiaObject.get_Position()
   at Zeta.Bot.Navigation.DefaultNavigationProvider.?????????????????????????????????????????.?????????????????????????????????????????()
   at System.Threading.Tasks.Task`1.InnerInvoke()
   at System.Threading.Tasks.Task.Execute()
--- 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 ?????????????????????????????????????????.?????????????????????????????????????????.?????????????????????????????????????????(Task , Int32 )
   at Buddy.Coroutines.Coroutine.W\&{\*9OC`}=9M1K3oVZ7POI\\ !.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 Buddy.Coroutines.Coroutine.=F7 YyR:0GSHVm@\]/\\#=3-|Q.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 Buddy.Coroutines.Coroutine.V\,XGkFlU>JXwWJ~YNE%>@tuw#.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 Zeta.Bot.Navigation.DefaultNavigationProvider.hfN=^ATvVe#$<Uz^|P8Xv=9R!.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 Zeta.Bot.Navigation.DefaultNavigationProvider.Cs(:vMo6\& _wTk/4S'}gnn>I.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 Zeta.Bot.Navigation.DefaultNavigationProvider.v=}Fpt\.y:2a}7(pyY"\."Lk;s$.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 Trinity.Components.Adventurer.Coroutines.NavigationCoroutine.<Moving>d__29.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 Trinity.Components.Adventurer.Coroutines.NavigationCoroutine.<GetCoroutine>d__20.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 Trinity.Components.Adventurer.Coroutines.NavigationCoroutine.<MoveTo>d__13.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 Trinity.Components.Adventurer.Coroutines.ExplorationCoroutine.<Exploring>d__19.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 Trinity.Components.Adventurer.Coroutines.ExplorationCoroutine.<GetCoroutine>d__10.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 Trinity.Components.Adventurer.Coroutines.ExplorationCoroutine.<Explore>d__2.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 Trinity.Components.Adventurer.Coroutines.RiftCoroutines.RiftCoroutine.<SearchingForExitPortal>d__57.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 Trinity.Components.Adventurer.Coroutines.RiftCoroutines.RiftCoroutine.<GetCoroutine>d__35.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 Trinity.ProfileTags.RiftProfileBehavior.<MainTask>d__22.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 Trinity.Components.QuestTools.BaseProfileBehavior.<Run>d__28.MoveNext()

Immediately after this bot started logging out.
 

Attachments

Last edited:
I pulled 775 from SVN (had to comment out the FireWorldTransferStart call in InteractionCoroutine to get it to run) to see if any progress had been made, but still seeing the same issue. Log of my most recent run attached.

If there are any specific log settings I should check to make these logs more useful, please let me know.
 

Attachments

@thegrimace Are you now or have you ever ran YAR with your current installation of DemonBuddy? If so, try this for me.

Make a completely fresh install. DO NOT RUN YAR. See if you still see the logging out issue. I did a fresh install two days ago. No issues. Last night, I started using YAR again. Issue immediately popped up-even when I didn't have YAR running. I tried deleting the plugin that YAR installs and then ran DB again without YAR. Same thing. Random logouts. Did another fresh install. Have not ran YAR since the new install. No issues.

Please post if your issues go away with a fresh install that hasn't been used with YAR.
 
Anonuzer01 said:
@thegrimace Are you now or have you ever ran YAR with your current installation of DemonBuddy? If so, try this for me.

Make a completely fresh install. DO NOT RUN YAR. See if you still see the logging out issue. I did a fresh install two days ago. No issues. Last night, I started using YAR again. Issue immediately popped up-even when I didn't have YAR running. I tried deleting the plugin that YAR installs and then ran DB again without YAR. Same thing. Random logouts. Did another fresh install. Have not ran YAR since the new install. No issues.

Please post if your issues go away with a fresh install that hasn't been used with YAR.
Click to expand...

Hey, thanks for the suggestion, but I have not used any plugins other than Trinity. That being said, I have done a few fresh installs and the issue persists.
 
I am also having the same prb...
Solution for me was to rollback to .767
It's looking oke at least for the last 3 hours....
 
I had the issue in .767 so I'm afraid you will end up seeing it pop up again.

Tonight, I looked through my installed programs. I had several versions of Microsoft C++ and several versions of NetFramework installed. I completely uninstalled all of them and then re-installed only what is linked in the Demonbuddy download page. So far, I haven't seen any pre-mature logouts but it's only been a couple of hours. I'll report back tomorrow and let you guys know whether this seems to have fixed the issue.
 
mmm...i i botting from more then 36 hours with .767....and not any prb related.
Not even one!
So....767 is very stable for me...
Ofc he has some other minor issues....but nothing that i cannot handle : ))
 
Dunno if i am the only one....but i updated to .789....and same problem.....the bot is leaving the game for sader and wizard too....anyone else still have this error?
I had to quit .767....couse of not entering portals error
Dunno what else shoud i do :(

''Leaving game, reason: Done
Last run acquired 0 gold.''
 

Attachments

You must log in or register to reply here.
Back
Top