Rift Bot - Yet Another Rifter!

[DyingHymn]

Hey DyingHymn, any chance you could run a change log for each update you make? I'd love to see how each revision of the profile and plugin is being improved.

See commit message.

 

[DyingHymn]

Ah, that makes sense. If it doesn't fix the issues, maybe one of the devs can at least make it an optional thing? I'm sure it wouldn't take long too implement in a separate profile. I have noticed great improvements from the last time I tried the profile though. It's almost afkable enough for me to leave it running outside of the blood shard issues

Now we have 6 profiles. We will have 12 profiles with pandemonium-excluded version.

 

[DyingHymn]

so, how are you here? w8ting for new trinity? profile keep updating but still not afk?

It is always AFKABLE for me.

 

[byobodybag]

Dying, do you reference the Bounties folder with your Rift with bounties profile? Or do you have your own copy of the bounties?

I see in your README that the bounties is at some revision older than the one being posted. Might be a good thing to call the bounties from their own folder? I just don't know if that's possible from the folder structures of players, wherever they saved DB.

 

[DyingHymn]

Dying, do you reference the Bounties folder with your Rift with bounties profile? Or do you have your own copy of the bounties?

I see in your README that the bounties is at some revision older than the one being posted. Might be a good thing to call the bounties from their own folder? I just don't know if that's possible from the folder structures of players, wherever they saved DB.

own copy. I believe the latest revisions of bounties does not change A4 bounties.

 

[Minseok]

Had it running for about 4 hours.

[Trinity][Performance] Execution of the block RefreshDiaObjectCache.Kiting took 7916.02ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 7945.86ms.
[Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 7946.09ms.
[Trinity][Performance] Execution of the block HandleTarget took 8156.38ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.Kiting took 8879.21ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 8899.44ms.
[Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 8899.64ms.
[Trinity][Performance] Execution of the block HandleTarget took 9089.00ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.Kiting took 5317.81ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 5327.42ms.
[Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 5327.61ms.
[Trinity][Performance] Execution of the block HandleTarget took 5502.69ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.Kiting took 7483.08ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 7492.14ms.
[Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 7492.37ms.
[Trinity][Performance] Execution of the block HandleTarget took 7633.82ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.Kiting took 8963.12ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 8972.22ms.
[Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 8972.49ms.
[Trinity][Performance] Execution of the block HandleTarget took 9092.67ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.Kiting took 9227.80ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 9239.38ms.
[Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 9239.63ms.
[Trinity][Performance] Execution of the block HandleTarget took 9369.25ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.Kiting took 9339.27ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 9351.76ms.
[Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 9351.95ms.
[Trinity][Performance] Execution of the block HandleTarget took 9517.58ms.

The lag killed it.

 

[byobodybag]

Stopping the bot. Reason:Failed to locate profile.

Reload your profile.

 

[tim1142]

What is the best profile (common,full,etc) to use for complete afking?

 

[morianxito]

Had it running for about 4 hours.



The lag killed it.

I have this problem too but the lag is not from me i havr lag only when i use db ... so there is something what is makong run the game so slow

 

[byobodybag]

What is the best profile (common,full,etc) to use for complete afking?

Rift with bounties - Explore

That's for me.

 

[BananaPants]

This is probably a really dumb question, but is there a way I could modify this to continually run the A4 bounties? This bot runs them so well comparatively speaking and I need to save up some rift keystone fragments.

 

[jao619]

This is probably a really dumb question, but is there a way I could modify this to continually run the A4 bounties? This bot runs them so well comparatively speaking and I need to save up some rift keystone fragments.

if I'm not mistaken it's using the act 4 bounty profile code from the the "adventure mode bounties..etc" thread a few down so you can just download the a4 bounties from there

 

[sowlinyin]

odd, the bot opened a new rift and then tp back in town right the way......until the gold inact timer gets triggered.....
[GameUI] Clicking UI element Conversation Button (1044983808)
[Trinity] Clicking UI element Conversation Button (1044983808)
[Trinity] Waiting for town run timer (Target Check)
Using town portal
Townportal successfull, we are in town!

The bot only starterd to move again after i close DB and restarted it....
seems like the bot was trying to complete a townrun but it couldn't.....

what the heck ==?

 

[sowlinyin]

Another problem i found is that when the bot is fighting Orlash, the boss may not appear due to the fact that it is invisible unless the player moves around abit; as for the bot, it will only shot in the direction that the boss is that but not being able to trigger the boss fighting

 

[user123]

Thanks, this profile is great! Currently running on Torment 1 at 2.8 legendaries an hour, although the gold and XP rate is pretty bad (I'm specifically running it for items so I don't really care).

 

[DyingHymn]

Another problem i found is that when the bot is fighting Orlash, the boss may not appear due to the fact that it is invisible unless the player moves around abit; as for the bot, it will only shot in the direction that the boss is that but not being able to trigger the boss fighting

View attachment 126513

A Trinity issue. Not solvable from profile.

 

[DyingHymn]

Thanks, this profile is great! Currently running on Torment 1 at 2.8 legendaries an hour, although the gold and XP rate is pretty bad (I'm specifically running it for items so I don't really care).

Rift is only for legs. xp & gold is below standard.

 

[mixmasta007]

DB issue on startup

i have installed everything the OP said to, and in the order he said to as well with all the settings and this is the log im getting. just continuous game spam about starting over n over. will someone plz help me out. I know HB well but DB is new to me.
View attachment 6696 2014-04-23 23.46.txt

 

[sowlinyin]

Found another location problem....bot looping around in the area



have to Stop db and restart the bot

 

[DyingHymn]

i have installed everything the OP said to, and in the order he said to as well with all the settings and this is the log im getting. just continuous game spam about starting over n over. will someone plz help me out. I know HB well but DB is new to me.
View attachment 126518

Use Trinity as combat routine.