[Release] Demonbuddy Release Thread

works very fine,thanks!

 

I can't imagine that it's the profile making D3 crash.
I allso got a crash like 5 seconds after starting DB.

The error was frome Diablo 3 tho, but didn't wrote down the error code.

 

MagicMissile (Seeker) : NOC
ArcaneOrb (Obliteration) : NOC
WaveOfForce (Forceful wave) : XMNY >= 1
Familiar (Sparkflint) : ENS = 300
DiamondSkin (Crystal Shell) : ENS = 15 (Might be changed)
MagicWeapon (Force Weapon) : ENS = 180

 

Well, the changelog looks sweet... hope you guys fix the crashes.
BTW did the FPS issues @ Core of Arreat ever get fixed?

 

i bet they are already working on a solution to the crashing problem

 

Wow, just updated to .99 and farming sarkoth with my barb has gotten 100% better.. TY!

 

Doesn't seem to help anything, still get stuck issues with "Waiting for path request to finish"

 

Crashing in 30secs after launch ...

 

Well, I thought the pathing issue was fixed.. But now we get crashing + stuck trying to figure a path forever. I let it sit for a few minutes trying to generate a path, when I realized it wasn't going to I clicked Stop, and immediately clicked Start and it figured the path immediately and resumed what it was doing. Don't understand how it can not get the path one minute, get stuck trying to figure it out, and then when restarted it just goes along its way like nothing happened. Diagnostic log included.

 

Awwwww :'(
If this didn't get fixed with the server move... /shrug

 

EDIT: Sorry, double post.

 

Crashing as well after only 6 runs..

 

It did for me, the problem now is the crashing of D3.

 

Pathing is the same it seems and just like others I'm experiencing crashes.

Stopped the bot manually after D3 crashed.

 

switch to default loot rules, it works for me

 

Pathing didnt get fixed, and now the bot crashes the game every few runs. Just going to stop trying for now.

 

Here's my log for crashes:

https://www.dropbox.com/s/omlqf5ef82a9haf/2012-06-14 23.46.txt

 

No ... not fixed unfortunately. It's bizarre ... if server side load were the problem, I would not expect a stop/start of the bot to fix it ... or just moving it further along manually to fix it either. It seems more like you end up standing in a particular location from which the navigation engine cannot produce a valid path. It's very strange, but surely doesn't seem load related.

Who knows ... I'm sure they will get it resolved soon enough.

 

Omg thank you! Not a single hickup:d:d:d

 

on another thread...