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

Finally have this running 100% with isboxer thx to tievovo and dtrick. This is the best relogger imo
I have not been able to get any other relogger to work besides this one (Though, i have not tried out Kane's Relogger; he does do excellent work)
An issue that I've encountered that I think I have found the remedy to: When more than one bot+D3 would get restarted, DB did not know which one to latch onto and would therefore not latch onto any D3s at all. Both D3 and DB would still be running, but I would not be logged in, D3 would not be crashed at all just sitting at log in, and DB would just be sitting there waiting to be logged in to run the bot.
I've managed to prevent this from happening.
In the batch file, where the min/max minutes to wait are, I changed them to their own values for each batch file, since I am running 4 accounts, and therefore 4 batch files.
For bot1, i set min and max BOTH to 3mins
For bot2, i set min and max BOTH to 4mins
For bot3, i set min and max BOTH to 5mins
and bot4, i set min and max BOTH to 6 mins
Why do this? Well, that would mean that if each file had to restart at exactly the same time (which happened occasionally), there would be a whole extra 1 minute buffer for d3 to load up and DB to latch on. Whereas before, more than one instance could be loaded up along with more than one DB, and DB wouldnt know which one to latch onto.
This way, my problem is solved and I can bot for as long as i want to.
Ty to tievovo for this excellent creation and dtrick for pioneering the isboxer compatability!!!
 
tren said:
Finally have this running 100% with isboxer thx to tievovo and dtrick. This is the best relogger imo
I have not been able to get any other relogger to work besides this one (Though, i have not tried out Kane's Relogger; he does do excellent work)
An issue that I've encountered that I think I have found the remedy to: When more than one bot+D3 would get restarted, DB did not know which one to latch onto and would therefore not latch onto any D3s at all. Both D3 and DB would still be running, but I would not be logged in, D3 would not be crashed at all just sitting at log in, and DB would just be sitting there waiting to be logged in to run the bot.
I've managed to prevent this from happening.
In the batch file, where the min/max minutes to wait are, I changed them to their own values for each batch file, since I am running 4 accounts, and therefore 4 batch files.
For bot1, i set min and max BOTH to 3mins
For bot2, i set min and max BOTH to 4mins
For bot3, i set min and max BOTH to 5mins
and bot4, i set min and max BOTH to 6 mins
Why do this? Well, that would mean that if each file had to restart at exactly the same time (which happened occasionally), there would be a whole extra 1 minute buffer for d3 to load up and DB to latch on. Whereas before, more than one instance could be loaded up along with more than one DB, and DB wouldnt know which one to latch onto.
This way, my problem is solved and I can bot for as long as i want to.
Ty to tievovo for this excellent creation and dtrick for pioneering the isboxer compatability!!!
Click to expand...

This is probably the fix to my problem as well!!! I also noticed this but made the min/max range bigger like 2 to 7 minutes, so that if 2+ bots stop at the same time it is very unlikely that they would resume at under 30 secs difference. But your way is much cleaner I will give it a go as well :)

I will start running a bot with Kane's DRelog. Tried it a bit and really liked it but the latest version acted weird on me. Will do a fresh install of it and run a comparison on two bots running the same plugins and profiles.
 
Last edited:
hyshakt said:
Ok I had it run all evening just fine, went to bed and maybe 1 hour later something must have happened...

When I woke up all clients were at the login screen. As soon as I typed in my password the bots picked it up again... I am thinking I would need a plugin that would relog me in... I will try AntiIdle again who has this function
Click to expand...

Hi there,

there is this plugin called Simple Relogger. Go do a search for it. It will handle network disconnections. On the first few runs, it tends to crash. But once its configured to start together with DB's startup, it works. :)
 
tren said:
Finally have this running 100% with isboxer thx to tievovo and dtrick. This is the best relogger imo
I have not been able to get any other relogger to work besides this one (Though, i have not tried out Kane's Relogger; he does do excellent work)
An issue that I've encountered that I think I have found the remedy to: When more than one bot+D3 would get restarted, DB did not know which one to latch onto and would therefore not latch onto any D3s at all. Both D3 and DB would still be running, but I would not be logged in, D3 would not be crashed at all just sitting at log in, and DB would just be sitting there waiting to be logged in to run the bot.
I've managed to prevent this from happening.
In the batch file, where the min/max minutes to wait are, I changed them to their own values for each batch file, since I am running 4 accounts, and therefore 4 batch files.
For bot1, i set min and max BOTH to 3mins
For bot2, i set min and max BOTH to 4mins
For bot3, i set min and max BOTH to 5mins
and bot4, i set min and max BOTH to 6 mins
Why do this? Well, that would mean that if each file had to restart at exactly the same time (which happened occasionally), there would be a whole extra 1 minute buffer for d3 to load up and DB to latch on. Whereas before, more than one instance could be loaded up along with more than one DB, and DB wouldnt know which one to latch onto.
This way, my problem is solved and I can bot for as long as i want to.
Ty to tievovo for this excellent creation and dtrick for pioneering the isboxer compatability!!!
Click to expand...

Hey there~!

I'm glad that you managed to get it working... DB_run is actually something very simple and lightweight but it works really well imo.. :)

As for your loading of the ISBoxer profiles, you can use the ISBoxerLoader to load them all sequentially. DTrick is the right guy to advise you on ISBoxer coz he's a big fan of it ^_^



Cheers and happy botting~! :)
 
teivovo said:
Hey there~!

I'm glad that you managed to get it working... DB_run is actually something very simple and lightweight but it works really well imo.. :)

As for your loading of the ISBoxer profiles, you can use the ISBoxerLoader to load them all sequentially. DTrick is the right guy to advise you on ISBoxer coz he's a big fan of it ^_^



Cheers and happy botting~! :)
Click to expand...
yup the isboxerloader is working beautifully :) Ty!
 
