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

R-Rift - rrrix's BETA Rifts

erxxlu said:
Use QuestTools Settings to configure the Grift Level.
Click to expand...
Is that the option for "Open Greater Rifts at Level..." option? I see it's defaulted to 999. Does that mean it always opens the highest possible GRift level?
 
I'm facing very weird backtracking with the new db, have no idea what caused it.
 
Heya... thx for the link. Can you tell me how im suppose to go about using it? I've only used SVN checkout thus far and don't know what to do with that link. much appreciated.
 
jarl8 said:
I'm facing very weird backtracking with the new db, have no idea what caused it.
Click to expand...

Force Route to one of the bottom 2 options. But it will still sometimes Mis the exit like it just out of range. This will also make the bot backtrack to areas un explored
 
I too am facing this back tracking issue. It will kill a mob, then run back to the beginning of the rift, then go and kill another and run back. It's preventing me from meeting the time requirements for higher level great rifts.
 
is anyone having the issue where it just finishes the first rift, goes to town to stash and then just sits there, doesnt go talk to orek to start a new rift or aything.
 
I am often stuck with below messaging in DB.
Hero just running back and forward and do nothing.

[QuestTools][GridRoute] Generated new Weighted Nearest Minimap Visited Route with 20 nodes in 21ms


Is there a solution of that promlem?

Thanks
 
Got the exact same problem and the characters keeps heading back to the start and comes back loosing a lot of time :(
 
Baresark said:
This is working great for me. Been running it since DB came back up. My Adventure one wasn't working and only really wanted to run rifts anyway. I'm at work and occasionally remote into my home computer to check it out, hasn't stopped yet. Never gets stuck or freezes.
Click to expand...

does the bot ever run back to the start of the rift level using rrix? i use to have that problem alot using rrix back in season 3 etc, especially the narrow paths or some specific rift levels. I wonder if the nav server fixed it or something. but the new adventuer .90 update is running rifts in record speed, and exploring them better than rrix profile ever could. I've been using rrix since the beginning too. Let me know next time your watching your bot lol
 
ridz89 said:
does the bot ever run back to the start of the rift level using rrix? i use to have that problem alot using rrix back in season 3 etc, especially the narrow paths or some specific rift levels. I wonder if the nav server fixed it or something. but the new adventuer .90 update is running rifts in record speed, and exploring them better than rrix profile ever could. I've been using rrix since the beginning too. Let me know next time your watching your bot lol
Click to expand...

This one does not get stuck for me. I was using the previous adventure one and it was running back to the beginning all the time. I started using this one and haven't had an issue with it. I haven't tried version 90 of Adventure.
 
Baresark said:
This one does not get stuck for me. I was using the previous adventure one and it was running back to the beginning all the time. I started using this one and haven't had an issue with it. I haven't tried version 90 of Adventure.
Click to expand...

No sooner than I typed the above, I started running into the issue where it runs back to the start. This is what is displayed on the log:

[QuestTools][ExploreDungeonTag] ExploreDungeon Started
[QuestTools][ExploreDungeonTag] Visited all nodes but objective not complete, forcing grid reset!
[QuestTools][ExploreDungeonTag] Visited all nodes but objective not complete, forcing grid reset!
[QuestTools][ExploreDungeonTag] Visited all nodes but objective not complete, forcing grid reset!
[QuestTools][ExploreDungeonTag] Visited all nodes but objective not complete, forcing grid reset!

Even if I change it to go back to the nearest unvisited, it constantly does a grid reset.
 
Baresark said:
No sooner than I typed the above, I started running into the issue where it runs back to the start. This is what is displayed on the log:

[QuestTools][ExploreDungeonTag] ExploreDungeon Started
[QuestTools][ExploreDungeonTag] Visited all nodes but objective not complete, forcing grid reset!
[QuestTools][ExploreDungeonTag] Visited all nodes but objective not complete, forcing grid reset!
[QuestTools][ExploreDungeonTag] Visited all nodes but objective not complete, forcing grid reset!
[QuestTools][ExploreDungeonTag] Visited all nodes but objective not complete, forcing grid reset!

Even if I change it to go back to the nearest unvisited, it constantly does a grid reset.
Click to expand...

Could happen to any plugin :)

Have you tried forcing QT to use the Default Route Mode?
 
TarasBulba said:
Could happen to any plugin :)

Have you tried forcing QT to use the Default Route Mode?
Click to expand...

I started there. Then tried switching it to anything else. I just switched back to your profile. The new update works really nice. Thanks for all of your work.
 
Baresark said:
I started there. Then tried switching it to anything else. I just switched back to your profile. The new update works really nice. Thanks for all of your work.
Click to expand...

Glad you liked it, thank you too :)
 
TarasBulba said:
Could happen to any plugin :)

Have you tried forcing QT to use the Default Route Mode?
Click to expand...

TB the problem here is that it's the same with one you recently fixed with adventurer. It gets so close to the end of the rift and the door then turns around it misses the exit. Do you mind fixing?
 
SIL3NT-DE4TH said:
TB the problem here is that it's the same with one you recently fixed with adventurer. It gets so close to the end of the rift and the door then turns around it misses the exit. Do you mind fixing?
Click to expand...

Adventurer uses a completely different exploration grid than QT's, I don't think it's fixable without a major rewrite, finding the problematic levelareaIds and lowering the boxsizes/boxtolerances for these levelareaIds would help but in cost of performance.
 
You must log in or register to reply here.
Back
Top