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

[wonsok]

It doesnt crash often, but it will either crash and the batch file will all try to restart it and hit max sessions, or it will run into a problem where it tries to attach to multiple instances of d3 with the drop down menu with multiple id's.

Hi wonsok,

Question for you... does DB or D3 crash on you quite often? (Meaning closes totally or hangs -- not responding)

Cheers~!

 

[teivovo]

Would it be possible to also detect disconnects? Like when 5 pings in a row fails, shut down D3+DB and wait until 5 pings in a row succeed, and fire up D3+DB again (and also wait for session timeout since first 5 pings failed)?

Hmmmm.... Interesting idea mate~! Yes! Would be possible... Standby for updates lol!

 

[teivovo]

It doesnt crash often, but it will either crash and the batch file will all try to restart it and hit max sessions, or it will run into a problem where it tries to attach to multiple instances of d3 with the drop down menu with multiple id's.

Hi there,

Ok, as tested with Dtrick yesterday, for multiple botting instances, it is imPortant that each set of bot is loaded sequentially. So let one set fire up completely before you fire up the next bot.

Try this first bro, let me know if you are still having problems after this.


Cheers~!

 

[tesslerc]

Those who want to lower waiting times and get better insurance that no errors will occur:

Download Session Killer by tehtoad.
Extract to desired folder and open the .exe once, enter the user and pw and run once.

Edit the .bat file.
I set my times to 1-5min (1min should be more than enough, and the 5 just to add some randomness).
Now roll down to where it says "Starting DB and Diablo 3"

BRUN
CLS
ECHO **************************************
ECHO * Starting Demonbuddy and Diablo III *
ECHO **************************************
ECHO.
ECHO.
ECHO.
ECHO.

TASKLIST /FI "IMAGENAME eq %D3Name%" /fo csv /nh > D3Before.txt

START "SessionKill" "C:/Authkiller/authkill.exe"
START "D3Run" "%D3Path%%D3Name%" -launch

Add the red line b4 the START D3 line, and edit the Green part to your path to the authkill.exe file.

*Remember the authkill.exe kills ALL auth sessions, DB should auto-reconnect once session is killed (if you kill a live session and not a fail one) but just incase didn't say you didnt know

---- EDIT ----

Just checked, i killed my session while running the bot and it does NOT auto connect.
So incase you were wondering if you run multiple instances of DB this won't work for you (unless you run with v1.3 which auto kills and auto runs all instances at once and not each independently).

 

[teivovo]

Those who want to lower waiting times and get better insurance that no errors will occur:

Download Session Killer by tehtoad.
Extract to desired folder and open the .exe once, enter the user and pw and run once.

Edit the .bat file.
I set my times to 1-5min (1min should be more than enough, and the 5 just to add some randomness).
Now roll down to where it says "Starting DB and Diablo 3"


Add the red line b4 the START D3 line, and edit the Green part to your path to the authkill.exe file.

*Remember the authkill.exe kills ALL auth sessions, DB should auto-reconnect once session is killed (if you kill a live session and not a fail one) but just incase didn't say you didnt know

---- EDIT ----

Just checked, i killed my session while running the bot and it does NOT auto connect.
So incase you were wondering if you run multiple instances of DB this won't work for you (unless you run with v1.3 which auto kills and auto runs all instances at once and not each independently).

Yes bud~! You are correct... Tehtoad and I are working on a method to correctly identify your sessions so that this does not happen... Check back soon

 

[tesslerc]

Btw also i recommend to add in the same area of the kill diablo3 and demon buddy command.

TASKKILL /im "BlizzardError.exe"

just in order to remove the error window after a crash.
(unless you keep a record of how many times the game crashed for you).

 

[teivovo]

Btw also i recommend to add in the same area of the kill diablo3 and demon buddy command.

TASKKILL /im "BlizzardError.exe"

just in order to remove the error window after a crash.
(unless you keep a record of how many times the game crashed for you).

Lol, yup that was the reason why I didn't add that line in

I'll put it as an option in the next release

 

[vither]

I added -pid to demonbuddy starting in batch just to make sure that it always attaches (otherwise it may sit there and ask which window should it attach to).

Do you know if positioning windows from batch file is possible? This along with session killer would make my day

 

[tehtoad]

