What's new
  • 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!

[Profiles] Adventure Mode Bounties - Community Edition

Status
Not open for further replies.
@sychotix I noticed on the Bounty List for "The Matriarch's Bones" the note is how to find out which one is the right one. In my experience from playing as many bounties as I have by hand, it's always been top left Crypt from waypoint, every single time. This could however be extremely high luck, but I doubt it. Figured I'd throw it in there to help you progress on this.
 
@sychotix I noticed on the Bounty List for "The Matriarch's Bones" the note is how to find out which one is the right one. In my experience from playing as many bounties as I have by hand, it's always been top left Crypt from waypoint, every single time. This could however be extremely high luck, but I doubt it. Figured I'd throw it in there to help you progress on this.

That is actually where it was for me as well. Maybe it isn't random, which would make it much easier to do that quest.
 
That is actually where it was for me as well. Maybe it isn't random, which would make it much easier to do that quest.

I've found a lot of things in adventure are no where near as random as story, so it probably is static.
 
I'm not sure what causes the performance issues, I'm pretty sure it's the caching (from both this plugin and trinity) as I've had less/shorter hanging when running DB as admin. (win7)

I've never had that issue with the diablo profile but I'm also pretty sure it's related to the caching/hanging where the cache ends up being nulled or incorrect.

Cursed chest is strange, the ID of the chests are different, but until you start the non-bounty chest it uses the same ID as the bounty chest. It didn't happen often enough for me to test it fully for a fix.


I'm hoping that someone more proficient in writing profiles can spot a way around this. Maybe I can blacklist the area that it spawns or something, not sure.


Anyone having 'path too long' errors:
That is an OS issue, the directory your DB (or the profile you are accessing) is in exceeds the built in character limit. Move it to a directory closer to root and you should be fine.
Zimble,

Another one for you buddy.

Bounty: Kill Pyres the Damned (Silver Spire Level 1): Bot wil port to Silver Spire Level 1 and then TP back to town claiming the bounty is finished.
 
My bot is still not collecting on the cache

It says resetting game because there is no more bounties to complete. The bot will kill the last boss ie: diablo thrn to town where my bot wl be hit with a massive lag attack. Then the game just leaves


Could it have something to do with db beta collecting too much
Cache memory?
 
Zimble,

Another one for you buddy.

Bounty: Kill Pyres the Damned (Silver Spire Level 1): Bot wil port to Silver Spire Level 1 and then TP back to town claiming the bounty is finished.

Hmm, are you using beta and trinity .18 etc.? My logs show no hitches doing pyres the damned.

My bot is still not collecting on the cache
It says resetting game because there is no more bounties to complete. The bot will kill the last boss ie: diablo thrn to town where my bot wl be hit with a massive lag attack. Then the game just leaves
Could it have something to do with db beta collecting too much
Cache memory?

Try increasing the wait timers in Profile.xml near the end, you might just be lagging through the tag. I used to have that issue sometimes before I started using Beta.
 
Hmm, are you using beta and trinity .18 etc.? My logs show no hitches doing pyres the damned.
Ah, yes. I am on Trinity .17 perhaps that's causing problems. Will update it now and let you know.
 
Amazing work, here's a little feedback from what I've tested so far;

Act 4 - Kill Izual doesn't start exploring the area automatically when the bot portals in. If I manually move my character to some mobs, the bot will continue running the profile.
 
any word on the town run script?
Town run doesn't work on Act1 because of DB, not these plugins/profiles.
You can see here that in DB 363 they fixed all Town Runs, Act1 just hasn't worked very well if at all since.
 
Hmm, are you using beta and trinity .18 etc.? My logs show no hitches doing pyres the damned.



Try increasing the wait timers in Profile.xml near the end, you might just be lagging through the tag. I used to have that issue sometimes before I started using Beta.
Yep, Trinity .18 seems to have solved it.
 
Amazing work, here's a little feedback from what I've tested so far;

Act 4 - Kill Izual doesn't start exploring the area automatically when the bot portals in. If I manually move my character to some mobs, the bot will continue running the profile.

That is almost a direct rip of rrrix's act 4 questing profile, and I have no experienced this in any way. Do you mean it doesn't explore Spire lvl 1 till you move?
 
@Kidrobot
@Zimble

That could be due to Trinity Trash/Elite pull distance, could it not?
 
@Kidrobot
@Zimble

That could be due to Trinity Trash/Elite pull distance, could it not?

That's what I was thinking, if your distances are extraordinarily low, but it has no effect on the actual exploration of the zone if he's talking about spire lvl 1 and not the actual boss level.

The most important thing is that you are using DB Beta .371+ and trinity .18.
 
Last edited:
@ NoWayLol there is a work around for it so it isn't a town run to act 1 just to another act it was posted a few pages back and i understand it is a trinity/db problem not in this script
 
That's what I was thinking, if your distances are extraordinarily low, but it has no effect on the actual exploration of the zone if he's talking about spire lvl 1 and not the actual boss level.
Just watched mine do it no problem. So I'm unsure really, I still think pull distance could be in play.
 
Status
Not open for further replies.
Back
Top