First, thank you Devs for all of your work here. It seems like with the release of the Necromancer you are all quite busy. I'm a long time subscriber and fan of the work you do here. I've been very pleased over the past seasons with the performance of DB (not to say that it's with out flaws, but your attention to bug fixes is noticed and appreciated).
This current season I'm running a Necro (because, duh, Necros are awesome) and I'm experiencing alot of erratic behavior of the bot. Each update release seems to have caused more sever eratic behavior over the past weeks even. I hope describing what I'm seeing and attaching some logs can assist you.
So I'm using 1.1.3197.498 currently. Fresh install with no addons, and as of this update, the prepackaged Rathma Face Roll routine.
Navigation seems really confused for now. The Bot often retraces already explored/cleared areas of the map for no apparent reason. (Shrines are already activated, monsters already cleared, items already retrieved, so why go back?)
At times either the navigation or the combat seems to stick. The Bot stands still while skeles attack a lone mob on the screen. No Mages or Bone Spikes get cast until the skeles lazily finish off the remaining mob and no avoidance seems to take place. This is typically when the bot begins back tracking already explored areas of the map as well.
I'm experiencing a frequent D3 Client Disconnect. Usually happens when I've walked away and return to find that the D3 Client is disconnected so I'm not sure what events lead to this. Possibly time out on the gold find or experience gain, but the Bot is usually just standing in a cleared area of the map.
Also, the last several updates have of course triggered the auto update on DB Launch. Once update completes successfully, it crashes upon launch. This has happened with the 3 most recent updates consistently for me. I have to manually download a fresh install into a new folder to get it going again.
Honestly I've seen other weird behaviors like drop in ticks per second, etc, that I'm not totally recalling right now so I'll just end it here. Curious, before I go uploading tons of logs, what is relevant and what would you like to see?
Thanks again for your efforts,
Debo
This current season I'm running a Necro (because, duh, Necros are awesome) and I'm experiencing alot of erratic behavior of the bot. Each update release seems to have caused more sever eratic behavior over the past weeks even. I hope describing what I'm seeing and attaching some logs can assist you.
So I'm using 1.1.3197.498 currently. Fresh install with no addons, and as of this update, the prepackaged Rathma Face Roll routine.
Navigation seems really confused for now. The Bot often retraces already explored/cleared areas of the map for no apparent reason. (Shrines are already activated, monsters already cleared, items already retrieved, so why go back?)
At times either the navigation or the combat seems to stick. The Bot stands still while skeles attack a lone mob on the screen. No Mages or Bone Spikes get cast until the skeles lazily finish off the remaining mob and no avoidance seems to take place. This is typically when the bot begins back tracking already explored areas of the map as well.
I'm experiencing a frequent D3 Client Disconnect. Usually happens when I've walked away and return to find that the D3 Client is disconnected so I'm not sure what events lead to this. Possibly time out on the gold find or experience gain, but the Bot is usually just standing in a cleared area of the map.
Also, the last several updates have of course triggered the auto update on DB Launch. Once update completes successfully, it crashes upon launch. This has happened with the 3 most recent updates consistently for me. I have to manually download a fresh install into a new folder to get it going again.
Honestly I've seen other weird behaviors like drop in ticks per second, etc, that I'm not totally recalling right now so I'll just end it here. Curious, before I go uploading tons of logs, what is relevant and what would you like to see?
Thanks again for your efforts,
Debo
