arthurmaple
Member
- Joined
- Aug 12, 2014
- Messages
- 41
- Reaction score
- 2
R-Rift - rrrix's BETA Rifts
- Thread starter rrrix
- Start date
Same, somehow...
people always blame profiles when they can't even make little easy things working.
When i start the profile my monk goes the my chest in hometown and then the log spams:
Triggering QTOpenRiftWrapper...
Triggering QTOpenRiftWrapper...
Triggering QTOpenRiftWrapper...
Triggering QTOpenRiftWrapper...
Triggering QTOpenRiftWrapper...
Triggering QTOpenRiftWrapper...
Triggering QTOpenRiftWrapper...
and on and on and on...
i got my rift keys in my backpack? what am i doing wrong??
Triggering QTOpenRiftWrapper...
Triggering QTOpenRiftWrapper...
Triggering QTOpenRiftWrapper...
Triggering QTOpenRiftWrapper...
Triggering QTOpenRiftWrapper...
Triggering QTOpenRiftWrapper...
Triggering QTOpenRiftWrapper...
and on and on and on...
i got my rift keys in my backpack? what am i doing wrong??
Same here...
where do I start....
Bot misses some of the loot at end of every rift guardian kill (always something different) which can some times be blood shards. If its blood shards bot will sit there till gold inactivity kicks it out of game. Other items like forgotten souls or random legendarys will just be left behind at times like they don't even exist. My settings in trinitys item pickup are setup correctly and had no issues with previous versions.
Bot does not listen to any of the settings I set in questtools in regards to highest trial level to do, start lowest greater rift key I have, requirements to select which gem to upgrade and much more.
Have Keep all 3 rift keys in bag options disabled yet it still withdraws them at end of every run
One in 50~ish runs bot will go full retard and break on either the blood shard vendor or when trying to turn quest in for completing a rift.
I get really bad fps in latest trinity release
Bot fails to enter the rift some times > http://i.imgur.com/gigb8R7.png < and log output just spams Entering rift until gold inactivity kicks in (waste of keys+time)
I don't know why I'm even posting this stuff see all the same issues from other users over the last 10 pages with no response.
Bot misses some of the loot at end of every rift guardian kill (always something different) which can some times be blood shards. If its blood shards bot will sit there till gold inactivity kicks it out of game. Other items like forgotten souls or random legendarys will just be left behind at times like they don't even exist. My settings in trinitys item pickup are setup correctly and had no issues with previous versions.
Bot does not listen to any of the settings I set in questtools in regards to highest trial level to do, start lowest greater rift key I have, requirements to select which gem to upgrade and much more.
Have Keep all 3 rift keys in bag options disabled yet it still withdraws them at end of every run
One in 50~ish runs bot will go full retard and break on either the blood shard vendor or when trying to turn quest in for completing a rift.
I get really bad fps in latest trinity release
Bot fails to enter the rift some times > http://i.imgur.com/gigb8R7.png < and log output just spams Entering rift until gold inactivity kicks in (waste of keys+time)
I don't know why I'm even posting this stuff see all the same issues from other users over the last 10 pages with no response.
Last edited:
From someone who has been using HB and DB for years, you have to give-in an accept that these profiles, plugins, and even the bot itself are essentially in a constant beta stage. I'm still using a DB install from 2-3 releases back and can bot rifts, bounties, keys, etc non stop and fully AFK. I'm missing out on a feature here and there, but it doesn't bug out on me overnight. I avoid all updates until I can confirm that all of my current plugins and profiles are working (it takes time, and that sucks). The allure of botting new content often makes you want to grab the newest versions and go all-out, but it simply won't work like that. These guys are essentially coding programs on the fly with input from the public. I've learned from experience to keep multiple installs of DB handy because losing an old version can be extremely frustrating when the new one is broken.
Chest farming is an amazing way to kick off your end-game botting. It doesn't require constant updates, and the directions are very well written and explained. You'll net yourself a ton of mats, gems, and legs. Keep that install as your "fall-back" in case the updates break your other methods. Keep up your support too!
S_o_M
Member
- Joined
- Jan 10, 2012
- Messages
- 651
- Reaction score
- 2
Same here
Impressive stuff!
I've noticed that when I set the wave limit, I will start to TP and if I make it out (It seems to be 2 waves late because of my M6 Turrets!) the bot goes back into the TP and continues the rift as if I simply died.
I've noticed that when I set the wave limit, I will start to TP and if I make it out (It seems to be 2 waves late because of my M6 Turrets!) the bot goes back into the TP and continues the rift as if I simply died.
From someone who has been using HB and DB for years, you have to give-in an accept that these profiles, plugins, and even the bot itself are essentially in a constant beta stage. I'm still using a DB install from 2-3 releases back and can bot rifts, bounties, keys, etc non stop and fully AFK. I'm missing out on a feature here and there, but it doesn't bug out on me overnight. I avoid all updates until I can confirm that all of my current plugins and profiles are working (it takes time, and that sucks). The allure of botting new content often makes you want to grab the newest versions and go all-out, but it simply won't work like that. These guys are essentially coding programs on the fly with input from the public. I've learned from experience to keep multiple installs of DB handy because losing an old version can be extremely frustrating when the new one is broken.
Chest farming is an amazing way to kick off your end-game botting. It doesn't require constant updates, and the directions are very well written and explained. You'll net yourself a ton of mats, gems, and legs. Keep that install as your "fall-back" in case the updates break your other methods. Keep up your support too!
Exactly what I have been saying, Great to know there are more then a few of us out there who think like this. Too many people quickly jump on that YES button to update, only to realize some new update just broke this profile or that plugin and they make a post saying their bot broke and what do they do now? I take a bot version, in fact I have several versions. Some vary in trinity or quest tool versions whatever it may be, but I have one bot that is for rifting. I have one that is specialized for M6 DH combat routine rifting(works best with a certain trinity version then the latest). I have a chest runner DB. All of them work flawless pretty much, The only new thing im testing is a goblin one that got me a gem my first time but I was quick enough to take over manually when I saw it, but second time around it failed me and inactivity timer was tripped and I didn't get my gem on non season.
Basically, Even after 2.1 hit I took all my old broken demonbuddy folders. Deleted all the logs and junk and zipped them up into a folder labeled pre 2.0 db. That way if I ever needed to I could go back and get a profile or a trinity version or combat routine if I had lost it. I do the same for new releases of things, I have like the last 20 releases of trinity, quest tools. various profiles etc. Get something that works, back it up/copy it and rename it something like DemonBuddy-Rift.AFKable and then if you decide you want to run chests. Either take the old folder, or take a new installation and put the chest files into it and rename it demonbuddy-chestrunner and test it, make sure no major issues and that it can run non stop then mark it down as 24/7 runner and do not update these ever. Back when Kevin was making three musketeer profiles, I was still using version 0.4 when he had 0.9 released and it was working 100% afk 0 issues meanwhile a few certain versions stopped working due to trinity updates and so on so people had to fall back to older versions of DB/plugins which most couldn't do because they saw an update and did it without thinking.
tl;dr - if somethin works, don't go and update it and expect it to work everytime. shit happens, shit breaks/changes.
im using newest DB
Trinity 2.1.13
Questtool 2.1.36
and i have the same prob as some others here...after the bot finished the frist Rift he stops and i have to start it manually...anyone could tell me what i set wrong or can tell me what im doing wrong?!
Trinity 2.1.13
Questtool 2.1.36
and i have the same prob as some others here...after the bot finished the frist Rift he stops and i have to start it manually...anyone could tell me what i set wrong or can tell me what im doing wrong?!
bestdamnwarrior
Member
- Joined
- Sep 3, 2014
- Messages
- 84
- Reaction score
- 2
I'm using the latest Trinity and QT and so far the profile is working very well. I'm curious using a M6 DH if there's a setting that I have set incorrectly to keep my DH from running/vaulting/staying within melee range of mob packs and/or elite packs. Instead of staying away from them, my DH loves to just sit on top of mob packs and take a crap ton of damage. Is there something I'm missing setting wise to keep my DH away from the middle of packs and stay on the outside of them? THanks
I had the same problem. The bot would stop after trial, and stop after the run. What it was for me was I had renamed the text file or had copies of it so it was R-RIFT(1).txt. This is a problem because if you edit the file at the bottom it will look for "R-RIFT".txt so make sure you have the exact name or it won't be able to find it.
View attachment 143436
RIFT PRIORITY does not seem to work. No matter how its setup, it always open normal rifts.
And yes, I have installed fresh copies of newest trinity and quest tools. Also deleted compiled asssemblies before I started.
RIFT PRIORITY does not seem to work. No matter how its setup, it always open normal rifts.
And yes, I have installed fresh copies of newest trinity and quest tools. Also deleted compiled asssemblies before I started.
It's under quest tools.