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

Grift Trial - Monk continues fighting despite Wave 7 disable combat

Xenetron

Member
Joined
Mar 5, 2013
Messages
627
Reaction score
4
[QuestTools][RiftTrial] Reached Wave 7 Disabling Combat
[QuestTools][QuestTools] System.NullReferenceException: Object reference not set to an instance of an object.
at QuestTools.Helpers.RiftTrial.SetCombatAllowed(Bool ean allowed) in c:\Users\XXX\Desktop\DB\Plugins\QuestTools\Helpers \RiftTrial.cs:line 114
at QuestTools.Helpers.RiftTrial.PulseRiftTrial() in c:\Users\XXX\Desktop\DB\Plugins\QuestTools\Helpers \RiftTrial.cs:line 78
at QuestTools.QuestTools.Pulse() in c:\Users\XXX\DB\Plugins\QuestTools\QuestTools.cs:l ine 79
[QuestTools][SafeMoveToTag] Initialized questId="312429" stepId="2" x="280" y="278" z="-11" pathPrecision=5 MoveResult=Moved statusText=SafeMoveToTag: IsDone: False, PathPrecision: 5, StraightLinePathing: False, UseNavigator: False, X: 280, Y: 278, Z: -11, Position: <280, 278, -11>, PathPointLimit: 250, Timeout: 180, AllowLongDistance: False, QuestId: 405695, StepId: 1, ObjectiveIndex: -1, QuestName: Quest Id: 630BF, IgnoreReset: False, IsDoneCache: False, Behavior: Zeta.Bot.ActionRunCoroutine,

Continues fighting, monk class

Tried all quest tools from 3 > 3.1.7 and release and beta version, always same shit

Using latest RRRIX profile
 
[QuestTools][RiftTrial] Reached Wave 7 Disabling Combat
[QuestTools][QuestTools] System.NullReferenceException: Object reference not set to an instance of an object.
at QuestTools.Helpers.RiftTrial.SetCombatAllowed(Bool ean allowed) in c:\Users\XXX\Desktop\DB\Plugins\QuestTools\Helpers \RiftTrial.cs:line 114
at QuestTools.Helpers.RiftTrial.PulseRiftTrial() in c:\Users\XXX\Desktop\DB\Plugins\QuestTools\Helpers \RiftTrial.cs:line 78
at QuestTools.QuestTools.Pulse() in c:\Users\XXX\DB\Plugins\QuestTools\QuestTools.cs:l ine 79
[QuestTools][SafeMoveToTag] Initialized questId="312429" stepId="2" x="280" y="278" z="-11" pathPrecision=5 MoveResult=Moved statusText=SafeMoveToTag: IsDone: False, PathPrecision: 5, StraightLinePathing: False, UseNavigator: False, X: 280, Y: 278, Z: -11, Position: <280, 278, -11>, PathPointLimit: 250, Timeout: 180, AllowLongDistance: False, QuestId: 405695, StepId: 1, ObjectiveIndex: -1, QuestName: Quest Id: 630BF, IgnoreReset: False, IsDoneCache: False, Behavior: Zeta.Bot.ActionRunCoroutine,

Continues fighting, monk class

Tried all quest tools from 3 > 3.1.7 and release and beta version, always same shit

Using latest RRRIX profile
I have this problem. Did it get fixed for you?
 
I also have this problem my monk went Yolo mode to like greater rift 40 when i can bearly handle 32 haha
 
It's a problem with QuestTools, and he already knows about it. Everyone is having the same problem atm.
 
Same issue here. I have to reinstall the entire program with all profiles and plugins every time i want to change wave number.
 
Mine works fine stopping at the desired wave but only if im solely doing Trials. First time it does a Greater Rift the next trial it doesnt stop at the desired wave.
 
rixx said it's currently a bug which will be fixed in the next updates i think,
until then you have to do (all) trials first and later then you do Greater Rifts.
To make it work afterwards i restart DB.

EDIT_

Strangely it doesn't happen if i set my max round to 8 (for me 29-33) there the Bot leaves properly.
 
Last edited:
Back
Top