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

tren said:
teivovo, you are the man. I got it running now thanks to you!
Now, I'm gonna go through the whole Thread again because I remember reading how someone figured out how to make several bots run with this. I want to run this on all 4 accounts. Will report back again with results. Thx again, awesome contribution
Click to expand...

no problem~! I'm afraid the multibot option is not available at the moment (or more likely not performing very well). I will be releasing the next version capable of controlling its own individual bot package (meaning 1 batch file will control its own D3 and DB). The new version will also be A LOT easier to configure... coz honestly, right now, even I feel its a bitch to configure this... :P


Cheers~!
 
teivovo said:
no problem~! I'm afraid the multibot option is not available at the moment (or more likely not performing very well). I will be releasing the next version capable of controlling its own individual bot package (meaning 1 batch file will control its own D3 and DB). The new version will also be A LOT easier to configure... coz honestly, right now, even I feel its a bitch to configure this... :P


Cheers~!
Click to expand...

Tried running 3 accts, all with their own batch/D3/DB path EACH. No luck :( I got them to all open up but only 1 logged in.
I would put together a setup like jeff explained but it's getting very late, I'll fool with it tomorrow
Thx for the help teivovo, keep us posted on the new version!
 
Hello there, at first I want to thank you for your effort.
Sadly however, here's an issue I have. Wondering what I've done wrong. :eek:

Batch File Path Settings.
::Change the following line to the path of your Demonbuddy working directory. -> Don't ask me why, but it's something required by AGB...
cd d:\Demonbuddy

::Change the following line to suit your needs (Pathing, user accounts, password, keys, etc)
START "DB_Running" "D:\Demonbuddy\Demonbuddy.exe" -key -------------------------- -bnetaccount ----------$----------- -bnetpassword ------$----- -d3path="C:\Program Files (x86)\Diablo III\Diablo III.exe" -profile="D:\Demonbuddy\empty.xml" -routine="AGB - Nullcombat" -autostart -noflash
Click to expand...

[10:08:16.786 N] Demonbuddy v1.0.648.160 started
[10:08:16.819 N] Logging in...
[10:08:17.070 N] Waiting for Diablo III to start
[10:08:25.231 N] Attached to Diablo III with pid: 4908
[10:08:27.631 N] Current bot set to Order Bot
[10:08:27.631 N] Loaded profile empty
[10:08:27.681 N] Chose AGB - Nullcombat as your combat routine.
[10:08:27.901 N] Loaded profile empty
[10:08:28.161 N] Logging into game
[10:08:36.671 N] [AntiIdle v0.6.2] Found Diablo III pid: 4908
[10:08:36.671 N] [AntiIdle v0.6.2] Enabling plugins from last save
[10:08:36.671 N] [AntiIdle] LastState: Profile: D:\Demonbuddy\empty.xml
[10:08:36.671 N] [AntiIdle] LastState: Enabling: AGB.Loader
[10:08:36.671 N] [AntiIdle] LastState: Enabling: AntiIdle v0.6.2
[10:08:36.671 N] [AntiIdle] LastState: Enabling: NotificationOKClick Plugin
[10:08:36.671 N] Enabled AGB
[10:08:36.681 N] [AntiIdle v0.6.2] Loading last saved profile
[10:08:36.681 N] [AntiIdle v0.6.2] Waiting for bot to start
[10:08:36.681 N] [AntiIdle v0.6.2] Bot is running + AntiIdle is running!
[10:08:36.911 N] Loaded profile empty
[10:08:36.911 N] [NotificationOKClick Plugin0.9] Initalized
[10:08:36.911 N] [NotificationOKClick Plugin0.9] Enabled
[10:08:36.911 N] [NotificationOKClick Plugin0.9] Start CheckNotificationUI thread
[10:08:36.921 N] [NotificationOKClick Plugin0.9] Start/Resume button found!!! Wait for next time
[10:08:37.011 N] Creating new game, Params: <Act:A1 Difficulty:Inferno Quest:72095 QuestStep:51 ResumeFromSave:True IsPrivate:True>
[10:08:41.310 N] Game joined, Reloading profile.
[10:08:41.520 N] Loaded profile empty
[10:08:41.550 N] ###################### REPORT ######################
[10:08:41.550 N] Gold: 3--------------
[10:08:41.550 N] Blues: 1
[10:08:41.550 N] Yellows: 0
[10:08:41.550 N] Legendaries: 0
[10:08:41.550 N] Set items: 0
[10:08:41.550 N] ####################################################
Click to expand...

That's it, nothing happening, character doesn't move. After a while AntiIdle activates, teleports to town, restarting game, and then character stays still.

P.S. AGB Config button doesn't work when I running Demonbuddy that way, it's fine however without batch file.
 
Wane said:
Hello there, at first I want to thank you for your effort.
Sadly however, here's an issue I have. Wondering what I've done wrong. :eek:

Batch File Path Settings.




That's it, nothing happening, character doesn't move. After a while AntiIdle activates, teleports to town, restarting game, and then character stays still.

P.S. AGB Config button doesn't work when I running Demonbuddy that way, it's fine however without batch file.
Click to expand...

Hi there, give this a try.
In the batch file replace the cd d:\demonbuddy\ with these two lines:

D:
Cd \demonbuddy

Then give it a try.

Next is to enable notificationokclick plugin.

Lemme know if this works for you :)
 
