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

teivovo · Jul 7, 2012

masterjeff said:
A very stresfull solution for the performance, isnt it? I dont like the idea to run a vm just because of 1 bot.

Maybe this works?

Yeah... VM eats into performance a lot...

Your suggestion would not work though... because windows recognizes the processes based on its ID and not the path in which it ran from....

masterjeff · Jul 7, 2012

teivovo said:
Yeah... VM eats into performance a lot...

Your suggestion would not work though... because windows recognizes the processes based on its ID and not the path in which it ran from....

Ok..then we have to find a working solution with pid's

Fuck i need to learn batch programming lol

KennyNinja · Jul 7, 2012

How do i setup to login in EU or US? 3 different diablo folders and 1 demon buddy folder, but not all go to US or EU, and saves the last one i logged in, and i need to log in EU and US. In case it does not select, goes to the wrong server.

DerekC · Jul 7, 2012

I got everything running but my plugins do not enable themselves, how do i do that?

teivovo · Jul 7, 2012

KennyNinja said:
How do i setup to login in EU or US? 3 different diablo folders and 1 demon buddy folder, but not all go to US or EU, and saves the last one i logged in, and i need to log in EU and US. In case it does not select, goes to the wrong server.

Hi, each individual diablo folders need to be served by its own demonbuddy. So 3 diablo folders = 3 demonbuddy folders = 3 copies of DB_Run

So you can still choose the servers that you want based on the D3 client.

protossop · Jul 7, 2012

Do we have to have the program Task Schedular running the entire time? Or can we close it once we've set everything up?

teivovo · Jul 7, 2012

DerekC said:
I got everything running but my plugins do not enable themselves, how do i do that?

Ok.. what you need to do is to open up your D3 and DB normally, load your loot rules, plugins, etc, normally. Then close then like you normally would. Open them again to check if the plugins are enabled. If they are, they will be enabled when you run the batch file.

teivovo · Jul 7, 2012

protossop said:
Do we have to have the program Task Schedular running the entire time? Or can we close it once we've set everything up?

Yes, task scheduler can be closed once everything is set up to your liking

teivovo · Jul 7, 2012

Update: DB_Run_v1.4 is coming... The guys that run multiple bots will be happy

protossop · Jul 7, 2012

So it checks every minute if DB/D3 freezes. If it finds that D3 has frozen, how long will it take to restart D3?

hikari118 · Jul 7, 2012

thanks for the awesome Batch! now I feel no more worries about the crashing game problems.
however, my DB just let me toon stand there without resuming the game, it login perfectly and everything is fine, but I have to manually click on the resume game after my daiblo accoutn login.
I followed all the steps on the first page and I read all the posts on this thread to make sure there is nothing I have done wrong. Someone said they use the plug in Anti Idle to make it works but I want to use as minimum plugins as possible to prevent some weird things happened.
although I read the post of masterjiff how to make it works with AGB, I use the empty.xlm and havent modified the Profilerestarter.cs.
do you have any idea of my idling problem after login?
toon: demon hunter
plugin: AGB .6.2
here is my batch:

Code:

::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\Marcus\Desktop\Demonbuddy 1.0.648.160

::Change the following line to suit your needs (Pathing, user accounts, password, keys, etc)
START "DB_Running" "C:\Users\Marcus\Desktop\Demonbuddy 1.0.648.160\Demonbuddy.exe" -key ___________________________ -bnetaccount _______@________ -bnetpassword ___________ -d3path="C:\Program Files (x86)\Games\Diablo.III.Collectors.Edition\Diablo III.exe" -profile="C:\Users\Marcus\Desktop\Demonbuddy 1.0.648.160\Profiles\empty.xml" -routine="AGB - Nullcombat" -autostart -noflash

here is my logs:

Code:

