Rifter - A Bot for Rifts!

Is there anyway to make this stop at 500 bloodshards and go and by items from the bloodhshard vendor? And then continue on with the bot? This question might have already been answered but I didn't come across it.

 

I suggest you keep looking, maybe at the post directly before yours

 

Newest version of Bot, Just updated all.
Still getting this:
--------------------WARNING--------------------
Found town stone but still haven't killed boss.
-Leaving game in 15 seconds, stop if you want.-
--------------------WARNING--------------------
Even tho the boss is dead.

Thanks

(Running Core)

 

How to make sure updates are picked up in EZupdater? Do I need to add something in the XML?

 

Hang in there guys, hopefully this time tomorrow a new version will be out and it should work much better.


@byobodybag Do you mean add this profile to EZUpdater? If so I am not sure I haven't tried, SVN is much easier for me. If you mean how to get it to work with QuestTools and Trinity, then it already does.

 

Yes, like adding the URL and repositories in EZupdater settings xml file. I think I found this in page 18.

Code:

<Repository>
      <Kind>Plugin</Kind>
      <Name>Rifter</Name>
      <RepoName>Rifter</RepoName>
      <RepoURL>http://nwl-svn.googlecode.com/svn/</RepoURL>
      <PluginSourceDirectory>trunk\Rifter</PluginSourceDirectory>
      <Enabled>true</Enabled>
      <LastUpdate>2014-04-13T20:53:47.3119418Z</LastUpdate>
</Repository>

 

Oh, then yeah give it a go! That needs to be added to DB Main Folder > Settings > EZUpdater > EZUpdater.xml
And you will need to put the Rifter folder inside of your plugins folder I believe, then it should keep it updated, all though I am not 100% sure.

 

Code:

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

On rifter core, this even when guardian is dead. Ports to town without talking to Orek and leaves game.


EDIT: Just realized this has been already reported.

 

Delete that code in the .xml. There are posts that explain it in prior pages.

 

I believe Rifts are the future of long term botting for Diablo 3. Can't wait to see the new changes that are coming to make it even better.

Thank you so much for all your hard work.

 

Uh no. I just checked, the questId and stepId is the same as before and after the boss is killed.

 

The bot sometimes skip picking up Death's Breath and I've seen it move so far away from a legendary that it didn't pick it up. Any suggestions?

 

Works great but a couple of problems (with the latest version)

Using the Core version:
1. Bot kills the boss but continues to roam around the map
2. Bot skips few mobs, gets to 97%, then resets the game, because it can't be arsed to re-sweep the area.

 

Yep got problem with missing some mobs in early Rifts and then running in final rift looking for more. Other then that itf a great thing.

 

I think a function that lets bot exploring full map is necessary for this profile, at least for 'Rifter-extended'.
There are few occasions (actually quite frequently) that bot does not explore full map, do not meet boss and leaves the game.
It's nice that the bot is directly finding the exit (I don't even know how it does that, but it's pretty amazing), but I think it actually cause the run to become longer as a result, considering that it misses the boss, portal to town, talk to Olek, wait for 30 seconds till re-entering back to the rift and do the run all over again. Plus, it doesn't heart to fight extra mobs, unless backtracking and gets lost

So.. any idea about this?

 

Also, though it might be a trinity issue, the bot seem to miss a lot of chests. If I'm running this for legendaries I certainly would have the bot pick up all the chests.

 

Trinity handles looting with loot radius input from the main DB settings, so not a problem with this profile. Check your loot radius in DB settings and your wait time for looting in Trinity. I think that if your kill radius is higher than your loot radius then when the bot kills something but other enemies are in range sometimes it will move to the edge of kill radius to attack enemies, moving the stuff that previously dropped out of your loot radius.

This is a known issue. In the recent DB update (yesterday) Nesox added API for rift boss mapmarker, so when NWL releases his new version tonight/tomorrow it will know when the rift boss has been killed. Right now if you get a rift boss it will kill it without registering it was killed, so it continues to explore the map 'looking' for the rift boss. On the flip side if you get to the end and you haven't killed the rift boss it will assume you have and teleport out.

Be patient and it will be solved soon

DB/Trinity issue. Check settings and make sure you have open all chests/loot radius high.

 

This profile is awesome, the only downside is that bot will try to finish whole rift till portal even if you set to finish rift after killing the boss. Keep up the good work!

 

Is there any reasons why the bot should not trigger gold inactivity even if i set it up? I just left my bot run for 2 hours and noticed once i came back it was running around in the big ass prison doing nothing ?

 

I have it on max. The problem seems to be bigger on certain levels like the Pandemonium Fortress. Even though Trinity handles these things I would imagine some tweaks could be applied to the profiles for each maps to help? Anyway just my observation