I am confused, which version should I use if I want it to explore as much as possible even if the rift boss is already killed?
i would guess that full clears all levels and explore maybe just the one your one after the boss is deadI am confused, which version should I use if I want it to explore as much as possible even if the rift boss is already killed?
Yeah i was saying it didn't do that anymore. But some rifts it still get's confused as to where to go. Keeps backtracking indeed, but eventually it will continue.Running 0.0.8 plugin, .24 trinity, and newest beta.
Running amazing! Except i wish it didn't still have the re-exploring issue, Been doubling back on the same rift for quite some time. =\
FInally it leaves the game and makes a new one. But still =\
Updated svn, trying again!![]()
[Trinity][Performance] Execution of the block HandleTarget took 1401.15ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1119.24ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1136.28ms.
[Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1136.64ms.
@benihana1212
updated 5min ago and they are all there (ezupdater)
db folder \Profiles\Rift Bot
Having the same problem. But it's been there for a while. It's a trinity problem not the profile. Some rifts still spam red errors, were going to have to be patient and wait for rrix to do his thing.Am I the only one lagging a bit while using this profile? I'm using the recommended versions, svn updated, etc.
This is what appears in red on DB:
Code:[Trinity][Performance] Execution of the block HandleTarget took 1401.15ms. [Trinity][Performance] Execution of the block RefreshDiaObjectCache.AvoidanceCheck took 1119.24ms. [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1136.28ms. [Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1136.64ms.
Sometimes it goes up to 5000ms.
Having the same problem. But it's been there for a while. It's a trinity problem not the profile. Some rifts still spam red errors, were going to have to be patient and wait for rrix to do his thing.
Stuck. Bot was trying to attack the elite while they were not reachable.
View attachment 126305
Sorry that I forgot to capture the log
lol thanks, i was looking all through trinitys forums and didnt even think to check hereHave you checked the first page of this thread?