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

[teivovo]

You could try NotificationAutoClick - by nooberry see if it works for you

 

[Vesparion]

But how can notification auto click help in this case ? there is no error or notification to click, it just demonbuddy in idle and D3 on character screen and nothing is going on.

 

[teivovo]

Just some updates. There is a 20 seconds timeout from the point DB starts D3 until D3 is idle. So if D3 can't start within this 20 seconds, then DB will not latch to the D3 instance and give a message:

"Waited 20 seconds for Diablo III to start but process isn't idle yet. Please restart Demonbuddy"

So if this is the case for you, then unfortunately this batch file won't work...



Cheers~!

 

[flupppa]

very good job!

 

[teivovo]

Thanks mate~! Hope it helped you as much as it helped me.

 

[Eutopia]

Just some updates. There is a 20 seconds timeout from the point DB starts D3 until D3 is idle. So if D3 can't start within this 20 seconds, then DB will not latch to the D3 instance and give a message:

"Waited 20 seconds for Diablo III to start but process isn't idle yet. Please restart Demonbuddy"

So if this is the case for you, then unfortunately this batch file won't work...



Cheers~!

Takes me 3 sec to start d3, it starts up db and d3 fine but it only idles battle net account login screen without logging in.

 

[teivovo]

Try running the 2nd last line of the batch file inside your command prompt. See if DB is running D3 as it should.

"c:\Users\XXX\Desktop\Demonbuddy 1.60\Demonbuddy.exe" -key 1234567890 -bnetaccount [email protected] -bnetpassword BnetPassword -d3path="C:\Program Files\Diablo III\Diablo III.exe" -profile="c:\Users\XXX\Desktop\Demonbuddy 1.60\Profiles\Example.xml" -routine="Belphegor All-in-One" -autostart -noflash

The batch file is not doing anything extra with DB other than opening it via command prompt.

 

[Lionel]

Just some updates. There is a 20 seconds timeout from the point DB starts D3 until D3 is idle. So if D3 can't start within this 20 seconds, then DB will not latch to the D3 instance and give a message:

"Waited 20 seconds for Diablo III to start but process isn't idle yet. Please restart Demonbuddy"

So if this is the case for you, then unfortunately this batch file won't work...



Cheers~!

Im having that damn problem :\
Are there are way to increase 20 seconds?

 

[lobonija]

I also have the same problem, this file starts demonbuddy and D3, then just idles at the login screen, doesn't seem interested in typing in the password. My D3 also loads very quickly.

 

[teivovo]

Im having that damn problem :\
Are there are way to increase 20 seconds?

Erm... I can't do anything about this as the timeout is due to the bot. Maybe the devs can take note and extend this timeout in future versions?

 

[teivovo]

I also have the same problem, this file starts demonbuddy and D3, then just idles at the login screen, doesn't seem interested in typing in the password. My D3 also loads very quickly.

Have you tried running DB using the 2nd last line of the batch file from an elevated command prompt to see if it works?

It should read something like this (just an example):
"c:\Users\XXX\Desktop\Demonbuddy 1.60\Demonbuddy.exe" -key 1234567890 -bnetaccount [email protected] -bnetpassword BnetPassword -d3path="C:\Program Files\Diablo III\Diablo III.exe" -profile="c:\Users\XXX\Desktop\Demonbuddy 1.60\Profiles\Example.xml" -routine="Belphegor All-in-One" -autostart -noflash

Try and see if it runs. If it shows the same symptoms, then it is unlikely the batch file is going to work for you.

 

[wowcheesestick]

The batch file doesn't kill diablo 3 or DB for me, although it says it suceeded

 

[teivovo]

2 things you could check and do:

1. Manually run the commands while DB and D3 is running:
taskkill /im "Diablo III.exe"
taskkill /im "Demonbuddy.exe"
Check if just plain running of the commands work for you.

2. Input these changes to these two lines in the batch file:
taskkill /im /f "Diablo III.exe"
taskkill /im /f "Demonbuddy.exe"

Take note though that if you choose to use /f which forcefully closes DB and D3, you need to set you min_minutes to at least a 5 minutes so that buddyauth can release your session. Any lesser, you could get a "Max_session" error the next time your DB runs.


Cheers~!

 

[wewanted]

waiting something like this after try hard with Arelog

 

[rcadams]

This is great. But how about a plugin to go along with the batch file. This is what I'm thinking, Have the plugin monitor activity of db. Have it somehow detect there there has been no changes "game joined", "movement", "or just d3 hung" then have the plugin issue the following command to shutdown db.

Application.Current.Shutdown();

then make the simple changes to batch file to create a loop. so that if db is shut down it loops to the top.

 

[teivovo]

This is great. But how about a plugin to go along with the batch file. This is what I'm thinking, Have the plugin monitor activity of db. Have it somehow detect there there has been no changes "game joined", "movement", "or just d3 hung" then have the plugin issue the following command to shutdown db.

Application.Current.Shutdown();

then make the simple changes to batch file to create a loop. so that if db is shut down it loops to the top.

Nice idea~! But alas... I didnt pay much attention during my programming classes... so this will probably take a long time..... Will try though


Cheers~!

 

[rcadams]

I thought maybe someone who coded http://www.thebuddyforum.com/demonb...kclick-auto-click-notification-ok-button.html
or http://www.thebuddyforum.com/demonb...er-restarts-if-your-character-gets-stuck.html could take a stab at it since they are already monitor activity in one sense.

 

[masterjeff]

I didnt tried it yet, but this seems great...my only problem is: im running 2 d3&db clients....dont know how your batch could handle this...i mean...the problem is, DB is asking u wich d3client should "flashing"...your batch file cant handle this, can it?

 

[teivovo]

Hmm... im not too sure with this... but what I could suggest is to have two sets of everything running via vmplayer or vmware....

Or if you are running let's say 2 DB cum D3 instances on one pc, you could differentiate both of them by changing file names and having different run paths eg: Diablo IIIA.exe and Diablo IIIB.exe, DemonbuddyA.exe and DemonbuddyB.exe and so forth. Make sure that you have two separate batch files controlling the different instances and amend the paths in them correctly. Fire up both batch files and see if they will work concurrently. If they do, run the batch files again and see if they close correctly. If that works too, then all you need to do is to create two separate tasks in the task scheduler to fire them up at different times.

Lemme know if it works for you! I'm quite interested to know too... But I'm currently only running 1 instance of D3

 

[masterjeff]

mmh, that was my idea at first too...but if it will kill all instances of d3&db, it couldnt work i tought - but with your trick it could work, i will try that when im back home and will post my results