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

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

Hey! I was testing the batch, and i'd a problem. My Diablo & DB don't close when it needs to (schdule & total bot restart), I tried manually "taskkill /im "Diablo III.exe" and works well. Any ideas what could be?
 
Hey! I was testing the batch, and i'd a problem. My Diablo & DB don't close when it needs to (schdule & total bot restart), I tried manually "taskkill /im "Diablo III.exe" and works well. Any ideas what could be?

Hi there,

are you using English OS or OS with other OS language? If you are, I'll need you to tell me what OS you are using. Check your PM and I'll send you the steps to help me solve this for you.
 
DB_Run v2.0b is released~!

Changes: Added more robust error detection. --> Thanks jacker25~! :)
 
DB_Run v2.0c is released~!

Changes: Added an option to start up DB slightly differently for those with plugin problems (not loading properly). --> Thanks GilesSmith and tesslerc :)

Please test this for me... I'm unable to replicate the plugin problem on my end... But this fix should do it...
Remember to set the additional settings in the Configurations Section.
 
Sorry how to do make this work with mutliple clients open?

I tried just copying the batch file and editing the path to my 2nd d3 client copy but it closes the first client thats open if i execute the 2nd batch file
 
Sorry how to do make this work with mutliple clients open?

I tried just copying the batch file and editing the path to my 2nd d3 client copy but it closes the first client thats open if i execute the 2nd batch file

You need to have an individual batch file for each bot.
 
Teivovo its easy to detect, Giles stash plugin fails to load up correctly and salvages EVERYTHING ;( ill try it later and tell u if its fine!
 
Works properly now, gj.
problem is it doesn't save the proper PID for DB atm and it thinks it has crashed making an infinite loop of restarts.
 
Works properly now, gj.
problem is it doesn't save the proper PID for DB atm and it thinks it has crashed making an infinite loop of restarts.

woah~! really?? OK... i'll do something about that. Thanks :)
 
Teivovo its easy to detect, Giles stash plugin fails to load up correctly and salvages EVERYTHING ;( ill try it later and tell u if its fine!

Hmmm... alrighty.. I'll try that out. :)


CHeers~!
 
DB_Run_v2.0d is Released~!

Sorry about the infinite looping of DB_Run. This should fix it~! Thanks for your support ~~ :)
 
This is working great for me now!!

thanks alot

Just a question

Does it also do 120 runs then has a break ? - this is a good thing if it does :)
 
This is working great for me now!!

thanks alot

Just a question

Does it also do 120 runs then has a break ? - this is a good thing if it does :)

Oh yes it does~! :) You can change the 120 to some other value.

Happy that it's working for you ^^ Like the thread if you're happy with this :)


Cheers~!
 
Last edited:
Woah... DB_Run is probably the longest batch file that I've ever written... thanks for everyone's support~! Otherwise this would have died long ago.... ^^ :):)
 
I just found a issue with one of my clients running via the batch file

I came back to check it and it had the dialog box saying Network Disconnect but the batch file did not click ok to get rid of it so it was just sitting there

The cmd line prompt was just saying

Will restart bot afer 100 runs

Will restart bot after 99 runs etc..
 
I just found a issue with one of my clients running via the batch file

I came back to check it and it had the dialog box saying Network Disconnect but the batch file did not click ok to get rid of it so it was just sitting there

The cmd line prompt was just saying

Will restart bot afer 100 runs

Will restart bot after 99 runs etc..

Ah... Yes! That is the correct response of db_run. Please understand that db_run only detects system level errors and not application level. So, for your error, this is an error within d3. So db_run does not take care of that.

Use these plugins: they will take care of almost all application level errors.

1. NotificationOkClick
2. Profile restarter
3. Simple relogger

Once u have these three plugins, everything will be smooth sailing. :)
 
Ah... Yes! That is the correct response of db_run. Please understand that db_run only detects system level errors and not application level. So, for your error, this is an error within d3. So db_run does not take care of that.

Use these plugins: they will take care of almost all application level errors.

1. NotificationOkClick
2. Profile restarter
3. Simple relogger

Once u have these three plugins, everything will be smooth sailing. :)

Man you are very quick to respond and very helpful

Thanks, what was strange is I did have notificationOkclick plugin enable, even that failed that time lol

So if the DB_run only takes care of system errors etc, would it re-log if my internet cuts out and I get booted to the login screen?

if not ill have to get simple-relogger


thanks alot for your help!!!!!!!!!
 
Back
Top