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

R-Rift - rrrix's BETA Rifts

Ya same for me im jsut spending my g key why?

i need to open portal manualy
 
Oddly enough this seemed to be working fine for me just lastnight. I even restarted DB completely and same deal
Enters GR
when I Die
Exits game
Re-enters game
Re-opens GR using another key


He doesnt res himself...
 
May i ask if someone have the same problem as me? or can help me? that use this bot alot, is there some kind of option to sign so it will open rifts alone :P
 
People getting logged out after,
Have you double checked under DB>Settings>Bot>Death Handling?
Or
Code:
-Uninstall DB
-DELETE DB folder
-Install New DB then update
-COPY a NEW Version of the plugins (DO NOT USE OLD plugin folders)
 
People getting logged out after,
Have you double checked under DB>Settings>Bot>Death Handling?
Or
Code:
-Uninstall DB
-DELETE DB folder
-Install New DB then update
-COPY a NEW Version of the plugins (DO NOT USE OLD plugin folders)

i do all this thing and i got the same probleme -_-
 
i do all this thing and i got the same probleme -_-
Post your log and hope that someone can help you.
The only recommendation i can give is revert back to an older version that was working for you.
 
All i am getting is Triggering QTOpenRiftWrapper..., it never actually opens a rift and just stands there.
 
at the end of the GRift the bot often stand here and does not loot items on the ground, if I monitor it and click on any loot on the ground it unstuck but if I leave it alone it remaines blocked and not any move until disconnected for 30mn+ AFK...Any idea ?
 
I have been using your bot for some time and I have never had any problems nor complaints. But since the new greater rifts I have one probleem. I am playing as a wizard and for some reason my character will only use normal attacks instead of the blizzard and black hole? I have searched the forums but couldn't find any useful information. Do any of you know how to fix this problem?
I also have same issue. I tried to test in every possible skills, only that black hole and meteor has never been fired. Dose anyone know how to fix this issue?
 
Ok so i enabled disable trial rift at lvl 4 and it continued to attack until i died. Any Idea how to fix this?

[QuestTools][RiftTrial] Starting Wave: 4
[QuestTools][RiftTrial] Reached Wave 4 Disabling Combat
Forced townrun initiated! Reason:Abort Trial
[Trinity] Looks like we are being asked to force a town-run by a profile/plugin/new DB feature, now doing so.
Using town portal
[QuestTools][RiftTrial] Starting Wave: 5
Using town portal
[QuestTools][RiftTrial] Starting Wave: 6
Using town portal
[QuestTools][RiftTrial] Starting Wave: 7
 
seems like this newer bot is broken. things use to work, now they are hit n miss.
i too have issues with latest bot and trinity.
i use older version of both and it works awsome for key runs/rifts/bounties
i can get the latest bot to run GR but always gets to ketstone lvl 38-40 and completely gets owned.
i too cant seem to figure out how to get it to leave at like wave 5-6 so it can actually handle the GR its about to make.
maybe people that have luck with getting this to run should not only post profile but what DB version ect they are using with what modifications.
 
All profiles work fine, but the R-rift stucks in the storage. Tell pls how to fix it =)
 
I hate to add to the rabble of people having issues..but, When I'm setting it to doing trials, it either just stands there till time runs out or it fights for like 1 wave then just stands there =S.

Sorry for adding to the issues.
 
Hi all. My question is - i put in rift setup - do not fight after 20wave in trial rift, but he fight and sometime make 28-32+ g rift keys but i just won't 18-22 keystones, does anyone know how to fix it ?
 
Last edited:
Hi all. My question is - i put in rift setup - do not fight after 20wave in trial rift, but he fight and sometime make 28-32+ g rift keys but i just won't 18-22 keystones, does anyone know how to fix it ?

... Wave number is the ACTUAL wave number, not the one shown in Diablo... but the one in DB's log window.
 
Back
Top