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

[Beta] Demonbuddy daily beta builds

Status
Not open for further replies.
Sicarius said:
Is the scheduler changed? Before I could select multiple profiles and DB would switch between them but now I can't seem to open scheduler. It highlights in blue but no window opening ...
Click to expand...

Try delete the settings file for the scheduler in the settings folder or Edit it and change all LoadProfile elements to SchedulerLoadProfile
 
bombastic said:
Bot stopping itself is back on #39 :|
Click to expand...
You mean after talking way points ?
I am running smooth with Beta 33, Rads 1.5.1 and Giles 1.6.3

No disconnect after ID for me with beta 33. I believe this because I always have a log of 300 ms ?!! lol..
 
So I thought this was suppose to be fixed many builds ago when the options in settigs popped up. I have it activated to make diablo 3 believe its always the selected window, but its actually doing the OPPOSITE. Its deselecting it. I know I'm suppose to be able to constantly hear the game sound but I can't unless i click the window, in which cause it immediatley deselects it again.
 
Same for me bombastic. Bot stops by itself, are you using Drelog by any chance?? Or vmware
 
Ghibli said:
Same for me bombastic. Bot stops by itself, are you using Drelog by any chance?? Or vmware
Click to expand...
same for me, only happens after using a tp or wp but occurs quite regularly. im not using drelog or vmware.
 
i got a problem: when my bot is dying, then the msg came up "you're dead" but in the background, he is still moving and then: disconnected. didn't seen that before but the problem is on every bot i have. idk why :/
 
Nesox, on this recent build whenever I get the inactive trigger, it will leave the game but will not start the following one.

It stays there "running" but w/o calling next game... it used to happen before, but now its 9 of 10 times.

Rather it just show the bot as stopped or load the next game correctly, since I don't have much time too look they close every time its really sad look its stopped for 2h on menu while it still appears to be "running".

(Got stuck)
[04:23:17.183 N] Inactivity timer tripped! Leaving game
[04:23:17.199 N] Leaving game
[04:23:17.215 D] Navigator.Clear
[04:23:17.215 N] Last run acquired 471637 gold.
(Quited game)
(1h after when I looked it, was still "running" for 1h but no game created so called stop then start again)
[05:18:57.243 D] Start/Stop Button Clicked!
[05:18:57.259 N] Stopping the bot.
[05:18:57.259 D] CurrentBot.Stop()
[05:18:57.259 D] Navigator.Clear()
[05:18:57.259 D] Navigator.Clear
[05:18:57.259 D] TreeHooks.Instance.ClearAll()
[05:18:57.259 D] OnStop event
[05:18:57.259 D] OnStop Event Invoking
[05:18:57.290 N] Bot Thread Ended. Was this requested?
[05:18:58.335 D] Start/Stop Button Clicked!
[05:18:58.335 D] Forcing profile reload.
 
I had two bots running when I went to bed 8 hours ago. One of them was still going strong when I woke up this morning. The other one had gotten a game error and was left at the "send Blizzard the error report" page. I'm going to blame the outdated A1 champion farming profile for that one.
Good build!
 
