Greater Rift Trial - Ignores Max Wave

[Xenetron]

Hi,

Anyone else having this issue?

Using DBeta .507 and Rrrix's latest Grift profile

Bot ignores the max wave and just continues fighting until it dies or can't complete the wave in time, resulting in alot higher grift keys than you ideally want

 

[Arotished]

The wave setting in QuestTool is not Gift Lvl but ithe trial wave Lvl. Start with 3 and see what key you get, increase if its to low. ect

 

[Oggy2k5]

Aim for around 6-8, you'll be between 28-35 grift

 

[Xenetron]

I am aware of this, I have it set on 6, it says Disabling Combat but continues to fight

tried questtools 3.1 & 3.1.7

 

[Xenetron]

[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

 

[rookiebot]

The wave setting in QuestTool is not Gift Lvl but ithe trial wave Lvl. Start with 3 and see what key you get, increase if its to low. ect

I never could get this thing to work, till I try what you said, I put it on 5 and it runs to the side of the trials map at around 15-18. It probably varies depending on how well built your character is but to anyone else I would try what arot has suggested to find what the range you want.

 

[nex1025]

So I think some people maybe confused as I was when I first started to get this to work. Stop on wave X does not mean the rank of the rift given after you smash that first group of mobs in the trial. "WAVES" meaning first group of mobs Wave 1...second group Wave 2...etc. So if you want the bot to stop after the third wave of mobs then pick wave 3 which leads to a much lower rift level.

If you did what I did to start and thought that your guy could roll a level 20 rift and picked stop on wave 20....then you're gonna have a bad time.

 

[Espial]

Confirmed to continue running with monk class. set to 1, 2, 3, and 5. None stop. My guy gets to wave 6 atm every time.
edit: quest tools 3.3.1 and trinity 2.4.1

 

[Shinyknight]

The check box appears to be broken. Enable it, select your wave, then DISABLE it, and it should work (going by whatever wave you selected).

Read: It's backwards at the moment, and doing that has been working for me.

 

[Espial]

The check box appears to be broken. Enable it, select your wave, then DISABLE it, and it should work (going by whatever wave you selected).

Read: It's backwards at the moment, and doing that has been working for me.

haha thats funny. I'll try that, thanks for the input!
edit : did not work. Problem still exists.