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

[Batch File] DB_Run: Command-line based Anti-Crash and Relogger

Do these lines kill ALL of the diablo processes currently open?

How do I adjust this so that one batch file only pertains to that one set of Diablo/DB that I want to affect (since I have no crashes whatsoever with basic profiles, only AGB) ?

ECHO Killing Diablo
taskkill /im "Diablo III.exe"
ECHO Killing Demonbuddy
taskkill /im "Demonbuddy.exe"
 
jeff_skilling said:
Do these lines kill ALL of the diablo processes currently open?

How do I adjust this so that one batch file only pertains to that one set of Diablo/DB that I want to affect (since I have no crashes whatsoever with basic profiles, only AGB) ?

ECHO Killing Diablo
taskkill /im "Diablo III.exe"
ECHO Killing Demonbuddy
taskkill /im "Demonbuddy.exe"
Click to expand...

Have different file names for each set of DB and D3 that you are running :)
 
Just tried it and I see the potential here - I actually wouldn't mind having the bat file run in the background the whole time....

Great work :)

Plus rep
 
However, the issue I am facing is that on restart, it does not autologin, and demonbuddy appears in some sort of Permanent Background state where I can't even bring the demonbuddy window back up by clicking on it....

Here is my command by line: START "DB_Running" "C:\Users\Maria\Desktop\Demonbuddy 1.0.648.160 - C44444\Demonbuddy.exe" -key cxxxxxxxL3W8A7V -bnetaccount [email protected] -bnetpassword hellopassword -d3path="C:\Program Files\Diablo III - Copy (3)\Diablo III.exe" -profile="C:\Users\Maria\Desktop\Demonbuddy 1.0.648.160 - C44444\Profiles\AGBLoader\empty.xml" -routine="AGB - Nullcombat" -autostart -noflash


Any ideas why it's not logging in and Demonbuddy isn't in it's proper state?
 
jeff_skilling said:
However, the issue I am facing is that on restart, it does not autologin, and demonbuddy appears in some sort of Permanent Background state where I can't even bring the demonbuddy window back up by clicking on it....

Here is my command by line: START "DB_Running" "C:\Users\Maria\Desktop\Demonbuddy 1.0.648.160 - C44444\Demonbuddy.exe" -key cxxxxxxxL3W8A7V -bnetaccount [email protected] -bnetpassword hellopassword -d3path="C:\Program Files\Diablo III - Copy (3)\Diablo III.exe" -profile="C:\Users\Maria\Desktop\Demonbuddy 1.0.648.160 - C44444\Profiles\AGBLoader\empty.xml" -routine="AGB - Nullcombat" -autostart -noflash


Any ideas why it's not logging in and Demonbuddy isn't in it's proper state?
Click to expand...


Hi jeff_skilling, from what i understand from your message is that the first run is ok? the next run is when the problem comes in? Try restarting your pc... sounds weird, but it sometimes work. Next thing you could check is the setting inside task scheduler (I'm assuming you're using that...) in the task properties, under the settings tab, check that "Stop the existing instance" is selected in the bottom most drop down list box. Also, check that the task is set to run with the highest privileges. Check that the "shortcut" is also set to "Run as administrator".

your command line seems ok. If all else fails, try on a fresh install of DB :)
 
Last edited:
teivovo said:
Hi, you could simulate that. You could set the min_minutes and max_minutes portion of the batch file. Let's say you set it to 30 - 60 minutes. So upon each taskscheduler run of the batch file, it would take a break of anywhere between 30 to 60 minutes.

You could also set a variety of other things inside the task scheduler. Try them to find your liking :) Simulating human "playtime" is totally possible.
Click to expand...
thank you!
 
So is it recommended to stack all bots into one .bat file, or to have a .bat file for every bot/instance?

IE:

ECHO Killing Diablo
taskkill /im "C:\Bot_1\Diablo III.exe"
ECHO Killing Demonbuddy
taskkill /im "C:\Bot_1\Demonbuddy.exe"ECHO Killing Diablo
taskkill /im "C:\Bot_2\Diablo III.exe"
ECHO Killing Demonbuddy
taskkill /im "C:\Bot_2\Demonbuddy.exe"ECHO Killing Diablo
taskkill /im "C:\Bot_3\Diablo III.exe"
ECHO Killing Demonbuddy
taskkill /im "C:\Bot_3\Demonbuddy.exe"ECHO Killing Diablo
taskkill /im "C:\Bot_4\Diablo III.exe"
ECHO Killing Demonbuddy
taskkill /im "C:\Bot_4\Demonbuddy.exe"

in one .bat file


OR

to separate all the bots into their own .bat files?
 
It runs pretty well now, but it somehow leaves Demonbuddy in a state of being minimized so that I can't even 'bring it up' ?


It's running in the background, but looks like I can't bring it to the foreground so I can, say, edit config on AGB or change loot rules?
 
jeff_skilling said:
So is it recommended to stack all bots into one .bat file, or to have a .bat file for every bot/instance?

IE:

