theorangeshield
New Member
- Joined
- Apr 28, 2014
- Messages
- 18
- Reaction score
- 0
Thanks.
Rift Bot - Yet Another Rifting Profile!
- Thread starter DyingHymn
- Start date
It never go lvl 2 on normal rifts and inactivity with git version trinity and quest tools. It explore on lvl 1 always and getting inactivity relog.
rift bot common profile
Last edited:
somethingthere
Member
- Joined
- Apr 21, 2014
- Messages
- 46
- Reaction score
- 1
I experienced a more unresponsive behaviour with the latest 463. Lower ticks, didnt always attack Rift Boss or other mobs and some looting issues. Tried alot of different settings, including the standard one with advice on first page.
Downgraded back to 462 and noticed a much more responsive bot, big increase in Legs per hour and not as many deaths either.
Dont know if its related to Trinity or if its just me who have bad luck
Running at 15 Legs per hour now, although only tested 462 for 2hours now, but with 463 I never came above 10 legs per hour.
Downgraded back to 462 and noticed a much more responsive bot, big increase in Legs per hour and not as many deaths either.
Dont know if its related to Trinity or if its just me who have bad luck
Running at 15 Legs per hour now, although only tested 462 for 2hours now, but with 463 I never came above 10 legs per hour.
Kadala profile works very well for me, it does not switch toons though. So it will gamble on whoever you are playing with. Still no damn furnace though...
I experienced a more unresponsive behaviour with the latest 463. Lower ticks, didnt always attack Rift Boss or other mobs and some looting issues. Tried alot of different settings, including the standard one with advice on first page.
Downgraded back to 462 and noticed a much more responsive bot, big increase in Legs per hour and not as many deaths either.
Dont know if its related to Trinity or if its just me who have bad luck
Running at 15 Legs per hour now, although only tested 462 for 2hours now, but with 463 I never came above 10 legs per hour.
yeah it looks so buggy. i just reverted back to 462 and everythings fine...
I experienced a more unresponsive behaviour with the latest 463. Lower ticks, didnt always attack Rift Boss or other mobs and some looting issues. Tried alot of different settings, including the standard one with advice on first page.
Downgraded back to 462 and noticed a much more responsive bot, big increase in Legs per hour and not as many deaths either.
Dont know if its related to Trinity or if its just me who have bad luck
Running at 15 Legs per hour now, although only tested 462 for 2hours now, but with 463 I never came above 10 legs per hour.
This and when using the common profile it continue to explore the current level area after killing the rift boss.
remtownloljk
New Member
- Joined
- Dec 4, 2011
- Messages
- 60
- Reaction score
- 0
its KadalaSpree, i turned it off and everything's perfect again.
alex4honor
New Member
- Joined
- Jan 23, 2014
- Messages
- 64
- Reaction score
- 0
Why does it log out of the game when it dies? Just watched him doing a normal rift and he died in trash, instead of revive at corpse, he left the game and startet a new one?!
somethingthere
Member
- Joined
- Apr 21, 2014
- Messages
- 46
- Reaction score
- 1
Just follow everything on the first page, second post. Doing everything that Oksehode explained there is the way to go. Have had your problem sometime but that was because I were too lazy to do fresh install of everything.
Dont forget to delete Plugin folder that comes with the DB install before you replace them with this zip-file.
And to the rest that having problem with the latest 463, use 462 instead for now.
lordunderdog
New Member
- Joined
- Jul 20, 2012
- Messages
- 12
- Reaction score
- 0
just a quick question, but how would i go about making the bot do greater rifts instead?
use R-Rift profile.
Is there any fix on this latest qt and trinity its not working correctly. So many stuck and most of time not finishing rifts. tried both 462 and 463.
463 - after boss died keep navigate till gold inactivity. rift bot common.xml
462 - doesnt go next level most of time if toon doesnt find boss in current level
463 - after boss died keep navigate till gold inactivity. rift bot common.xml
462 - doesnt go next level most of time if toon doesnt find boss in current level
Last edited:
QuestTool problem I believe? Same problem in grift, if the RIft Guardian spawns behind the bot, he continues until he finishes the level and enters ned next level.