Blizzhackers

No tools or programs.

I have seen recommendations to run in windows and have my .NET Framework and C++ Redistributable installed but same stuff still.

Try as Chrissm22 did and delete the Generic routine

It is now deleted but did not do anything for me :S

Yes, you must run in window mode. Please run the Demonbuddy dependency installer.exe in your bot help folder.

Also, please post the log as there must be something more to that error. Logs are located in bots log folder.

Unfortunately I've also done that as well :S I even uninstalled them before running it then reinstalled and restarted with the same problem, have also reinstalled D3. I don't understand how only I can be getting this issue :S Frustrating.

Running D3 as admin?

Nvm I found your DB thread.

If you use the old method of Auth remove all lines from host file except 127.0.0.1 localhost.


Why? even if its working fine for me, should i delete the other lines?

If it isn't broken don't bother, it's recommended.

Work perfect! thank you so much.

So frustrating, how can everyone be 100% fine when I've followed everything and nothing works :S

Just curious...total nub here

How does the crack work? Are we actually connected to the servers? I ask this because demonbuddy has a tripwire for warden stuff and can kill bots if a known vulnerability. If this tripwire activated, will the cracked version also be shut off? Or does the crack version only trick into thinking that its connected but wont respond?

Cheers!

You aren't actually connecting to the servers. You can block Demonbuddy with firewall and still logs in.


If you're desperate you could always try to run in VM ware.

So, I finally got the bot working a few nights ago, and ever since last night, I'll leave my computer with the bot running just fine, and when I get back to the computer, my D3 & DB are both gone. What is causing this? D:

Theres a new update which stops demonbuddy from authenicating the serial key and it says invalid serial key and which stops the bot from logging in. I had to revert back to the old version.

Diablo is crashing, probably due to a fault in the Demonbuddy release version and Demonbuddy auto closes when Diablo is not running. Try a beta version instead.
http://www.thebuddyforum.com/demonbuddy ... uilds.html




Just tested. Patch2 (2nd method) works just fine as of today and even on DemonbuddyBETA 1.0.1154.70, not sure what update you are referring to, although I didn't try the first method.