ECHO Killing Diablo
taskkill /im "C:\Bot_1\Diablo III.exe"
ECHO Killing Demonbuddy
taskkill /im "C:\Bot_1\Demonbuddy.exe"ECHO Killing Diablo
taskkill /im "C:\Bot_2\Diablo III.exe"
ECHO Killing Demonbuddy
taskkill /im "C:\Bot_2\Demonbuddy.exe"ECHO Killing Diablo
taskkill /im "C:\Bot_3\Diablo III.exe"
ECHO Killing Demonbuddy
taskkill /im "C:\Bot_3\Demonbuddy.exe"ECHO Killing Diablo
taskkill /im "C:\Bot_4\Diablo III.exe"
ECHO Killing Demonbuddy
taskkill /im "C:\Bot_4\Demonbuddy.exe"

in one .bat file


OR

to separate all the bots into their own .bat files?
Click to expand...

Separate the bots into their own batch files please... Also, the executable files must be different names too. e.g: Diablo IIIA.exe Diablo IIIB.exe DemonbuddyA.exe, DemonbuddyB.exe, etc. They must all have unique names.
 
jeff_skilling said:
It runs pretty well now, but it somehow leaves Demonbuddy in a state of being minimized so that I can't even 'bring it up' ?


It's running in the background, but looks like I can't bring it to the foreground so I can, say, edit config on AGB or change loot rules?
Click to expand...

This is has something to do with DB. I had this problem previously on win7. What I did was simple: Left Click on the DB icon on the taskbar below to select it. Then press "Alt + Spacebar". A context menu will appear in the top left corner of the screen. Choose Maximize and tadah... your DB window will open full screen. In order to bring it back to windowed mode, click hold and drag Demonbuddy's title bar towards the centre of the screen and it will become a regular sized window again.

I have only tried this is Win7, btw...
 
Hi guys, I've looked into the Buddy Auth releasing of sessions request that some of you requested.

And the solution is very simple....

According to the devs, Buddy Auth will only keep the session locked for 2 minutes. After 2 mins, if there is no activity on the session, it will be released automatically by the authentication server. So....

All you need to do is to have min_minutes set to anything more than 2 mins, that will be fine. I think to be on the safe side, anywhere from 5 mins and above is good.

Usually there will be no such problem as the script will graciously shutdown DB and D3. It will only forcefully shutdown DB in the event of "NOT RESPONDING" --> which could possibly cause the session locks. But gracious shutdown will not lock the session. Actually this was mentioned somewhere earlier in this thread. :)


Cheers~!
 
Last edited:
Hi guys, I actually have a way to randomly rotate profiles at each execution of DB_run but will be a real bitch to setup. Would you guys prefer to try it in the next version? Or are you guys happy with whatever you are using now?

Just wondering :)
 
hey guys,

my problem is, that every time i had an internet disconnect, he only close d3 and leaves DB open...and after that nothing happens...he just continue with the "1 min controll"-process and says its all fine. D3 will stay in loginscreen. Any idea whats the problem?
 
masterjeff said:
hey guys,

my problem is, that every time i had an internet disconnect, he only close d3 and leaves DB open...and after that nothing happens...he just continue with the "1 min controll"-process and says its all fine. D3 will stay in loginscreen. Any idea whats the problem?
Click to expand...

Hmm... this should not be happening... can you set your DB log level to Diagnotistic, then simulate your Internet Disconnect? Lemme take a look at your log file and if you could, describe in detail what's going on during the restarts.


Cheers~!
 
teivovo said:
Hmm... this should not be happening... can you set your DB log level to Diagnotistic, then simulate your Internet Disconnect? Lemme take a look at your log file and if you could, describe in detail what's going on during the restarts.


Cheers~!
Click to expand...

i think its because if have two acc boting...if one d3 is still there and other acc freezed nothing happens, cause your batch thinks its allright ^^ MMhhh...how to solve this problem...trying rename the exe's dont work, cause DB wont start then, cause he cant find "diablo3.exe"...
 
masterjeff said:
i think its because if have two acc boting...if one d3 is still there and other acc freezed nothing happens, cause your batch thinks its allright ^^ MMhhh...how to solve this problem...trying rename the exe's dont work, cause DB wont start then, cause he cant find "diablo3.exe"...
Click to expand...

Run VMPlayer? :) Free and good~!

Edit: I think I do have a solution for this.. Gimme a while...
 
Last edited:
teivovo said:
Run VMPlayer? :) Free and good~!

Edit: I think I do have a solution for this.. Gimme a while...
Click to expand...

A very stresfull solution for the performance, isnt it? I dont like the idea to run a vm just because of 1 bot.

Maybe this works?
ECHO Killing Diablo
taskkill /im "C:\Bot_1\Diablo III.exe"
ECHO Killing Demonbuddy
taskkill /im "C:\Bot_1\Demonbuddy.exe"ECHO Killing Diablo
taskkill /im "C:\Bot_2\Diablo III.exe"
ECHO Killing Demonbuddy
taskkill /im "C:\Bot_2\Demonbuddy.exe"ECHO Killing Diablo
taskkill /im "C:\Bot_3\Diablo III.exe"
ECHO Killing Demonbuddy
taskkill /im "C:\Bot_3\Demonbuddy.exe"ECHO Killing Diablo
taskkill /im "C:\Bot_4\Diablo III.exe"
ECHO Killing Demonbuddy
taskkill /im "C:\Bot_4\Demonbuddy.exe"
Click to expand...
 
You must log in or register to reply here.
Back
Top