I’d say that they give the players the information to make decisions, in a way that sidesteps Blizz’s deliberately obscurantist designs.
Blizz has a long and ugly track record to go by here… of lying and of not following through because they get distracted or next quarter’s executive instruction changes KPOs entirely.
No, they sometimes literally tell you what to do, and why do you think theses designs exist? Because of the arms race with addons.
Source?
Because Blizz is has always been extra salty, and couldn’t just let people get around their carefully curated metrics. Nothing else.
The issue is that there’s two camps here
Those that have been burned by Blizzard too many times and realize to take absolutely nothing they have to say at face value, especially when they’ve failed to be honest through this very process about their intentions of addon removal and speed at which they would do it.
Those that are absolute Blizz-drone lapdogs that bark and playfully wiggle at any lie Blizzard tells them, and jumps through any and all hoops to defend them no matter what, because to them Blizzard is their god.
We’re in camp 1. If you’re going to try to prove anything to us, their word isn’t good enough because they’ve already proven to be liars time and time again. We need more than your cult opinion on anything, because again, your camp has a massive bias and worships the company. We instead will always point to their contradictions, their lies, and give our frustrations and warnings about it, because we can clearly see them and aren’t blinded by your obsession with a company that doesn’t care about you.
You’ll need to give me some examples of lies. Cus what I’m hearing is failing to deliver which is not lying. It’s not meeting expectations. Maybe over promising. Keep in mind I’m of the opinion this entire addon nuke is a mistake of grandiose proportions and I’m eating popcorn while they shoot themselves several times in the foot.
I’m in the third camp, I trust the devs, but if they make the game not enjoyable for me I just drop it. And the changes they are making now look great to me.
Then if you’re just vibe and opinion based, then don’t argue with anyone. Just play the game and enjoy it, and let those of us that see the flaws and issues they’re releasing talk about it.
People in camp 1 don’t want to watch the game burn. In fact, we have a high amount of passion for the game because we see what the game either once was and/or has the potential to be. We instead are trying to save the game from the very clear train wreck it’s heading into.
I argue because I want them to proceed with their changes, because I genuinely like them, especially because I think it will make PvP better. And I don’t remember lies, as post above said, there were failures to deliver, but that’s not lies, maybe I just don’t remember.
From my experience on beta every class I play just feels empty / boring or in some way worse than on live. Devourer is in a completely unserviceable state for a new spec in beta, and we’re fast approaching code lock with holiday break in the middle. Feedback has been ignored, iteration is nonexistent, and we’re already seeing announcements that they’re moving into the tuning phase.
I don’t have beta and I’ve only looked at Affli, Demo and UDK changes, they look nice. But I imagine not every class this lucky.
Affliction doesn’t have a functional aoe rotation, at all. The thing completely breaks down on any more than a handful of targets and seed of corruption would need an 800% buff to bandaid fix it. Which as far as solutions go makes you question how on earth we got to this point.
Demonology feels extremely rotationally bland. I get as a pvper you largely don’t care about rotational gameplay but with how much they’ve taken out the experience of hitting one target for any prolonged period of time feels extremely monotonous with little to look forward to besides waiting for tyrant cd.
You’d be correct. There are a good many specs worse than even affliction. I wouldn’t feel uncomfortable saying that Devourer DH in it’s current state effectively doesn’t work.
From this addon purge alone:
Saying that they don’t want things in place that “play the game for you” while releasing a one button rotation macro that plays the game absurdly more than WA’s ever did. This is a lie and hypocrisy.
Eluding to their encounters had to keep up with how in depth WAs were. This is a flat lie. Mythic Plexius WA’s do basically nothing other than have timers. These timers aren’t even necessary and if all encounters were like this one, WA’s wouldn’t be a thing many people downloaded for encounters. The only time WA’s “solve” a boss fight is when it’s a heavy gimmicky fight that requires lightning fast role assignment due to randomized mechanics and short duration windows. So it’s a design issue and WA’s are a response to these poorly designed bosses, not something that has to be designed because of WAs.
That addons that are just for graphics/skins won’t be affected by the purge. We’re finding out that’s also not true at all as several UI addons (most popular being Elvui) aren’t usable.
When they first released the statement about the addon purge, they said it would be gradual and they would slowly scale things back. It’s instead a rash amputation of addons, completely cutting and gutting what addons have access to and slowly easing some of the restrictions due to people like me yelling about how absurd this is.
Failure to deliver is a lie when they promise to deliver a fix for what they’re intentionally breaking. And currently the failure to deliver is on the following
a) DPS meters tracking things correctly, not to mention how limited it is vs how Details was
b) Blizzard’s version of WA’s cooldown tracker not working correctly with dots
c) Trackers (as well as combat trackers) lack audio capability when they’ve mentioned that they wanted to put those for accessibility reasons.
*There’s more but I can’t think of them off the top of my head this very moment. Either way this is more than enough to not trust anything they say about this matter due to how they’ve handled it.
I don’t think this will happen in the first iteration.
If these changes mean that raid participation drops through the floor, Blizzard will have to react to save raiding. If raiding feels the same difficulty on mythic to the most experienced raiders, but lower difficulties are designed to prove that most players are bad, there’s going to be a massive dieback that will result in so few players raiding that it’s not going to be worth development resources.
That’s one of the goals of these changes, to make players who aren’t ready for mythic raiding realize that they have no choice but to commit their lives to making themselves ready.
The demo changes in the first alpha were a spec-killing dumpster fire.
At least the second iteration seems to have pulled back from the brink of the abyss a little.
Or do like I’ve done since back before my hiatus, and just not raid.
This is the more likely result, that players at the lower levels of difficulty will give up on raiding. Some will quit because there is less to do. Raiding participation numbers would drop through the floor, even as the best players brag about the game putting “baddies” in their place.
They already know, they just use it as an excuse.
I mean design wise Affli is better than it is now. Numbers can be fixed, it’s design that is important.
I’m not PvPer, I do pretty much all content, PvP included.
Second iteration Demo doesn’t seem bland to me. There is limited on-demand Dog/Imp, Nether Portal-ish Apex talent and Doomguard button with CDR.
Yea, that the point of testing stuff, so they can fix it. They can’t fix everything, but they do fix stuff based on feedback.
Yeah, just another non-sequitor response.
“I like the changes!”
“I disagree.”
“The point of testing stuff is to test it!”
Whatever.
I think if the number fix is an 800% buff to a spell then maybe the design has some flaws. That’s the equivalent of whitewashing a cracked brick wall then claiming to have fixed the cracks.
Affliction doesn’t work in AoE. That’s not a tuning issue, it’s a design issue.