[Release] Demonbuddy stable build #399

Use version 392 to fix the Error in HandleTarget: Only part of a ReadProcessMemory or WriteProcessMemory request was completed, at addr: 00000000, Size: 416 issue

 

where can we dl it?

 

ask the developer

PS: But they will say that this issue is not demonbuddy related....and ask you to post log

 

tripwire update kill all older versions no more 392.. anyone having the 416 error with build 400?

 

so sad it never happens on my monk but on my DH, Wizard and WD it happens pretty often.

 

update please.

 

Any time soon this will be updated, the memory issue need to be addressed

Error in HandleTarget: Only part of a ReadProcessMemory or WriteProcessMemory request was completed, at addr: 00000000, Size: 416

 

db v400 with older trinity and questtools will fix that bug. I use version 3.1.14 and 2.3.2

 

It seems there is a failsafe switch that makes the bot log out when durability is 0 and we are in combat. It is heavily messing with the possibility of upgrading gems, since its quite normal to die more than 10 times to the rift guardian in high Greater rifts.

I can see the logic behind that autologgin off, but it would be amazing if we can choose between using it or not. Definitely, I'd rather not have it on while doing greater rifts. If possible, of course.

 

I don't even know where to start, I was botting 24/7 using beta and or release builds just fine, i would occasionally get the 416 game remake error like once every few days at best, twice in one day rarely. Exp buff just hit, now my bot is constantly getting the 416 error AND its stopping mid-rift always at the same 2 spots on the dahlgur oasis or sewers map before it enters a next level. Not sure what causes it...It happened very little before but with the exp buff I still have been running bot 24/7 no changes, and I have had to restart for 416 error probably 6 times since 1am(832pm now) and found my bot disconnected or standing with bot session stopped at dahgul oasis rift level. I saved the logs, I really am interested in seeing why the bot will stop its session in the same spot each time on the same map.


edit - well that was simple enough, appears its a rift468 profile issue:

Code:

10:28:29.509 DEBUG DefaultNavigationProvider Generated path to <1573.75, 543.75, 0> (Dungeon Node 1574, 544, 0, Dir=W) with 8 hops.
10:28:29.576 DEBUG IfTag   File "", line 5
        return bool(Zeta.Bot.Settings.GlobalSettings.Instance.LastProfile.Contains('RBF') and not         (ActorExistsAt(135248, ZetaDia.Me.Position.X, ZetaDia.Me.Position.Y, ZetaDia.Me.Position.Z, 100))
                                                                                                                                                                                                           ^
SyntaxError: unexpected token '<newline>'

10:28:29.577 INFO  BotMain Stopping the bot.
10:28:29.577 INFO  BotMain Session lasted for: 02:20:16.7955763
10:28:29.578 DEBUG BotMain CurrentBot.Stop()
10:28:29.998 DEBUG BotMain Navigator.Clear()