tren said:
Tried running 3 accts, all with their own batch/D3/DB path EACH. No luck :( I got them to all open up but only 1 logged in.
I would put together a setup like jeff explained but it's getting very late, I'll fool with it tomorrow
Thx for the help teivovo, keep us posted on the new version!
Click to expand...

Sure no problem! Soon... V soon... :)
 
teivovo said:
Hi there, give this a try.
In the batch file replace the cd d:\demonbuddy\ with these two lines:

D:
Cd \demonbuddy

Then give it a try.

Next is to enable notificationokclick plugin.

Lemme know if this works for you :)
Click to expand...

Oh I see now, in order to use "cd", you have to switch to specified disk at first.
And yeah, it worked, thanks. :)
 
I actually have 4 bots on 4 different batch files running right now. Initial execution is good, and it will all automatically start, but a BIG problem I've seen is it is not completely killing dead processes (neither Diablo nor DB), and one error leads to another.....

Here's the code if anyone wants to check it out. I have two AGB and two fast wiz 1.60 running.

@ECHO OFF

:START
cls
::Change the two following parameters
set min_minutes=2
set max_minutes=3
::---------------------------------------------------------------------------
::Do not touch this portion
::---------------------------------------------------------------------------
set /a min_seconds=%min_minutes%*60
set /a max_seconds=%max_minutes%*60
set /a range=(%max_seconds%+1)-%min_seconds%
set /a rand=%random%%%(%range%)+%min_seconds%
set /a timer=%rand%
cls
ECHO.
ECHO ************************************************************
ECHO * DEMONBUDDY RESETTER *
ECHO * ------------------- *
ECHO * Killing any existing Diablo III and Demonbuddy processes *
ECHO ************************************************************
set min_minutes=4
set max_minutes=7
set /a min_seconds=%min_minutes%*60
set /a max_seconds=%max_minutes%*60
set /a range=(%max_seconds%+1)-%min_seconds%
set /a rand=%random%%%(%range%)+%min_seconds%
set /a timer=%rand%
cls
ECHO.
ECHO ************************************************************
ECHO * DEMONBUDDY RESETTER *
ECHO * ------------------- *
ECHO * Killing any existing Diablo III and Demonbuddy processes *
ECHO ************************************************************
ECHO.
ECHO.
ECHO Killing Diablo
taskkill /im "Diablo IIId.exe"
ECHO Killing Demonbuddy
taskkill /im "Demonbuddydh2.exe"
ECHO .
ECHO .
ECHO .
ECHO Done!
ECHO.
ECHO.
ECHO Please be Patient. Waiting for %rand% seconds before starting a fresh run.
ECHO.
timeout /t %timer%
cls
ECHO **************************************
ECHO * Starting Demonbuddy and Diablo III *
ECHO **************************************
ECHO.
ECHO.
ECHO.
ECHO.

