The MAIN problem is that after a fresh restart it doesn't reinsert the account data, so d3 doesn't log in, so db doesn't start....
Please tell me what to do
you guys just use YAR (yet another relogger), i switched as soon as it supported innerspace and it works way better. This does the job but it gets tangled up (all 4 batch files hooks onto one diablo game and thinks everything runs fine). it works and its better then nothing but its kinda messy
Anyone know the lines i should remove so it does not detect if diablo iii crashed? it seems to keep killing my D3 in my VM due to thinking it crashed when it really didn't. Thanks,
EDIT: i commented out the checks i think i may have got it waiting...
EDIT2: nope commented out too many it starts everything then quits....
This is exactly what I'm looking for also. I noticed since the last few DB updates that I get a little video lag here and there when Diablo is running and I only get this lag when DB is running. Well, whenever DB_RUN does the 1 min. check for crash and if at that exact same moment I'm getting a little video lag, DB_RUN thinks my game is crashed when it really isn't and shuts it all down. I wish there was a way to make the 1 min. check actually check for a longer period of time instead of just an instant 1 sec. check it seems like.
ECHO Checking in another 1 minute.
ECHO.
ECHO ******************************************************
ECHO.
TIMEOUT /T 30 /NOBREAK > NUL 2>&1
ECHO Checking in another 2 minute.
ECHO.
ECHO ******************************************************
ECHO.
TIMEOUT /T 90 /NOBREAK > NUL 2>&1
I still use the 2.3 version that isn't available on the first page. I posted it somewhere halfway in this thread.
sameim using the 2.4 version and i have everything set up it loads the plugins and logs in but then diablo crashes. What do i do?
anyone has any idea?same
If you are using trinity .11, try version before? Cant test it right now, but maybe this is a problem.anyone has any idea?