What's new
By:
  • Visit Rebornbuddy
  • Visit Resources
  • Visit API Documentation
  • Visit Downloads
  • Visit Portal
  • Visit Panda Profiles
  • Visit LLamamMagic

[Beta] Demonbuddy daily beta builds

Status
Not open for further replies.
I have been running 13 for the past 8 hours without any problems. I used the following plugins: latest trinity, beta radsatom (1.3.8) and latest unsteckme. What I noticed was that trinity logged only 2 stucks in those 8 hours!! I am going to try 14 now for the next 12 hours.
 
I would just like to applaud this initiative! It gives plugin-makers and profile-makers time to adjust their profiles, and it should help in releasing stable versions of DB. Of course a bug can always pop up, but this should get rid of most of them :)
 
I hope i am not breaking in but s the DB beta version Windows 8 compatible?
 
Guys keep in mind the purpose of this thread


"We will be using this to determine if a beta build is good enough to be pushed to as a regular build, feel free to help us test them and give good feedback."


its not a requests thread
 
gotteshand said:
Glad to hear it -1 issue awesome thanks allot.

If you don't mind I'll give you a list of the top 3 things that need to be added / changed to DB
  1. A Gettable and Settable ZetaDia.Me.IsTryingToTownPortal value
  2. Ability to quickly/easily tell what rune each skill has on it
  3. Inactivity Timer changes
Click to expand...

I consider this feedback too, it depends how you look at it.
But it would help plugin creators alot, and the end user will benefit off it (if they use plugins ofc)


Anyway, good job with the new build
 
@nesox expections are still being thrown after world changes (WP use, Portal use, etc) after some testing I found a wait timer between 1000 and 1500 solves this issue so I'd guess depending on hardware it takes time to load new grids and right now DB does not wait for that to finish.. or it does but not long enough.
 
Try using a while loop:
Code: 
<!-- while our WorldID is [B]not[/B] the currentWorldID, keep trying to portal and wait untill finished -->
    <While questId="x" condition="CurrentWorldId != xxxxxx">
     <UseTownPortal questId="x" />
     <WaitTimer questId="x" WaitTime="50" />
    </While>

Maybe that helps to avoid the exceptions?
 
nice version, very stable.
one small bug on the exp monitor: if you bot a low level char than switch to a lvl60 char DB seems to go crazy with the xp (displaying 40 billion/h for me :) )
Hope it helps
 
Tony said:
Guys keep in mind the purpose of this thread


"We will be using this to determine if a beta build is good enough to be pushed to as a regular build, feel free to help us test them and give good feedback."


its not a requests thread
Click to expand...

Ya because the request section is ignored nothing requested has been added in months so ask yourself why would we make a request in the right section and get no response ? At least we know nesox is gonna read it here.
 
New build up!

Changelog #15

  • FallenShaman_B added to the summoner list..
  • Should now always click error dialogs if they appear.
  • FallenShaman_D, crater_HellPortal_Node_Monster added to the summoner list.
  • Now moves a little if still casting town portal after 10 seconds since start when taking tp's to town.
 
#15 is up now, had some issues with the upload stuff
 
#15+trinity 1.6.1.1 runs smoothly for 2 hours. no more interrupts.
seems radsatom is still not compatible with new build.
 
ksmaze said:
#15+trinity 1.6.1.1 runs smoothly for 2 hours. no more interrupts.
seems radsatom is still not compatible with new build.
Click to expand...
That's weird, I'm running with RadsAtom 1.4 and everything is fine so far
 
RadAtom don't work for me too.

try to load profile with infinite loop :(
 
Is there any chance to change the sequence how DB is initializing itself when started for the first time?

I still would love to see this plugin working: http://www.thebuddyforum.com/demonbuddy-forum/plugins/63868-plugin-battle-net-authenticator.html

The problem now is that DB first logs into Diablo after that the plugins are compiled, initialized and enabled

It would be really nice if this could be changed to: First Compile plugins, initialize and enable them so the Authenticator could do its job in detecting the need to Authenticate stuff when logging in
 
Nesox said:
New build up!

Changelog #15

  • FallenShaman_B added to the summoner list..
  • Should now always click error dialogs if they appear.
  • FallenShaman_D, crater_HellPortal_Node_Monster added to the summoner list.
  • Now moves a little if still casting town portal after 10 seconds since start when taking tp's to town.
Click to expand...

Listed changes are working!
 
there is sometimes network disconnect message, which cannot be clicked and cause bot stop. is there a way to solve that?
the log just give nothing special about it.
 
Status
Not open for further replies.
Back
Top