i can tell you guys that by end of tommorow there will be a authauth.exe that can handle multiple bots, it takes a argument passed to it that is a timestamp (ie: -stamp"00:00:00"), then it creates 20 more stamps based off 00:00:00, by adding up to 10 then subtracting up to 10, then it searches all collums on buddyauth.com untill it finds a matching timestamp (any of the 20) then it kills it.... (The other 20 timestamps make sure it can find it, sometimes the autoauth time dosnt match with the log time, but most time it does, both are taken from the server and not your local time ^_*)

This should make it possible to use with multiple bots, hopefully teivovo can find a way to scrape the timestamp from the logfiles and parse it to autoauth, if not we will work something else out.

But this will insure it dosnt kill all bots and just kills the bot that crashes
(Current version KILLS ALL SESSIONS)

 

[teivovo]

I added -pid to demonbuddy starting in batch just to make sure that it always attaches (otherwise it may sit there and ask which window should it attach to).

Do you know if positioning windows from batch file is possible? This along with session killer would make my day

Aha~! Yes, that is a very good idea. But usually that won't happen unless you fire them bots up really quickly. In order to prevent that, I have included a Loader inside the IS_Boxer package which is very useful for multibot users. It will fire up the bots sequentially so that no clashes of PIDs may occur. As the bots are executing, DB_run will pick up their PIDs.

I will look in your idea. Possible to pm me the changes that you have done so that I can take a look and possibly put into the next release for the guys?


Cheers~!



Oh~!!.. session killer is coming... v soon... Positioning, I do not think so... It can be done... but it is a very very tedious task. You could check out the thread under Guides on how to resize your D3 wiindow. If I do come across any method of doing this easily, I will definitely let you know bud!


Cheers~!

 

[teivovo]

Done~! ^_^

Doing integration work...

 

[maddjester]

Same issue no plugin...

Had something interesting happen... D3 got stuck on loading game screen.. Using http://www.thebuddyforum.com/demonbuddy-forum/plugins/58848-plugin-antiidle.html?highlight=antiidle which detected and shutdown both d3 and db. But the batch file didn't restart.. In fact it seemed to be stuck in the checking if tasks are non-responding routine.

I have had the same issue but i am not using a plugin, i will start the process, it will do a few sarkoth runs then get stuck when trying to start a game at the loading screen, its not frozen or anything, just like an infinite loop of the loading animation, i've noticed the CPU priority of d3 and demonbuddy is set to Below Normal, is there anyway to change this? i feel like this might be the problem...

 

[KennyNinja]

Since i told you i would say how to do it i asked technical support on blizz and they answered

It's stored on the Windows registry. You could use a .reg or a batch file to select a different region before launching the game.

US:
Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Blizzard Entertainment\Battle.net\D3]
"RegionURL"="us.actual.battle.net"


EU:
Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Blizzard Entertainment\Battle.net\D3]
"RegionURL"="eu.actual.battle.net"


Asia:
Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Blizzard Entertainment\Battle.net\D3]
"RegionURL"="kr.actual.battle.net"



If you want to set the RegionURL and launch the game using a batch file, you could use this code:
Reg add "HKEY_CURRENT_USER\Software\Blizzard Entertainment\Battle.net\D3" /v RegionURL /d us.actual.battle.net /f"
start "" "C:\Program Files(x86)\Diablo III\Diablo III.exe" -launch
The above code will set RegionURL to us.actual.battle.net and then launch the game bypassing the launcher. If your game is not installed on the default location or if your OS isn't 64-bit, you need to edit the filepath.

 

[chrisssj3]

Oh I forgot to change that line~! LOL...

That line was meant for v1.3... when the code was still messy... Thanks for reminding me bro...



Cheers~!

So looking at that line isn't needed anymore?

And what about the 1 hour thing? does it restart everything every hour or something?

 

[teivovo]

Since i told you i would say how to do it i asked technical support on blizz and they answered

Nice~! Thanks bud

 

[chrisssj3]

I tried ur script just now, and it starts D3 and DB correctly, I am using AGB.

However! the start button seems pressed though the charachter is still at mainmenu and the bot won't start!

EDIT:
Notifcication OK wasn't enabled yet. It seems it solves that problem. Though I still think it isn't normal?

By the way the run as administrator checkbox is greyed out for me... I can't click it??

 

[teivovo]

