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

R-Rift - rrrix's BETA Rifts

Suddenly after running for some hours my game is closed down due to inactivity.

I check the logs and I see this:

09:48:43.933 DEBUG Logger [QuestTools][ExploreDungeonTag] ExploreDungeon ResetCachedDone()
09:48:43.934 DEBUG ProfileOrderManager Resetting current behavior.
09:48:43.934 DEBUG InactivityDetector [GameEvents.OnGameJoined] Resetting inactivity detector
09:48:43.934 DEBUG BrainBehavior [GameEvents.OnGameJoined] Clearing actors
09:48:43.949 DEBUG DungeonExplorer [GameEvents.OnGameJoined] Reseting dungeon explorer
09:48:43.949 DEBUG GridSegmentation ========== Grid segmentation resetting!!! ============
09:48:43.950 DEBUG GridSegmentation ========== Grid segmentation resetting!!! ============
09:48:43.978 INFO Logger [QuestTools][GridRoute] Generated new Weighted Nearest Minimap Visited Route with 35 nodes in 13ms
09:48:43.981 DEBUG DefaultNavigationProvider Generating path to a3dun_Crater_ST_Chest 34 yds Elite=False LoS=False HP=-1,00 Dir=W - <600, 820, -59.29417>
09:48:44.064 DEBUG DefaultNavigationProvider Successfully generated path from {X=197,Y=91} to {X=184,Y=96} in 00:00:00.0813309 with 15(5) hops
09:48:44.073 DEBUG DefaultNavigationProvider Client path generated.
09:48:44.073 DEBUG DefaultNavigationProvider Generated path to <600, 820, -59.29417> (a3dun_Crater_ST_Chest 34 yds Elite=False LoS=False HP=-1,00 Dir=W) with 5 hops.
09:49:01.782 ERROR Logger [Trinity] Error in HandleTarget: Only part of a ReadProcessMemory or WriteProcessMemory request was completed, at addr: 00000000, Size: 416
10:19:02.511 ERROR Logger [Trinity] Hero is invalid!
10:19:02.514 ERROR Logger [Trinity] Error in HandleTarget: Only part of a ReadProcessMemory or WriteProcessMemory request was completed, at addr: 00000000, Size: 416
10:19:02.521 ERROR Logger [Trinity] Hero is invalid!
10:19:02.522 ERROR Logger [Trinity] Error in HandleTarget: Only part of a ReadProcessMemory or WriteProcessMemory request was completed, at addr: 00000000, Size: 416
10:19:02.623 ERROR Logger [Trinity] Hero is invalid!
10:19:02.624 ERROR Logger [Trinity] Error in HandleTarget: Only part of a ReadProcessMemory or WriteProcessMemory request was completed, at addr: 00000000, Size: 416

What does it mean?
 
not sure if its trinity or this profile but does anyone else see it acting really retarded sometimes?.. like running back and forth in the same spot for 20-30 seconds? or if I have it set to trash mobs 4+ and the group has like 6-7atleast it doesn't attack them and just stands there til my followers kill them


this doesn't happen everytime only some times and it wastes valued seconds in G rifts
 
Last edited:
emerysong said:
not sure if its trinity or this profile but does anyone else see it acting really retarded sometimes?.. like running back and forth in the same spot for 20-30 seconds? or if I have it set to trash mobs 4+ and the group has like 6-7atleast it doesn't attack them and just stands there til my followers kill them


this doesn't happen everytime only some times and it wastes valued seconds in G rifts
Click to expand...

im also expieriencing derping of the bot on this profile - though not so often tbh :)
 
A few fixes.

Those who are having problems, make sure you're running Quest tools 3.3.1, any newer versions will bug out when trying to stop at certain waves. Also, disallow EZUpdater from updating it any further, as that will also cause problems.

If you're having problems running normal rifts, and are only running trials/GRifts, make sure Normal is set highest priority within the list, and you've not simply highlighted it, you've got to actually move it to the above section of the list.

The bot does act strangely at times, but that is what bots do, they're not humans, and cannot replicate what you'd do 100% of the time, set your trash count to 3 and be happy that it works.

