This issue needs to be addressed urgently, this is the type of stuff that makes people quit a game when they spend tons of hours on earning something and then can't get it because of some bug. The subset of the player base that does these kinds of achievments is already small enough without these types of situations making people quit. It needs to be said that many of the people who play that kind of content almost exclusively spend all of their game time on those achievments, it's not something minor that you can afford to not treat seriously.

Varana wrote: »

Remember that thread from a guy where Customer Support tried to grant him an achievement afterwards, and totally fried their character in the process?

At this point, I'm pretty convinced that for some obscure reason, achievements are not just a flag on the character record, but getting an achievement shifts something deeper in the database around. And meddling with them is apparently ... dangerous.

There are other ways to do that. For example we all saw godmode tool that allows to 1shot things in trials. That is how trials are tested on PTS. You could simply gather the team members together and bring 1 mod. Start the trial, afk for 20 minutes at the start (to make realistic score and not screw the leaderboards) and then just godmode the whole thing. 11 people get achieve. Cycle through the remaining people who have not gotten the achievement yet.

There were precedents of the Sunspire collectibe mount granted to people who have GS achieve bugged. Yes that is also a thing. One of the team members who got Planesbroken also has GS achieve completely screwed on her main toon. She reached out to support and they were able to give her the mount, but not the achieve. But currently support refuses to grant anything at all.

What is very concerning is that it's been half a year since the reports of the achievement being broken were submitted. It keeps repeating, but none of the people who has Planesbroken saw any recuperation from ZOS. At least later in the lifecycle of bug report Kevin started to respond sensibly, i.e. actual truth why it is still not fixed which is definitely a step forward. Earlier reports god copypastas such as "Disable addons and do it again". Can you imagine how heart broken those people were.

it's funny that we only got an answer about this bug when the fourth bug happened, we also got a bug with the PB in september...
still frustrating that we didn't get ANY adequate response other than to do it again...

I have one more question.
Why did the company apologize and make a mount when exactly this time there was a mistake with the title?
I don't want to say by this that the last group is not worthy of an apology, mount and everything else.
I'm just saddened by the fact that from that moment on, the ZOS started responding to people about the error. why didn't previous groups who encountered the same error also receive a mount as an apology? also had all the logs, correct score, video