Hardcore latency, major issues [PETITION]
|
To clarify, this thread is not meant to be about Save & Exit death evasion. It is meant to be about a legitimate problem that stems from the client not properly communicating with the server, resulting in the player seeing something different than the server.
Save & Exit was merely an excuse brought up for why things are the way they are. While the intentions are good, the results are very bad for a game as fast-paced as this. Give me hardcore or give me death.
|
|
|
You're making false assumptions about how the system works, and why it is how it is.
I've explained to the best of my knowledge the facts of the situation. |
|
" Any assumptions I've made are in favor of GGG being competent developers, meaning heartbeat/keepalive routines are either not active during loadscreens or operate in the background with higher priority than loading an area, not that they require any sort of computational power a computer that meets the minimum requirements wouldn't have 10,000-fold. If tpapp157 and the players driving the conversation towards exploit discussion are wrong, and I'm wrong about it being about it being to save server cycles, and the reason heartbeats are exchanged so infrequently is because people are missing them during load screens.. well, then there's no excuse to not to use less frequent heartbeats or an alternative system during and shortly after loading, and use more frequent ones during any other time including gameplay. The only justifiable reason to NOT use more frequent heartbeats is saving server bandwidth and cycles, really, if there's already a separate (bad) system in place that waits 3 seconds before logging you off to work in combination with it. Give me hardcore or give me death. Last edited by MusicGTELife#4330 on Jan 18, 2012, 7:14:49 AM
|
|
"It's not an excuse; it's the reason. Curbing exploits is an important part in balancing the game to make it fair for all players. Network/server issues can be improved without allowing this exploit. Closed Beta/Alpha Tester back after a 10-year hiatus.
First in the credits! |
|
|
Let me put it this way: if the goal of someone pulling the plug on their connection was to avoid death, or some other imminent occurrence, then having a short time-out would actually benefit that person - in exactly the same way that it would benefit someone whose connection is lost accidentally.
So the idea of introducing a time-out to discourage that type of behaviour does not make sense. The time-out is in place for precisely the reasons you outline in your original post, to minimise the risk of deaths for players that have lost contact with the server. I don't know how the code itself works, but I can say that when the time-out was first reduced to around 5 seconds, some players experienced frequent disconnections, mainly when loading areas. A few patches ago, the load times for entering areas was reduced dramatically, enabling the time-out to also be reduced. However since then there seems to have been a regression, and the "freeze-frame" upon entering a new area has returned. So you can can expect that the time-out will be reduced again in the future when possible. |
|
" I wouldn't call some players dying and losing all their progress because of unstable connections fair. And yes, network/server issues can be improved without allowing this exploit, there are several suggestions in this thread on how to do it. Talk to malice I guess, he just said this is not the reason. Give me hardcore or give me death. Last edited by MusicGTELife#4330 on Jan 18, 2012, 10:59:33 AM
|
|
" Most of this still has nothing to do with what I'm talking about. I'm not going to expect anything until I've spoken with a dev about this issue, that's how things go overlooked and make it out of beta. I'm really not enjoying talking in circles, I know my walls of text are intimidating, but please read them before you say that reducing the heartbeat will cause players to get disconnected when loading or saying that it will allow exploits. Edit: If I'm coming off as rude I sincerely apologize, this is an important issue to me and I'm trying to explain things the best I can to people that I think might not understand what I'm trying to convey. Nothing I have typed has been with any amount of hostility so please do not take it that way. Give me hardcore or give me death. Last edited by MusicGTELife#4330 on Jan 18, 2012, 11:05:32 AM
|
|
" This is more of an issue of my ISP dropping and my client staying in game for well over 15 seconds after the last packet sent, I've spent a few minutes looking into just how long it takes before my client is disconnected for non-response. Suspending the process for 5 seconds, then resuming brings no connection drop; Suspending the process for 10 seconds, then resuming brings no connection drop; Suspending the process for 15 seconds, then resuming brings no connection drop; Suspending the process for 20 seconds, then resuming results in connection drop. So I have had two deaths due to this in a week now, and have since stopped bothering to play until this is sorted out. Though I have added a few bug reports recently I am waiting until this and other usability issues are resolved before I give this game another try. |
|
" This is disgusting, thanks. I am also waiting for this to be fixed to resume playing, though I might play an extremely tanky marauder while I wait. Edit: confirmed this myself, 15 seconds with no disconnect. Went as long as 20 seconds once in 3 tries. Give me hardcore or give me death. Last edited by MusicGTELife#4330 on Jan 18, 2012, 2:05:37 PM
|
|
|
Well.. I don't know about anyone else but I've Alt + F4'd plenty of times in the heat of battle. I've done it on tanky Mara's and squishy Rangers and Witches. I've never once lost a character in Hardcore. Although it takes about 25 seconds for me to boot PoE back up, so maybe I just got lucky..?
What I do know, however, is that I can click 'Exit to Login Screen' and Relog in 3 seconds flat(it's actually closer to 2.8-2.9 seconds) and I'm back in the nearest Encampment. Last edited by FaceLicker#6894 on Jan 18, 2012, 2:05:39 PM
|
|
