TLDR: A timeout auto-quit function to prevent HC chars from dying to lag
Sometimes, servers lag up, or sometimes its my own Wifi. Regular resets reduce the probability, but not eliminate it.
Either way, losing a character to momentary timeout or lag after a month or more of leveling a hardcore character - is devastating.
Dying to my own failures of imagination, preparation, adaptation or awareness is always acceptable as a means to learn and grow. However, I’ve never had a hardcore char die from lag and said, “I learned something valuable here” other than to quit the game and focus on IRL pursuits.
A feature where if it detected a pattern of timeout, exited your char from the game, would be amazing. I would never be upset if it did so even while I’m sitting in town with a ground full of uniques and HRs to be transferred and lose it all, if it meant there was some kind of lag death prevention.
I know its a niche demand from a poor HC player… but it would be godly as a feature
2 Likes
I don’t think hardcore is for online, honestly…or if you do play it online, you inherently enter into a contract accepting that you WILL die whether it’s your fault or not, it’s not a question of if but when. That’s why only crazy people play hardcore online.
1 Like
so
you think hardcore is just offline
and when you die
you can just restore your character
1 Like
Yeah but I like to play with others. When there’s a community of HC players its actually really fun. Besides single player is just too isolating. The social component keeps things more interesting.
1 Like
I mean, I agree and I get that. But then you must accept the Online HC contract that states you WILL die, whether it be your fault or not. There’s no real right to complain. It’d be like walking through fire then complaining you got burned, and saying we gotta do something about getting burned when walking through fire, so let’s put on this fireproof suit. But then what’s the point of walking through fire in the first place if there was no risk…
Have you ever got running too fast → dissconnected-> die after re-login with a Barb? The old D2 said running fast will casue lost sync with server due to network limit. But 20 years later with much gowth of network technology but still having same problem…
I understand and accept the risks of hardcore and ultimately, the tradeoff is worth it for me.
But to be fair, connectivity issues aren’t part of the scope of game design or intended user experience. We’ve all learned to accept the limitations of the game over time (been playing for over 20 years). However, with D2R showing promise of improvement, and even (gasp) expansions… there may be light at the end of the tunnel for a better UX in hardcore mode 