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

List of current bugs

ok man ill try that out thank you...also he stands around and gets killed without fighting...also bot keeps trying to open cursed chest and doesn't fight, alo bot does not complete all bounties...



You know what....I didn't realize that I had to manually replace the trinityplugin and the quest tools plugin to get the most up to date version...Silly
 
List of current bugs
  • Dumping active bounties etc. info not working Fixed
  • Not showing Battle tag etc. in window title Fixed
  • Rift keystone fragment shows ItemType "Unknown" Fixed

Please post any issues you come across in this thread.

Here it is Nesox, nasty Nancy is back after month and a half. It was present on latest prepatch release but i was using some older version that didnt had it.

Going for past month and a half...

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

Bot randomly stops in char screen.
 
Quote Originally Posted by quinsy View Post
For those with the issue that the bot keeps going to hell rift level one with r-rift, edit the xml file.

<UseWaypoint questId="312429" stepId="2" waypointNumber="48" name="Waypoint-5820" statusText="" />

just search for 312429 and edit the line from "46" to"48" and "300 something" to 5820.

This worked perfectly, Thank you for posting. I was having a helluva issue getting this too start normal rifts.
 
so far I have just noticed it has been pretty laggy that's it as of now
 
Running latest version of trinity, quest and db.
the list.

1) Character will not heal with a normal potion (but will with a legendary)
2) Latency spikes with DB program to diablo 3. (at startup and in game)
3) No current bounty working profiles for the new bounties.
4) New Quest tools avoidance is very over board (maybe a guide to turn this down / off?
5) Armory shard cap now needs updating, but also its ignoring the spend at value.
i may update this as i go on, but these are just a few overall issues i have found since the new update,

Regards
 
also gold and exp inactivity always gets tripped here, db doesnt record exp/gold gain except from bounties finishing. rendering rifts useless, always leaving after 180 seconds in my case (exp inactivity at 180s).
 
A new rift map X1_LR_Tileset_Exterior_Highlands (LevelAreaId: 347562) has the same problem with raycasts as p1_TieredRift_Challenge (405915) map (which was added to NeverRaycastLevelAreaIds list in Trinity for this reason I think). None of the ISearchAreaProvider functions seem to work in this map.
Does this mean Demonbuddy will not support any of the new maps or we can hope that this will get fixed?
 
Dont know if this goes here, but the bot is ignoring the new 3 goblin types no matter what setting you got on in Trinity
 
demonhunter keeps shooting east, even if the creauteres are south...just updated the bot and now that's a desaster, redownloading, deleting everything and so on doesnt solve this problem...
 
A new rift map X1_LR_Tileset_Exterior_Highlands (LevelAreaId: 347562) has the same problem with raycasts as p1_TieredRift_Challenge (405915) map (which was added to NeverRaycastLevelAreaIds list in Trinity for this reason I think). None of the ISearchAreaProvider functions seem to work in this map.
Does this mean Demonbuddy will not support any of the new maps or we can hope that this will get fixed?

Also in Act 2 Dahlgur Oasis (57425 A2_caOut_Oasis) ISearchAreaProvider.GetHeight always returns 0 while the real values of height are around 98
 
Dont know if this goes here, but the bot is ignoring the new 3 goblin types no matter what setting you got on in Trinity

This is a frequent one I have noticed, even almost since blood goblins I want to say... But lately they do a good job of the original goblins, however my bot will easily ignore the Insufferable Miscreant, the Gelatinous Sire, and the Gilded Baron. I do know that if you have item pickup for like all rares, all blues, gold cap under 30-50k whatever(I let my ferrets pickup my gold, but then again I run boon + goldfind set for a day or two of botting, get my few billion gold and stop using it). The picking up of items/gold will distract the bot even further from attacking the goblins, as it prioritizes the items first.

Which actually leads me to one of another sort of annoying bugs, since s3 is new and all. Like any good hoarder I have my bot set to pickup every white, blue, rare, leg, open chests/weapon and armor racks. Now some maps the bot can run into anywhere from 2-4 elite/rare mix packs, or even just 2 elite/rare packs with dangerous affixes(I do not have a templar relic/dual unity setup yet, missing 1 unity 1 relic) I may one shot everything on t6, but I also get one-shotted when my bot sweeps an area, a bunch of rares/blues drop, bot walks straight into dangerous elite pack/mobs to pick items up, giving little to no effort to attack the monsters now beating on him in melee range, and in fact crowding him to the point he cant move, and either dies or luckily vaults out in time as awareness pops off.