::Change the following line to the path of your Demonbuddy working directory. -> Don't ask me why, but it's something required by AGB...
cd C:\Users\Maria\Desktop\Demonbuddy 1.0.648.160 - C44444\

::Change the following line to suit your needs (Pathing, user accounts, password, keys, etc)
START "DB_Running" "C:\Users\Maria\Desktop\Demonbuddy 1.0.648.160 - C44444\Demonbuddydh2.exe" -key xxxxxxxxxxxx-bnetaccount [email protected] -bnetpassword jeff -d3path="C:\Program Files\Diablo III - Copy (3)\Diablo IIId.exe" -profile="C:\Users\Maria\Desktop\Demonbuddy 1.0.648.160 - C44444\Plugins\AGBLoader\empty.xml" -routine="AGB - Nullcombat" -autostart -noflash

ECHO Waiting to commence DB and D3 checks...
timeout /t 300 /NOBREAK


::This portion listens if DB or D3 are not responding. If they are, they will be restarted
::Change the application names if you are not using the defaults
cls
ECHO ******************************************************
ECHO * Listening for Misbehaving Diablo III or Demonbuddy *
ECHO ******************************************************
ECHO.
ECHO.
ECHO.
ECHO.
ECHO Checking in 1 minute.
ECHO.
ECHO ******************************************************
ECHO.
TIMEOUT /T 30 /NOBREAK > NUL 2>&1


:LISTENING
TIMEOUT /T 30 /NOBREAK > NUL 2>&1
ECHO Checking if DB or D3 is NOT RESPONDING...


:CHECKD3
ECHO Diablo III Status...
TASKLIST /FI "IMAGENAME eq Diablo IIId.exe" | findstr "INFO: No tasks are running which match the specified criteria."
IF NOT ERRORLEVEL==1 GOTO :DETECTED
TASKKILL /F /FI "STATUS eq NOT RESPONDING" /IM "Diablo IIId.exe" | FINDSTR SUCCESS > NUL 2>&1
IF NOT ERRORLEVEL==1 GOTO :DETECTED
ECHO OK...


:CHECKDB
ECHO Demonbuddy Status...
TASKLIST /FI "IMAGENAME eq "Demonbuddydh2.exe"" | findstr "INFO: No tasks are running which match the specified criteria."
IF NOT ERRORLEVEL==1 GOTO :DETECTED
TASKKILL /F /FI "STATUS eq NOT RESPONDING" /IM "Demonbuddydh2.exe" | FINDSTR SUCCESS > NUL 2>&1
IF NOT ERRORLEVEL==1 GOTO :DETECTED
ECHO OK...


:CHECKSOK
ECHO.
ECHO All OK. Checking in another 1 minute.
ECHO.
ECHO ******************************************************
ECHO.
TIMEOUT /T 30 /NOBREAK > NUL 2>&1
GOTO LISTENING


:DETECTED
cls
ECHO ******************************************************
ECHO * Error Detected. Restarting the full suite. Standby *
ECHO * Please Wait....................................... *
ECHO ******************************************************
ECHO.
ECHO.
ECHO.
ECHO.
TIMEOUT /T 15 /NOBREAK
GOTO START


:END
 
Killing off dead DB processes is especially unreliable and that causes the whole thing to fuck up.

Also you can see my renaming of the various .exe's there
 
Last edited:
jeff_skilling said:
Killing off dead DB processes is especially unreliable and that causes the whole thing to fuck up.

Also you can see my renaming of the various .exe's there
Click to expand...

Hi jeff,

Kindly try out the updated v1.4. It should solve your problem. Lemme know if you run into other problems yah?


Cheers~!
 
Few questions u talk about profilerestarter do you mean the plugin profilerestarter that is located here in plugin section?

1. Does not detect any in application errors of DB and D3... only OS system level errors --> there are many great plugins that can do this anyway

Soo it only sees if DB/D3 freezes/not respond right? If it's crash with error code it's tough luck?

You say there are other plugins that can do this? Could you please give an example?
 
chrisssj3 said:
Few questions u talk about profilerestarter do you mean the plugin profilerestarter that is located here in plugin section?

1. Does not detect any in application errors of DB and D3... only OS system level errors --> there are many great plugins that can do this anyway

