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

Rift Bot - Yet Another Rifting Profile!

Strange. It seems to happen intermittently but without fail it always misses at least 1 gem.

I need to run but I'll see what the logs say later this evening.
 
What is different between the stock trinity and the one you are bundling? When I follow your directions it works fine and when I try to use my normal install with EZ updater it gets stuck with the unknown XML tag issue.

This used to work, and I'm just confused about why it no longer is

-Xaq
 
What I don't understand is why people just want to use the same folder, for everything. I have at least 6 different DB folders, for different things. I find a version, and settings that work, I'm not going to update it. I'm using I think Oks version 0.92. It works great, clears the Rifts, and gets me blood shards, and has no problems. So why the hell would I update?

Same with Ghom, or bounty profiles. Different folders for each.

The Rift profile for a long time has been complete, and working, and at this point, the Devs are just working to fix bugs brought on my new versions of Trinity or DB, and has nothing to do with their profile.

TL;DR - Find a working version, and don't update!
 
What I don't understand is why people just want to use the same folder, for everything. I have at least 6 different DB folders, for different things. I find a version, and settings that work, I'm not going to update it. I'm using I think Oks version 0.92. It works great, clears the Rifts, and gets me blood shards, and has no problems. So why the hell would I update?

Same with Ghom, or bounty profiles. Different folders for each.

The Rift profile for a long time has been complete, and working, and at this point, the Devs are just working to fix bugs brought on my new versions of Trinity or DB, and has nothing to do with their profile.

TL;DR - Find a working version, and don't update!

I'm not necessarily opposed to that answer, However being relatively new to riftbot I've never found a complete version that worked... I am using the latest pack that is posted on the first page and am having what I believe are probably trinity issues - It is not opening doors or destroying them if necessary it will just stand at a door unless I manually click it - I never noticed this before, on my wizard the doors would get auto destroyed so that may be why it's new to me as I am seeing this on my barb.
 
I'm not necessarily opposed to that answer, However being relatively new to riftbot I've never found a complete version that worked... I am using the latest pack that is posted on the first page and am having what I believe are probably trinity issues - It is not opening doors or destroying them if necessary it will just stand at a door unless I manually click it - I never noticed this before, on my wizard the doors would get auto destroyed so that may be why it's new to me as I am seeing this on my barb.

Did you turn on force ignore destructibles?
 
just curious when i run this i run my barb and its fine but when i try running my demon it seems to get stuck a lot doors mainly do i need to change some setting for it to not get stuck?
 
negatory, I have it set to skip destructables unless stuck...

Also it gets stuck at the draw bridge style gates where it has to click the wheel to lower it - Again I'm not blaming anything specifically because I don't know enough to determine where the problem is, that type of stuff seems like it would be CR based not profile though?
 
Your avoidance settings in trinity.. I'd suggest you take the time to READ what does what.. I mean you are using the plugins so I'd take the time to actually understand what it does.. the issues you are having have NOTHING to do with Rift-bot..



No offense but we don't care and we don't think it is needed the way loot-tables work anyone staying in the same game is just stupid.. I can understand staying if you find an awesome item but given that you BOT which you normally do AFK there is little to no point you want to have as much loot variety as possible. Everyone who read and understood the leaked info of how Diablo 3 loot works and what chances are would never say in the same game for more then 1 rift. Only the turds who didn't read it and or did not understand it still keep rifting in the same game over and over again. If you don't like it don't use it or change it yourself. What you brought is a 'Framework' not a all inclusive bot this requires you to have basic scripting skills if not try to acquire them.

Can you explain the avoidance settings? I'm running into the same problem of the bot not attacking the rift guardian. Everything else is perfect
 
It seems to be getting stuck right at the door after entering, just walking back and forth on it. Not sure if this is a trinity problem or a profile problem but I figured I should post it somewhere. Running DB Beta v1.1.1882.407, Trinity 1.9.4, QuestTools 2.0.67. I went afk on a previous run and found it doing the same thing on the rift boss, just running back and forth on it but not actually attacking the boss.

Code:
[MiniMapMarker] Was able to generate full path to failed MiniMapMarker 1877684886 at <170.1127, 138.3032, 7.110113>, marking as good
[MiniMapMarker] Moved to inspect nameHash 1877684886 at <170.1127, 138.3032, 7.110113>, IsPOI: False IsExit: False MoveResult: Moved
[MiniMapMarker] Moved to inspect nameHash 1877684886 at <170.1127, 138.3032, 7.110113>, IsPOI: False IsExit: False MoveResult: ReachedDestination
[MiniMapMarker] Setting MiniMapMarker 1877684886 as failed, MoveResult=ReachedDestination
[MiniMapMarker] Was able to generate full path to failed MiniMapMarker 1877684886 at <170.1127, 138.3032, 7.110113>, marking as good
[MiniMapMarker] Moved to inspect nameHash 1877684886 at <170.1127, 138.3032, 7.110113>, IsPOI: False IsExit: False MoveResult: Moved
[MiniMapMarker] Moved to inspect nameHash 1877684886 at <170.1127, 138.3032, 7.110113>, IsPOI: False IsExit: False MoveResult: ReachedDestination
[MiniMapMarker] Setting MiniMapMarker 1877684886 as failed, MoveResult=ReachedDestination
[MiniMapMarker] Was able to generate full path to failed MiniMapMarker 1877684886 at <170.1127, 138.3032, 7.110113>, marking as good
[MiniMapMarker] Moved to inspect nameHash 1877684886 at <170.1127, 138.3032, 7.110113>, IsPOI: False IsExit: False MoveResult: Moved
[MiniMapMarker] Moved to inspect nameHash 1877684886 at <170.1127, 138.3032, 7.110113>, IsPOI: False IsExit: False MoveResult: ReachedDestination
[MiniMapMarker] Setting MiniMapMarker 1877684886 as failed, MoveResult=ReachedDestination
... repeat forever.
 
