Hardcore Character Restoration after 1.0.1 Carrion Queen Bug

"

ToxicRatt wrote:

It NEVER should have been done. Going back on your word. Makes me glad I haven't supported so far...

I really can't understand people reacting like this.

GGG had the ability to perfectly track down who was affected by this bug and was able to restore them in a quick fashion. The reason they don't normally do this is because dying to to various other bugs is not necessarily easy to track or something they'd spend their effort on. That policy isn't because GGG hates players, it's because it's something they can't judge effectively.

In this case it was a massive bug that was easy to fix and easy to track down so restoring people who died for no fault of their own is a good thing.

I see many selfish people bashing this for some reason and acting like they'll have to deal with any of the many liars potentially sending GGG messages in the future.. that's their problem, not yours.

I originally made this topic : http://www.pathofexile.com/forum/view-thread/609879 So people could avoid this bug. Very impressed that GGG actually decided to restore characters. GGG just keeps proving what a great company they are.

"

tobes111 wrote:

Great.

How about a reverse of the CwDT gem?

This isn't Path of Easymode, go somewhere else.

"

Rampe69 wrote:

"

BerMalBerIst1 wrote:

"

tobes111 wrote:

Great.

How about a reverse of the CwDT gem?

LOL

Wow talk about ungrateful lol

How about you just cast skills yourself instead of using a trigger gem :D

So what was the point of even introducing trigger gems then?

I'm sorry but, does the gem trigger? Sure does, move along whiner.

"

opkast wrote:

Completely disagree, this is the reaction of a responsive and aware company, that made a gamebreaking mistake that caused a ton of people to get 1shotted instantly. They tracked the deaths due to this and therefore are able to restore any deaths related to this bug.

No, its the reaction of a company slowly going back on its initial design values and promises. The addition of instanced loot after previously claiming loot tension was a core part of the game that they would never remove is another glaring example of this.

There have also been plenty of previous incidents where some horrible bug ate a load of HC characters, and none of them were restored. This isnt "the reaction of a responsive and aware company", its an absolutely random reaction that makes no sense and also represents a major shift in a long standing policy- a policy thats been in force for both poe and several of its HC-enabled predecessors, and with good reason.

"

opkast wrote:

Also, when you say another, it seems that you think the community thinks the same way as you about the changes, when infact its a very loud minority spamming the forum. Most of us believe that GGG is doing an excellent job.

Citation needed.

"

evilTricKs wrote:

An accidental mass killing of hardcore characters needs special attention.

And the special attention isnt breaking the HC no-resurrection policy, its actually testing the damn patches.

"

Alysma wrote:

I remember one incident where GGG restored a dead HC character because someone from GGG's Support made a mistake. This one is basically the same: An error on GGG's side (that should have never made it into the game). Which is quite different from deaths because of lags and desync. Just saying. :-)

GGG support fucking up and outright giving someones account away then restoring it fully (which afaik has happened once, ever) is not at all the same as players dying to bugs, or desync, or anything else game-related, which happens constantly and has never been subject to resurrections in the past. I dont see how the two can even be compared.

"

No, its the reaction of a company slowly going back on its initial design values and promises.

Not restoring HC characters is not a "design value", it was never done since it's not something usually feasible. A warning is given since it should never be expected.

In this case they were able to perfectly track down the bug and quickly fix it/anyone affected by it.

hardcore got it's reputation from the no-restore policy. these were the times.

welcome in "scrubcore" where you can be resurrected. (being called a scrub so often by hc players that i quite enjoy using it now).

if i were a hc player with a restored char, i would delete it by myself as the game has beaten me. on the other hand i would accept a restoration to hc if the death was caused by a technical bug.

"

on the other hand i would accept a restoration to hc if the death was caused by a technical bug.

It was a technical bug...

GGG did the right thing.

Can't believe they did this. Something similar happened in Onslaught with monster damage being increased way to high (a bug that was fixed), and they didn't even apologize to all the people who died.

"

kasub wrote:

"

on the other hand i would accept a restoration to hc if the death was caused by a technical bug.

It was a technical bug...

a technical death would be "death while loading the instance" or "death while the game crashed". there were overpowered devourers(?) in maps which did huge damage and will probably be nerfed soon, is this a technical bug as well? at which damage value normal damage is switching to a technical problem?

we can endlessly argue about the definition of "technical" ... eventually it's software and everything is technical here.

they got killed by a monster with overpowered damage values. hc players constantly die to unexpected damage, they're used to it. they're proud of the fact that they can die in hardcore league.

err, correction: they used to be proud of it.