The new Demonbuddy

[Xilana]

The Report isnt important for me!

if they report every 5 runs its okay ;9

Important is that they run stable!

 

[Crown]

I've tried .95, .99, .100, and .118 with all of the working Sarkoth profiles, and various combinations of plugins and they all have different types of defects but what they all share in common that kills botting AFK, is that after quite a few runs it will just pause at the character screen and just sit there, forever.

EDIT: Forgot to mention .125, but I'm sure everyone is aware of what crap that version is.

runs just perfect for me since more than 24 hours.

 

[ddmisho]

The bot still not as smooth as you promise today is the june 19 2012 and the major problem we have is the Nav server connection.

[02:08:26.440 D] Could not connect to nav server!
[02:08:26.440 D] System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 188.165.14.154:804
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
at System.Net.Sockets.Socket.Connect(IPAddress address, Int32 port)
at (Object , IPAddress , Int32 )
at Zeta.Navigation.DefaultNavigationProvider.(Vector3 dest)

 

[Mr Ekko]

.100 still kickin' )

 

[galizaidypk]

I keep crashing and haven't received the proper support for it. http://www.thebuddyforum.com/demonb.../56351-diablo-3-crashes-after-20-minutes.html

 

[DaSoul]

The bot still not as smooth as you promise today is the june 19 2012 and the major problem we have is the Nav server connection.

[02:08:26.440 D] Could not connect to nav server!
[02:08:26.440 D] System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 188.165.14.154:804
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
at System.Net.Sockets.Socket.Connect(IPAddress address, Int32 port)
at (Object , IPAddress , Int32 )
at Zeta.Navigation.DefaultNavigationProvider.(Vector3 dest)

Hawker already said that they currently implement the pathing into db to make it local. So just wait. Should be released today or tomorrow.

 

[alaerwen]

Hawker already said that they currently implement the pathing into db to make it local. So just wait. Should be released today or tomorrow.

actually, it should be released yesterday. however guys really just wait for it, they are obviously working on it since we got like 15 updates on 10 days, hopefully it will come today.

 

[Xilana]

actually, it should be released yesterday. however guys really just wait for it, they are obviously working on it since we got like 15 updates on 10 days, hopefully it will come today.

Yes i hope it too.
But pls a stable Version

 

[Toney001]

I'm sure it'll come out today, just chill. Had they released it yesterday they'd still have to update today anyway, for the new offsets.

 

[KiLLian]

actually, it should be released yesterday.

Thats what they said

 

[DaSoul]

Thats what they said

I will rather wait another day than get frustrated with a version that doesn't work or only particular works.

 

[micc]

which version has the local nav? or it hasnt come out yet?

 

[DavidKDean]

Local Nav isn't out yet. The newest version is .125. Wait for them to release the newest version for that I believe.