[Profiles] Adventure Mode Bounties - Community Edition

db-bounty-profiles - Revision 130: /trunk

Do I just copy & paste each act 1 quest into its own text document and then combine it all in a folder? (new to this).

 

First post says how to set up SVN. I'd recommend doing that, it makes it a lot easier.

 

I'm doing both bounty's and rifts. It didn't matter what I did that caused the memory leak, but now DB is working again with latest Trinity without the memory leak problem.

 

I understand that, what are you using to do rifts though?

 

This profile. Extended edition.
http://www.thebuddyforum.com/demonbuddy-forum/demonbuddy-profiles/157991-rifter-bot-rifts.html

 

Doing act 1, when porting to weeping hollow, for the bounty of "Kankerrot", the profile tries to load one for "Horrus", then stops the bot.

 

Is this still necessary with the .22 release of Trinity?

 

Failed to load profile: Element HaveBounty is not supported. Please check your XML and try again. (<HaveBounty questId="369944">
<LoadProfile file="369944_the_cursed_cellar.xml" />
</HaveBounty>) Line 15
System.Exception: Element HaveBounty is not supported. Please check your XML and try again. (<HaveBounty questId="369944">
<LoadProfile file="369944_the_cursed_cellar.xml" />
</HaveBounty>) Line 15
at ..
(PropertyInfo , XElement , Object )
at Zeta.XmlEngine.XmlEngine.Load(Object obj, XElement element)
at ..
(XElement , Type )
at ..
.
(XElement )
at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
at ..
(XElement , PropertyInfo )
at ..
(PropertyInfo , XElement , Object )
at Zeta.XmlEngine.XmlEngine.Load(Object obj, XElement element)
at Zeta.Bot.Profile.Profile.Load(XElement element, String path)
at Zeta.Bot.Profile.Profile.Load(String path)
at Zeta.Bot.ProfileManager.Load(String profilePath, Boolean rememberPath)

 

There's an error message

1. it's still wandering after bounty completion (silver spire lvl1)
2. it activates CCs and runs away if they are not part of the quest
3. it clicks furiously on protected cursed chests instead of fighting the event creeps

 

You do not have Trinity updated and/or enabled.

 

Looking into it, Kankerott and Horrus are the same quest with different BountyIds so i tried to merge them into one file, sounds like i messed that up.

 

If you have a HaveBounty in there, that will cause problems since they have different IDs.

 

Keep getting no return on bounties, Bot will spam make and leave game because it finds no bounties. Most recent version of trinity have tried with .19 /.20 / .22 all the same problem tried both demonbuddy and demonbuddy beta both have the same issue

Act 4 Bounties
[BountyProfile] Initializing cache!
[BountyProfile] Active Bounty returned null during init, hope that is OK
Checking if we have all bounties complete
[BountyProfile] Bounties complete returned null.
Leaving game, reason: No more bounties that we can do. Resetting game.
Last run acquired 0 gold.
[Trinity] New Game - resetting everything
Waiting 2 seconds before next game...

 

@Sychotix Loving the profile as always, collecting me some more keys for testing my stuff out. Much afk, such bounties, wow!

Also grats on 600 posts.

 

can anyone report what is ACT1 current state.


been running ACT4 very smoothly, 100% afk.

 

Delete BountyProfile's plugin. It is no longer used.

@iPanda, it is working fairly well. If you have gold inactivity enabled, feel free to run it. It isn't 100% AFKable, but gold inactivity should fix any problems it runs into with time.

 

First thanks for the profil dude!
<GameParams act="OpenWorld" difficulty="Master" resumeFromSave="False" isPrivate="True" numGames="-1" />
But he set it auto to normal why?

 

I already deleted it. and im still getting these errors

Edit: solved it with new install

 

Change your difficulty in Settings > Bot on DB not in the profile itself.

 

Oh really? You sure about that? Because NOTHING else uses [BountyProfile] at the start of the log. If you can't figure out what the problem is, please do a fresh install and that will fix your problem.