Learn how to read and type Custom loot rules, there are a few you can choose from, but they're important if you running for long periods of time, it'll sort out quality legends compared to just junk/trash ones.

Those who are overshooting Trials and end up in a too high of a Grift.. Make sure you're more toughness based than damage, the bot will likely die more than a human, and giving it a chance to survive is far more important than trying to deal more damage. With QT 3.3.1 you'll more than likely be able to cap your GRift wave, however if not, run quite a few trials, and remove any Grifts that are too high, and start from the lowest. Providing quite a few hours of 30-35Grifts.

What I do

Runs Trials in DPS based gear, ranging from 33-43 GRift Keys. Switch gems and gear to obtain higher Toughness, and begin running GRifts from lower levels upwards. You can choose whether you want to upgrade gems, or GRift keys.

I will run from a 43 GRIFT key, I can survive, but it may not be able to upgrade the key, which then will upgrade the gems I use. It'll then use a 42 GRift key, if I finish it in time, I'll rerun a 43, if not, It'll upgrade Gems. This way, you'll get many more games from your one GRift key, specially at lower levels, as it'll continue to level 35 gems to level 40+ gems, meaning that I get 1-5 more runs out of just one GRIFT.
 
Last edited:
Oggy2k5 said:
A few fixes.

Those who are having problems, make sure you're running Quest tools 3.3.1, any newer versions will bug out when trying to stop at certain waves. Also, disallow EZUpdater from updating it any further, as that will also cause problems.

If you're having problems running normal rifts, and are only running trials/GRifts, make sure Normal is set highest priority within the list, and you've not simply highlighted it, you've got to actually move it to the above section of the list.

The bot does act strangely at times, but that is what bots do, they're not humans, and cannot replicate what you'd do 100% of the time, set your trash count to 3 and be happy that it works.

Learn how to read and type Custom loot rules, there are a few you can choose from, but they're important if you running for long periods of time, it'll sort out quality legends compared to just junk/trash ones.

Those who are overshooting Trials and end up in a too high of a Grift.. Make sure you're more toughness based than damage, the bot will likely die more than a human, and giving it a chance to survive is far more important than trying to deal more damage. With QT 3.3.1 you'll more than likely be able to cap your GRift wave, however if not, run quite a few trials, and remove any Grifts that are too high, and start from the lowest. Providing quite a few hours of 30-35Grifts.

What I do

Runs Trials in DPS based gear, ranging from 33-43 GRift Keys. Switch gems and gear to obtain higher Toughness, and begin running GRifts from lower levels upwards. You can choose whether you want to upgrade gems, or GRift keys.

I will run from a 43 GRIFT key, I can survive, but it may not be able to upgrade the key, which then will upgrade the gems I use. It'll then use a 42 GRift key, if I finish it in time, I'll rerun a 43, if not, It'll upgrade Gems. This way, you'll get many more games from your one GRift key, specially at lower levels, as it'll continue to level 35 gems to level 40+ gems, meaning that I get 1-5 more runs out of just one GRIFT.
Click to expand...

Is the same version i'm using with quest tools but it still overkills :(
 
I am running quest tools 3.3.1
yet I still see it do rere stuff a lot around doorways and other things. like double checking areas already cleared. what you guy have set for your explore route? if enabled at all


Attached to Diablo III with pid: 3792
Flashing window
[Armory] v1.2.29 Initialized
[GearSwapReloaded] 1.0.4.3 Initialized
[Trinity] Initialized v2.4.2
[Armory] v1.2.29 Enabled
[QuestTools][Plugin] v3.3.1 Enabled
 
Unvisited Weighted Minimap, I believe that would be most efficient, as it'll only run off a short distance, I did have it Unvisited Weighted Map, but it would generally run riot to all corners of the map.

It often does rere stuff, it is a bot, not a human, and can become problematic at times. When it overkills, it is often forced to fight back, but i agree, it does overkill sometimes, that is why I run 30-50 trials so I can take out any "difficult" ones.
 
not sure if its trinity or this profile but my charge barb will charge through molten explosion or w/e when you kill a enemy and it will die any way to have it not do that while still fighting mobs in AoE?

