[Beta] Demonbuddy daily beta builds

Nice I'll start testing right away one request though could you include a changelog.txt into each beta build so we know whats been changed and kinda know what to look for specifically and not just general checking..

 

build notes would be beneficial

 

I like this idea, more testing is always good.

I'd reccommend people use the beta version as they normally would WITH plugins etc and see what happens, then if they run into crashes or problems THEN turn off all the plugins (or have a seperate plugin free install dir) and see if no plugins still causes an issue and if so then feedback.

 

First feedback..
DemonbuddyBETA v1.0.1042.12

So far very stable and the problem with z-axis is gone no issues there.. RadsAtom 1.3.8 and such seem to be unable to handle this version for whatever reason I guess some internal changes. But after disabling RadsAtom, reenabling DB's internal inactivity timer and relying on Trinity for profiles it works really really well. Trinity has no problems at all with the new version. After ~1 hour of testing all I can say is that this is the best build in quite some time soo far.. I'll continue testing .. because to early for final judgement after 10+ hour run-time I'll be able to tell for sure.

Also thanks for the changelog it makes testing allot easier.

 

I think we should be using plugins to give feedback.

When this build goes live, everybody is going to use RadsAtom and Trinity so why not test to see if it works in the BETA?

 

because nesox isnt making radsatom or trinity, so if theres issues he wants to isolate it to demonbuddy.

 

I don't think so first testing I'm doing is standalone just DB without any plugins if there is no errors or misbehavior then I'll activate one plugin at a time to see how it does and well Trinity works with the new DB and really really good I might add.. RadsAtom had issues even before so nothing new there just that with this build it throws a few more exceptions but that is not DB's fault. Besides I'm not saying RadsAtom is not working I'm saying its throwing allot of exceptions so I'd refrain from using it until they iron that out.

PS: Can tony or another mod pls keep this thread clean for actual feedback on beta's rather then dumb shit THANKS

 

I am using RadsAtom 1.3.6 (and latest trinity) and it's working great. Death coung is still zero after hour of testing, but I don't knowif that is due to this beta. Allthough nothing else changed.

 

He'll now take the waypoints all the time so no issue there but he wont wait for the new area to fully load causing him to skip one profile entirely and move on to the next if I don't have a wait timer added after waypoint use in the profile.

 

please paragon XP per hour we neeed

 

Waypoint problem still not solved. Without wait timer in profiles not working probably.

 

There part of act3 farming pack..

Code:

		<!-- From Town -->
		<If condition="Zeta.ZetaDia.CurrentWorldId==172909">
			<MoveTo questId="1" x="402.5403" y="414.342" z="1.5338" />
			<WaitTimer questId="1" waitTime="150" />
			<UseWaypoint questId="1" actorId="6442" x="402.5403" y="414.342" z="1.5338" waypointNumber="7" />
				<While condition="Me.IsInTown">
					<WaitTimer WaitTime="50" />
				</While>		
		</If>

this way it works just fine with the loop to wait on completing WP action before proceeding but.. if I remove it like this

Code:

		<!-- From Town -->
		<If condition="Zeta.ZetaDia.CurrentWorldId==172909">
			<MoveTo questId="1" x="402.5403" y="414.342" z="1.5338" />
			<WaitTimer questId="1" waitTime="150" />
			<UseWaypoint questId="1" actorId="6442" x="402.5403" y="414.342" z="1.5338" waypointNumber="7" />	
		</If>

he will skip the profile entirely jump to the next and so one..

 

and still no exp per hour :/

 

No offense to the people asking for paragon exp/H but I think the important stuff should come first. Like this one:
http://www.thebuddyforum.com/demonb...le-zetadia-me-istryingtotownportal-value.html

 

Being able to cast beams like Archon Disintegration continuously in the background is also pretty important. Currently the bot will only do that if diablo's window is focused, otherwise it will only shoot the beam in bursts resulting in a serious loss of dps. Please look into that!