Soo it only sees if DB/D3 freezes/not respond right? If it's crash with error code it's tough luck?

You say there are other plugins that can do this? Could you please give an example?
Click to expand...

Hi chrisssj3,

Firstly, yes, the profilerestarter is the plugin within this plugin section.

Secondly, yes, it will is able to determine if DB or D3 is 1. Not responding 2. Crash with application closure (usually accompanied by the window that asks if you want to reopen D3 or send a report to Blizzard). Crash with error code within D3 itself is not handled by my batch file. Simply put, this batch file detects Application crashes to both D3 and DB and corrects it by restarting them.

As for plugins that handle clicking away of in game error messages, you can try NotificationOKClick. It has yet to fail on me.

I personally use:
1. NotificationOKClick - to handle and clear in-game error and/or message boxes.
2. ProfileRestarter - to do a fresh load of which ever profile I'm running every run.
3. DB_Run - to handle "out of game" errors like D3 dying on me through the night or during office hours. (It checks for application level errors once every 1 minute - can be adjusted to your preferences)
4. Windows Task Scheduler - Controls my per hour restarts of DB_Run. Sort of like a "fail safe". So that if I am not at the pc, should anything happen for god knows what reason, the task scheduler will restart the whole batch file, clearing away whatever "hung" DB and D3 and loads them all over again. So the most it will ever get stuck is 1 hour rather than having that WTF moment when I wake up or get home from work.

I use the above hand in hand and have been able to afk for close to a month now without me requiring any manual intervention. So far, I have yet to come across something that can handle all this in one single package.... so I'm currently sticking with this until I can find one :)

Hope this answers your questions yah?


Cheers bro~! :)
 
Hey thanks for the fast reply. Much appreciated.

1. I thought notification OK click wasn't needed anymore with new DB and was actually part of freezing the game/bot itself? Anyways if your batch really works I guess it doesn't matter that much.
2. Profile restarter- Do i need to config this a certain way or just install and check the plugin box?
4. So you mean it will restart the entire game+ db every hour as a failsafe?

Will try this out as soon as possible :) Is there anyway to know how many times it has frozen/ crashed ? Because I would like to know if it does job correctly?


EDIT:

Oh and what do you mean with amend line 62? Am using AGB.

On line 62 I find:
GOTO DBRUN
 
Last edited:
Does anyone got this running with BuddyStats plugin? I would be glad to hear how u made that one work!
 
So, auto-loggin is not working for alot of people, anyone know the cause of this? What are the settings for those who have this working so well? Running all programs as admnistrator and in compatabilty? I'm running win7 Ult 64 bit and having alot of problems getting this right... >_<
 
Any way to make it attempt to relog back on if you're logged out for whatever reason? I found a few times that my D3 was stuck in the login menu, had to manually relog back on.
 
Excellent, looks like .169 has assignment added:

-windowTitle added. example: -windowTitle="MyBTag #1337 " will set the title of the Demonbuddy window to the string provided.
-attachTitle command line argument added. Looks for the window title of all d3 processes that starts with the provided string eg; "is4" will make the bot attach to the first d3 process it finds that starts with the window title "is4"
 
jeff_skilling said:
Excellent, looks like .169 has assignment added:

-windowTitle added. example: -windowTitle="MyBTag #1337 " will set the title of the Demonbuddy window to the string provided.
-attachTitle command line argument added. Looks for the window title of all d3 processes that starts with the provided string eg; "is4" will make the bot attach to the first d3 process it finds that starts with the window title "is4"
Click to expand...
Jeff do you have this working with isboxer + DB 169? Can't wait to tinker with it when I get home from work :)
 
DTrick said:
omg if this is the only problem and u get this working ill seriously hug you.

-PS: I spoke to Hawker in PM and he stated as i thought it had somthing to do with window titles.

ISBoxer loads their titles with is# hotkey windowname. hes gonna try to get it added with the next patch for DB so IsBoxer users can auto login.
Click to expand...

it just updated on .169...u tried to see how it work yet? i want to get this work too for auto login...thanks im also isboxer user, hit me pm if u can get it to work or post here
 
You must log in or register to reply here.
Back
Top