I tried ur script just now, and it starts D3 and DB correctly, I am using AGB.

However! the start button seems pressed though the charachter is still at mainmenu and the bot won't start!

EDIT:
Notifcication OK wasn't enabled yet. It seems it solves that problem. Though I still think it isn't normal?

By the way the run as administrator checkbox is greyed out for me... I can't click it??

Hey bud~! That's great news~!

OK.. the not clicking of the start button happens sometimes. That's why i use NotificatioOKClick. Sometimes DB doesn't register or keep the settings of the previously enabled plugins. Do this instead:

1. Go to your Demonbuddy folder and locate the Settings sub-folder.
2. Inside Settings, your should see a folder with your Battletag on it. Enter that folder.
3. Locate a ChracterSettings.xml file and edit it.
4. Manually add the entry for NotificationOKClick as shown below:

 <EnabledPlugins>
    <Value>NotificationOKClick Plugin</Value>
     .    any other plugins that you want DB to startup with.
     .
  </EnabledPlugins>

OK. As for your Administrator checkbox being greyed out:

You cannot set Run as administrator for a batch file. There is a workaround as mentioned in my first post regarding creating a shortcut to point to the batch file. You can assign the shortcut to Run as administrator which will in turn run the batch file with admin rights. Take a look at the first post bud. Its explained there (a little messy though )

Have fun with the batch file


Cheers~!

 

[teivovo]

I tried ur script just now, and it starts D3 and DB correctly, I am using AGB.

However! the start button seems pressed though the charachter is still at mainmenu and the bot won't start!

EDIT:
Notifcication OK wasn't enabled yet. It seems it solves that problem. Though I still think it isn't normal?

By the way the run as administrator checkbox is greyed out for me... I can't click it??

Hey bud~! That's great news~!

OK.. the not clicking of the start button happens sometimes. That's why i use NotificatioOKClick. Sometimes DB doesn't register or keep the settings of the previously enabled plugins. Do this instead:

1. Go to your Demonbuddy folder and locate the Settings sub-folder.
2. Inside Settings, your should see a folder with your Battletag on it. Enter that folder.
3. Locate a ChracterSettings.xml file and edit it.
4. Manually add the entry for NotificationOKClick as shown below:

 <EnabledPlugins>
    <Value>NotificationOKClick Plugin</Value>
     .    any other plugins that you want DB to startup with.
     .
  </EnabledPlugins>

OK. As for your Administrator checkbox being greyed out:

You cannot set Run as administrator for a batch file. There is a workaround as mentioned in my first post regarding creating a shortcut to point to the batch file. You can assign the shortcut to Run as administrator which will in turn run the batch file with admin rights. Take a look at the first post bud. Its explained there (a little messy though )

Have fun with the batch file


Cheers~!

 

[teivovo]

Hi guys, DB_Run_v1.6 will be released soon~!

Updates:
1. Will now check for network connectivity as well. Currently based on 3/5 ping drops, DB and D3 will be restarted (and hopefully the connection will become better).

2. Will now interface with tehtoad's AutoAuth app and kill BuddyAuth sessions so that you will not get the Max session errors anymore.
(Why do I need this when DB 173 already does this?)
Yes, DB 173 does this if you close it manually or if D3 closes first. If DB 173 crashes, or is forcefully closed, the session will remain on BuddyAuth. So AutoAuth takes care of the other half of the problem.


Cheers~!


Erm.... nope... there'll be no v1.5.....

 

[chrisssj3]

Thanks teivovo, well the shortcut is also blanked out for some reason! But it seems to work so no worries?

Btw if I just started bot 13 minutes.. 3 stucks.. check my log right now and I see

[23:22:44.506 N] [NotificationOKClick Plugin0.9] Warning ! NotificationOKClick thread is not working!!!
[23:22:44.594 N] [NotificationOKClick Plugin0.9] Warning ! NotificationOKClick thread is not working!!!
[23:22:44.684 N] [NotificationOKClick Plugin0.9] Warning ! NotificationOKClick thread is not working!!!
[23:22:44.774 N] [NotificationOKClick Plugin0.9] Warning ! NotificationOKClick thread is not working!!!
[23:22:44.854 N] [NotificationOKClick Plugin0.9] Warning ! NotificationOKClick thread is not working!!!

Into infinity.. Though bot is still running so.. weird.