[07:15:39.572 D] [GilesTrinity] Destructible: Name=a3dun_crater_BonePile-13044. SNO=192867, Range=10,87976. Needed range=10. Radius=1. Type=Destructible. Using power=Weapon_Melee_Instant
[07:15:39.996 D] [RadsAtom] - System.AccessViolationException: Could not read bytes from 00000000 [299]!
bei Zeta.MemoryManagement.ExternalProcessReader.ReadBytes(IntPtr address, Int32 count, Boolean isRelative)
bei Zeta.MemoryManagement.ExternalProcessReader.Read[T](IntPtr address, Boolean isRelative)
bei Zeta.Internals.Actors.DiaObject.()
bei Zeta.Internals.Actors.DiaObject.get_ACDGuid()
bei Zeta.Internals.Actors.DiaObject.get_CommonData()
bei RadsAtom.Functions.Inactivitytimer.isBusy()
[07:15:51.333 D] Navigator.Clear
[07:15:51.393 D] Replaced hook [ProfileOrderBehavior_Hook] dbc849b9-3b01-405c-9daa-f293047cc63c
[07:15:51.393 D] Generating path to Tower of the Cursed Level 2:2A-18 - <1004.612, 1098.036, -8.133423>
[07:15:51.423 D] Successfully generated path from {X=135,Y=78} to {X=151,Y=114} in 00:00:00.0027065 with 37(7) hops
[07:15:51.423 D] Client path generated.
[07:15:51.423 D] Generated path to <1004.612, 1098.036, -8.133423> (Tower of the Cursed Level 2:2A-18) with 7 hops.
[07:15:52.606 D] [GilesTrinity] Destructible: Name=a3dun_crater_BonePile-12857. SNO=192867, Range=10,81431. Needed range=10. Radius=1. Type=Destructible. Using power=Weapon_Melee_Instant
[07:16:05.635 N] Stopping the bot.
[07:16:05.635 D] CurrentBot.Stop()
[07:16:05.635 D] Navigator.Clear()
[07:16:05.635 D] Navigator.Clear
[07:16:05.635 D] TreeHooks.Instance.ClearAll()
[07:16:05.635 D] OnStop event
[07:16:05.635 D] OnStop Event Invoking
[07:16:05.645 D] QuestOrderManager.OnBotStop(). Resetting caches.
[07:16:05.655 D] Resetting current behavior.
[07:16:05.655 D] QuestOrderManager.OnBotStop(). Resetting caches.
[07:16:05.655 D] Resetting current behavior.
[07:16:05.655 D] QuestOrderManager.OnBotStop(). Resetting caches.
[07:16:05.655 D] Resetting current behavior.
[07:16:05.655 D] QuestOrderManager.OnBotStop(). Resetting caches.
[07:16:05.655 D] Resetting current behavior.
[07:16:05.655 D] QuestOrderManager.OnBotStop(). Resetting caches.
[07:16:05.655 D] Resetting current behavior.
[07:16:05.655 D] QuestOrderManager.OnBotStop(). Resetting caches.
[07:16:05.655 D] Resetting current behavior.
[07:16:05.655 D] QuestOrderManager.OnBotStop(). Resetting caches.
[07:16:05.655 D] Resetting current behavior.
[07:16:05.655 D] Calling OnDone() on current behavior. MoveToTag: X: 1004,612, Y: 1098,036, Z: -8,133423, PathPrecision: 0, Position: <1004.612, 1098.036, -8.133423>, UnsafeRandomDistance: 0, Name: Tower of the Cursed Level 2:2A-18, IsDone: False, QuestId: 1, StepId: 0, QuestName: Quest Id: 1, IsDoneCache: False, Behavior: Zeta.TreeSharp.PrioritySelector,
[07:16:05.655 N] Session is invalid!
[07:16:05.674 N] Bot Thread Ended. Was this requested?


newest beta always session invalid after an hour or less
 
Fantas said:
i got a problem: when my bot is dying, then the msg came up "you're dead" but in the background, he is still moving and then: disconnected. didn't seen that before but the problem is on every bot i have. idk why :/
Click to expand...


same here
 
Bot gets stuck in one certain spot at the core. I changed my logging to detailed and then get a bunch of these.

