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

Rift Bot - Yet Another Rifting Profile!

superwash said:
@Syn-Ack

Hey thanks for that information. I checked in my logs and your spot on.
Are there any other Profiles that only do rifts? The R-Rift one always does Grifts which i do not want.
Click to expand...

You can still use the r-rift profile to do rifts. But instead of using rift FULL, use rift EXPLORE. Even if you get a cursed hold map for this, when the trinity gold reset is activated, it will not reload the cursed hold map but load the EXPLORE and start all over again. Tested. 100% afkable
 
It says;

''Diablo III is running but no build supported by Demonbuddy detected, was there a patch?''

And i don't wanna use unstabilized version of DB. Using old version, what can i do?
 
coffeeortea said:
You can still use the r-rift profile to do rifts. But instead of using rift FULL, use rift EXPLORE. Even if you get a cursed hold map for this, when the trinity gold reset is activated, it will not reload the cursed hold map but load the EXPLORE and start all over again. Tested. 100% afkable
Click to expand...

To me, Explore rift works as common rift, it leaves when it killes the Rift Guardian...kinda enjoying because that EATS rift keys superfast. I dont like Full Rift because it often leaves the bots running around looking for the key stone.

Dogger said:
Maybe you look on the first page ?

I only see up to 467
Click to expand...

Use Ezupdater
 
My bot keeps getting stuck in Act 1, does anyone else have this problem? Bot just goes full retard and keeps trying to ram open the gate to the East in New Tristram.
 
Yes djdigital I started having the Exact same problem running into the gate in act1, the bot doesnt seem to restart the game even though I got gold/exp ticked to 240 sec and restarts allowed.
 
Would anyone mind uploading v 468 and link it in this thread? I don't wanna use Ezupdater. Would really appreciate =)
 
So I am updated to 468, and someone posted that they DID or no longer get any cursed hold bugs? I second the comment about rift bot explore, its essentially the same thing as common. you are 99% most likely to spawn RG before ever setting eyes on a town portal stone. Some maps are so huge youll spawn RG before its 25% complete if its a 1 level map. others have 8 different map levels to go through with plenty of mobs to spawn a RG by level 2 or 3. If 468 has truly fixed the cursed hold reload bug then nothing is to worry.
 
I have twice over seen the bot run cursed hold on 468 rev and can confirm 100% it is working on rift bot full profile. No issues yet. Thanks! Also for anyone who doesn't want to use ezupdater, you can simply download the files one by one but its tedious. Google tortoise SVN and download it, then click or copy this link https://rift-bot-demonbuddy.googlecode.com/svn/trunk/ then go to your D3 profile folder, or anywhere you want to copy it to, and simply right click - SVN checkout and itll copy all the revised files over.
 
Cursed hold seems fine now, but i been waking up to my char constantly getting stuck in the dalghur oasis map now doing the full profile. Anyone else having the same issue ?
 
turkeyslayer said:
Cursed hold seems fine now, but i been waking up to my char constantly getting stuck in the dalghur oasis map now doing the full profile. Anyone else having the same issue ?
Click to expand...
Yes dhalgur jams the profile every time, that's why I dont run full overnight
 
howmakewood said:
Yes dhalgur jams the profile every time, that's why I dont run full overnight
Click to expand...

thks , yeah i been doing explore mode since . On a side note, i found another error with my bot, a couple of times i have seen my bot walking in circles not picking up anything and twice it was the seasonal templar relic thats on the ground.
Havent seen an issue like this since the start of season 1 when i found my sader not picking up the condemn shield.
 
What is happening? lol

