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

R-Rift - rrrix's BETA Rifts

My crusader does not use Heaven's Fury in Rift Trials. Any idea why? He uses it in regular and G rifts just fine.
 
williewill said:
Doing trials over and over no matter what i set in questtools. Help please
Click to expand...
I had that problem the first time as well, I had to redo the settings in QuestTools to get it to work the first time. Just make sure Greater is above Trial in the priority, it seems sometimes the setting undoes itself but a quick flip back and it works like a charm.
 
In MoveToActor.cs:

.Where(o => Position.Distance(Position) <= MaxSearchDistance)

probably should be:

.Where(o => Position.Distance(o.Position) <= MaxSearchDistance)
 
Is the rift trial phase a DB plugin thing or a profile thing? Cause I checked the box in the quest tools options to stop combat at level 25, yet it goes until it dies and time runs out. Any way to fix this or did I miss something?
 
Also in MoveToActor.cs:

.Where(i => i.IsValid && i.CommonData.IsValid && i.ActorSNO == ActorId)

replace with:

.Where(i => i.IsValid && i.CommonData != null && i.CommonData.IsValid && i.ActorSNO == ActorId)

This fixed NPE for me.
 
cfalls said:
Anyone know how to fix this

Exception during bot tick.Buddy.Coroutines.CoroutineUnhandledException: Exception was thrown by coroutine ---> System.NullReferenceException: Object reference not set to an instance of an object.
at QuestTools.ProfileTags.Movement.MoveToActor.<get_Actor>b__5(DiaObject i)
at System.Linq.Enumerable.WhereEnumerableIterator`1.MoveNext()
at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
at QuestTools.ProfileTags.Movement.MoveToActor.get_Actor()
at QuestTools.ProfileTags.Movement.MoveToActor.get_TargetIsDungeonStone()
at QuestTools.ProfileTags.Movement.MoveToActor.<MainCoroutine>d__1.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.ActionRunCoroutine....()
--- End of inner exception stack trace ---
at Buddy.Coroutines.Coroutine.CheckPostConditions(Boolean shouldBeCanceled)
at Buddy.Coroutines.Coroutine.Resume(Boolean forStop)
at Buddy.Coroutines.Coroutine.Resume()
at Zeta.Bot.ActionRunCoroutine.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.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.()
Click to expand...

on top of this i cant pick up greater rift keys bot just sits there and doesnt pick it up, anyone know why?
 
Ledge said:
Also in MoveToActor.cs:

.Where(i => i.IsValid && i.CommonData.IsValid && i.ActorSNO == ActorId)

replace with:

.Where(i => i.IsValid && i.CommonData != null && i.CommonData.IsValid && i.ActorSNO == ActorId)

This fixed NPE for me.
Click to expand...


was this meant for me, if so where is the movetoactor.cs file?
 
Ledge said:
Plugins\QuestTools\ProfileTags\Movement\MoveToActor.cs
Click to expand...


unfortunately that did nothing for me, my char still put the keystone in the pillar and then just sits there, this is extremely frustrating :(
 
So after some more testing and watching, here is some issues I've found. Maybe it's how I have it setup or just how it is right now, so feel free to correct me.

1) It doesn't repair in town between games, this can make your bot require an unnecessary repair in the middle of a grift which can make a pointless loss.

2) As a monk, with a complete fresh install, during the trial is goes full-retard. It hardly ever leaves the dead center so the long range mobs just sit around in a circle 'out of range' and either kill you eventually or the timer runs out. It's able to do up to about tier 25 by leveling the keystone, but during the trial is lucky to even pull a 10 starting stone.

3) Sometimes it misses the little purple orbs from an elite kill, the things that add a lot of mob kill % to your timer.

Just for some added info, I am using the popular standard build that most high-rank monks are using. Holy/Attack Speed using Way of the Hundred Fists, Epiphany, and Sweeping Wind.

Edit: Figured out the reason I was having issue 2 was because trash pack size, setting it to 1 gets me to tier 20 right away.
 
Last edited:
Eventine said:
I'm getting this error when it finishes a rift and is trying to upgrade the gem

Exception during bot tick.Buddy.Coroutines.CoroutineUnhandledException: Exception was thrown by coroutine ---> System.NullReferenceException: Object reference not set to an instance of an object.
at QuestTools.ProfileTags.Movement.MoveToActor.<get_Actor>b__5(DiaObject i)
at System.Linq.Enumerable.WhereEnumerableIterator`1.MoveNext()
at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
at QuestTools.ProfileTags.Movement.MoveToActor.get_Actor()
at QuestTools.ProfileTags.Movement.MoveToActor.get_TargetIsDungeonStone()
at QuestTools.ProfileTags.Movement.MoveToActor.<MainCoroutine>d__1.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.ActionRunCoroutine....()
--- End of inner exception stack trace ---
at Buddy.Coroutines.Coroutine.CheckPostConditions(Boolean shouldBeCanceled)
at Buddy.Coroutines.Coroutine.Resume(Boolean forStop)
at Buddy.Coroutines.Coroutine.Resume()
at Zeta.Bot.ActionRunCoroutine.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.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.()

Is this a boon of the hoarder problem?
Also lowest grift first doens't seem to work
Click to expand...

Still getting this error, i started completely over, installed new DB, newest trinity/questtools profile all the works and left default settings all the same and still get this error
 
cfalls said:
so unbelievably frustrating since update to newest trinity i cant even bot.
Click to expand...
Now I'm just botting for keys. got stuck on talking to orek everytime. and during trials, the bot cant click the portal. So a lot of problems after update.
 
NoWayLol said:
So after some more testing and watching, here is some issues I've found. Maybe it's how I have it setup or just how it is right now, so feel free to correct me.

1) It doesn't repair in town between games, this can make your bot require an unnecessary repair in the middle of a grift which can make a pointless loss.

2) As a monk, with a complete fresh install, during the trial is goes full-retard. It hardly ever leaves the dead center so the long range mobs just sit around in a circle 'out of range' and either kill you eventually or the timer runs out. It's able to do up to about tier 25 by leveling the keystone, but during the trial is lucky to even pull a 10 starting stone.

3) Sometimes it misses the little purple orbs from an elite kill, the things that add a lot of mob kill % to your timer.

Just for some added info, I am using the popular standard build that most high-rank monks are using. Holy/Attack Speed using Way of the Hundred Fists, Epiphany, and Sweeping Wind.

Edit: Figured out the reason I was having issue 2 was because trash pack size, setting it to 1 gets me to tier 20 right away.
Click to expand...

Where is this Quest Tools config everyone is talking about?
 
Awesome update on plugin, it makes things easier to configure.

I have everything as a new install, but for some reason the QT setting to use the Lowest GR key is not working.
Anyone else having this problem?
 
Winchester said:
Awesome update on plugin, it makes things easier to configure.

I have everything as a new install, but for some reason the QT setting to use the Lowest GR key is not working.
Anyone else having this problem?
Click to expand...

I don't think most people are even able to bot right now, we get errors.
 
Just ran into another problem, sometime my char wont pick up legionaries anyone know why this is?
 
Winchester said:
Awesome update on plugin, it makes things easier to configure.

I have everything as a new install, but for some reason the QT setting to use the Lowest GR key is not working.
Anyone else having this problem?
Click to expand...

Yes. It is using higher keys, even though I set it to use the lowest keys first.
 
You must log in or register to reply here.
Back
Top