[Beta] Demonbuddy daily beta builds

Yes, I have all waypoints! But my problem was solved few minuts agor when the program auto install a update.

 

Very nice update, will be tested and feed back

 

Windows 8 error:

[20:44:04.995 N] DemonbuddyBETA v1.0.1138.63 started
[20:44:06.822 N] Logging in...
[20:44:07.228 N] Error attaching to Diablo III, Reason:System.Exception: Failed to create device.
at ..
(Int32 )
at ...ctor(MemoryBase mem)
at Zeta.MemoryManagement.ExternalProcessReader..ctor(Process proc)
at Zeta.ZetaDia.TryInitialize(Process proc, String& reason)

 

#62 more stable than #54 ?

G

 

I have been running #63 for over 2 hrs. No problems.

 

has #62 fixed inactivity time not recreating the game sometimes? (not radsatom fault as far as i know, already disabled the entire inactivity time code there and games are not being recreated - build #54)

 

How about having only the newest beta playable, the old ones disabled? This is getting stupid, this BETA thread reads just like the normal release thread. People using older BETA versions cause their more stable lol. Its really not my headach but i had to comment on the fact that we no longer have a beta thread, just 2 release threads.

 

build 63 sucks
wasted a lot of time of my bot

View attachment 2276 2012-10-31 11.30.txt

 

So much this. This may as well be the official release thread.

 

For those w8 users with errors: after installed visualc and netframework all works well

@wutknutsel: i just misclicced the repply with quote button...

 

This is a beta thread, so you are supposed to give constructive feedback on problems, not bitch about it. If you don't like it, stick to the release thread.

 

My 63 crashed once after a radsatom break. After that went all night while I slept no problems. Shut off in morning to let it 'sleep' while Im at work.

 

The rads' atom problem is not fixed yet and notification clicker is not working..

 

Guys, look at this pic! I don`t know what happened, maybe some kind of bug with windows 8.

 

The bug being? I don't see anything wrong with the picture.

 

his gold/hr is on bottom and his xp is on top... numbers switched....

LOL

 

Honestly, this is the BETA testing threads so users can point out their point of view of which version is the most stable, and which bugs they are encountering in order for the developers to fix. So stop bitching or giving stupid comment about this thread.

In my opinion as my last reply, .54 still be the most stable so far. .58 makes the bots unable to move or stuck and .62+ makes the same thing happen.

I guess, the problem is in the build .56 (or .58), I forgot, when Nex was trying to integrate DB with Win8, after that build, everything went wrong.

My opinion is, why don't we just take out the features on that build (after .54 - for db to work with Win8), and keep everything else, let's see what happen next.

Thank for the great work, Nex.

Edit: up to this time, i'm still using .54

 

Still on #54 too

G

 

Been getting some UseWaypoint errors recently, not entirely sure what build it started on either!

A snippet of the log:

Code:

[12:51:24.282 D] Generating path to Moving to use waypoint - <1161.723, 686.8927, 0.1>
[12:51:24.283 D] Waiting for path request to finish...
[12:51:27.464 N] Using Waypoint Waypoint-2232 Number:7
[12:51:28.571 D] Navigator.Clear
[12:51:28.604 N] Using Waypoint Waypoint-2232 Number:7
[12:51:32.319 D] Navigator.Clear
[12:51:32.355 N] Using Waypoint Waypoint-2232 Number:7
[12:51:36.078 D] Navigator.Clear
[12:51:36.116 N] Using Waypoint Waypoint-2232 Number:7
[12:51:39.767 D] Navigator.Clear
[12:51:44.818 N] ========== Grid segmentation resetting!!! ============
[12:51:47.339 N] Using Waypoint Waypoint-2232 Number:7
[12:51:48.498 D] Navigator.Clear
[12:51:51.616 N] Using Waypoint Waypoint-2232 Number:7
[12:51:52.729 D] Navigator.Clear
[12:51:52.742 N] Using Waypoint Waypoint-2232 Number:7
[12:51:56.378 D] Navigator.Clear
[12:51:56.442 N] Using Waypoint Waypoint-2232 Number:7
[12:52:00.070 D] Navigator.Clear
[12:52:00.140 N] Using Waypoint Waypoint-2232 Number:7
[12:52:03.768 D] Navigator.Clear
[12:52:03.874 N] Using Waypoint Waypoint-2232 Number:7
[12:52:07.482 D] Navigator.Clear
[12:52:10.722 N] Using Waypoint Waypoint-2232 Number:7
[12:52:11.832 D] Navigator.Clear
[12:52:11.846 N] Using Waypoint Waypoint-2232 Number:7
[12:52:15.483 D] Navigator.Clear
[12:52:15.500 N] Using Waypoint Waypoint-2232 Number:7
[12:52:19.133 D] Navigator.Clear
[12:52:19.157 N] Using Waypoint Waypoint-2232 Number:7
[12:52:22.833 D] Navigator.Clear
[12:52:22.847 N] Using Waypoint Waypoint-2232 Number:7
[12:52:26.473 D] Navigator.Clear

The profile tag that triggers this seemingly random error is:

Code:

<UseWaypoint questId="101758" stepId="1" waypointNumber="7" x="1161.723" y="686.8927" z="0.1" />

This is for the Waypoint in Core of Arreat, it will jump to the correct destination, however, it will not properly finish, and continue spamming waypoint 7 while at waypoint 7 until the bot is stopped and restarted.

The kicker is this doesn't happen 100% of the time, and sometimes I get a solid 3-4 hours of botting in before the first occurence appears.

EDIT: It should also be noticed that this example isn't the only location it has happened in.

 

Nesox, could we get a Page with all Changelogs combined? So that you can look in which version which feature was implemented, I mean for the beta and for the stables.