See also: people who roll into a conversation a whole week+ late and still haven’t even grasped the context.
You were willing to pay for 30 days for something that could have been done in 3. Just use the remaining 27 days to get better gear, friends, etc. That’s all gonna help you come DF no?
It’s not live until you can actually achieve it.
Otherwise it’s about as live as martin’s fury.
1 Like
What am I paying for exactly?
Access to server?
Not sure how that works.
It’s live when it’s on the live version of the game
Yall love just making up definitions for words.
4 Likes
What server?
So Martin’s Fury is live? Great “live” is a meaningless term now. Thanks for twisting it when it’s convenient to being mad about things changing before release.
Blizzard’s server that hosts all realms and the game? Is there a point to this line of questioning?
What does all this have to do with anything I said?
What am I paying for that I could get in 3?
What even is the 3 supposed to be?
To inform me about what you’re talking about, because I have no idea what you’re accusing me of or telling me to do.
https://twitter.com/itsneryssa
I see nothing that indicates that’s a Blizzard employee so good job to Wowhead, now we just need Blizzard to get on the ball 
1 Like
I think Blizzard should have compromised.
They should have admitted their mistake, owned up to the fact it mislead people for three months, allowed the cat to be earned in RF but told people this was the last time and that all future seasonal raid mounts will be normal or higher.
2 Likes
In a pure economical standpoint, all Blizzard would have had to do is delay fated LFR from opening for 2 weeks, which would push the “grind” for the slimecat to 5 weeks, thus ensuring that they get 2 months sub instead of just 1.
Or make Fateds rotation 2 weeks to let people “progress” through the system, dragging the grind out to 6 weeks.
Those systems are both part of the standard model of milking LFR players. Keep in mind that Sepulcher fully opened on March 8 for N+. For LFR it fully opened 6 weeks later on April 19.
I’m sure that there will be some people who’ll buy a token to buy a carry. But for normals, the mode is so easy that that’s never going to be as big a driver of token sales as making it Heroic would be.
2 Likes
It existed on the live game for people to pull up and read in the achievements list, long enough for many many people to walk away with a misunderstanding of the wording.
Is it allowed for Blizzard to change things that are already live in the game? Absolutely. I don’t think anyone (rational) is arguing against that point.
Does it feel underhanded for this change to be pushed in an unannounced hotfix with no dev commentary whatsoever? To a lot of people it does, and that’s what this conversation is about.
How many times do devs drop a comment in the patch notes to explain a change the community might take issue with? And what was stopping them from doing that this time? That’s what people are talking about here: communication to the community as a whole, not just one-off comments in a 700+ post thread that most people will never see because they don’t commit time theft at work to browse GD all day the way many of us do lol.
5 Likes
Sounds like the mistake wasn’t changing the achievment prior to release, but rather allowing the community to see things pre-release, since they can’t behave.
1 Like
Honestly I don’t think they should. If their intent going forward is to have yet another FOMO mount at the end of each xpac with fated raids that is only available from normal+ then they should leave it as it is because changing it for this one but not for the future ones is going to create confusion.
If they leave it as it is now then everyone will remember getting screwed and it won’t be a surprise in 10.4 or whatever the final patch is for DF when fated raids come and it is normal+ again.
The community behaves precisely as they have always behaved This shouldn’t be a shock to anyone.
They already created confusion and anger. If they make an actual announcement and explain things, there won’t be confusion.
I know there will always be anger 
2 Likes
Okay, obvious attempts to instigate aside, let me just say this once for public record: no one was “misbehaving”. They read an achievement that was worded poorly and made very reasonable assumptions based on that wording. The misbehavior was with Blizzard and their usual goofing around, not updating the playerbase, not communicating any mistakes, or generally putting out half-finished content into the live game when they hadn’t really finished making all of their decisions (e.g., clearly waffling back and forth on whether or not to make LFR fated).
People wanted to be acknowledged on this. That’s all. I am not surprised they’re mad that they haven’t been, and anyone who’s ever seen the public react to any decision in any game probably isn’t surprised either. I guarantee there are plenty of Blizz staffers who were also warning that this was gonna go over poorly, but there’s someone higher-up saying, “Nah, just ignore them until we make them angry about a different thing instead.”
4 Likes
That’s fair. And admittedly why I’m still putting the blame on Blizzard.
1 Like