Great profile. Tested it 2 nights in a row with 3 accounts. Getting about 3-5 legs / hour on t3. 0 deaths which is amazing. One thing. I do understand that DB doesn't recognize blood shards. But is it possible to make DB ignore them? That's the only thing that can stop the bot atm (I do have the gold inactivity set to 240, maybe i should just put it to like 100-150?)
Bot opens rift, enter rift and to back to town instant after enter rift. Whats the problem? Doesnt kill anything in rift and just waiting at town
need to prioritize bloodshard and legdrop. Just seen situation with profile, when bot killed Rift boss, then went to clear out mobs around him and then forgot to go back and pickup loot. Don't know if this is trinity problem or Rifter.
Been running this the past couple of days with great success. However last night it got stuck trying to pick up blood shards when I was capped. Is there a way to prevent that?
Theres something broken about your new extended profile. I keep finding the bot in town with the rift incomplete trying to talk to orek...really frustrating
Working pretty well so far. The pathing in Ethereal Descent I is really bad, could not find next level . Will keep you up to date when i stumble upon anything. Also ! Thanks for your work and the community around it ! EDIT : I believe this is the ID of the map (might help ?) : <TrinityExploreDungeon questId="312429" stepId="2" until="ExitFound" exitNameHash="0" actorId="0" pathPrecision="25" boxSize="25" boxTolerance="0.01" objectDistance="45"> and a screenshot Fyi manually found exit
the problem with mine is I use a TR monk and it leaves the rift guardian behind sometimes causing them not to fight :|
no idea why mine is not working Trinity] Active bounty returned null, Assuming done. [Trinity] Bounty is done. Tag Finished. [Trinity] Clicking UI element Conversation Button (152637440) [Trinity] Clicking UI element Conversation Button (152637440) [Trinity] Clicking UI element Conversation Button (152637440) [Trinity] Clicking UI element Conversation Button (152637440) Exception when terminating bot thread. System.Exception: Only part of a ReadProcessMemory or WriteProcessMemory request was completed, at addr: 00000198, 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 QuestTools.MoveToActor.WithinInteractRange() at QuestTools.MoveToActor.<CreateBehavior>b__30(Object ret) at Zeta.TreeSharp.Decorator.CanRun(Object context) at Zeta.TreeSharp.Decorator..() at Zeta.TreeSharp.Composite.Tick(Object context) at Zeta.TreeSharp.Wait..() at Zeta.TreeSharp.Composite.Tick(Object context) at Zeta.TreeSharp.PrioritySelector..() at Zeta.TreeSharp.Composite.Tick(Object context) at Zeta.TreeSharp.Sequence..() at Zeta.TreeSharp.Composite.Tick(Object context) at Zeta.TreeSharp.PrioritySelector..() at Zeta.TreeSharp.Composite.Tick(Object context) at Zeta.TreeSharp.PrioritySelector..() at Zeta.TreeSharp.Composite.Tick(Object context) at Zeta.Common.HookExecutor.Run(Object context) at Zeta.TreeSharp.Action.RunAction(Object context) at Zeta.TreeSharp.Action..() at Zeta.TreeSharp.Composite.Tick(Object context) at Zeta.TreeSharp.PrioritySelector..() at Zeta.TreeSharp.Composite.Tick(Object context) at Zeta.TreeSharp.PrioritySelector..() at Zeta.TreeSharp.Composite.Tick(Object context) at Zeta.Common.HookExecutor.Run(Object context) at Zeta.TreeSharp.Action.RunAction(Object context) at Zeta.TreeSharp.Action..() at Zeta.TreeSharp.Composite.Tick(Object context) at Zeta.TreeSharp.PrioritySelector..() at Zeta.TreeSharp.Composite.Tick(Object context) at Zeta.Bot.BotMain.()
For the most part, it does it's job. Kills monster. That's all we need for legs, the other 1% of the time is if boss spawns behind him or he back track loops or he reaches the end without ever completing enough for boss to spawn.
So used the extended version and bot thought he was done and had cleared the area before rift boss spawned...
Bot gets stuck a lot. Mostly it gets stuck on completely nothing. Nothing is in it's way. Just running back and forth on random places.