Rifter - A Bot for Rifts!

[mrbigsexy]

When did I say I wasn't happy? I am happy with it and thankful. But I think of a bot I think it should run itself, not me having to babysit lol. I remember waaay back when I was younger. I played runescape and they had the program for the bots for free, but then the script writers sold their profiles and made quite a bit of money.

There are a lot of profiles available that you can have the bot run and not babysit. Go run the 3 musketeers profile, you can leave it running for 10 days straight and not have to worry about anything.

 

[mrbigsexy]

No, it works much like HaveBounty tag (normally executes what is inside the tag if specified quest/step is currently active otherwise just skips it).
Here is the modified "Rifter Core.xml" I am currently using. View attachment 125313
It solves two major problems I had with your version:
- bot sometimes left prematurely when he found town stone
- and sometimes it didn't detect that boss is dead.

Your XML is working great, thank you for providing this!

 

[NoWayLol]

so the not killing the rift guardian problem and randomly running around problem ist just fixable for the db devs?

For the most part yea, if the boss spawns to far away you can't use MoveToActor because they aren't loaded is my guess. DB needs support for the map marker so I can properly add in support to go toward the boss from any range.

 

[dioxy186]

Getting this error:
[Trinity] Loading new profile.
Failed to load profile: Path to profile element is not valid; file not found
System.IO.FileNotFoundException: Path to profile element is not valid; file not found
File name: 'C:\Users\Brandon's\Desktop\Rifter Core.xml'
at Zeta.Bot.Profile.Profile.Load(String path)
at Zeta.Bot.ProfileManager.Load(String profilePath, Boolean rememberPath)

It just gets really laggy and sits in town. Stop bot + start bot will fix it. Anyone know how to get rid of that? Main issue I've came across with this script.

 

[NoMenko]

Getting this error:
[Trinity] Loading new profile.
Failed to load profile: Path to profile element is not valid; file not found
System.IO.FileNotFoundException: Path to profile element is not valid; file not found
File name: 'C:\Users\Brandon's\Desktop\Rifter Core.xml'
at Zeta.Bot.Profile.Profile.Load(String path)
at Zeta.Bot.ProfileManager.Load(String profilePath, Boolean rememberPath)

It just gets really laggy and sits in town. Stop bot + start bot will fix it. Anyone know how to get rid of that? Main issue I've came across with this script.

did you download it via svn?

 

[myglarn12]

For the most part yea, if the boss spawns to far away you can't use MoveToActor because they aren't loaded is my guess. DB needs support for the map marker so I can properly add in support to go toward the boss from any range.

It feels like im the only one having a issue with blood shards, everytime im capped its trying to tp to town but as blood shards are auto pickup it gets stuck! would really be nice if their is a fix for this, maybe that the bots move a few yards from rift "corpse"? everything else works like a charm and i would like to thank you for making this! (im running latest trinity and beta db)

and i have unchecked the box with "Pickup Blood shards"!

 

[janomaw]

Hello, i the profile and char is not moving at all, in DB gives me non stop msg :

''[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior
[MoveToActor] Timeout of 180 seconds exceeded for Profile Behavior ''

..?

 

[NoMenko]

It feels like im the only one having a issue with blood shards, everytime im capped its trying to tp to town but as blood shards are auto pickup it gets stuck! would really be nice if their is a fix for this, maybe that the bots move a few yards from rift "corpse"? everything else works like a charm and i would like to thank you for making this! (im running latest trinity and beta db)

and i have unchecked the box with "Pickup Blood shards"!

and i have unchecked the box with "Pickup Blood shards"!
???

 

[Fase89]

Hi! I'm trying to download the document with tortoise SVN but when I checkout it will simply do nothing, even though it has worked with other profiles. Would it be too much trouble if you uploaded the file already as XML? I'd really appreciate it.

 

[myglarn12]

and i have unchecked the box with "Pickup Blood shards"!
???

yes, so it wont try to stand there picking them up!

 

[NoWayLol]

Everyone that is having trouble on page 51 of this thread seems to be related to Trinity, make sure you are on the newest version which is 1.8.22, if you have issues make sure to report it in the Trinity thread so they can be fixed.

 

[NoMenko]

ezupdater says 21 is newest

 

[Dotfix]

So is this AFKable over an 8 hour period?

 

[dioxy186]

the bot? or the script? I assume the script, if so, yes.

 

[NoWayLol]

So is this AFKable over an 8 hour period?

Yes and no. I haven't really tested it since the DB update and the Trinity update so I'm not completely sure. Before that it was but it would make mistakes sometimes but could normally correct itself. Got a big update planned but need DB to add something first.

 

[Aznbukake]

My bot keep resetting game without killing Rift guardian. sometimes it leaves at 95%. new to DB bot. i dont know what kind of log to show you my issue. my trinity is 1.8.22. im playing on monk.

--------------------WARNING--------------------
Found town stone but still haven't killed boss.
-Leaving game in 15 seconds, stop if you want.-
--------------------WARNING--------------------
[Trinity] TrinityTownPortal started - clearing area, waitTime=2500, startHealth=502635
[Trinity] Town Portal timer finished
Leaving game, reason: We were unable to complete the Rift.
Last run acquired 166001 gold.
[Trinity] New Game - resetting everything

 

[Karls]

It's afk'able in the sense that it will keep going (at least from my botting experience with it)

But it's not worth afk'ing over long periods imo, because you'll hit blood shard cap pretty quickly. And being not too far can be even better sometimes, to take over yourself when it's about to skip on boss (or give up a well advanced single level rift after finding the stone)

 

[Dotfix]

Yes and no. I haven't really tested it since the DB update and the Trinity update so I'm not completely sure. Before that it was but it would make mistakes sometimes but could normally correct itself. Got a big update planned but need DB to add something first.

I've been tracking this thread a lot as I have been thinking of switching to this. However, I don't want to setup my DB for this if it turns out it doesn't work the way I want it to.

The most common issues here seems to be the bot not killing the boss and shards not being spent / picked up. Furthermore, a problem with the bot not teleporting to town because its trying to pick up shards which it can't because of a full inventory.

Are those issues still present and is a fix coming for them? I think having a script to purchase items for shards is a feature that is highly sought after, as I'd imagine a person would be missing out on quite a lot of shards if they ran it over a night.

 

[Aznbukake]

i ran it for 4hrs on T2. i lost over 100+ keys and only got about 50 something shards. wtf. obviously the bot just return to town without killing boss and reset then do over again. wasted my fcking keys.

 

[Reckiit]

I noticed that the bot will report print out this warning even after it has killed the boss. It doesn't return to town to talk to Orek, just leaves.

--------------------WARNING--------------------
Found town stone but still haven't killed boss.
-Leaving game in 15 seconds, stop if you want.-
--------------------WARNING--------------------