[13:00:54.668 D] QuestOrderManager.OnBotStop(). Resetting caches.
[13:00:54.668 D] Resetting current behavior.
[13:00:54.668 D] QuestOrderManager.OnBotStop(). Resetting caches.
[13:00:54.668 D] Resetting current behavior.
[13:00:54.668 D] Calling OnDone() on current behavior. UseWaypointTag: X: 402.5403, Y: 414.342, Z: 1.5338, Position: <402.5403, 414.342, 1.5338>, WaypointNumber: 10, IsDone: False, QuestId: 1, StepId: 0, QuestName: Quest Id: 1, IsDoneCache: False, Behavior: Zeta.TreeSharp.Decorator,
[13:00:54.668 D] QuestOrderManager.OnBotStop(). Resetting caches.
[13:00:54.668 D] Resetting current behavior.
[13:00:54.668 D] QuestOrderManager.OnBotStop(). Resetting caches.
[13:00:54.668 D] Resetting current behavior.
[13:00:54.669 D] Calling OnDone() on current behavior. UseWaypointTag: X: 402.5403, Y: 414.342, Z: 1.5338, Position: <402.5403, 414.342, 1.5338>, WaypointNumber: 10, IsDone: False, QuestId: 1, StepId: 0, QuestName: Quest Id: 1, IsDoneCache: False, Behavior: Zeta.TreeSharp.Decorator,
[13:00:54.669 D] QuestOrderManager.OnBotStop(). Resetting caches.
[13:00:54.669 D] Resetting current behavior.
[13:00:54.669 D] QuestOrderManager.OnBotStop(). Resetting caches.
[13:00:54.669 D] Resetting current behavior.
[13:00:54.669 D] Calling OnDone() on current behavior. UseWaypointTag: X: 402.5403, Y: 414.342, Z: 1.5338, Position: <402.5403, 414.342, 1.5338>, WaypointNumber: 10, IsDone: False, QuestId: 1, StepId: 0, QuestName: Quest Id: 1, IsDoneCache: False, Behavior: Zeta.TreeSharp.Decorator,
[13:00:54.669 D] QuestOrderManager.OnBotStop(). Resetting caches.
[13:00:54.669 D] Resetting current behavior.
[13:00:54.669 D] QuestOrderManager.OnBotStop(). Resetting caches.
[13:00:54.669 D] Resetting current behavior.
[13:00:54.669 D] QuestOrderManager.OnBotStop(). Resetting caches.
[13:00:54.669 D] Resetting current behavior.
[13:00:54.669 D] QuestOrderManager.OnBotStop(). Resetting caches.
[13:00:54.669 D] Resetting current behavior.
[13:00:54.669 D] QuestOrderManager.OnBotStop(). Resetting caches.
[13:00:54.669 D] Resetting current behavior.
[13:00:54.669 D] Calling OnDone() on current behavior. UseWaypointTag: X: 402.5403, Y: 414.342, Z: 1.5338, Position: <402.5403, 414.342, 1.5338>, WaypointNumber: 10, IsDone: False, QuestId: 1, StepId: 0, QuestName: Quest Id: 1, IsDoneCache: False, Behavior: Zeta.TreeSharp.Decorator,
[13:00:54.669 D] QuestOrderManager.OnBotStop(). Resetting caches.
[13:00:54.669 D] Resetting current behavior.
[13:00:54.669 D] QuestOrderManager.OnBotStop(). Resetting caches.
[13:00:54.669 D] Resetting current behavior.
[13:00:54.670 D] Calling OnDone() on current behavior. UseWaypointTag: X: 402.5403, Y: 414.342, Z: 1.5338, Position: <402.5403, 414.342, 1.5338>, WaypointNumber: 10, IsDone: False, QuestId: 1, StepId: 0, QuestName: Quest Id: 1, IsDoneCache: False, Behavior: Zeta.TreeSharp.Decorator,
[13:00:54.670 D] QuestOrderManager.OnBotStop(). Resetting caches.
[13:00:54.670 D] Resetting current behavior.
[13:00:54.670 D] QuestOrderManager.OnBotStop(). Resetting caches.
[13:00:54.670 D] Resetting current behavior.
[13:00:54.670 D] QuestOrderManager.OnBotStop(). Resetting caches.
[13:00:54.670 D] Resetting current behavior.
[13:00:54.670 D] Calling OnDone() on current behavior. UseWaypointTag: X: 402.5403, Y: 414.342, Z: 1.5338, Position: <402.5403, 414.342, 1.5338>, WaypointNumber: 10, IsDone: False, QuestId: 1, StepId: 0, QuestName: Quest Id: 1, IsDoneCache: False, Behavior: Zeta.TreeSharp.Decorator,
[13:00:54.670 D] QuestOrderManager.OnBotStop(). Resetting caches.
[13:00:54.670 D] Resetting current behavior.
[13:00:54.670 D] QuestOrderManager.OnBotStop(). Resetting caches.
[13:00:54.670 D] Resetting current behavior.
[13:00:54.670 D] Calling OnDone() on current behavior. UseWaypointTag: X: 402.5403, Y: 414.342, Z: 1.5338, Position: <402.5403, 414.342, 1.5338>, WaypointNumber: 10, IsDone: False, QuestId: 1, StepId: 0, QuestName: Quest Id: 1, IsDoneCache: False, Behavior: Zeta.TreeSharp.Decorator,
[13:00:54.721 N] Bot Thread Ended. Was this requested?

http://i46.tinypic.com/2mydts2.png
 
Last edited:
Fantas said:
i got a problem: when my bot is dying, then the msg came up "you're dead" but in the background, he is still moving and then: disconnected. didn't seen that before but the problem is on every bot i have. idk why :/
Click to expand...
This is also happening with 279
 
Woke up this morning with 2 of my 3 bots just standing there because something went wrong with the DB authentication.
 
Nesox really, why u cant make this.. after:

[16:50:40.199 N] Profile completed
[16:50:40.199 N] Number of games completed:1
[16:50:41.353 N] Loaded profile [A3 - Inferno]Champion-Hunting 1.3.6.3 BigRed - Stonefort
[16:50:42.835 N] Using Waypoint Waypoint-55051 Number:1
[16:50:44.691 N] ========== Grid segmentation resetting!!! ============
[16:50:45.924 N] Stopping the bot.
[16:50:45.924 N] Session is invalid!
[16:50:45.986 N] Bot Thread Ended. Was this requested?

bot just should press "Start" button but they dont do that;/
if i press it manualy then its ok but i cant sit 24h/7
 
Download link doesn't work :(

Edit: My fault, sorry, it works ;D
 
Last edited:
nedudej said:
Nesox really, why u cant make this.. after:

[16:50:40.199 N] Profile completed
[16:50:40.199 N] Number of games completed:1
[16:50:41.353 N] Loaded profile [A3 - Inferno]Champion-Hunting 1.3.6.3 BigRed - Stonefort
[16:50:42.835 N] Using Waypoint Waypoint-55051 Number:1
[16:50:44.691 N] ========== Grid segmentation resetting!!! ============
[16:50:45.924 N] Stopping the bot.
[16:50:45.924 N] Session is invalid!
[16:50:45.986 N] Bot Thread Ended. Was this requested?

bot just should press "Start" button but they dont do that;/
if i press it manualy then its ok but i cant sit 24h/7
Click to expand...

this!
 
Status
Not open for further replies.
Back
Top