hyshakt said:
This is probably the fix to my problem as well!!! I also noticed this but made the min/max range bigger like 2 to 7 minutes, so that if 2+ bots stop at the same time it is very unlikely that they would resume at under 30 secs difference. But your way is much cleaner I will give it a go as well :)

I will start running a bot with Kane's DRelog. Tried it a bit and really liked it but the latest version acted weird on me. Will do a fresh install of it and run a comparison on two bots running the same plugins and profiles.
Click to expand...
let me know if my fix works for you! Also, i am interested on hearing about your experience with DRelog!
 
tren said:
let me know if my fix works for you! Also, i am interested on hearing about your experience with DRelog!
Click to expand...
Well last time I tried using it it would resize and rename my DB and this would mess with the DBs running with DRun script. So I don't think I can have both running together.

So far I really like the simplicity of a scirpt. DRelog looks to be full of features as well, will try it again in a couple updates. edit: newest update fixed my problem it seems, will give it another go on it's own.

Also what do you mean by the ISBoxerloader? The shortcut that will start all slots one after the other?

Anyways got my setup to work so far, and relog when needed using a modified version of ReloggerV1.0.3 I posted my modification in it's topic: http://www.thebuddyforum.com/demonbuddy-forum/plugins/58268-plugin-simple-relogger-4.html#post634210
 
Last edited:
hyshakt said:
Well last time I tried using it it would resize and rename my DB and this would mess with the DBs running with DRun script. So I don't think I can have both running together.

So far I really like the simplicity of a scirpt. DRelog looks to be full of features as well, will try it again in a couple updates. edit: newest update fixed my problem it seems, will give it another go on it's own.

Also what do you mean by the ISBoxerloader? The shortcut that will start all slots one after the other?

Anyways got my setup to work so far, and relog when needed using a modified version of ReloggerV1.0.3 I posted my modification in it's topic: http://www.thebuddyforum.com/demonbuddy-forum/plugins/58268-plugin-simple-relogger-4.html#post634210
Click to expand...