[20:33:43.487 D] Reloading AssemblyLoader<Zeta.CommonBot.ICombat> - RoutineManager.Reload !THROTTLED!
[20:33:43.487 D] Routines were reloaded. New routine list:
[20:33:43.487 D] AGB - Nullcombat v0.0.0.0
[20:33:43.487 D] Belphegor All-in-One v1.0.648.160
[20:33:43.488 D] Generic v0.0.0.0
[20:33:43.488 N] Chose AGB - Nullcombat as your combat routine.
[20:33:43.488 D] Forcing profile reload.
[20:33:43.759 N] Loaded profile empty
[20:33:43.759 D] Starting bot Order Bot
[20:33:43.773 D] Added new hook [OutOfGame] 46ce1f14-7a6a-4198-ae6a-0d873904e006
[20:33:43.773 D] Added new hook [Death] 74d9254e-2299-411a-bcca-1cf6dbdef723
[20:33:43.774 D] Added new hook [RoutineBuffs] da7b7cdd-3615-4851-a7f8-a5f5f082ed03
[20:33:43.774 D] Added new hook [RoutineCombat] c49ff85a-3612-482e-9b27-c045928ea0f5
[20:33:43.774 D] Added new hook [Combat] 3cfedeb8-0867-4bf7-937f-91551e2ae511
[20:33:43.784 D] Added new hook [VendorRun] d54e6806-07f2-4666-8d55-12203a47cc73
[20:33:43.791 D] Added new hook [Loot] 33e5007c-098f-4ecb-b768-e576249bfa43
[20:33:43.792 D] Replaced hook [BotBehavior] c12ffcb0-acdc-4383-b323-979249e6dcd9
[20:33:43.794 D] Spooling up bot thread.
[20:33:43.794 D] Bot thread started.
[20:33:44.035 N] Logging into game
[20:33:51.103 D] Reloading AssemblyLoader<Zeta.Common.Plugins.IPlugin> - Initializing
[20:33:51.516 N] Enabled AGB
[20:33:51.516 N] Instanciated
[20:33:51.520 N] Instanciated UnitManager
[20:33:51.521 N] Modules Starting
[20:33:51.521 N] Starting: Lobby
[20:33:51.521 N] Starting: Arms
[20:33:51.521 N] Starting: Face
[20:33:51.521 N] Starting: Legs
[20:33:51.521 N] Starting: CerebralCortex
[20:33:51.521 N] Starting: FrontalLobe
[20:33:51.522 D] Replaced hook [TreeStart] 0ce25efd-6dbc-4ff0-93db-49b58c076864
[20:33:51.534 D] Replaced hook [TreeStart] 19901694-f93a-4d2c-a43a-e355a3dcc3ee
[20:33:51.553 D] There are 1 plugins.
[20:33:54.663 D] System.NullReferenceException: Object reference not set to an instance of an object.
   at AGB.Modules.CerebralCortex.<GenerateStartQuestBehavior>b__6e(Object context)
   at Zeta.TreeSharp.Action.RunAction(Object context)
   at Zeta.TreeSharp.Action..MoveNext()
   at (Object )
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.TreeSharp.PrioritySelector..MoveNext()
   at (Object )
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.TreeSharp.Sequence..MoveNext()
   at (Object )
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.TreeSharp.PrioritySelector..MoveNext()
   at (Object )
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.Common.HookExecutor.Run(Object context)
   at Zeta.TreeSharp.Action.RunAction(Object context)
   at Zeta.TreeSharp.Action..MoveNext()
   at (Object )
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.TreeSharp.PrioritySelector..MoveNext()
   at (Object )
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.CommonBot.BotMain.()
[20:43:54.993 D] Joined a game!
[20:43:54.993 D] [BotEvents] EventChecker  threw exception Object reference not set to an instance of an object. in check
[20:43:55.013 D] System.NullReferenceException: Object reference not set to an instance of an object.
   at AGB.Modules.CerebralCortex.<GenerateStartQuestBehavior>b__6e(Object context)

KennyNinja · Jul 7, 2012

teivovo said:
Hi, each individual diablo folders need to be served by its own demonbuddy. So 3 diablo folders = 3 demonbuddy folders = 3 copies of DB_Run So you can still choose the servers that you want based on the D3 client.

I understand, but when i login in america and then swap to another diablo it stays as america, not sure why they link each other sometimes, gotta test to know better, will try more and try to give u some info.

KennyNinja · Jul 7, 2012

Looking good, too bad was not clicking resume neither saving the region, maybe my diablo folders are linked and i have no idea why.

dernacktekaiser · Jul 7, 2012

for me it justs stand still at the checkpoint

hikari118 · Jul 7, 2012

wowcheesestick said:
My antiidle kicks in and fixes it...

Hey man, would you share how the setting of anti idle to prevent the batch waiting on the resume?

teivovo · Jul 7, 2012

protossop said:
So it checks every minute if DB/D3 freezes. If it finds that D3 has frozen, how long will it take to restart D3?

Hi there, it will take a random amount of time between the min_minutes and max_minutes you have set.

hikari118 · Jul 7, 2012

hi teivovo,
I realised that my toon waiting at the resume screen is because my D3 took more than 20 sec to the select menu, are you able to make some changes in 1.4 so that I can use your awesome batch?

teivovo · Jul 7, 2012

hikari118 said:
Hey man, would you share how the setting of anti idle to prevent the batch waiting on the resume?

Hi there,

I have tried and it works. All you need to do is to enable the AGB Plugin, MSFIX and NotificationOKClick. Make sure you have the latest version of NotificationOKClick (v0.9)

Then you should be good to go~!

teivovo · Jul 7, 2012

hikari118 said:
hi teivovo,
I realised that my toon waiting at the resume screen is because my D3 took more than 20 sec to the select menu, are you able to make some changes in 1.4 so that I can use your awesome batch?

