teivovo
New Member
- Joined
- Jun 25, 2012
- Messages
- 353
- Reaction score
- 5
Hi guys,
Firstly, this is not a plugin. This was originally created to help me restart the entire D3 and DB periodically. It has somewhat evolved away from its primary purpose and become a simple and effective DB and D3 relogger.
This is an Ultra Simple, Stable and Effective Relogger: AFK for almost 3 months now...
No fancy GUI or window placements.
DB_Run Features:
1. Kills any existing D3 and DB instances.
2. Waits a random time (you can set the min [pref 5 minutes] and max range) Please set min_minutes to a value above 2 minutes so that buddy auth will release the previous session in the event of forceful shutdown of DB. - thanks to the idea from no1knowsy for his BreakTaker plugin.
3. Starts DB and D3 and loads the profile and starts the runs.
4. Detects if DB and/or D3 has closed and re-fire everything up again.
5. Detects if DB and/or D3 has crashed (NOT RESPONDING state only) and re-fire everything up again.
6. If DB or D3 freezes for whatsoever reason and DB_Run is unable to detect, bot will restart totally upon reaching the limit of the restart timer.
7. Supports ANY OS Language
8. Supports ISBoxer.
9. Closes any open Blizzard Error windows.
10. Performs network checks and restarts bot if network is unstable (3/5 ping drops --> you can change this to your preference)
11. Integrated to work with tehToad's AutoAuth BuddyAuth Session killer to kill sessions TAGGED to the bot that crashed (currently still in testing phase for AutoAuth)
12. Allows users to set their desired bot schedule (Start time and Stop time). Will randomize the start time and stop time with the start - stop minutes settings.
13. Detects DB and Diablo III windows crash errors (windows error prompt that does not close DB)
-------------------------------------------------------------
INSTRUCTIONS
1. Edit DB_Run.bat and change the parameters in the CONFIGURATIONS portion.
2. Open D3 and DB as you would normally. Set all the settings (Loot, combat radius, enable plugins, etc). Then close them as you would normally. --> This would save the settings so that when the batch file runs, it will use these settings.
Additional instructions for running AGB (for all you DH's out there):
3. Make sure that you point profile to empty.xml instead of AGBLoader.xml --> Thanks to masterjeff~!
4. Be sure to put "AGB - Nullcombat" as the combat profile.
5. No additional modifications to ProfileRestarter required.
6. NotificationOKClick v0.9 OR AntiIdle is required to make AGB work with this. (Different people have had different results with these two plugins. Try and see which one works best for you)
-------------------------------------------------------------
Hope this is useful to you guys... and Thanks for your support thus far~!
Limitations:
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
2. AutoAuth assumes that your sessions starts more than 10 seconds apart of each other. If bots are started too close to each other, it will not be possible to correctly identify the correct session.
3. I can't seem to get the Czech fonts to stay after I edit the files on my computer. Czech DB_Run users, please PM me and I will guide you on what needs to be changed. Sorry about this...
4. DB_Run will never have any pretty GUI and pretty window arrangements.
Thanks for all your support guys! Keep the ideas and suggestions coming~!!
Cheers~!
P.S. The different language versions still inherently display in English. But it is designed to work with different language OS.
Firstly, this is not a plugin. This was originally created to help me restart the entire D3 and DB periodically. It has somewhat evolved away from its primary purpose and become a simple and effective DB and D3 relogger.
This is an Ultra Simple, Stable and Effective Relogger: AFK for almost 3 months now...
No fancy GUI or window placements.
DB_Run Features:
1. Kills any existing D3 and DB instances.
2. Waits a random time (you can set the min [pref 5 minutes] and max range) Please set min_minutes to a value above 2 minutes so that buddy auth will release the previous session in the event of forceful shutdown of DB. - thanks to the idea from no1knowsy for his BreakTaker plugin.
3. Starts DB and D3 and loads the profile and starts the runs.
4. Detects if DB and/or D3 has closed and re-fire everything up again.
5. Detects if DB and/or D3 has crashed (NOT RESPONDING state only) and re-fire everything up again.
6. If DB or D3 freezes for whatsoever reason and DB_Run is unable to detect, bot will restart totally upon reaching the limit of the restart timer.
7. Supports ANY OS Language
8. Supports ISBoxer.
9. Closes any open Blizzard Error windows.
10. Performs network checks and restarts bot if network is unstable (3/5 ping drops --> you can change this to your preference)
11. Integrated to work with tehToad's AutoAuth BuddyAuth Session killer to kill sessions TAGGED to the bot that crashed (currently still in testing phase for AutoAuth)
12. Allows users to set their desired bot schedule (Start time and Stop time). Will randomize the start time and stop time with the start - stop minutes settings.
13. Detects DB and Diablo III windows crash errors (windows error prompt that does not close DB)
-------------------------------------------------------------
INSTRUCTIONS
1. Edit DB_Run.bat and change the parameters in the CONFIGURATIONS portion.
Code:
[COLOR="#800080"][SIZE=4][B][U]General Configurations[/U][/B][/SIZE][/COLOR]
set min_minutes=[COLOR="#0000FF"]4[/COLOR] [COLOR="#008000"]----> Do not to set the min_minutes to less than 3 minutes or your DB session may still be locked. I would recommend about 5. (in minutes only)[/COLOR]
set max_minutes=[COLOR="#0000FF"]7[/COLOR][COLOR="#008000"] ----> Don't set this less than your min_minutes value. The min and max minutes will be used to calculate the random breaktime that your bot will take in between reload cycles. (in minutes only)[/COLOR]
set Scheduler=[COLOR="#0000FF"]0[/COLOR][COLOR="#008000"] ----> 0=Off, 1=On[/COLOR]
set start_hours=[COLOR="#0000FF"]5[/COLOR][COLOR="#008000"] ----> Start Hour in 24 Hour format. Please remove the leading zero. (Put 5 instead of 05)[/COLOR]
set start_minutes=[COLOR="#0000FF"]25[/COLOR][COLOR="#008000"] ----> Start Minutes in 24 Hour format. Please DO NOT remove the leading zero. (Put 06 instead of just 6)[/COLOR]
set stop_hours=[COLOR="#0000FF"]23[/COLOR][COLOR="#008000"] ----> Stop Hour in 24 Hour format. Please remove the leading zero. (Put 5 instead of 05)[/COLOR]
set stop_minutes=[COLOR="#0000FF"]30[/COLOR][COLOR="#008000"] ----> Start Minutes in 24 Hour format. Please DO NOT remove the leading zero. (Put 06 instead of just 6)[/COLOR]
set min_restart_minutes=[COLOR="#0000FF"]60[/COLOR][COLOR="#008000"] ----> The number of minutes the bot will run before it restarts DB and D3 totally.[/COLOR]
set max_restart_minutes=[COLOR="#0000FF"]120[/COLOR][COLOR="#008000"] ----> The number of minutes the bot will run before it restarts DB and D3 totally.[/COLOR]
set D3Name=[COLOR="#0000FF"]Diablo III.exe[/COLOR][COLOR="#008000"] ---> Name of your D3 executable.[/COLOR]
set DBName=[COLOR="#0000FF"]Demonbuddy3.exe[/COLOR][COLOR="#008000"] ---> Name of your DB executable.[/COLOR]
set DBDrive=[COLOR="#0000FF"]C:[/COLOR][COLOR="#008000"] ---> Drive that your DB folder is located.[/COLOR]
set D3Path=[COLOR="#0000FF"]C:Program Files (x86)Diablo III[/COLOR][COLOR="#008000"] ---> Path of your D3.[/COLOR]
set DBPath=[COLOR="#0000FF"]C:UsersXXXDesktopDemonbuddy[/COLOR][COLOR="#008000"] ---> Path of your DB.[/COLOR]
set DBKey=[COLOR="#0000FF"]1234567890ABCD[/COLOR][COLOR="#008000"] ---> DB license key.[/COLOR]
set BNetAcctName=[COLOR="#0000FF"][email protected][/COLOR][COLOR="#008000"] ---> Email address for logging into D3.[/COLOR]
set BNetPwd=[COLOR="#0000FF"]XXXXXXX[/COLOR][COLOR="#008000"] ---> Password for logging into D3.[/COLOR]
set Profile=[COLOR="#0000FF"]C:UsersXXXDesktopDemonbuddyProfilesProfile.xml[/COLOR][COLOR="#008000"] ---> Profile that you want the bot to use. (include full path)[/COLOR]
set CombatRoutine=[COLOR="#0000FF"]Belphegor All-in-One[/COLOR][COLOR="#008000"] ---> Combat routine to be used.[/COLOR]
[COLOR="#800080"][SIZE=4][B][U]ISBoxer and AutoAuth Configurations[/U][/B][/SIZE][/COLOR]
set ISBoxer=[COLOR="#0000FF"]0[/COLOR][COLOR="#008000"][COLOR="#008000"] ---> 0 = disable, 1 = enable[/COLOR]
set AutoAuth=[COLOR="#0000FF"]0[/COLOR][COLOR="#008000"][COLOR="#008000"] ---> 0 = disable, 1 = enable[/COLOR]
set ISBoxerLinkName=[COLOR="#0000FF"]Bot 1.lnk[/COLOR][COLOR="#008000"] ---> Your ISBoxer .lnk file with path.[/COLOR]
set ISBoxerLoadTime=[COLOR="#0000FF"]20[/COLOR][COLOR="#008000"] ---> The amount of time it takes from the point that you click the ISBoxer .lnk file till the D3 window appears. Try to give a 2 to 3 second buffer. (in seconds only)[/COLOR]
set AutoAuthPath=[COLOR="#0000FF"]C:UsersXXXDesktopAutoAuth[/COLOR][COLOR="#008000"] ---> Path of your AutoAuth (if any)[/COLOR]
[COLOR="#800080"][SIZE=4][B][U]For Those Having Plugin Problems (Plugins not loading properly e.g. Giles Loot and Stasher[/U][/B][/SIZE][/COLOR]
set PluginProblem=[COLOR="#0000FF"]0[/COLOR][COLOR="#008000"][COLOR="#008000"] ---> 0 = disable, 1 = enable. Enable if you have problems.[/COLOR]
set LoginScreenAppear=[COLOR="#0000FF"]10[/COLOR][COLOR="#008000"][COLOR="#008000"] ---> The number of seconds from the opening of DB window till it starts makes the D3 authentication window appear.[/COLOR]
set EmptyProfile=[COLOR="#0000FF"]C:UsersXXXDesktopDemonbuddyProfilesempty.xml[/COLOR][COLOR="#008000"][COLOR="#008000"] ---> Download empty.xml. Enter path of empty.xml.[/COLOR]2. Open D3 and DB as you would normally. Set all the settings (Loot, combat radius, enable plugins, etc). Then close them as you would normally. --> This would save the settings so that when the batch file runs, it will use these settings.
Additional instructions for running AGB (for all you DH's out there):
3. Make sure that you point profile to empty.xml instead of AGBLoader.xml --> Thanks to masterjeff~!
4. Be sure to put "AGB - Nullcombat" as the combat profile.
5. No additional modifications to ProfileRestarter required.
6. NotificationOKClick v0.9 OR AntiIdle is required to make AGB work with this. (Different people have had different results with these two plugins. Try and see which one works best for you)
-------------------------------------------------------------
Hope this is useful to you guys... and Thanks for your support thus far~!
Code:
[COLOR="#FF8C00"][SIZE=5][B][U]FAQ[/U][/B][/SIZE][/COLOR]
[B]1. My D3 does not log in?[/B]
[COLOR="#008000"]If your any of the parameters that you are setting uses the exclamation mark (!) make sure that you input it as ^^! Eg, if your password is AbCd12345! make sure you put is as AbCd12345^^![/COLOR]
[B]2. DB says unable to latch on to D3?[/B]
[COLOR="#008000"]Does it take DB more than 20 seconds to load D3 (until character select menu - idle) PM me and I will explain how to make some adjustments to make it work. There is a timeout period for DB to latch onto D3.[/COLOR]
[B]3. Why doesn't DB Run work with ISBoxer?[/B]
[COLOR="#008000"]If you need this to work with ISBoxer, makes sure that your download the ISBoxer package. Use the ISBoxer_Loader.bat to load the bots sequentially. Right now, if the bots are loaded too close to each other, the sessions may get mixed up. You can refer to a great guide by DTrick: [/COLOR][COLOR="#008000"][URL="http://www.thebuddyforum.com/demonbuddy-forum/demonbuddy-guides/60163-guide-isboxer-batch-file-db_run.html"]http://www.thebuddyforum.com/demonbuddy-forum/demonbuddy-guides/60163-guide-isboxer-batch-file-db_run.html[/URL][/COLOR]
[B]4. Why do my DB_run seem to lock on to different DB and D3 sessions? It is closing the D3 (or DB) that it is not responsible for. It seems that DB run is mixed up.[/B]
[COLOR="#008000"]If the bots are loaded too close to each other, the sessions may get mixed up and this condition will happen. Please load the bots sequentially. Let each bot load fully before you start the next one. A good way is to use the ISBoxer_Loader.bat from the ISBoxer package - Just make the necessary amendments.[/COLOR]
[B]5. Why are the plugins not working well?[/B]
[COLOR="#008000"]Feel free to experiment. Some people have reported AntiIdle working well for them, others have said NotificationOKClick. See what works best for you~![/COLOR]
[B]6. I'm using the non-English version, why doesn't it recognize the errors correctly? ---> For DB_Run_v2.0 and older only [/B]
[COLOR="#008000"]PM me and I'll guide you through this. It is something to do with errString1 and errString2 being inaccurate. The German version should be ok. The Czech version may require some modification as my pc can't recognize the Czech font.[/COLOR]
[B]7. My D3 stays at the Character Select screen. Why is that?[/B]
[COLOR="#008000"]Please try to use the plugins: NotificationOKClick (or AntiIdle) and ProfileRestarter from the plugins section. Sometimes DB's native clicker does not click the START/RESUME game button.[/COLOR]
[B]8. DB_Run stops working and closes even before D3 and DB starts up. What can I do?[/B]
[COLOR="#008000"]Please delete the DBPID.txt and D3PID.txt files located inside the folder containing DB_Run and start DB_Run again.[/COLOR]
[B]9. Can I make modifications to your code?[/B]
[COLOR="#008000"]Of course you can~! Feel free to make it suit your needs~! :) If you have any useful suggestions or ideas you wish to see inside the next version, lemme know and I'll include it in the next release. :)[/COLOR]
Code:
[B][I][COLOR="#0000FF"][U]Updates:[/U]
[B]DB_Run_v2.4[/B]
1. Further attempts to fix up the "Plugin Problem" Fix. Please test again for me guys. Sorry for the trouble~!
[B]DB_Run_v2.3[/B]
1. Fixed up the "Plugin Problem" Fix. Please test for me guys :)
[B]DB_Run_v2.2[/B]
1. Added randomization for the duration of total bot restart.
2. Fixed some minor bugs.
[B]DB_Run_v2.1a[/B]
1. Fixed some timing issues. Sorry about that guys...
[B]DB_Run_v2.1[/B]
1. :) DB_Run will now work with ANY OS Language :)
[B]DB_Run_v2.0d[/B]
1. DB looping bug solved. --> Thanks tesslerc :)
[B]DB_Run_v2.0c[/B] ---> Axed!
1. Fixed an issue that DB was not loading some plugins correctly. --> Thanks GilesSmith and tesslerc :) *-----> Please test this for me.... as I do not face the plugins problem...
Take note that DB will start once, log in D3, shut down and start DB again.... A retarded fix... but I have no other options with this one... :(
[B]DB_Run_v2.0b[/B]
1. More robust error detection added. --> Thanks jacker25 :)
[B]DB_Run_v2.0a[/B]
1. Added an exception handler to solve a bug for AutoAuth users. --> Thanks tesslerc~! :)
[B]DB_Run_v2.0[/B]
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~! :)
[B]DB_Run_v1.9c[/B]
1. Added support for French. --> Thanks wootwoot911!
[B]DB_Run_v1.9b[/B]
1. Added support for Danish. --> Thanks jaimay!
2. Fixed up some errors regarding ISBoxer launching. --> Thanks Hyshakt!
[B]DB_Run_v1.9[/B]
1. Revamped the logs. --> Displaying more details now especially after a long period of AFK.
2. Combined all versions into 1. No more different packages and different language packs. Now, one batch file fits all. Take note of the necessary additional configurations required (Minimal).
[B]DB_Run_v1.8[/B]
1. Finally gotten around to implementing a basic log. DB_Run.log -> Located in the same folder as the batch file. - thanks to Chrisssj3's suggestion :)
2. DB_Run will no longer require the Windows Task Scheduler ~YAY!!! - thanks to tesslerc's idea :)
* * a) Set the "restart_minutes" parameter in the CONFIGURATION portion to determine how long the Bot will run before restarting totally followed by taking a break.
3. Four different versions are available due to requests.
* * a) Standard - does not include AutoAuth integration.
* * b) AutoAuth - works with AutoAuth.
* * c) ISBoxer - ISBoxer version without AutoAuth integration.
* * d) ISBoxer - AutoAuth - ISBoxer version with AutoAuth integration.
[B]DB_Run_v1.7[/B]
1. Fixed some code. ^_^
[B]DB_Run_v1.6[/B]
1. Closes any open Blizzard Error windows.
2. Performs network checks and restarts bot if network is unstable (3/5 ping drops --> you can change this to your preference)
3. Integrated to work with tehToad's AutoAuth BuddyAuth Session killer to kill sessions TAGGED to the bot that crashed. Refer to: [URL="http://www.thebuddyforum.com/demonbuddy-forum/plugins/60517-standalone-sessionkiller-autoauth-multibot-support.html"]http://www.thebuddyforum.com/demonbuddy-forum/plugins/60517-standalone-sessionkiller-autoauth-multibot-support.html[/URL] by tehToad
[B]DB_Run_v1.4c_ISBoxer_ENG (Special Release)[/B]
1. Now works with ISBoxer. Refer to this great guide by DTrick[COLOR="#008000"] [URL="http://www.thebuddyforum.com/demonbuddy-forum/demonbuddy-guides/60163-guide-isboxer-batch-file-db_run.html"]http://www.thebuddyforum.com/demonbuddy-forum/demonbuddy-guides/60163-guide-isboxer-batch-file-db_run.html[/URL][/COLOR]. Maake sure you use ISBoxer_Loader to fire up your bots sequentially or it does not work properly.
[B]DB_Run_v1.4c:[/B]
1. Biggest update yet. The batch file will now be responsible for it's own DB and D3 session. So each set will not interfere with one another. You can have as many instances that you want. Just note that for each botting instance, you will need one batch file to control each one. Individual bots crashing will no longer affect the rest. Those botting with just 1 account will not really feel the difference though.
2. Code cleanup. --> Really sorry about the mess in the code... Been pumping out updates too quickly to have time for housekeeping.... Now it's good. The configuration of the batch file is a lot simpler now. All you need to do is to key in the details in the front portion of DB_Run.bat.
3. As a request from you guys, DB_Run now supports German and Czech OS. If you wish to have it localized for your OS language, drop me a PM. :)
[B]DB_Run_v1.3:[/B]
1. Error detection of the script has been improved. Now it detects NOT RESPONDING states as well as if DB or D3 has crashed == Closed.. and will restart everything again. - Take note that it is only able to detect these two types of errors presently.
2. AGB working.
[B]DB_Run_v1.2:[/B]
1. Fixed a serious error.. thanks to masterjeff and bullet07 -----> Axed.... again...
DB_Run_v1.1:[/B]
1. It will scan and determine if DB and/or D3 has gone into NOT RESPONDING state == HANG and restart the whole run. ----> Axed....
[/COLOR][/I]Limitations:
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
2. AutoAuth assumes that your sessions starts more than 10 seconds apart of each other. If bots are started too close to each other, it will not be possible to correctly identify the correct session.
3. I can't seem to get the Czech fonts to stay after I edit the files on my computer. Czech DB_Run users, please PM me and I will guide you on what needs to be changed. Sorry about this...
4. DB_Run will never have any pretty GUI and pretty window arrangements.
Thanks for all your support guys!
Keep the ideas and suggestions coming~!!Cheers~!
P.S. The different language versions still inherently display in English. But it is designed to work with different language OS.
Last edited:
