It has been change to the current behavior for this reason (Against maphack and its hardcore dying hack ).
It didn’t solve that issue bots still survive on vanilla d2 lod with active maphacks i have already pointed that out! and i already said it’s bad “design” to keep characters in the game ( not only technology) + they did suffer from heavy activity load for a long perdiod which lead to queues and disconnects so it is also their technology (not only bad design).
@xRazielx
Yeah it’s your fault for chosing to play HC i get that. But you also get disconnected when their server suffer from heavy load or just simply DDos attacks and thats on them. You can’t react to that and there is currently no rubberbanding that would indicate that. You simply get the message of the DC and your character is still in the game for several seconds (and thats also on them). You may be fine with random deaths but i am not. I prefer to play with less issues than with more and i really don’t get how you can argue otherwise. Other games have different kind of issues but they already solved that random death DC problem to a better extend than d2r does which is all i am asking for.
Alot of people don’t play Hardcore or generally D2 exactly because of the fear of death to DC’s and not because of the fear of death alone. Making the situation less frustrating would lead to more people playing hardcore and make the game more attractive to a hardcore audience.
But you can also leave the situation as it is and slowly decline that kind of nieche players until everyone has lost interest. And again it’s not about losing your stuff. It is about how you lose your stuff.
Personnaly i am against the “keep in game few second after a disconnect” feature.
And yes it counters HC never_die hack so it really solves this issue.
Everyone hates this feature. instead of complaining about TCP/IP we should ask for a change and all sign it with a simple “agree, please Blizzard, remove it”.
well, I guess i’m a genius but I got solutions: if player got +90% hp / server lost connexion with client / the player don’t move for 10 sec in a battle : auto kick.
Yeah you can pay me for this
Another solution: semi hardcore: if you die you cannot play for 14 days with the death char / drop penality (for a ladder its strong)
this way we wont see trash softcore playstyle with -75 all res rushing all the waypoints
I already explained in another thread that is is just not true. Diablo 2 never implemented an anti-S&E feature in the game. And the reason is obvious: the solution would suck and be very detrimental to HC characters.
Show us when Blizzard ever implement this, or stop saying they did.
Let me try again: Blizzard never implemented this. This is simply a consequence of their legacy networking code not having more modern latency or lag protection features. This problem was very common in online games well into the 00s.
You forgot stupidity. For not trying to increase quality of life. Living in the stoneage where people died at the age of 30. But yeah “death is always the same” and there is no need to change that. Guess nihilism is popular again.
No, i don’t. Yes, it’s are realy stupid - buy a game with “no changes, exept graphics” and then whine on “stupid old code/mechanics/game rules”
As one player sayed “i want D2R was as D3 but D2, yes i hate D3, but i want D2R same game mechanics as D3 but in D2 look a like”…
Personaly, i want lootfilter, but devs say “no” and i take it. Should i start a topick about “they take my money as for full priced new product but even not add a lootfilter in this damn old piece of sh@t”?
Improving the net code to more modern user expectations fits perfectly well with the idea of wanting a remaster true to its original. It’s in fact expected by almost everyone. Clearly, not by you of course.
Of course, implement new net code is less then northing if compare with loot filter implementation. I’m pretty sure, you change a whole net core of product at least twice per day.
So much nonsense. And now you spin it to make it look like a discussion on it being hard or easy, instead of being right or wrong…
For your information solving these problems is exactly what they are doing. The effort to bring the first ladder season and setting up PTR servers includes improving the servers stability and solving the bnet issues currently plaguing users. As announced by them!
So, no. Blizzard thinks differently from you, and agrees constant disconnects is not how a game should be experienced in 2021.
There are no “constant disconnects” since first first weeks from launch. And yes, disconnect still may happen, because its not only you device and they servers. There are many cases why and how it can happen. And no one “root cause”, so it’s can’t be solved with one solution. Even with reduce “keepalive” delay, where game close after not recive keeplaive packets from client - there still can be “time window” where you character stay uncontrolled. And there still can be in game situation, where character can be killed in less then second without you reaction- Uber Tristram, some afficses on De Seis minions, some afficses on random packs, tele to Baal on map with dolls, etc, etc.
And yes, Blizzard reduce numbers of such things. Already fix many and going to fix more.
But, you talk about 100% insurance from any network or hardware events… I’m not sure if it’s possible
Well, then i don’t understand this. This topic created 22 Dec, 3 month since launch. And as we all agreed Blizzard did they job - they fix a lot of game issues for this period. But of course some issues may still and will be fixed soone, but some issues is not on they side and even after all d/c may occure in rare curcumstances.
Realy, after some periodical game crashes first weeks since launch i’m not faced any issues till i god my first and last d/c in my assasin first Uber Tristram and lost her.
Ok, it’s happen once. It’s hurt. I’m frustrated. But why i should blame Blizzard?
I didn’t understand. Yes, it’s extremaly unluck. For the other hand - i found 5 Ber runes, 2 was found on assasin charater. I saw d/c issue (happen once) as same as Ber drop issue. It’s not by any fault or bad game code - it’s very rare, very probability, it’s a thing, what just happen sometimes somehow.
If issues like d/c was happen at least once per day or once pper week or any regular base…
Then yes - i can agree with you, guys. It’s ridiculous and Blizz should to hard work and fix it… But wait - they did. They fix and watch on this and try to improve.
but you all still standing there and discuss about quality of life and stoneage and fear of death to d/c…
We all understand there can be connection issues outside of blizzards backend that’s not the point and just shows that you can’t think outside of the current box. It’s not only about their backend it is about the implementation. There is no need to keep a character longer than 1 or 2 seconds after a DC in the game and yes there are ways to get it done in this time. You are repeating your arguments over and over but you don’t add anything new to it. They can make the situation better and as people have written it is not so hard to do so. They simply don’t care or prioritize it and people like you neither. And again i am fine starting over and over again. That’s not an issue. Like so many others i would prefer not to loose to something i have no control over. Random Deaths are NOT fun. And i play to have fun. I don’t play to be frustrated.
And yes their server still have issues. They are not fine. We still have gamecreation timer. We still have laggy instances. We still have disconnects. They got much better that may be true. But we lost a lot of players aswell. So you can’t tell what happens after ladder reset.
I still don’t understand how you can defend the current situation. What is effectivly better right now? You need to add arguments instead of your nihilistic attitude. This is not about shaming or defending the devs this is about adding value to a game by making “Quality of Life” changes. Your overprotectionism doesn’t make the game better.
Now pick what i have said and use counterarguments please. Instead of repeating: “Don’t be frustrated - Death is Death - DC’s are Rare”
Improving Server stability + Removing Characters from game after DC much faster:
Pro:
-less people die to disconnects
-more people play hardcore
-less frustrated players
-game is up to ‘current’ standards
-may enable alt+f4 to save your character ( A town portal has the same effect )
-they promised a polished version of d2 ( not only graphics )
-more fun ( less lag/delays equals more fun )
Contra:
-developement costs
-may enable alt+f4 to save your character ( A town portal has the same effect )
-no changes ( i guess this is already of the board )
Apparently I confused with diablo 3. Yet I seem to remember that this had been discussed with Isolde ,. undoubtedly a Mandella effect. So I stop actually saying it.
Despite this, it works better on Diablo2 classic. for these reason I am not sure than this can be qualified as a bug and it is not related to an "old '.00 code.
Other games like PoE handle disconnects better, it is easy to see that D2R would profit. Also figuring out the relevant details like timings, etc., all not that hard to do. There is also no clear abuse potential, as you already can quickly disconnect when in immediate danger. So I would be in for this. Not that I have experienced disconnects in D2R, but I can see enough situations where this becomes relevant, bad connections may pop up anywhere once in a while and in fact are common in many regions. Not everything is under our control we excert as players.