[Trinity] Your bot got stuck! Trying to unstuck (attempt #2 of 10 attempts) Act="OpenWorld" questId="312429" stepId="2" worldId="288454"
[Trinity] Saving Config file
[Trinity] Your bot got stuck! Trying to unstuck (attempt #3 of 10 attempts) Act="OpenWorld" questId="312429" stepId="2" worldId="288454"
[Trinity] Your bot got stuck! Trying to unstuck (attempt #4 of 10 attempts) Act="OpenWorld" questId="312429" stepId="2" worldId="288454"
[QuestTools][GridRoute] Generated new Weighted Nearest Minimap Unvisited Route with 12 nodes in 1ms
[QuestTools][<MainCoroutine>d__1] ReachedDestination! questId="312429" stepId="2" x="597" y="840" z="0" pathPrecision=5 MoveResult=Moved statusText=SafeMoveToTag: IsDone: False, PathPrecision: 5, StraightLinePathing: False, UseNavigator: False, X: 597, Y: 840, Z: 0, Position: <597, 840, 0>, PathPointLimit: 250, Timeout: 180, AllowLongDistance: False, QuestId: 312429, StepId: 2, ObjectiveIndex: -1, QuestName: Quest Id: 4C46D, IgnoreReset: False, IsDoneCache: False, Behavior: Zeta.Bot.ActionRunCoroutine,
[QuestTools][SafeMoveToTag] Initialized questId="312429" stepId="2" x="728" y="822" z="0" pathPrecision=5 MoveResult=Moved statusText=SafeMoveToTag: IsDone: False, PathPrecision: 5, StraightLinePathing: False, UseNavigator: False, X: 728, Y: 822, Z: 0, Position: <728, 822, 0>, PathPointLimit: 250, Timeout: 180, AllowLongDistance: False, QuestId: 312429, StepId: 2, ObjectiveIndex: -1, QuestName: Quest Id: 4C46D, IgnoreReset: False, IsDoneCache: False, Behavior: null,
[QuestTools][<MainCoroutine>d__1] ReachedDestination! questId="312429" stepId="2" x="728" y="822" z="0" pathPrecision=5 MoveResult=Moved statusText=SafeMoveToTag: IsDone: False, PathPrecision: 5, StraightLinePathing: False, UseNavigator: False, X: 728, Y: 822, Z: 0, Position: <728, 822, 0>, PathPointLimit: 250, Timeout: 180, AllowLongDistance: False, QuestId: 312429, StepId: 2, ObjectiveIndex: -1, QuestName: Quest Id: 4C46D, IgnoreReset: False, IsDoneCache: False, Behavior: Zeta.Bot.ActionRunCoroutine,
[QuestTools][SafeMoveToTag] Initialized questId="312429" stepId="2" x="967" y="817" z="0" pathPrecision=5 MoveResult=Moved statusText=SafeMoveToTag: IsDone: False, PathPrecision: 5, StraightLinePathing: False, UseNavigator: False, X: 967, Y: 817, Z: 0, Position: <967, 817, 0>, PathPointLimit: 250, Timeout: 180, AllowLongDistance: False, QuestId: 312429, StepId: 2, ObjectiveIndex: -1, QuestName: Quest Id: 4C46D, IgnoreReset: False, IsDoneCache: False, Behavior: null,
Stopping the bot.
Session lasted for: 02:59:56.9052672
Bot Thread Ended. Was this requested?
Chose Trinity as your combat routine
[Trinity] Inserting GoldInactivity into TreeStart
[Trinity] Inserting XPInactivity into TreeStart
Loaded profile Rift Bot Common r467
Chose Trinity as your combat routine
Loaded profile Rift Bot Common r467
Chose Trinity as your combat routine
[Trinity] Inserting GoldInactivity into TreeStart
[Trinity] Inserting XPInactivity into TreeStart
Adding Gamble into BotBehavior Hook at Position 0
Adding Townrun into BotBehavior Hook at Position 0
[BotEvents] Bot is Starting
[Trinity] Bot Starting
[Trinity] Note: Maintaining item stats from previous run. To reset stats fully, please restart DB.
[Trinity] Replacing Combat Hook
[Trinity] Replacing VendorRun Hook
[Trinity] Replacing Loot Hook
[Trinity] Inserting GoldInactivity into TreeStart
[Trinity] Inserting XPInactivity into TreeStart
[Trinity] Bot Starting, Resetting Gold Inactivity Timer
Loaded profile Rift Bot Common
Loaded profile Rift Bot Loader
[Rift Bot] Main Loader
Loaded profile Rift Bot
ToggleTargeting, new values: Looting:True LootRadius:150 Combat:True KillRadius:80
Loaded profile Rift Bot Optimized Explore
ToggleTargeting, new values: Looting:True LootRadius:150 Combat:True KillRadius:80
Loaded profile Rift Bot Optimized Explore
[Rift Bot] Explore Large Cursed Hold with SafeMoveTo.
[QuestTools][SafeMoveToTag] Initialized questId="312429" stepId="2" x="727" y="817" z="0" pathPrecision=5 MoveResult=Moved statusText=SafeMoveToTag: IsDone: False, PathPrecision: 5, StraightLinePathing: False, UseNavigator: False, X: 727, Y: 817, Z: 0, Position: <727, 817, 0>, PathPointLimit: 250, Timeout: 180, AllowLongDistance: False, QuestId: 312429, StepId: 2, ObjectiveIndex: -1, QuestName: Quest Id: 4C46D, IgnoreReset: False, IsDoneCache: False, Behavior: null,
 
My bot is STILL getting stuck in this stupid Rift Bot Optimized Explore RiftExploreCursedHold profile... why is it even loading this stupid ass profile while I'm in town??

ugh
 
You must log in or register to reply here.
Back
Top