[Beta] Demonbuddy daily beta builds

aabsolutely, they are in the same directory. after changing their tag to continue, the profile works again to me.

 

Explorer seems to be working fine again, except that when exit is a TPStone, he goes there and keep running around the stone until D3 crashes. Pretty funny though.

This is the tag I'm using.
<ExploreArea questId="1" boxTolerance="0.30" boxSize="15" until="ExitFound" exitNameHash="1740006581" leaveWhenFinished="True" />

 

For now: Have to use ObjectFound, and run a UseObjectTag with a custom behaviour/plugin to confirm the dialog.

 

Those who have tried the random explorer, does it still explores already explored areas like before?

 

Just with Stones, because with normal portals ExitFound works flawless.

@Nesox A working TeleportStone builtin OK Clicker would be nice

 

[00:58:47.287 N] DemonbuddyBETA v1.0.1097.42 started
[00:59:05.342 N] Logging in...
[00:59:06.512 N] Error attaching to Diablo III, Reason:System.IO.FileNotFoundException: Could not load file or assembly 'fasmdll_managed, Version=1.0.1097.42, Culture=neutral, PublicKeyToken=f20f8f99ca0718ca' or one of its dependencies. The system cannot find the file specified.
File name: 'fasmdll_managed, Version=1.0.1097.42, Culture=neutral, PublicKeyToken=f20f8f99ca0718ca'
at Zeta.MemoryManagement.ExternalProcessReader..ctor(Process proc)
at Zeta.ZetaDia.TryInitialize(Process proc, String& reason)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

 

still getting afk messages on the latest build not sure why.

 

42 works great, as usuall fresh install, trinity 1.6.3.4, rads atom 1.5.1

AND i dont know whether its just me, but the cpu load decreased immense!

 

42 auth failed very much

 

Tested and working list

• LogMessage tag now works.
• Added CurrentLevelAreaId in ZetaDia.
• ConditionParser now uses the LevelAreaId property in ZetaDia instead of attempting to acess it directly, this should stop the bot from stopping randomly because Me.CurrentScene is null causing it to display the error message NoneType has no member Mesh when evaluating conditions.
• Siege_wallMonster_A_captainAmbush added to the summoner list, wallmonster that spawns demon troopers in stonefort.
• LoadProfile, "file" added "file" as an alias for the profile, eg; <LoadProfile file="" />
• LoadProfile now supports loading a random profile, see example below.
  <LoadProfile loadRandom="True">
  <Profiles>
  <Profile>BigRed_DamnedTower.xml</Profile>
  <Profile>BigRed_ArreatCraterLevel1.xml</Profile>
  <Profile>BigRed_Battlefields.xml</Profile>
  <Profile>BigRed_CoreAzmodan.xml</Profile>
  </Profiles>
  </LoadProfile>
• Issues with if/while tag's not reporting as done when they actually are should be fixed.
• Now waits a little after identifying an item before taking the next to avoid any errors or disconnects.
• Accidental bug that broke the bot fixed
• Added ACD.AnimationState
• Added ACD.CurrentAnimation
• ACD - Added AnimationInfo. Contains information about the current animation being played and the state.
• Updated the SNOPower enumeration
• LoadProfile tag added, let's you load a profile from a profile if you wish to split up your profile into smaller profiles, note: it only check the directory of the current profile for other profiles used in the "profile" attribute. Usage: <LoadProfile profile="SomeProfileHere.xml" />
• LogMessage tag added. example usages:
  "<LogMessage output="I'm a little teacup!" logLevel="Verbose" />" "<LogMessage message="short and stout!" />" "<LogMessage output="here is my handle!" logLevel="Verbose" />".

Not tested list

• Exploring random dungeons and other areas should work properly again.
• No longer places navigable centers outside of the nav grid when creating the dungeon explorer grid.
• No longer deques dungeon explore nodes too soon causing it to run out of nodes or get stuck

Not working / bugged:

• WaitWhile tag added. Example usage: <WaitWhile conditon="not Me.IsInTown" />
• Auth/session invalid should work better in #39 still droping session ...

I've been playing around with it and used it like this <WaitWhile condition="CurrentWorldId==172909" /> for it to wait until new area change is completed.. and its not working its stopping the bot.. throwing errors in logfile.
Even <WaitWhile conditon="not Me.IsInTown" /> isnt working its causing the bot to stop..
here the error log..

Code:

[10:38:03.594 D] Calling OnDone() on current behavior. UseTownPortalTag: IsDone: True, QuestId: 1, StepId: 0, QuestName: Quest Id: 1, IsDoneCache: True, Behavior: Zeta.TreeSharp.PrioritySelector, 
[10:38:03.594 D] Exception during scheduling Pulse: System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
   bei Zeta.Common.ScriptManager.GetCondition(String expression)
   bei Zeta.CommonBot.Profile.Common.WaitWhileTag.GetConditionExec()
   bei Zeta.CommonBot.Profile.Common.WaitWhileTag.get_IsDone()
   bei Zeta.CommonBot.Profile.Composites.IfTag.
(ProfileBehavior )
   bei System.Linq.Enumerable.All[TSource](IEnumerable`1 source, Func`2 predicate)
   bei Zeta.CommonBot.Profile.Composites.IfTag.get_IsDone()
   bei Zeta.CommonBot.Profile.ProfileBehavior.get_IsDoneCache()
   bei Zeta.CommonBot.ProfileOrderManager.
(IEnumerable`1 )
   bei Zeta.CommonBot.ProfileOrderManager.UpdateCurrentBehavior()
   bei Zeta.CommonBot.ProfileManager.UpdateCurrentProfileBehavior()
   bei Zeta.CommonBot.Logic.OrderBot.
(Object , EventArgs )
   bei Zeta.CommonBot.Logic.BrainBehavior.()
[10:38:03.595 N] Bot Thread Ended. Was this requested?

All testing has been conducted with and without plugins.

 

Do you guys still get disconnect when you identify items?

 

_ 1st, thx too Nesox and DB team, for great work they have done

_ Im using Beta # 42, Plugins : RadsAtom 1.5.1 + Trinity 1.6.3.4 ( i think those are newest ). Im running champion farming profile in act 3 ( bid red, i think ), it works pretty good, stabble, and smooth, except ... sometimes i got session invalid ! Is it server side or DB client itself ? That bug happened not frequently, but once every 3-4 hours Hope that bug can be fixed soon, keep going u guys

 

Quoting with the hope that the few of us still getting AFK Flagged can get some help.

 

Bot is still stopping randomly.

 

oh my bad. thanks !

 

yep bot randomly stopping xD

 

yeah, sometimes it's getting stopped

 

Same here, but only on one of my 3 pcs... All running identical db setups, latest giles and rads. Tried with #39 and 42, but it only happens on one PC I have no idea what's causing it.

 

build 279 is stopping also, its not the db version its the auth servers again.