I may be targeting mobs on top of it but sometimes its targeting things on the other side and the timing is just wrong and it explodes while im going over it

also anyway to have it not auto swing with charge on CD cause I have no primary and it just stacks on boss while its on CD and its stupid. it should kite til off CD and then ram through the boss rinse repeat.

TY for any response and just know im very happy with how its working on all toons "other then few things"
 
Last edited:
I remember RRRIX said, never run without a primary attack. Can't make loads of different "techniques" got to use what you've got.
 
[HIDE]Hm, when my WD runs greater rifts, it doesn't attack. It just dodges all the monsters and runs to the exit to the next level. Anything fundamental I missed? Bounties and regular rifts works just fine.[/HIDE]

Never mind, I seemsed to have an old version, downloaded latest from svn and it works fine.
 
Last edited:
Hi, I'm getting errors especially when my character tries to STASH ITEMS,

it goes something like this "[QuestTools][<GetItemFromStashRoutine>d__16] Already have x items in our backpack"

Is it a conflict with Quest Tool or Trinity?

thanks
 
SO for anyone who wants a Rift Profile that will not only kill the RG but also finish every level after that...Follow these instructions.

Google EZUpdater for Demonbuddy

Find and download the plugin, put the plugin into your plugins folder of Demonbuddy.

Copy SharpSVN.dll from the EZUpdater folder into the native Demonbuddy folder to get EZUpdater to work.

Open the pluing up in Demonbuddy and check off all of Rrrix profiles, then click check for updates.

EZUpdater will update the files you selected to update and you will have to restart Demonbuddy.

Click on load profile and you will now see you have more profiles to choose from in your profiles folder in demonbuddy.

Load Riftbot Full Explore and enjoy!!
 
Is it possible to config it so it does the WHOLE rift, and not ending it after the boss is killed? :)

Nevermind me, the above post sorted it all out + bunch of extra things! :) Much love to all!
 
Last edited:
[QuestTools][<GetItemFromStashRoutine>d__16] Already have 71 items in our backpack (GameBalanceId=0 ActorSNO=323722 GreaterRiftKey=False)
Triggering QTOpenRiftWrapper...
[QuestTools][QTOpenRiftWrapperTag] Using Normal Rift Keystone to open the Rift Portal
[QuestTools][TownRunTag] TrinityTownRun, freeBagSlots=60 minDurabilityPercent=100
[QuestTools][<TownRun>d__3] Town-run request received, will town-run at next possible moment.
[QuestTools][<GetItemFromStashRoutine>d__16] Opening Stash
[QuestTools][<GetItemFromStashRoutine>d__16] Unable to find item in stash with ActorSNO 408416

This gets spammed a LOT in the bot window after the rift is closed and it's looking for trial keys, I think?
 
usually don´t comment, but this is a great profile, not got stuck in 2 hours and quite efficient aswell!
 
Hey! Thanks a lot for the profiles, all your work is great.

But the "Trial Rifts: Disable combat at wave..." feature isn't working for me. I got it working for level 1 rifts, but I've tried level 10, 15, 20, 25, 30, and it always keeps going until it dies. So I always end up in level 40'ish rifts, which the bot can't solo without dying 30 times.. :/
 
zhadowmarkuz said:
Hey! Thanks a lot for the profiles, all your work is great.

But the "Trial Rifts: Disable combat at wave..." feature isn't working for me. I got it working for level 1 rifts, but I've tried level 10, 15, 20, 25, 30, and it always keeps going until it dies. So I always end up in level 40'ish rifts, which the bot can't solo without dying 30 times.. :/
Click to expand...

Quest Tools is currently bugged and tends to do that, and you're using it incorrectly. They're the wave numbers, try and stop around wave 7.
 
Oggy2k5 said:
Quest Tools is currently bugged and tends to do that, and you're using it incorrectly. They're the wave numbers, try and stop around wave 7.
Click to expand...


So I have my set to wave 7 and ya same thing keeps going but I was able to fine tune my character to kinda make him not able to finish past a certain wave but if anyone knows how to make this wave thing actually work in quest tools that would be amazing. He could be much more efficient.
 
You must log in or register to reply here.
Back
Top