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

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

Rift Bot - Yet Another Rifter!

Status
Not open for further replies.
OkseHode i tried your profile/package thing and damn :(
The game gets Network disconnect ALL THE TIME and i know for sure that it is NOT my internet that is the problem...
I never got this error before using your package thing.
Also the bot is acting very weird, like running around itself right on its spot and running back and forth etc. etc...
Also saw it skipping several magic, rare items as well a lot of chests!!

Ah i miss the ol'days when DB was so simple and always worked 100% and there never was any problems of any kind :rolleyes: But im really happy that you try to solve errors and buggs still. Really am!
 
I must be tired... Just read breaking news that this is something at blizzard end of the connection...
Will test again later (Y)
 
Found an interesting fact, alot of times the stuck problem can be resolved by stopping and restarting the bot.
However, it still cannot get the bot to unstuck on this map.

Stuckl.webp

the red spots are the entrance to this level and the final town stone... the bot first got stuck by the stone then it kept on looping within the grey areas after i stop-restarted the bot. Seems like this is one of the problematic maps.
 
Do we need to upgrade to next version all files, or just RiftCommon, RiftExploreCommon and RiftExploreFull?
 
I am not entirly sure what is going on, if it's the Blizzard servers reacting to something and causing me to DC everytime the bot attempts to kill Diablo in the Common-Bounty profile. Tried a fresh install with the package provided in post #2, seems like it still DCing. Happends everytime. I'll post the error in a second.
 
hagert said:
I am not entirly sure what is going on, if it's the Blizzard servers reacting to something and causing me to DC everytime the bot attempts to kill Diablo in the Common-Bounty profile. Tried a fresh install with the package provided in post #2, seems like it still DCing. Happends everytime. I'll post the error in a second.
Click to expand...

Maybe DB-driven. Maybe something wrong with the server.
 
hey DyingHymn,

I was getting stucks every now and then on Southern Highlands with the default explorer settings so I changed em a bit stucks gone..

Code: 
		<If condition="CurrentLevelAreaId == 347562"> <!-- Southern Highlands-->
			<LogMessage quest="1" step="2" output="[Rift Bot] Explore Southern Highlands @ 15/30/0.22" />
			<TrinityExploreRift questId="337492" stepId="1" until="RiftComplete" markerDistance="45" boxSize="15" pathPrecision="30" boxTolerance="0.22"/>

Thats what I'm using also for The Cursed Hold (Warden) we should concider doing a static script rather then using the explorer because he is really really slow and bad dealing with that map.. having a static just rune around the map along the "border" should be enough to get the kills required to spawn the Rift guardian because most of the unique mobs/elites are along the border around the map. Basiclly having it run around and if it then still didn't get enough having him move to the center and from there load the explorer.. or something like it:)

Also getting suck a lot of times on this one: 352713 he is exploring it with [Rift Bot] Explore Catacomb @ 30/30/0.2

ngkK7bs.jpg


Stuck points marked down yellow.
 
Last edited:
gotteshand said:
hey DyingHymn,

I was getting stucks every now and then on Southern Highlands with the default explorer settings so I changed em a bit stucks gone..

Code: 
		<If condition="CurrentLevelAreaId == 347562"> <!-- Southern Highlands-->
			<LogMessage quest="1" step="2" output="[Rift Bot] Explore Southern Highlands @ 15/30/0.22" />
			<TrinityExploreRift questId="337492" stepId="1" until="RiftComplete" markerDistance="45" boxSize="15" pathPrecision="30" boxTolerance="0.22"/>

Thats what I'm using also for The Cursed Hold (Warden) we should concider doing a static script rather then using the explorer because he is really really slow and bad dealing with that map.. having a static just rune around the map along the "border" should be enough to get the kills required to spawn the Rift guardian because most of the unique mobs/elites are along the border around the map. Basiclly having it run around and if it then still didn't get enough having him move to the center and from there load the explorer.. or something like it:)
Click to expand...

Thanks, will be included.

The curse hold has a problem. It has two versions, normal warden one and a super big one. We cannot distinguish them using anything we can get so that is the problem.
 
Trinity .26 is out. Any experienced user can test whether it works better than .25 or comparable with .24? I am currently not able to test them :(
 
Updated my post with another stuck Dying:) For that one I'd recommend box-size 13 tolerance 0.3 but it will need testing I cant test with anything other then wizard. And sadly the explorer seems to behave differently depending on character class not that that makes any sense. I wish more people would start taking down stucks and shit so we can get this completely right one day:)

Yeah we can actually tell the difference by using scene ID.. I used to do that to tell the difference between cursed tower version A/B.. should work for that as well though we gotta test it:) another way would be to look for a specific actor thats only present in one of the two.. there are ways to tell the difference its just a lot of work to find data points allowing us to tell that difference..
 
Last edited:
.26 seems pretty good with DB release. Considering recommending an upgrade. Need more testing tho
 
i get this everytime i try to start it :( can anyone help me?

Loaded profile Rift Bot Common
Game joined, Resetting profile caches.
[Trinity] Clicking UI element Conversation Button (772796416)
=================WARNING=================
Currently Trinity .25 seems not working well with exploration.
I strongly recommend you to downgrade to Trinity .24
If you are using .24 Trinity, just ignore this message.
=================WARNING=================
Stopping the bot. Reason:Failed to locate profile.
Session lasted for: 00:00:24.0399404
Chose Trinity as your combat routine
Bot Thread Ended. Was this requested?

tried fresh install several times. trinity .24 , questtools .45 riftbot 008 and DB .394
 
vindi said:
i get this everytime i try to start it :( can anyone help me?

Loaded profile Rift Bot Common
Game joined, Resetting profile caches.
[Trinity] Clicking UI element Conversation Button (772796416)
=================WARNING=================
Currently Trinity .25 seems not working well with exploration.
I strongly recommend you to downgrade to Trinity .24
If you are using .24 Trinity, just ignore this message.
=================WARNING=================
Stopping the bot. Reason:Failed to locate profile.
Session lasted for: 00:00:24.0399404
Chose Trinity as your combat routine
Bot Thread Ended. Was this requested?

tried fresh install several times. trinity .24 , questtools .45 riftbot 008 and DB .394
Click to expand...

use svn
 
Status
Not open for further replies.
Back
Top