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

Rift Bot - Yet Another Rifting Profile!

Oksehode said:
That is what i call a "fluke". In very rare occasions, the bot just stands by the exit portal. I've seen this happening twice in 30 hours of running the profile.
Click to expand...

mate one problem in kadala_spree 1.14 bot cant spent shards on act 1 :D stucking on loop. any idea? cuz the * Added additional nav targets when DB doesn't know where kadala actor is (common in Act4 town) is added in 2.0
 
r3plic4tor said:
mate one problem in kadala_spree 1.14 bot cant spent shards on act 1 :D stucking on loop. any idea? cuz the * Added additional nav targets when DB doesn't know where kadala actor is (common in Act4 town) is added in 2.0
Click to expand...

i've never seen riftbot in act 1. maybe ask in the kadala spree thread
 
r3plic4tor said:
mate one problem in kadala_spree 1.14 bot cant spent shards on act 1 :D stucking on loop. any idea? cuz the * Added additional nav targets when DB doesn't know where kadala actor is (common in Act4 town) is added in 2.0
Click to expand...

I have no problem with act 1 and Kadalaspree 1.0.14. Bot runs for Kadala as normal.
 
[Rift Bot] Open Rift
[SafeMoveToTag] Initialized
[SafeMoveToTag] ReachedDestination!
[SafeMoveToTag] Timeout of 180 seconds exceeded for Profile Behavior (start: 1/1/0001 2:00:00 AM now: 7/5/2014 9:00:01 PM)
[SafeMoveToTag] Timeout of 180 seconds exceeded for Profile Behavior (start: 1/1/0001 2:00:00 AM now: 7/5/2014 9:00:06 PM)
[SafeMoveToTag] Timeout of 180 seconds exceeded for Profile Behavior (start: 1/1/0001 2:00:00 AM now: 7/5/2014 9:00:11 PM)
[SafeMoveToTag] Timeout of 180 seconds exceeded for Profile Behavior (start: 1/1/0001 2:00:00 AM now: 7/5/2014 9:00:15 PM)
[SafeMoveToTag] Timeout of 180 seconds exceeded for Profile Behavior (start: 1/1/0001 2:00:00 AM now: 7/5/2014 9:00:20 PM)
[SafeMoveToTag] Timeout of 180 seconds exceeded for Profile Behavior (start: 1/1/0001 2:00:00 AM now: 7/5/2014 9:00:24 PM)
[SafeMoveToTag] Timeout of 180 seconds exceeded for Profile Behavior (start: 1/1/0001 2:00:00 AM now: 7/5/2014 9:00:29 PM)
[SafeMoveToTag] Timeout of 180 seconds exceeded for Profile Behavior (start: 1/1/0001 2:00:00 AM now: 7/5/2014 9:00:34 PM)
[SafeMoveToTag] Timeout of 180 seconds exceeded for Profile Behavior (start: 1/1/0001 2:00:00 AM now: 7/5/2014 9:00:38 PM)
[SafeMoveToTag] Timeout of 180 seconds exceeded for Profile Behavior (start: 1/1/0001 2:00:00 AM now: 7/5/2014 9:00:43 PM)
[SafeMoveToTag] Timeout of 180 seconds exceeded for Profile Behavior (start: 1/1/0001 2:00:00 AM now: 7/5/2014 9:00:47 PM)
[SafeMoveToTag] Timeout of 180 seconds exceeded for Profile Behavior (start: 1/1/0001 2:00:00 AM now: 7/5/2014 9:00:52 PM)
[SafeMoveToTag] Timeout of 180 seconds exceeded for Profile Behavior (start: 1/1/0001 2:00:00 AM now: 7/5/2014 9:00:57 PM)
[SafeMoveToTag] Timeout of 180 seconds exceeded for Profile Behavior (start: 1/1/0001 2:00:00 AM now: 7/5/2014 9:01:03 PM)
[SafeMoveToTag] Timeout of 180 seconds exceeded for Profile Behavior (start: 1/1/0001 2:00:00 AM now: 7/5/2014 9:01:07 PM)
[SafeMoveToTag] Timeout of 180 seconds exceeded for Profile Behavior (start: 1/1/0001 2:00:00 AM now: 7/5/2014 9:01:12 PM)
[SafeMoveToTag] Timeout of 180 seconds exceeded for Profile Behavior (start: 1/1/0001 2:00:00 AM now: 7/5/2014 9:01:17 PM)
[SafeMoveToTag] Timeout of 180 seconds exceeded for Profile Behavior (start: 1/1/0001 2:00:00 AM now: 7/5/2014 9:01:21 PM)
[SafeMoveToTag] Timeout of 180 seconds exceeded for Profile Behavior (start: 1/1/0001 2:00:00 AM now: 7/5/2014 9:01:26 PM)
[SafeMoveToTag] Timeout of 180 seconds exceeded for Profile Behavior (start: 1/1/0001 2:00:00 AM now: 7/5/2014 9:01:31 PM)
[SafeMoveToTag] Timeout of 180 seconds exceeded for Profile Behavior (start: 1/1/0001 2:00:00 AM now: 7/5/2014 9:01:37 PM)
[SafeMoveToTag] Timeout of 180 seconds exceeded for Profile Behavior (start: 1/1/0001 2:00:00 AM now: 7/5/2014 9:01:42 PM)
[SafeMoveToTag] Timeout of 180 seconds exceeded for Profile Behavior (start: 1/1/0001 2:00:00 AM now: 7/5/2014 9:01:46 PM)
[SafeMoveToTag] Timeout of 180 seconds exceeded for Profile Behavior (start: 1/1/0001 2:00:00 AM now: 7/5/2014 9:01:51 PM)
[SafeMoveToTag] Timeout of 180 seconds exceeded for Profile Behavior (start: 1/1/0001 2:00:00 AM now: 7/5/2014 9:01:56 PM)
[SafeMoveToTag] Timeout of 180 seconds exceeded for Profile Behavior (start: 1/1/0001 2:00:00 AM now: 7/5/2014 9:02:00 PM)
[SafeMoveToTag] Timeout of 180 seconds exceeded for Profile Behavior (start: 1/1/0001 2:00:00 AM now: 7/5/2014 9:02:05 PM)
[SafeMoveToTag] Timeout of 180 seconds exceeded for Profile Behavior (start: 1/1/0001 2:00:00 AM now: 7/5/2014 9:02:09 PM)
[SafeMoveToTag] Timeout of 180 seconds exceeded for Profile Behavior (start: 1/1/0001 2:00:00 AM now: 7/5/2014 9:02:14 PM)
[SafeMoveToTag] Timeout of 180 seconds exceeded for Profile Behavior (start: 1/1/0001 2:00:00 AM now: 7/5/2014 9:02:19 PM)
[SafeMoveToTag] Timeout of 180 seconds exceeded for Profile Behavior (start: 1/1/0001 2:00:00 AM now: 7/5/2014 9:02:23 PM)
[SafeMoveToTag] Timeout of 180 seconds exceeded for Profile Behavior (start: 1/1/0001 2:00:00 AM now: 7/5/2014 9:02:28 PM)
[SafeMoveToTag] Timeout of 180 seconds exceeded for Profile Behavior (start: 1/1/0001 2:00:00 AM now: 7/5/2014 9:02:33 PM)
[SafeMoveToTag] Timeout of 180 seconds exceeded for Profile Behavior (start: 1/1/0001 2:00:00 AM now: 7/5/2014 9:02:38 PM)
[SafeMoveToTag] Timeout of 180 seconds exceeded for Profile Behavior (start: 1/1/0001 2:00:00 AM now: 7/5/2014 9:02:43 PM)
[SafeMoveToTag] Timeout of 180 seconds exceeded for Profile Behavior (start: 1/1/0001 2:00:00 AM now: 7/5/2014 9:02:48 PM)