Hmm.. you could do this..: Remember the LONG command required to start Demonbuddy with your account name passwords etc...? Replace the entire thing with this:

::Change the following line to your Diablo III Path (keep START and -launch in the line. Remember the "quotes")
START "D3Run" "C:\Program blahblahblah\Diablo III.exe" -launch

::Time how long your D4 takes to start (x seconds). Then change the number after /t to a good (x seconds + 5) ie. if your D3 takes about 30 seconds to load, then replace X with 35.
timeout /t X /NOBREAK

::Change the following line to suit your needs (Pathing, user accounts, password, keys, etc)
START "DB_Running" "C:\Users\xxxxxxx\Demonbuddy 1.60\Demonbuddy.exe" -key xxxxxxxxxxxxxx -bnetaccount [email protected] -bnetpassword xxxxxxxxxxx -profile="C:\xxxxxxxxxxxxxx\Demonbuddy 1.60\Profiles\xxxxx.xml" -routine="Belphegor All-in-One" -autostart -noflash

If your only problem is due to the delays, then this will definitely solve your problem. This is going to come out in v1.4.. Lucky guess.

Cheers~!

hikari118 · Jul 7, 2012

teivovo said:
Hmm.. you could do this..: Remember the LONG command required to start Demonbuddy with your account name passwords etc...? Replace the entire thing with this:

::Change the following line to your Diablo III Path (keep START and -launch in the line. Remember the "quotes")
START "D3Run" "C:\Program blahblahblah\Diablo III.exe" -launch

::Time how long your D4 takes to start (x seconds). Then change the number after /t to a good (x seconds + 5) ie. if your D3 takes about 30 seconds to load, then replace X with 35.
timeout /t X /NOBREAK

::Change the following line to suit your needs (Pathing, user accounts, password, keys, etc)
START "DB_Running" "C:\Users\xxxxxxx\Demonbuddy 1.60\Demonbuddy.exe" -key xxxxxxxxxxxxxx -bnetaccount [email protected] -bnetpassword xxxxxxxxxxx -profile="C:\xxxxxxxxxxxxxx\Demonbuddy 1.60\Profiles\xxxxx.xml" -routine="Belphegor All-in-One" -autostart -noflash

If your only problem is due to the delays, then this will definitely solve your problem. This is going to come out in v1.4.. Lucky guess.

Cheers~!

thanks teivovo,
I tried, but it seems not working for me.
I set it as 45 second until DB loaded and start logging my D3 account.
Plugins: AGB, ProfileRestarter

ProfileRestarter has default setting

it took me 15 sec:

Code:

[19:57:13.919 N] Logging in...
[19:57:14.795 N] Attached to Diablo III with pid: 2688
[19:57:18.553 N] Current bot set to Order Bot
[19:57:18.554 N] Loaded profile empty
[19:57:18.613 N] Chose AGB - Nullcombat as your combat routine.
[19:57:18.891 N] Loaded profile empty
[19:57:19.166 N] Logging into game
[19:57:28.044 N] [AntiIdle v0.6.1] Found Diablo III pid: 2688
[19:57:28.051 N] [Profile Restarter]-> Enabled.
[19:57:28.052 N] [Profile Restarter]-> 0 scheduled profiles loaded.
[19:57:28.054 N] Enabled AGB
[19:57:28.054 N] Instanciated
[19:57:28.058 N] Instanciated UnitManager
[19:57:28.059 N] Modules Starting
[19:57:28.059 N] Starting: Lobby
[19:57:28.059 N] Starting: Arms
[19:57:28.059 N] Starting: Face
[19:57:28.059 N] Starting: Legs
[19:57:28.059 N] Starting: CerebralCortex
[19:57:28.059 N] Starting: FrontalLobe

Here is the batch file with the information:

Code:

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\Marcus\Desktop\Demonbuddy 1.0.648.160

::Change the following line to your Diablo III Path (keep START and -launch in the line. Remember the "quotes")
START "D3Run" "C:\Program Files (x86)\Games\Diablo.III.Collectors.Edition\Diablo III.exe" -launch

::Time how long your D4 takes to start (x seconds). Then change the number after /t to a good (x seconds + 5) ie. if your D3 takes about 30 seconds to load, then replace X with 35.
timeout /t 45 /NOBREAK

::Change the following line to suit your needs (Pathing, user accounts, password, keys, etc)
START "DB_Running" "C:\Users\Marcus\Desktop\Demonbuddy 1.0.648.160\Demonbuddy.exe" -key __________________ -bnetaccount _________@_________ -bnetpassword _________ -profile="C:\Users\Marcus\Desktop\Demonbuddy 1.0.648.160\Profiles\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

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

New Member

New Member

New Member

New Member

New Member

New Member

New Member

New Member

New Member

New Member

New Member

New Member

New Member

New Member

New Member

New Member

New Member

New Member

New Member

New Member