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

chrisssj3 said:
Just did an overnight run of 12 HOURS, without crash with this batchfile, without using profilerestarter/antiidle. Though I crashed 15 min after using pc, it's way better without those plugins.

[12:13:57.933 N] Creating new game, Params: <Act:A1 Difficulty:Inferno Quest:72095 QuestStep:51 ResumeFromSave:True IsPrivate:True>
[12:14:00.076 N] Game joined, Reloading profile.
[12:14:00.487 N] Loaded profile empty

I see this, seems to be a function of DB itself, so why would you need profile restarter anyway? if it's already being reloaded each game by DB.
Click to expand...

Hi Chris~!

LOL, glad that you managed to find a good solution for running your bots. Actually to be very honest, after answering the queries by the guys on the threads and pms, it seems that many times, certain plugins will work for some computers, and some, not so well for others. It's hard for me to diagnose in detail, unless I can so lab comparisons between the different machines lol. That being said, whatever I have recommended are the stuff that has worked for me on my pc and some others. Either way, everyone will have to find their own working combination (someone had to actually get this to run with 6 different plugins LOL~!).

So great to have yours working and happy botting~! :)
 
Just my 2cents..
Incase you run several instances i would recommend running this line:
Code: 
START "DB_Running" "!DBPath!!DBName!" -key !DBKey! [COLOR="#FF0000"]-pid !D3PID![/COLOR] -bnetaccount !BNetAcctName! -bnetpassword !BNetPwd! -profile="!Profile!" -routine="!CombatRoutine!" -autostart -noflash
colored in red the part to add, it tells DB to which d3 instance to attach itself (when you run over 1 it will get stuck in the selection menu of DB).
Also i would recommend adding the following lines:
Code: 
At the start: [COLOR="#FF0000"]set numruns=[/COLOR]
at the :dbrun part: [COLOR="#FF0000"]set /a numruns = 0[/COLOR]
at the :checkdb part: [COLOR="#FF0000"]set /a numruns=%numruns%+1[/COLOR]
and at :checksok i would add: [COLOR="#FF0000"]IF %numruns%==90 (GOTO :DETECTED)[/COLOR]
What this does is eliminate the need to re-open the .bat file every X time and it will just reset d3 and db every X runs (in this case 90).
Remember each run has a 1min wait b4 it does the checks + the run time for ping command - 90runs > 90min.
 
tesslerc said:
Just my 2cents..
Incase you run several instances i would recommend running this line:
Code: 
START "DB_Running" "!DBPath!!DBName!" -key !DBKey! [COLOR="#FF0000"]-pid !D3PID![/COLOR] -bnetaccount !BNetAcctName! -bnetpassword !BNetPwd! -profile="!Profile!" -routine="!CombatRoutine!" -autostart -noflash
colored in red the part to add, it tells DB to which d3 instance to attach itself (when you run over 1 it will get stuck in the selection menu of DB).
Also i would recommend adding the following lines:
Code: 
At the start: [COLOR="#FF0000"]set numruns=[/COLOR]
at the :dbrun part: [COLOR="#FF0000"]set /a numruns = 0[/COLOR]
at the :checkdb part: [COLOR="#FF0000"]set /a numruns=%numruns%+1[/COLOR]
and at :checksok i would add: [COLOR="#FF0000"]IF %numruns%==90 (GOTO :DETECTED)[/COLOR]
What this does is eliminate the need to re-open the .bat file every X time and it will just reset d3 and db every X runs (in this case 90).
Remember each run has a 1min wait b4 it does the checks + the run time for ping command - 90runs > 90min.
Click to expand...

Gorgeous~! I will look into this~!


I smell the next version coming soon lol :)
 
Hi Guys~!!

DB_Run v1.8 is out!!

1. Windows Task Scheduler is no longer required~! --> Thanks to tesslerc's idea~! DB_run is now standalone.
2. A basic log file (DB_Run.log) will now keep track of errors and events. --> Thanks to Chrisssj3's suggestion.

Check out the Change log in the first post. Keep the suggestions coming through~!

Once again, I thank all of you for your valuable suggestions and ideas. Without you, DB_Run will not be what it is today :)



Cheers~!
 
How do u get this to login?

or do u need to use somthing else?
 
segafreakone said:
My bot not log into D3 ! Pls help me
Click to expand...


yogiz said:
How do u get this to login?

or do u need to use somthing else?
Click to expand...

Hi segafreakone and yogiz,

Nope you do not need any other things.

Please let me know what version you are using and whether you have filled in the configurations portion of DB_run?

Also, do you have exclamation marks in your password (!)? E.g: AbCd12345!
If you have (!) in your password or anywhere within the configurations, please put ^^ infront of the (!).
That means if your password is AbCd12345!, you must put it as AbCd12345



Cheers~!
 
Last edited:
i just tried v1.8 and it the batch file ALWAYS auto closes a few mins after running it

why did it do that? previous versions never did that
 
Last edited:
protossop said:
i just tried v1.8 and it the batch file ALWAYS auto closes a few mins after running it

why did it do that? previous versions never did that
Click to expand...


Hmm... might I ask what version you are using? The standard, isboxer, autoauth or isboxer autoauth? Please include your log as well so that I can see where it stops.


Cheers~!
 
teivovo said:
Hmm... might I ask what version you are using? The standard, isboxer, autoauth or isboxer autoauth? Please include your log as well so that I can see where it stops.


Cheers~!
Click to expand...

using the standard version.

log:
Code: 
---------------------------------------------------------------------- 
Sat 07/14/201222:53:07.21 - DB_Run starting Up.
 
protossop said:
using the standard version.

log:
Code: 
---------------------------------------------------------------------- 
Sat 07/14/201222:53:07.21 - DB_Run starting Up.
Click to expand...

Hi there,

I have just tried out the files which were uploaded. They are fine. Have you changed anything other that the parameters in the configuration portion?

It would help if you could send the batch file to me without your keys, email and passwords and I will take a look at it for you.


Cheers~!
 
wootwoot911 said:
So does it support multiboxing? Can i run 3 dbs with 3 d3s?
Click to expand...

Hi there,

Oh yes it does~! You can run as many bots as you would like (until your pc limitation that is.)

Once done properly it will just keep going and going and going.... The only time it will stop working is if windows crashes. :)


Cheers~!
 
teivovo said:
Hi there,

Oh yes it does~! You can run as many bots as you would like (until your pc limitation that is.)

Once done properly it will just keep going and going and going.... The only time it will stop working is if windows crashes. :)


Cheers~!
Click to expand...
Most crashes end in a restart = reopens the bat :)
 
tesslerc said:
Most crashes end in a restart = reopens the bat :)
Click to expand...

Hey, there's actually a rather interesting app called cmdow recommended to be by vither. It allows windows to be manipulated via the command line. It is possible to get the effects of the likes of ISBoxer using that.

cmdow.webp

Wondering how to integrate this into DB run and how to o some controls... Hmm... Any ideas?
 
Teivovo nice new version :O gonna try it out, task scheduler not required anymore? It wasn't required to begin with? Wasn't like a shortcut if u wanted to start script fast? Will try the new version looking good!

I have run .176 DB with notification ok, agb and anti idle plugin again 10 hours overnight no flaw no restart required on script part. (I needed anti idle as I noticed during the day it was standing still @ start of cellar for no reason, and the .176 logout feature when idling does not seem to work.) Also antiidle seems to reload the profile each time, so this may be the reason that it conflicted with profilerestarter

Still keep getting,

[12:03:27.173 N] [NotificationOKClick Plugin0.9] Warning ! NotificationOKClick thread is not working!!!
[12:03:27.295 N] [NotificationOKClick Plugin0.9] Warning ! NotificationOKClick thread is not working!!!

I have all plugins enabled @ start as suggested in an earlier post. In the earlier post he suggested this was caused by starting/stopping bot after it started. Which does seem to be the case if I look at the log, altough I have no idea why, im not doing anything.

This is my log

[12:02:34.784 N] Demonbuddy v1.0.720.176 started
[12:02:34.857 N] Logging in...
[12:02:35.404 N] Attached to Diablo III with pid: 4172
[12:02:38.850 N] Current bot set to Order Bot
[12:02:38.851 N] Loaded profile empty
[12:02:38.926 N] Chose AGB - Nullcombat as your combat routine.
[12:02:39.255 N] Loaded profile empty
[12:02:39.558 N] Logging into game
[12:02:48.348 N] [AntiIdle] Initializing...
[12:02:48.350 N] [AntiIdle] Found Diablo III pid: 4172
[12:02:48.354 N] [AntiIdle] Enabling plugins from last save
[12:02:48.356 N] [AntiIdle] Profile: C:\Users\Chrisje\Desktop\173\DB_Run_v1.6_Package\empty.xml
[12:02:48.356 N] [AntiIdle] Enabling: AGB.Loader
[12:02:48.356 N] [AntiIdle] Enabling: AntiIdle v1.0
[12:02:48.356 N] [AntiIdle] Enabling: NotificationOKClick Plugin
[12:02:48.356 N] [AntiIdle] Enabling: Thiole Identify
[12:02:48.357 N] Enabled AGB
[12:02:48.357 N] Instanciated
[12:02:48.362 N] Instanciated UnitManager
[12:02:48.365 N] Modules Starting
[12:02:48.365 N] Starting: Lobby
[12:02:48.365 N] Starting: Arms
[12:02:48.365 N] Starting: Face
[12:02:48.365 N] Starting: Legs
[12:02:48.365 N] Starting: CerebralCortex
[12:02:48.365 N] Starting: FrontalLobe
[12:02:48.400 N] [AntiIdle] Reset all
[12:02:48.404 N] [AntiIdle] Thread started
[12:02:48.405 N] [AntiIdle] Enabled
[12:02:48.405 N] [AntiIdle] Loading last saved profile
[12:02:48.415 N] [AntiIdle] Bot is running -> AntiIdle is checking
[12:02:48.754 N] Loaded profile empty
[12:02:48.755 N] [NotificationOKClick Plugin0.9] Initalized
[12:02:48.756 N] [NotificationOKClick Plugin0.9] Enabled
[12:02:48.759 N] [NotificationOKClick Plugin0.9] Start CheckNotificationUI thread
[12:02:48.760 N] ThioleIdentify: Adding hooks
[12:02:48.767 N] [NotificationOKClick Plugin0.9] Start/Resume button found!!! Wait for next time
[12:02:49.348 N] Stopping the bot.
[12:02:49.365 N] [AntiIdle] Bot stop detected
[12:02:49.366 N] Bot Thread Ended. Was this requested?
[12:02:49.366 N] [NotificationOKClick Plugin0.9] OnStop
[12:02:49.366 N] [NotificationOKClick Plugin0.9] Kill CheckNotificationUI thread
[12:02:49.925 N] [AntiIdle] Bot is stopped for a unknown reason!
[12:02:49.927 N] [AntiIdle] Safe Restart
[12:02:49.927 N] [AntiIdle] Restarting..
[12:02:51.719 N] Loaded profile empty
[12:02:51.743 N] [AntiIdle] Bot start detected
[12:02:51.743 N] [AntiIdle] Reset all
 
chrisssj3 said:
Teivovo nice new version :O gonna try it out, task scheduler not required anymore? It wasn't required to begin with? Wasn't like a shortcut if u wanted to start script fast? Will try the new version looking good!

I have run .176 DB with notification ok, agb and anti idle plugin again 10 hours overnight no flaw no restart required on script part. (I needed anti idle as I noticed during the day it was standing still @ start of cellar for no reason, and the .176 logout feature when idling does not seem to work.) Also antiidle seems to reload the profile each time, so this may be the reason that it conflicted with profilerestarter

Still keep getting,

[12:03:27.173 N] [NotificationOKClick Plugin0.9] Warning ! NotificationOKClick thread is not working!!!
[12:03:27.295 N] [NotificationOKClick Plugin0.9] Warning ! NotificationOKClick thread is not working!!!

I have all plugins enabled @ start as suggested in an earlier post. In the earlier post he suggested this was caused by starting/stopping bot after it started. Which does seem to be the case if I look at the log, altough I have no idea why, im not doing anything.

This is my log