The one MAJOR bug I have, its a profile bug. RiftBot from DyingHmmn. Unfortunately it has not been updated in a long time. rev467 was broken because blizz changed the jailer/warden maps to multiple map areas, so a rev468 was released. Whatever happened with the DB updates, or if it was an existing profile issue. I can no longer run this rift bot, on rift full because there are about a dozen different map spots where the bot thread will stop on its own because of this error:

Code:
10:33:26.195 DEBUG Logger [KadalaSpree][KadalaPlugin] Not in Town or Adventure Mode
10:33:26.221 DEBUG Logger [KadalaSpree][KadalaPlugin] below portal threshold or setting turned off!
10:33:26.244 DEBUG Logger [QuestTools][ExploreDungeonTag] Nodes [Unvisited: Route:28 Grid:28 | Grid-Visited: 82/110] Box:28/0.05 Step:MainBehavior PP:10 Dir: N Current: 314, 1364, 0
10:33:26.394 DEBUG Logger [QuestTools][ExploreDungeonTag] Marking nearby node <313.75, 1363.75, 0> as visited, distance 10/10, IsVisited=False
10:33:26.415 INFO  Logger [QuestTools][GridRoute] Generated new Weighted Nearest Minimap Unvisited Route with 27 nodes in 19ms
10:33:26.472 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:33:26.473 INFO  BotMain Stopping the bot.
10:33:26.473 INFO  BotMain Session lasted for: 01:53:21.8352083
10:33:26.474 DEBUG BotMain CurrentBot.Stop()
10:33:26.903 DEBUG BotMain Navigator.Clear()
10:33:26.904 DEBUG DefaultNavigationProvider Navigator.Clear
10:33:26.905 DEBUG BotMain TreeHooks.Instance.ClearAll()
10:33:26.906 INFO  RoutineManager Chose Trinity as your combat routine
10:33:26.907 DEBUG TreeHooks Replaced hook [RoutineCombat] 4d84cf3d-9ab0-4394-8e46-5b6972a75686
10:33:26.908 DEBUG Logger [QuestTools][BotBehaviorQueue] Inserting BotBehaviorQueue Hook
10:33:26.909 DEBUG TreeHooks Inserted new hook [BotBehavior @0] efd475db-c965-4118-b4f0-a5fc405bb781
10:33:26.910 INFO  Logger [Trinity] Inserting GoldInactivity into TreeStart
10:33:26.911 DEBUG TreeHooks Inserted new hook [TreeStart @0] 1d489efc-75d0-410b-8582-a928f8f81d76
10:33:26.912 INFO  Logger [Trinity] Inserting XPInactivity into TreeStart
10:33:26.913 DEBUG TreeHooks Inserted new hook [TreeStart @0] 45cca8c1-597c-426a-9b9b-c05003810f19
10:33:26.914 DEBUG BotMain OnStop event
10:33:26.915 DEBUG BotMain OnStop Event Invoking
10:33:26.918 DEBUG ProfileOrderManager [BotMain.OnBotStop] Resetting caches
10:33:26.919 DEBUG Logger [QuestTools][ExploreDungeonTag] ExploreDungeon ResetCachedDone()
10:33:26.921 DEBUG ProfileOrderManager Resetting current behavior.
10:33:26.925 DEBUG BrainBehavior Exception during scheduling Pulse: Microsoft.Scripting.SyntaxErrorException: unexpected token '<newline>'
   at Microsoft.Scripting.ErrorSink.Add(SourceUnit source, String message, SourceSpan span, Int32 errorCode, Severity severity)
   at IronPython.Compiler.Parser.ReportSyntaxError(Int32 start, Int32 end, String message, Int32 errorCode)
   at IronPython.Compiler.Parser.ReportSyntaxError(Token t, IndexSpan span, Int32 errorCode, Boolean allowIncomplete)
   at IronPython.Compiler.Parser.ReportSyntaxError(TokenWithSpan t, Int32 errorCode)
   at IronPython.Compiler.Parser.FinishArgListOrGenExpr()
   at IronPython.Compiler.Parser.AddTrailers(Expression ret, Boolean allowGeneratorExpression)
   at IronPython.Compiler.Parser.ParsePower()
   at IronPython.Compiler.Parser.ParseFactor()
   at IronPython.Compiler.Parser.ParseExpr(Int32 precedence)
   at IronPython.Compiler.Parser.ParseComparison()
   at IronPython.Compiler.Parser.ParseNotTest()
   at IronPython.Compiler.Parser.ParseAndTest()
   at IronPython.Compiler.Parser.ParseOrTest()
   at IronPython.Compiler.Parser.ParseExpression()
   at IronPython.Compiler.Parser.ParseTestListAsExpr()
   at IronPython.Compiler.Parser.ParseReturnStmt()
   at IronPython.Compiler.Parser.ParseSmallStmt()
   at IronPython.Compiler.Parser.ParseSimpleStmt()
   at IronPython.Compiler.Parser.ParseStmt()
   at IronPython.Compiler.Parser.ParseSuite()
   at IronPython.Compiler.Parser.ParseClassOrFuncBody()
   at IronPython.Compiler.Parser.ParseFuncDef()
   at IronPython.Compiler.Parser.ParseStmt()
   at IronPython.Compiler.Parser.ParseFileWorker(Boolean makeModule, Boolean returnValue)
   at IronPython.Compiler.Parser.ParseFile(Boolean makeModule, Boolean returnValue)
   at IronPython.Runtime.PythonContext.ParseAndBindAst(CompilerContext context)
   at IronPython.Runtime.PythonContext.CompilePythonCode(SourceUnit sourceUnit, CompilerOptions options, ErrorSink errorSink)
   at IronPython.Runtime.PythonContext.CompileSourceCode(SourceUnit sourceUnit, CompilerOptions options, ErrorSink errorSink)
   at Microsoft.Scripting.SourceUnit.Compile(CompilerOptions options, ErrorSink errorSink)
   at Microsoft.Scripting.SourceUnit.Execute(Scope scope, ErrorSink errorSink)
   at Microsoft.Scripting.Hosting.ScriptSource.Execute(ScriptScope scope)
   at Zeta.Common.ScriptManager.GetCondition(String expression)
   at Zeta.Bot.Profile.Composites.IfTag.GetConditionExec()
   at Zeta.Bot.Profile.Composites.WhileTag.get_IsDone()
   at Zeta.Bot.Profile.ProfileBehavior.get_IsDoneCache()
   at Zeta.Bot.ProfileOrderManager.(IEnumerable`1 )
   at Zeta.Bot.ProfileOrderManager.(IEnumerable`1 )
   at Zeta.Bot.ProfileOrderManager.UpdateCurrentBehavior()
   at Zeta.Bot.ProfileManager.UpdateCurrentProfileBehavior()
   at Zeta.Bot.Logic.OrderBot.(Object , EventArgs )
   at Zeta.Bot.Logic.BrainBehavior.DoScheduling()
