Not sure what you guys are doing, but I've had ARelog up since the Friday update and it's been running perfectly aside from not killing the DB process when it kills the Diablo process.
Would you mind explaining how you set yours up? I've been following the configuration in the OP, but it still won't work, so maby I've missed something that you have catched?
Been hassling with this shit for too long I should NOT have to use this crap. I used HBRelog for so long, but now with Diablo I have to use this again. Relogging/Auto Launching has been a part of much simpler bots. It should be included, or this should be a finished and stable product.
Amazed by this "little" program. So damn powerful! But I confess I was scared at first... you know, giving away such delicate information. I'm gonna try it tonight and edit with the results. I mean, it works just fine, but I hadn't had the opportunity to see how it works when I get dced. EDIT: Yep, working like a charm. Rep +
Anyone have a solution for it not logging into D3? It runs D3 and DB, but it starts D3 and does not login.
Session Invalid Fix - Autohotkey script for you fellow Arelog fans. http://www.thebuddyforum.com/demonb...nvalid-temporary-fix-autohotkey-required.html
Enter too fast the password in D3 Windows and is unable to login. Password Characters only appear 10 secs later and login button become enable .
hmm changing the screen resolution does nothing for me. i set it to 400x300 but it still runs at 800x600 after i start it up...
I keep getting the same error over and over, it was working fine a few days ago, but now it's always this error and it won't resize/login or anything.
Hate to say it. But ARelog is not even close to being ready for demonbuddy. It cant do its job of "Relog" after a crash or a problem.
Did this allways require .NET 4.0? I had to remove all .NETs appart from 3 or 3.5 (Dont remember) to be able to run HB. If I install .NNET 4.0 I cant run HB anymore! I have Windows XP 32bit.
Still getting stuck with D3 when there is a disconnect and NOTHING happens. When WoW disconnects, both WoW and HB are closed and restarted completely. When D3 disconnects, NEITHER D3 or DB are restarted. Why in the world does the relogger not relog? This is rediculous... >_>