Hi hyshakt,

Lol~! My bad.. I forgot to attach the ISBoxerLoader to the first post for this version. You can find it there now.

It is essentially a very simple batch file that will load the ISBoxer .lnk files sequentially. All you need to do is to set the delay time to cater for the load times of each bot.

I agree that Drelog has tons of features that DB_run will most probably never have. But right now, this still serves its purpose for me and for many others so that's why I'm still supporting it :)

I have seen your modifications with the Simple Relogger... Nice work~! :) I'm using it at the moment and it's great~! :)


Cheers mate~!
 
DB_Run_v1.9c now supports French for our French OS users~! :) --> Thanks wootwoot911~!
 
teivovo said:
Hi hyshakt,

Lol~! My bad.. I forgot to attach the ISBoxerLoader to the first post for this version. You can find it there now.

It is essentially a very simple batch file that will load the ISBoxer .lnk files sequentially. All you need to do is to set the delay time to cater for the load times of each bot.

I agree that Drelog has tons of features that DB_run will most probably never have. But right now, this still serves its purpose for me and for many others so that's why I'm still supporting it :)

I have seen your modifications with the Simple Relogger... Nice work~! :) I'm using it at the moment and it's great~! :)


Cheers mate~!
Click to expand...

Ah ok I remember seeing it in earlier versions :)

Concerning the mod I did to the relogger plugin, it really needs to know if the bot is running or not before hitting resume, or it becomes a pain to stop it for unloading or whatever, easy fix I suppose. It was the ONLY plugin I ran to take care of error messages and connection lost relogs, seemed to work fine. I'll look into a check for bot running status, shouldn't be too hard :P
 
https://www.dropbox.com/s/zel8g3yr7yupq1g/DB_Run_v1_9c_Universal.bat

Edited the newest DB_Run 1.9c.
*Added scheduler - start and stop time.