Then restarts game and does it again.

Stands at Act 1 trying to open a rift with no rift fragments. Says: five rift key fragments are needed to conjure a Nephalem rift.
Spamming his buffs too, I have to stop the bot then start it again when this happens.

Any fix to this, to let him timeout after Gold timeout then do the bounty then rift?

Untitled.webp
 
Last edited:
BugzBunny said:
*snip*

Then restarts game and does it again.

Stands at Act 1 trying to open a rift with no rift fragments. Says: five rift key fragments are needed to conjure a Nephalem rift.
Spamming his buffs too, I have to stop the bot then start it again when this happens.

Any fix to this, to let him timeout after Gold timeout then do the bounty then rift?

View attachment 134915
Click to expand...

Everything you need to know is in my post on the first page.

I don't understand why you're trying to do a rift without key fragments? What profile are you running?
 
r3plic4tor said:
sry mate here you are. i meant with flipping back and forward on same spot


View attachment 134916
Click to expand...

This is the "OutOfMemory" problem that is written in my first post under "Known Issues".

Known Issues
  • Some Bastion Keep maps is causing "OutOfMemory" errors which in turn makes the bot useless and gets stuck. *This is a DemonBuddy issue and I have no control over it*
 
Oksehode said:
This is the "OutOfMemory" problem that is written in my first post under "Known Issues".

Known Issues
  • Some Bastion Keep maps is causing "OutOfMemory" errors which in turn makes the bot useless and gets stuck. *This is a DemonBuddy issue and I have no control over it*
Click to expand...
No mate that was not a Memory Problem i had it too but earlier the other Problem was later nothing with zeta. Believe me
 
Using Rift Bot Full with Bounties.xml

I thought this will allow the bot to run act 4 bounty first which will acquire a total of 5+ fragments then open a rift, finish then close it, repeat.

Problem I get is Act 4 bounty - Rift - Trys another rift, gets stuck, timeout, restarts, rift, timeout and so on.
 
r3plic4tor said:
No mate that was not a Memory Problem i had it too but earlier the other Problem was later nothing with zeta. Believe me
Click to expand...

According to your log this is a "OutOfMemory" problem.

It's either that or the bot is trying to target something. flip-flopping is caused by trinity trying to target something.
 
Last edited:
r3plic4tor said:
Yes the First lines are but it happend after it. I dont Know the time :(. Maybe next time.
Click to expand...

You posted 3 screenshots from 3 different Bastion Keep maps.

The log you posted had stucks and "OutOfMemory" errors and all on Bastion Keep maps. The timestamps in the log doesn't match the clock in your screenshots. They seem very unrelated.
 
Oksehode said:
Everything you need to know is in my post on the first page.

I don't understand why you're trying to do a rift without key fragments? What profile are you running?
Click to expand...

Yea there isn't anything about my problem on the first page. :/

Like I said: i'm using Rift Bot Full with Bounties.xml

Problem I get is Act 4 bounty - Rift - Trys another rift, gets stuck, timeout, restarts, rift, timeout and so on. (Does a bounty once, have to Stop and Start the bot to repeat this process)
 
You must log in or register to reply here.
Back
Top