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

Rifter - A Bot for Rifts!

that's actually an excellent idea! :) I think I need to read up on Demonbuddy profiles, so I can make a personal optimized version. Thanks alot for your hard work - appreciated alot.
 
May I ask what feature you are waiting for? Some eyes on the issue may result in other dev assistance.
 
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.
Ok it works, will only need the profile to be opened within the plugins folder now. For those using EZUpdater, same process - add the following in to the EZUpdater.xml file.

NWL, I suggest adding this into the first post to make full use of the SVN update capability. Less headache telling people you have a new update! :)

Code:
    <PluginRepo>
      <PluginName>Rifter</PluginName>
      <RepoName>Rifter</RepoName>
      <RepoURL>http://nwl-svn.googlecode.com/svn/</RepoURL>
      <PluginSourceDirectory>trunk\Rifter</PluginSourceDirectory>
      <Enabled>true</Enabled>
      <LastUpdate>2014-04-17T10:14:01.2821126+08:00</LastUpdate>
    </PluginRepo>
 
Last edited:
Dev's have very little if any interest in this BOT anymore..

They will keep it functional, And dangle the carrot with some new half ass features... But i can assure you requesting a feature is next to pointless.

Ive seen how good the devs can work and how quickly feature requests can be implemented, They are bloody good. However this bot now has little income (no more professional botters)
 
May I ask what feature you are waiting for? Some eyes on the issue may result in other dev assistance.
Mapmarker support for the Rift Guardian, that skull icon thing.

Ok it works, will only need the profile to be opened within the plugins folder now. For those using EZUpdater, same process - add the following in to the EZUpdater.xml file.

NWL, I suggest adding this into the first post to make full use of the SVN update capability. Less headache telling people you have a new update! :)

Code:
    <PluginRepo>
      <PluginName>Rifter</PluginName>
      <RepoName>Rifter</RepoName>
      <RepoURL>http://nwl-svn.googlecode.com/svn/</RepoURL>
      <PluginSourceDirectory>trunk\Rifter</PluginSourceDirectory>
      <Enabled>true</Enabled>
      <LastUpdate>2014-04-17T10:14:01.2821126+08:00</LastUpdate>
    </PluginRepo>

I will add it in, thanks for confirming it. :)

Dev's have very little if any interest in this BOT anymore..

They will keep it functional, And dangle the carrot with some new half ass features... But i can assure you requesting a feature is next to pointless.

Ive seen how good the devs can work and how quickly feature requests can be implemented, They are bloody good. However this bot now has little income (no more professional botters)

I actually think Hearthbuddy is getting a lot of the attention, I noticed yesterday that there is like 3-4 devs posting actively in there. But they post as if they are taking part in making it, so I think that has been taking away from the others until they get that in a good working order.
 
Mapmarker support for the Rift Guardian, that skull icon thing.



I will add it in, thanks for confirming it. :)



I actually think Hearthbuddy is getting a lot of the attention, I noticed yesterday that there is like 3-4 devs posting actively in there. But they post as if they are taking part in making it, so I think that has been taking away from the others until they get that in a good working order.


I said "THIS BOT" as in Deamonbuddy... And you have made my point even more clear - Exactly they are focusing on other bots that make them money.
 
I said "THIS BOT" as in Deamonbuddy... And you have made my point even more clear - Exactly they are focusing on other bots that make them money.
Right I was agreeing with you in a sense, but I think it's a temporary issue.
 
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.

change it to this and it will stay in profiles...much smoother

Code:
<Repository>
      <Kind>[COLOR="#FF0000"]Profile[/COLOR]</Kind>
      <Name>Rifter</Name>
      <RepoName>Rifter</RepoName>
      <RepoURL>http://nwl-svn.googlecode.com/svn/</RepoURL>
      <Enabled>true</Enabled>
      <LastUpdate>2014-04-17T03:19:17.483373Z</LastUpdate>
    </Repository>
 
change it to this and it will stay in profiles...much smoother

Code:
<Repository>
      <Kind>[COLOR="#FF0000"]Profile[/COLOR]</Kind>
      <Name>Rifter</Name>
      <RepoName>Rifter</RepoName>
      <RepoURL>http://nwl-svn.googlecode.com/svn/</RepoURL>
      <Enabled>true</Enabled>
      <LastUpdate>2014-04-17T03:19:17.483373Z</LastUpdate>
    </Repository>
Thanks, had no idea that tag existed. I will add it to main post. :)
 
I believe <PluginRepo> is no longer valid unless u have an old settings file
the newer versions of ezupdater use <Repository> tags....so you will need
Code:
 <Repository>
      <Kind>Profile</Kind>
      <Name>Rifter</Name>
      <RepoName>Rifter</RepoName>
      <RepoURL>https://nwl-svn.googlecode.com/svn/trunk/Rifter/</RepoURL>
      <Enabled>true</Enabled>
      <LastUpdate>2014-04-17T00:16:07.3404276-04:00</LastUpdate>
    </Repository>

I just deleted my plugins and settings file to make sure.
sorry for the hassle NWL
 
I believe <PluginRepo> is no longer valid unless u have an old settings file
the newer versions of ezupdater use <Repository> tags....so you will need
Code:
 <Repository>
      <Kind>Profile</Kind>
      <Name>Rifter</Name>
      <RepoName>Rifter</RepoName>
      <RepoURL>https://nwl-svn.googlecode.com/svn/trunk/Rifter/</RepoURL>
      <Enabled>true</Enabled>
      <LastUpdate>2014-04-17T00:16:07.3404276-04:00</LastUpdate>
    </Repository>

I just deleted my plugins and settings file to make sure.
sorry for the hassle NWL
All good hah, I will update it.
 
Testing .73

It was clearing a pack as the boss spawned. It switched immediatly to boss and killed it, after that it switched back to the pack and it never picked the loot as it recalled due to Boss Killed. Probably a Trinity issue?
 
ahh finally i can write on db forum again without getting "internal server error 500"

my rift bot first did entire rift, killed boss returned to town but then entered same rift
2nd time my rift bot quitted rift without it was being finished
3rd time it finished and left right after boss was dead without pickingup

o.O
 
Hey NoWayLOL(Or Anyone that can give me some feedback), I've been away for a couple days...

Is Core, or Extended working Afkable for long botting sessions now? :) any reported loots per hour now for either one?
 
Hey NoWayLOL(Or Anyone that can give me some feedback), I've been away for a couple days...

Is Core, or Extended working Afkable for long botting sessions now? :) any reported loots per hour now for either one?

Saying about lph, I got average of 2.5-3 lph T2/T3. But, it's not fully AFKable, you need to use this with r-Yar in case it gets stuck somewhere, then r-Yar will reset the whole thing for you.
 
ahh finally i can write on db forum again without getting "internal server error 500"

my rift bot first did entire rift, killed boss returned to town but then entered same rift
2nd time my rift bot quitted rift without it was being finished
3rd time it finished and left right after boss was dead without pickingup

o.O

any1 got some intel towards this issue?
 
Trinity .23 caused this profile to stop working for me. I had to go back to .22. Not sure if anyone else experienced that as well
 
Trinity .23 caused this profile to stop working for me. I had to go back to .22. Not sure if anyone else experienced that as well

Same, it starts to get stuck a lot here and there so I'm doing 3 Musketeers right now waiting for this to be fixed.
 
Back
Top