Also it gets stuck at the draw bridge style gates where it has to click the wheel to lower it - Again I'm not blaming anything specifically because I don't know enough to determine where the problem is, that type of stuff seems like it would be CR based not profile though?

So more specifics - In "Maddening Realm 1" It gets stuck standing at weak wooden doors - and turning on destructables does NOT fix it, so the door is definitely being treated different than a destructable item would be.
 
It seems to be getting stuck right at the door after entering, just walking back and forth on it. Not sure if this is a trinity problem or a profile problem but I figured I should post it somewhere. Running DB Beta v1.1.1882.407, Trinity 1.9.4, QuestTools 2.0.67. I went afk on a previous run and found it doing the same thing on the rift boss, just running back and forth on it but not actually attacking the boss.

Code:
[MiniMapMarker] Was able to generate full path to failed MiniMapMarker 1877684886 at <170.1127, 138.3032, 7.110113>, marking as good
[MiniMapMarker] Moved to inspect nameHash 1877684886 at <170.1127, 138.3032, 7.110113>, IsPOI: False IsExit: False MoveResult: Moved
[MiniMapMarker] Moved to inspect nameHash 1877684886 at <170.1127, 138.3032, 7.110113>, IsPOI: False IsExit: False MoveResult: ReachedDestination
[MiniMapMarker] Setting MiniMapMarker 1877684886 as failed, MoveResult=ReachedDestination
[MiniMapMarker] Was able to generate full path to failed MiniMapMarker 1877684886 at <170.1127, 138.3032, 7.110113>, marking as good
[MiniMapMarker] Moved to inspect nameHash 1877684886 at <170.1127, 138.3032, 7.110113>, IsPOI: False IsExit: False MoveResult: Moved
[MiniMapMarker] Moved to inspect nameHash 1877684886 at <170.1127, 138.3032, 7.110113>, IsPOI: False IsExit: False MoveResult: ReachedDestination
[MiniMapMarker] Setting MiniMapMarker 1877684886 as failed, MoveResult=ReachedDestination
[MiniMapMarker] Was able to generate full path to failed MiniMapMarker 1877684886 at <170.1127, 138.3032, 7.110113>, marking as good
[MiniMapMarker] Moved to inspect nameHash 1877684886 at <170.1127, 138.3032, 7.110113>, IsPOI: False IsExit: False MoveResult: Moved
[MiniMapMarker] Moved to inspect nameHash 1877684886 at <170.1127, 138.3032, 7.110113>, IsPOI: False IsExit: False MoveResult: ReachedDestination
[MiniMapMarker] Setting MiniMapMarker 1877684886 as failed, MoveResult=ReachedDestination
... repeat forever.

I mentioned this to rrrix and he already fixed it. Download the latest revision of Ques Tools. It should be at 26 now.
 
My barb runs the rift without any problems, but when the boss spawns, my barb does not attack the boss and leaves the game, is this issue known? I didn´t find anything yet -.-

I have db 360 trini 1.9.3 and quest 2.0.57.
 
My barb runs the rift without any problems, but when the boss spawns, my barb does not attack the boss and leaves the game, is this issue known? I didn´t find anything yet -.-

I have db 360 trini 1.9.3 and quest 2.0.57.

I can't speak for barbarians, I play only a Wizard. I have no trouble with rift guardians. I'm also running Quest Tools 2.0.69, but that shouldn't matter. Trinity takes care of combat routines.
 
Issue i noticed, when there's a door with enemies pressed right up against it, the bot will stand trying to attack the enemies not realising the door is there and closed.
 
I'm not necessarily opposed to that answer, However being relatively new to riftbot I've never found a complete version that worked... I am using the latest pack that is posted on the first page and am having what I believe are probably trinity issues - It is not opening doors or destroying them if necessary it will just stand at a door unless I manually click it - I never noticed this before, on my wizard the doors would get auto destroyed so that may be why it's new to me as I am seeing this on my barb.

Mine is getting stuck behind breakables and some doors as well... I do have skip breakables unless stuck... Maybe its a trinity issue. Any ideas?
 
Last edited:
Mine is getting stuck behind breakables as well... I do have skip breakables unless stuck... Maybe its a trinity issue. Any ideas?

It is a Trinity issue. I don't experience it because I use GearSwap with Fire walkers when near breakables.
 
Back
Top