Currently at work so I can't test it properly
config section is as following:
Code: 
::------------------------------------------------------------------------------
::CONFIGURATIONS: Change ONLY the following parameters (No quotes (") required)
::------------------------------------------------------------------------------

set min_minutes=2
set max_minutes=10
set restart_minutes=120
set D3Name=Diablo III.exe
set DBName=Demonbuddy.exe
set DBDrive=C:
set D3Path=C:\Program Files (x86)\Diablo III\
set DBPath=C:\Users\XXX\Desktop\DemonBuddy160\
set DBKey=5J34AZ7L27N8LK123B
set [email protected]
set BNetPwd=hubabua
set Profile=C:\Users\XXX\Desktop\DemonBuddy\Profiles\Profile.xml
set CombatRoutine=Belphegor All-in-One
[COLOR="#FF0000"]set start_time=05 ----> 24h format - when to start the bot.
set stop_time=23 ----> 24h format - when to stop the bot.[/COLOR]

::---------------------------------------------------------------------------------------
::OPTIONAL CONFIGURATIONS FOR AUTOAUTH AND ISBOXER: (No quotes (") required) 1=On, 0=Off
::---------------------------------------------------------------------------------------

set ISBoxer=0                                
set AutoAuth=1
set ISBoxerLinkName=Bot 1.lnk
set ISBoxerLoadTime=20
set AutoAuthPath=C:\Users\XXX\Desktop\AutoAuth\


::-------------------------------------------------------------------------------------
::CONFIGURATIONS for International OS Language (1=On, 0=Off) - Can only set 1 Language!
::-------------------------------------------------------------------------------------

SET ENGLISH=1
SET GERMAN=0
SET CZECH=0
SET DANISH=0
SET FRENCH=0

known problems
- If you start it between the stop and start time (i.e shouldn't be working time) it will run until it reaches the stop time.
- Start and stop time (at this moment) can only be in hours.


-----------

It runs does usual checks and waits for the stop hour.
Once stop hour arrives it kills all D3 and DB processes and enters a waiting period.

During this waiting period it checks every 30minutes whether or not it is time to start again.
 
tesslerc said:
https://www.dropbox.com/s/zel8g3yr7yupq1g/DB_Run_v1_9c_Universal.bat

Edited the newest DB_Run 1.9c.
*Added scheduler - start and stop time.

Currently at work so I can't test it properly
config section is as following:
Code: 
::------------------------------------------------------------------------------
::CONFIGURATIONS: Change ONLY the following parameters (No quotes (") required)
::------------------------------------------------------------------------------

set min_minutes=2
set max_minutes=10
set restart_minutes=120
set D3Name=Diablo III.exe
set DBName=Demonbuddy.exe
set DBDrive=C:
set D3Path=C:\Program Files (x86)\Diablo III\
set DBPath=C:\Users\XXX\Desktop\DemonBuddy160\
set DBKey=5J34AZ7L27N8LK123B
set [email protected]
set BNetPwd=hubabua
set Profile=C:\Users\XXX\Desktop\DemonBuddy\Profiles\Profile.xml
set CombatRoutine=Belphegor All-in-One
[COLOR="#FF0000"]set start_time=05 ----> 24h format - when to start the bot.
set stop_time=23 ----> 24h format - when to stop the bot.[/COLOR]

::---------------------------------------------------------------------------------------
::OPTIONAL CONFIGURATIONS FOR AUTOAUTH AND ISBOXER: (No quotes (") required) 1=On, 0=Off
::---------------------------------------------------------------------------------------

set ISBoxer=0                                
set AutoAuth=1
set ISBoxerLinkName=Bot 1.lnk
set ISBoxerLoadTime=20
set AutoAuthPath=C:\Users\XXX\Desktop\AutoAuth\


::-------------------------------------------------------------------------------------
::CONFIGURATIONS for International OS Language (1=On, 0=Off) - Can only set 1 Language!
::-------------------------------------------------------------------------------------

SET ENGLISH=1
SET GERMAN=0
SET CZECH=0
SET DANISH=0
SET FRENCH=0

known problems
- If you start it between the stop and start time (i.e shouldn't be working time) it will run until it reaches the stop time.
- Start and stop time (at this moment) can only be in hours.


-----------

It runs does usual checks and waits for the stop hour.
Once stop hour arrives it kills all D3 and DB processes and enters a waiting period.

During this waiting period it checks every 30minutes whether or not it is time to start again.
Click to expand...

This thread is alive again~~!! lol... for a moment I thought it would die out soon...

Btw tesslerc, thanks for your input. Take note that your start time MUST NOT include the leading zero otherwise it may not work. :) Maybe if you don't mind, I can help you refine this and add it into the next version? I also need to add in another type of error check into DB_Run as well. Recently, I have been experiencing DB crashes that keep the DB window open with another windows message box that shows DB has crashed. Not sure if anyone else is experiencing this.


Cheers~! :)
 
teivovo said:
This thread is alive again~~!! lol... for a moment I thought it would die out soon...

Btw tesslerc, thanks for your input. Take note that your start time MUST NOT include the leading zero otherwise it may not work. :) Maybe if you don't mind, I can help you refine this and add it into the next version? I also need to add in another type of error check into DB_Run as well. Recently, I have been experiencing DB crashes that keep the DB window open with another windows message box that shows DB has crashed. Not sure if anyone else is experiencing this.


Cheers~! :)
Click to expand...

Sure do w\e you wish.
I'm thinking of some additional options to add, this was just a quick edit from work - ill add randomization and such l8r on.
 
DB_Run_v2.0
1. Added in a scheduler with randomizer. You can now set your schedule that your bot should run. DB_Run will inject some random minutes so that the start and stop schedule will not be the same --> Thanks tesslerc~! :)

Cheers~!
 
My AGB Profile wont start :( have loaded the empty profile and set the AGB routine can someone help me?
 
Hey! will be possible to add a feature like d3loader for win.user change? Or combine both .bat someway...
 
You must log in or register to reply here.
Back
Top