Is there some way to tell the bot (or some plugin/profile that has the function) "do enough trial waves to get a rift tier X-Y"? My bot is so good at the trial, that it gets a rift level so high it cannot finish it without dying a LOT. It's extremelyyyyyy inefficient... Any help appreciated. Thanks.
Check Funky Riftbor or R-Rift profiles - there are suggestions on how to fix it. Note: Make sure to read through previous pages, the answer is there.
The answer is definitely *not* there. There is no fix yet from what I can find, and believe me, I've looked. The best option right now is to just run the trials yourself if you want a specific tier.
guys you can do it in questtools (newest versions) just needs some figuring out if you are dh with sentries (your character stops fighting but sentries finish couple more waves)
If you say so brother. Just so you know, only a handful are complaining about it now compared before. Good luck!
yah depends on your gear, change the wave combat disable. my dh well geared so i stop putting sentries at wave four takes me to lvl 33 ish rifts.
I am using Funky bot but the bot exit the game if he dies once or it finishes not even half way. do you have any idea what is causing this? RRix rift doesn't work, I love rrix but something wrong with his rift profile or I didn't set up right
There is no string AFAIK with funkybot, i have WD dying a lot with some mobs, but it doesnt leave. Have you checked DB>Setting>Bot>Death Handling>Ignore. Coz update might have caused it to change.
I'm using R-rift's profile along with the new Questtools with options for greater rifts and it works great for me. The only hiccup was realizing that the stop trial at certain level actually meant wave. It would be nice if I could set it to do a trial, then greater rift, and repeat... since I have about 800 trial keys - but you can't have everything . I'll just let it go for a few hours on trials and then switch to Grifts.
Its confusing i agree; i searched the UIMap and couldn't find any way to access the actual wave level, and progress varies based on how fast you kill each wave. There is a new version of the trial aborting behavior in the unreleased QT on GIT if you'd like to help test that it works.
Yeah I would be interested in trying it out. Right now it works fairly well, but there is still quite a delay between the bot realizing it needs to cancel and return it town and actually casting the TP. It's usually a 2 round delay to be quite honest, which isn't the end of the world. I usually just let the bot run for a few hour @ trials, and I end up with an inventory of keystones ranging from say 27-37.
