But I want to discuss another matter. After rip I called a friend and we do small experiment - I intentionally unplug my ethernet cable and he counts for hor long my hero will be in game after that. It was tremendous 40 seconds! Why it is so much when the game should disconnect you after 10 seconds?
It's not that hard to code - just send small packets to client every 1 or 2 second and if server dont have response in 10 seconds or any other network input from client it should assume that DC occured 10 seconds ago and instantly remove you from the game! My WD surely would survive 10 seconds on Butcher...
Now if you get disconnected because of blizzard's fault you immediately login on your second pc/laptop by pressing enter.
Normally if your char is ingame and someone logs into your account you immediately get kicked to login screen. With this method your char is saved from a disconnect death.
Create a shortcut to Diablo III.exe and change it like this:
"C:\Program Files (x86)\Diablo III\Diablo III Launcher.exe" -launch"
Now change 1 diablo 3 client to 800x600 all settings low/off, windowed mode and make the window as small as possible so it doesn't cost much system memory. And just press Alt Tab.
Personally I never did this, but it's one way..
Blizzard will not fix the DC issue, because they don't care about hardcore.
But I just wanted to raise the problem on forum because its not so difficult to fix it and I offered the solution in my post above and its lame that Blizzard haven't employed it in game :(
I'm not THAT good in programming (at least in gaming programming - I mostly write bank and finance sql-related c/c++ code) and I'm quite sure that I got much less monthly fee than Bliz programmers so its double lame that they are so bad...
Also copy the Diablo III.exe to your desktop as shortcut not the launcher.exe
Let me know if it works.
You need to copy the whole diablo 3 folder and run both instances as admin.
I have these 2 shortcuts on my desktop:
"C:\Program Files (x86)\Diablo III - Copy\Diablo III.exe" -launch
"C:\Program Files (x86)\Diablo III\Diablo III Launcher.exe" -launch
After you open the first client. The second client MUST be opened by loading diablo III.exe with the launch command (not diablo III launcher.exe) Otherwise it does not work.
I have to run launcher not as admin because I got file not found error otherwise. But I can run Diablo III as admin and it worked I have 2 Diablo copies running now.
03/03/2013 11:37Posted by GlaDOSBut I can run Diablo III as admin and it worked I have 2 Diablo copies running now.
Just a shame you have to do this to play a HC Blizzard game and prevent avoidable DC deaths, when in reality for a £50 game, I'd expect that the game producer woul have some sort of FAIL SAFE for HC characters.
03/03/2013 15:04Posted by Leviathanhow can someone spent more then 500k on character under lv 60?
Here is my dead WD:
63 level weapon
63 level shield with AR
63 crafted shoulders
61 belt with AR
58 bracers with AR + Armor
All this costs you know. I don't remember the exact price, but its smth. near 5 mil
All these items allow you to go solo mp10 hell to level up faster.
When you have around 150 millons gold its not THAT much to spend 5 mil on your low level hero.
02/03/2013 20:33Posted by MeltykissNormally if your char is ingame and someone logs into your account you immediately get kicked to login screen. With this method your char is saved from a disconnect death.
thats wrong, got "fixed" months ago... when you log in second time it takes 10 seconds for char to leave the game, except youre in town
Unfortunately it has its "workarounds": my monk's been through only one disconnect, but 3 or 4 power outages, in which case no computer in the neighborhood can help anymore.
Luckily none during an elite fight, but I'd still like best a solution directly from Blizzard. :)
It should be 10 seconds - NOT 40. And I offered an algorythm that allows the exact 10 seconds in such case (look at my first post). It is very sad that bliz network programmers are so lame that it actually takes 40 seconds for the game to determine that you are off and kick you from the game (again look at my fist post).
01/03/2013 20:54Posted by GlaDOSIt's not that hard to code - just send small packets to client every 1 or 2 second and if server dont have response in 10 seconds or any other network input from client it should assume that DC occured 10 seconds ago and instantly remove you from the game!