Nice! And congrats
Happy botting~!
Thx... and thx for a very good and simpel relogger (this relogger is the only one that works like i wan't it) - very good job.
[Batch File] DB_Run: Command-line based Anti-Crash and Relogger
- Thread starter teivovo
- Start date
Thx... and thx for a very good and simpel relogger (this relogger is the only one that works like i wan't it) - very good job.
Pachi
Member
- Joined
- May 31, 2011
- Messages
- 117
- Reaction score
- 9
Hello, I just want to say love the Command Line Based Anti-Crash and Relogger. I have one question I would like to ask that would greatly help with my setup. When the game or bot crashes it uses the min_restart_minutes / max_restart_minutes time before it starts everything back up. What would I need to edit to have it use the min_minutes / max_minutes time?
teivovo
New Member
- Joined
- Jun 25, 2012
- Messages
- 353
- Reaction score
- 5
Hi there,
Lol, I got to rename the variables
The min/max_restart_minutes actually determine how many minutes the bot should run before the bot is totally shut down and restarted (with no errors encountered). The min/max_minutes is the number of minutes is how long the bot will rest after being stopped before it is powered on again.Hope that clears your confusion
Cheers~!
teivovo
New Member
- Joined
- Jun 25, 2012
- Messages
- 353
- Reaction score
- 5
Nope, this is not a typo. Both sets of variables are being used. Just for different purposes. They are working as it is supposed to. Just probably need to emphasize more on what makes them different
Pachi
Member
- Joined
- May 31, 2011
- Messages
- 117
- Reaction score
- 9
Ah, maybe I should tell you want I am trying to do and maybe and we would see more eye to eye on what I was trying to do. I wanted to the bot to run for 4hr and then shut down for 4 hrs, after that it would start back up in 4 hours. But if the bot is running and an Error is detected, it will sleep for another 4 hrs and then start. I wanted it to use the lower time restart like 3 - 5 minutes if Error is detected.
Update: Ah, I got it to do what I was looking to do. I just changed the goto in Detected. That way after an Error is Detected and the bot restarts it does not sleep for that long time at the start. Thank you for the great work you have done with this my good sir.
Update: Ah, I got it to do what I was looking to do. I just changed the goto in Detected. That way after an Error is Detected and the bot restarts it does not sleep for that long time at the start. Thank you for the great work you have done with this my good sir.
Code:
:DETECTED
CLS
ECHO ******************************************************
ECHO * Error Detected. Restarting the full suite. Standby *
ECHO * Please Wait....................................... *
ECHO ******************************************************
ECHO.
ECHO %ERROR%
ECHO. >> %Log_file%
ECHO %Date% %Time% - %ERROR% ************* >> %Log_File%
ECHO. >> %Log_file%
ECHO.
ECHO.
TIMEOUT /T 15 /NOBREAK
[COLOR="#FF0000"]GOTO :[B]START[/B] Change to [B]DBRUN[/B][/COLOR]
Last edited:
teivovo
New Member
- Joined
- Jun 25, 2012
- Messages
- 353
- Reaction score
- 5
Ah yes... That would do... I didnt do it this way initially coz I was afraid at the start that some D3 crash errors were purposely triggered by Blizzard. Therefore I didnt want the batch file to keep launching the bot so soon after encountering a crash (coz crashes were quite frequent a few months back). So I did this in order to back off a little rather than be too aggressive with the bot restarts.
Looks like i was a little to fast in my statement. I worked fine just after the fresh install. But today, 1 day after it dosen't work again. =( Think i will try a new fresh install again later today, and see if that can make it work again.
Pachi
Member
- Joined
- May 31, 2011
- Messages
- 117
- Reaction score
- 9
Ah yes... That would do... I didnt do it this way initially coz I was afraid at the start that some D3 crash errors were purposely triggered by Blizzard. Therefore I didnt want the batch file to keep launching the bot so soon after encountering a crash (coz crashes were quite frequent a few months back). So I did this in order to back off a little rather than be too aggressive with the bot restarts.
It still saves the total bot restart time from before the crash, so it just picks up right where it was time wise. Not as aggressive as it would be if it just start the time all over from the start.
teivovo
New Member
- Joined
- Jun 25, 2012
- Messages
- 353
- Reaction score
- 5
2 questions:
Where in the bat file can i change the time it waits to open DB AFTER D3 is open? It seems to wait too long in the main menu before trying to open DB. Can you specify which line code is it?
Also is it possible to have Diablo 3 login into the account before trying to open DB? Currently the batch file would first open the game, wait about 2min then open DB, once it loads a profile then it will log into the account. I believe this would sometimes cause a problem with the plugins not loading correctly because i have seen that they arent checked in the plugins tab.
I think if you can have D3 Login first then load DB, it would solve some plugin issues.
Thanks
Where in the bat file can i change the time it waits to open DB AFTER D3 is open? It seems to wait too long in the main menu before trying to open DB. Can you specify which line code is it?
Also is it possible to have Diablo 3 login into the account before trying to open DB? Currently the batch file would first open the game, wait about 2min then open DB, once it loads a profile then it will log into the account. I believe this would sometimes cause a problem with the plugins not loading correctly because i have seen that they arent checked in the plugins tab.
I think if you can have D3 Login first then load DB, it would solve some plugin issues.
Thanks
Last edited:
solution to fix plugin autostart:
1. run d3, run demonbuddy, mark plugins you want to autostart
2. close demonbuddy
3. change file attributes of "settings\%battletag%\CharacterSettings.xml" to read-only
now i will successfuly load that plugins every time you run db_run.bat
remove "read-only" flag, if want to disable some plugins.
1. run d3, run demonbuddy, mark plugins you want to autostart
2. close demonbuddy
3. change file attributes of "settings\%battletag%\CharacterSettings.xml" to read-only
now i will successfuly load that plugins every time you run db_run.bat
remove "read-only" flag, if want to disable some plugins.
for those settings did you set PluginProblem to 0 or 1 ?
tested and it doesn't work with gileas stash replacer, bot pick up every crap that mobs drop :/
teivovo
New Member
- Joined
- Jun 25, 2012
- Messages
- 353
- Reaction score
- 5
Hi there,
its somewhere in this thread... You'll need many copies of everything: DB, D3, batch file. Each set of bot is controlled by 1 batch file so you will have to configure each batch file for the specific bot that you will be running it for.
Cheers~!
teivovo
New Member
- Joined
- Jun 25, 2012
- Messages
- 353
- Reaction score
- 5
strange, but it works for me. gileas stash replacer, only plugin i have
^ True story.....
I tried with a new install, but couldn't get it to work. I went back to version 2.2 and changed the wait time for "loginsceenappear" to about 25 sec. Now it works just fine with Gilesstashreplacer. I have restarted several times, and it still works. I guess the thing (version 2.2 of this batch file) do when it restart buddy after D3 login, works just as it should - atleast for me.
Tried this last night myself and it didnt work for me,
. i found that DB's high level rules works but it will pickup potions and jewel blacksmith tomes so i deleted those out in the xml. i edited the potion to mythic