[12:02:34.784 N] Demonbuddy v1.0.720.176 started
[12:02:34.857 N] Logging in...
[12:02:35.404 N] Attached to Diablo III with pid: 4172
[12:02:38.850 N] Current bot set to Order Bot
[12:02:38.851 N] Loaded profile empty
[12:02:38.926 N] Chose AGB - Nullcombat as your combat routine.
[12:02:39.255 N] Loaded profile empty
[12:02:39.558 N] Logging into game
[12:02:48.348 N] [AntiIdle] Initializing...
[12:02:48.350 N] [AntiIdle] Found Diablo III pid: 4172
[12:02:48.354 N] [AntiIdle] Enabling plugins from last save
[12:02:48.356 N] [AntiIdle] Profile: C:\Users\Chrisje\Desktop\173\DB_Run_v1.6_Package\empty.xml
[12:02:48.356 N] [AntiIdle] Enabling: AGB.Loader
[12:02:48.356 N] [AntiIdle] Enabling: AntiIdle v1.0
[12:02:48.356 N] [AntiIdle] Enabling: NotificationOKClick Plugin
[12:02:48.356 N] [AntiIdle] Enabling: Thiole Identify
[12:02:48.357 N] Enabled AGB
[12:02:48.357 N] Instanciated
[12:02:48.362 N] Instanciated UnitManager
[12:02:48.365 N] Modules Starting
[12:02:48.365 N] Starting: Lobby
[12:02:48.365 N] Starting: Arms
[12:02:48.365 N] Starting: Face
[12:02:48.365 N] Starting: Legs
[12:02:48.365 N] Starting: CerebralCortex
[12:02:48.365 N] Starting: FrontalLobe
[12:02:48.400 N] [AntiIdle] Reset all
[12:02:48.404 N] [AntiIdle] Thread started
[12:02:48.405 N] [AntiIdle] Enabled
[12:02:48.405 N] [AntiIdle] Loading last saved profile
[12:02:48.415 N] [AntiIdle] Bot is running -> AntiIdle is checking
[12:02:48.754 N] Loaded profile empty
[12:02:48.755 N] [NotificationOKClick Plugin0.9] Initalized
[12:02:48.756 N] [NotificationOKClick Plugin0.9] Enabled
[12:02:48.759 N] [NotificationOKClick Plugin0.9] Start CheckNotificationUI thread
[12:02:48.760 N] ThioleIdentify: Adding hooks
[12:02:48.767 N] [NotificationOKClick Plugin0.9] Start/Resume button found!!! Wait for next time
[12:02:49.348 N] Stopping the bot.
[12:02:49.365 N] [AntiIdle] Bot stop detected
[12:02:49.366 N] Bot Thread Ended. Was this requested?
[12:02:49.366 N] [NotificationOKClick Plugin0.9] OnStop
[12:02:49.366 N] [NotificationOKClick Plugin0.9] Kill CheckNotificationUI thread
[12:02:49.925 N] [AntiIdle] Bot is stopped for a unknown reason!
[12:02:49.927 N] [AntiIdle] Safe Restart
[12:02:49.927 N] [AntiIdle] Restarting..
[12:02:51.719 N] Loaded profile empty
[12:02:51.743 N] [AntiIdle] Bot start detected
[12:02:51.743 N] [AntiIdle] Reset all
Click to expand...


Yeah... this really beats me too chris... there are quite a few peeps getting the same error on the NotificationOKClick thread too... This didnt happen until I started using 173... probably need to wait for it to be updated I guess.

Lemme know how you feel about the new version 1.8 yah?


Cheers~!
 
Oh ok so I know it isn't just me xD

I am trying it right now, but it doesn't show how much times it has restarted diablo 3/demonbuddy. Or for what reason it was restarted (freeze/ app error etc. )

And it has already restarted bot atleast once during crash/freeze because I happen to see it with own eyes.
 
Last edited:
chrisssj3 said:
I am trying it right now, but it doesn't show how much times it has restarted diablo 3/demonbuddy. Or for what reason it was restarted (freeze/ app error etc. )

And it has already restarted bot atleast once during crash/freeze because I happen to see it with own eyes.
Click to expand...

Yep, right now I'm just starting with a basic log. Will expand it in future releases. So for now, it's just rather basic information.


Cheers~! (At least it restarts properly :))
 
Do I have to create multiple folders to get more bot accounts to load. Once I am able to get this working I will write how to make it so that you are on 24/7 even with BSOD. Thanks!
 
You must log in or register to reply here.
Back
Top