No but you know those threads they’ve been creating giving updates on patch notes, Dragonflight and Fated Raids? They could have done it there. On May 27th they made a thread on the Fated Schedule. They could have said “btw, the achievement is wrong and will be fixed at a later date. You can only get slime kitty from normal or higher.”
That would have been a check box under “communication.”
You keep claiming they don’t come to the forums yet if they don’t, they wouldn’t be aware of the achievement as I’m fairly certain someone that only does LFR wouldn’t randomly stumble on a new achievement that just popped out of nowhere at the very bottom of the shadowland raid achievement tab. Then the only mention of fated would be from the “Welcome to Season 4” with the already corrected achievement.
Again you’re lying, linking to an achievement that says you get the mount for completing Fared Raids does not in any way translate into “LFR was not supposed to have Fated”.
PROVIDE AN ACRUAL SOURCE FOR THIS CLAIM PLEASE, do you have trouble reading?
Hours, not days.
That is a ridiculous take.
Complete all three Fated raids in Shadowlands Season 4.
It doesn’t say Normal now does it?
You: but LfR wasn’t supposed-
Actually provide a source for the claim that LFR was not supposed to be Fated or stop lying.
Oh I agree it could have been better, but I’m very much in the camp of “changing stuff before they release is absolutely fair game”.
And no, “but the achievement was in the game!” doesn’t count if you can’t actually put any progress towards that achievement.
I gotta disagree here.
Mistakes make it into the game literally all the time, even when Blizzard are actually devoting their resources to current expansion Dev and QA. There’s been some absolute whoppers of bugs and oversights.
Some all stars include:
Fixing pets hitting tanks in PvP somehow allowed Paladins (only Paladins) to one-shot people.
Letting people who ignored the core feature of 8.3 queue for N’zoth and get immediately mind-controlled.
Blizzard accidentally making a pandemic simulator.
Accidentally giving a GM testing tool to a player and them immediately one-shotting entire raids with it.
DK’s one-shotting Sinestra with Dark Simulacrum.
And so on.
EDIT: Forgot pretty much the most fun one. DK’s being able to kill allied players by typing /cast (disease name) while targeting them.
At it’s core, this is a tooltip that was wrong in the middle of a season that is basically just the previous season with a new hat.
Because it wasn’t just datamined. The live achievement they themselves added to the game said any difficulty. It was easily findable in the raid achievement list for 3 months. They led everyone on just to flip them off a few days before the season launched.
Me personally I post when I’m walking my cat or at work, so kinda can’t play WoW then.
I would need to get geared first, for months we thought LfR could do it so I didn’t put much effort into gearing for a mode I had no intention of doing.
And that’s without getting into
Putting group together > group bad > leave > start over
is a major time sink
I would assume most of those are errors in code, which are a more difficult fix than spelling or verbiage in a tooltip. A tooltip fix should be only too easy for a wealthy corporation to disseminate in timely fashion to its paying customers.
That it wasn’t is telling.
Edit: This is not to say that tooltip text is not present in code, but that they are less abstract in their presentation than the string of commands necessary for an interaction or event or what-have-you to take place as intended.
Tons of errors make it through in stuff like achievements, spell tooltips and quests.
They don’t get all caught in the PTR.
If I had to guess, this particular error came up because they C+P’d the achievement for completing raids like Sepulcher or Sanctum (which CAN be done in any difficulty) and forgot to change the text.
Just maxing out ZM and your legendaries would have had you plenty geared, and could have been completed 2 months ago. Did you just not do current content all patch?
It just strikes me as odd that a lot of people who say they only do open world and LFR seem to not even have done that stuff.
What is it about you guys reading into some achievement text pre-release too much and it being changed before its release that you think warrants a response?
If it were me, the response would be to start enforcing an NDA because y’all can’t be trusted not to start drama over any little thing in a beta you don’t like.
The achievement made it to live with the mistake. That’s their one and only good point about all this.
Not quite sure there wouldn’t be any less drama if they had put the fixed achievement on the release date though. Just, they wouldn’t have their one bullet.
If you actually read the link it shows that LFR was never getting the slimecat. You’re only argument that it was is on an achievement that was hit fixed because …. It was wrong!
See above.
It’s already been linked. If you’re struggling to understand that’s a personal issue.
And thus reach we the crux of our difference in opinion.
One is willing to attribute to ignorance, the other to malice, both with some good reason. A corporation is constructed to make money, and there is money to be had in leading people on. A corporation is comprised of humans, and now and then do humans err.
What is true we won’t know until all the facts of concern are released, but I think we both agree that that’s never going to happen.