Silence on Slime Cat

if they “win the lotto” and the mount they seek drops on the first kill, they will not go back again for it, thats a bit pointless. If the mount takes 1000 kills to drop, then sure they will (did) go back more than once

1 Like

I’m making noise over a mount I’d never get no matter what, because I won’t even do LFR.

It isn’t about the mount. It’s the principle behind the decision.

Thou must simply L2P.

6 Likes

They didnt do that because most CE guilds arent even bothering with CE this tier.

CE guilds that want the mount will just smash out normal/heroic in 3 weeks and then sell runs until DF to pay for their sub or just unsub till DF.

If Blizzard made it a Mythic mount then they wouldnt be able to boost token sales for the poor LFR people that eventually cave and buy a boost.

The silence is because the devs are now all on DF, not shadowlands. Do not expect slime cat in LFR, just cut your losses and go into normal.

OP has a point. Blizz has been completely silent on this matter apart from a “No”. Which is not communicating anything other than what we already know. We want to know why it was retroactively changed. It’s not like it’s a big ask. Blizz often puts in “Dev notes” as commentary explaining their logic about changes they implement. They did it just recently with the Dracthyr Soar nerf and dozens of class and talent changes on the alpha. It’s all there on Wowhead for you to see. It is…telling that they suddenly decided to clam up about this. Almost as if they know that they couldn’t muster even a cursory feeble excuse for the change.

They know what they did was wrong. They know there is no reasonable excuse they could use to justify it. They know that if they so much as open their mouth about it, they will get eviscerated by the majority of the community. So what can they do? The classic “lalalalalalala, I’m not listening” approach. And then they wonder why you have the FF14 dev meme dumping all over the WoW devs.

2 Likes

Nobody proofread the achievement text.

Actually I could accept this. It would look super stupid of them to admit it but it would probably be believable. Just tell everyone the guy who signs off on the new commits was sick and some intern stuffed up.

Although that being said, the excuse kinda falls apart somewhat due to the fact that the achievement wasn’t amended for months?

It wasn’t retroactively changed. It’s been normal+ for as long as the season (and thus progress towards the achievement) has been available.

There’s literally nothing to justify or apologize for.

I don’t think they need to say anything. We’ll be OK.

2 Likes

Well then I wonder why there are dev notes on alpha class changes? Or the Dracthyr thing? Why did blizz feel the need to explain reasoning behing something that isn’t out yet? What makes this change different?

:thinking:

1 Like

You’re just playing semantics games. You know full well the achievement was in retail for months. It was changed a few days before the patch.

Blizzard’s PR skills are right up there with their communication skills and ethics.

4 Likes

Those are the exceptions. Silence is the norm from Blizzard, on just about everything.

In BfA beta there was, famously, a 1200-post megathread from Guardian Druids begging for changes to fix the spec. It went completely unanswered by Blizzard through the entire beta test.

1 Like

Haha. So true. Blizz should really go back to never communicating with the playerbase ever again. At least then they’d be consistent :rofl:

honestly, I’m more annoyed with the time limit rather than the fact it’s not in LFR.

Why can’t fated raids be a recurring event after S4, with a recurring cosmetic reward? Like as a recurring event I feel fated raids could be a ton more fun. They could do Fated Legion and fated BfA raids along side Season 1-3 of Dragonflight and that sounds like it’d be a lot more fun.

2 Likes

There was a random blue post in a thread saying it was normal only a few days before the patch.

It was only hotfixed a few hours before the patch, which is even worse -_-

5 Likes

Yes.

I suppose what the OP wants is for Blizzard to say “It never occurred to our staff that “any difficulty” would be interpreted by some as including LFR, since LFR is not actually raiding.”

But would that really make people happy? I don’t think it would.

It would also be lying.

1 Like

Always gotta get those digs in, huh

6 Likes

I’m not making digs, I’m asking what people expect an “explanation” to be.

It’s gonna be one of these:

  1. Nobody proofread the achievement.
  2. Whomever wrote AND whomever proofread the achievement, it didn’t occur to either of them that anyone would consider LFR “raiding”.

What else are people actually expecting an “explanation” to be? That’s it.

If there’s a “3” I’m missing, I’m all ears. (ho ho ho, vulpera)