10:33:26.926 INFO  BotMain Bot Thread Ended. Was this requested?

A lot of people are getting the exact same problems, as this person posted this:

hey DyingHymn i found the spot where the bot stops working .

world id: 288454
level id : 332323
quest id: 312429

player postiion: x=799,1096 y=807,2026 z=0,10


Imgur

That image, that is one of the few areas the bot will stop on its own and your shit out of luck until restarted and you don't know if its going to stop on its own again in 5 minutes, 30 minutes, or 2 hours. I managed to get a 3 hour run was the longest, mind you this was over a 2-3 day period when I was super low on fragments, and simply put for exp/LPH doing rift full runs IS way better hence the preference. I now use r-rift to kill RG, close and repeat. This is very fragment intensive. I go to bed, and wake up with ~100 frags gone easy.

So basically with the new A4 profiles I need to spend anywhere from a full 2-3 days of running cache profile to get a few hundred rift keys, then run out again in just a few days or less. 4 frags per full bounty act + the 1-3 in cache. Back when portals were 5 per, you got 2-3 frags per bounty, and upwards of 4-8 frags per cache but we are at the point where opening rift portals with 5 for everyone was so long ago, no one has a massive stash of 5-10k fragments anymore. Prior to season 3 ending, I took my raekor barb and used war cry/sprint marathon with chilanik chain and FC to rape the hell out of A4 bounties(super fast return time, blacklisted diablo/izual) and stashed 2500 fragments literally in just a day and a half because I saw the pending changes coming to A4 bounty swaps. But the new work buddyme and co have done on the latest a4 bounty is great, it works good. but obv with the bounty changes itll never be as fast as it used to be.

So yes running RG close repeat can be very good for shards, to target gambling certain items. However once you have done that, you can get way more LPH/exp doing full on rift clears albeit slower blood shard gain but still a gain plus the chances of lots more goblins/packs.
 
When doing a townrun and "Keep Legendaries Unidentified" is ticked, and the LAST STASH TAB is full, it will continuously loop the townrun. I had a rimaldinis gift and legendary potions in the bag and it kept running to stash "Not enough space to perform this operation" would pop up in D3 as a warning, then it would run to the salvage again and repeat. With Legendaries Unidentified OFF this is not a problem.

Please investigate.
 
I've got two log files one from beta version of demonbuddy and one from stable repeating the same error a few people have.

Code:
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>'

https://www.thebuddyforum.com/demonbuddy-forum/demonbuddy-support/212279-random-bot-thread.html
 
Back
Top