[Release] Demonbuddy - Swinging Wednesday build (#282)

I have been using the profile switcher with my own profiles and some modified (merged) ciggarc profiles and they work fine. Too many problems looping with rads atom, and it always runs profiles in the same order. Both of these are deal breakers as far as I am concerned. Now the question is, will the new tags support the Continue profile or nextProfile tags, or will multi-part profiles need to be merged?

 

profile switchers adds better customizable randomization. ie: setting battlefields/barracks, fos, sky, stone, rakkis, underbridge all random, then everythinig else from tower in order. If you choose to skip Cydaea, you can opt to also randomize damned and cursed towers, Core and Azmo. But imo, first 6 maps which is randomized all the time is good enough.

 

everytime I tried to start db i get this message :

 

so is the session invalid and auth fixed on this build???

or...????

 

Im getting

Code:

Exception during scheduling Pulse: System.NullReferenceException: Object reference not set to an instance of an object.
   at Zeta.CommonBot.ProfileOrderManager.
(IEnumerable`1 )
   at Zeta.CommonBot.ProfileOrderManager.UpdateCurrentBehavior()
   at Zeta.CommonBot.ProfileManager.UpdateCurrentProfileBehavior()
   at Zeta.CommonBot.Logic.OrderBot.
(Object , EventArgs )
   at Zeta.CommonBot.Logic.BrainBehavior.()

On last build 281. Just stands there doesn't do anything.
No plugins.

 

I was checking my toon, and *again*, it was stoped standing still.

When I check the logs... "could not connect to nav server"

 

same with me...

was there an update with their load balancing on their servers?

 

exact same issue
with this profile
[A3 - Inferno]Champion-Hunting 1.3.6.3 BigRed

 

@Nesox can you pls take a look at DB's inactivity timer because its not working.. when the inactivity timer kicks in and DB leaves a game afterwards it will just idle in main menu and not proceed to create a new game.
The inactivity timer in general could really use a work over in how it detects inactivity

 

I'm not using rads herpaderpa because I don't like that its throwing exceptions left and right. I posted you the log from the inactivity timer fuckup last night in the beta thread..

 

I changed all the profiles to use your random LoadProfile tag instead of rads, but I ran into an issue, you don't have a reload current profile for death handling which the champion farming profiles need. Only options i see are logout and ignore. The champion farming profiles need to reload the current profile everytime it detects the toon died. Please add reloading current profile for death handling option. Then there will be no need for rads plugin.

 

Authentication failed! once again

 

DB can/will reload the profile without any problems. Only difference now using a profile manager vs DB tag is you have the ability to manage what to do on X amount of deaths.

 

I was able to fix that issue with using trinity by adding the following to the profile:

<TrinityMaxDeaths questId="1" max="5" />

 

Not to be rude, but:
Where is the option to have inactivity timer load the next profile?
Where is the option to set max deaths before loading next profile or at least a leave game on death count?

Touting half-functional features as full replacements is not a wonderful thing.
Just saying.

Put those options in and you'll have a fully functional replacement for RadsAtom that will make everybody happy.
Not having them.. makes it necessary to continue using RadsAtom in my opinion.

 

Glad to hear it's on your to-do list, it would make a great core feature

 

RadsAtom is essential, imo. Like devious21 said, we need some of the features db doesn't have yet.

But Rads inactivity time is bugged with current releases, so I disabled it. Now DB can recreate games (don't forget to re-enable db time)