And there it is, the real reason for all the hubbub. It was never concern about a character in a work of fiction.
No thatâs one of quite a few reasons but whatever helps you sleep at night.
good some of us donât want to be reminded of something that a lot of us have to deal with in some form or another in our everyday lives. with that im muting this thread because i know most of the responses will be âLOLS WHO CARES DEAL WITH IT!â responses made by people trying to be edgelords.
It wasnât nuanced though.
Like thatâs the entire problem. It was a quest that should be nuanced and then did the complete opposite.
It was basically âWeâre visiting one of the darkest moments of WoWâs history to ensure that it happens, donât get caught by the person whose suffering youâre extending teeheeâ.
It can be more than one thing.
But realistically, Blizzard writing about SA these days is like Lance Armstrong writing about integrity in sports.
No matter how well you write it, people ainât gunna forget who wrote it.
Yes it still happened and already happened in the lore so it doesnât really make a difference. Players werenât going to be forced. It was an optional quest. It wasnât enabling the continued assault on her because, as you said, it already happened and still happened. Itâs so silly to be outraged over an optional quest in a video game with a fictional world thatâs not even close to realistic. I mean the quest revolves around time travel. If theyâre going to change stuff every time Twitter wants to start virtue signalling then they might as turn the game into Hello Kitty Island Adventure. Even then people would find something to be offended by, Iâm sure.
The point of the original quest was to make you feel complicit in it. Itâs both why Chromieâs dialogue is so cagey and weirdly jokey about you not letting Alexstrasza know what youâre doing, and Alexstrasza herself becoming extremely upset upon seeing you afterward.
Tea
This is the best case scenario.
Not many players are aware of this part of Alexâs background. Now we get to relive a book moment and be in the positive side of it by rescuing her.
And instead of just changing that aspect of it they threw out all that time taken that was put in, just to appease hurt feelings.
Could of been a hint of Chromie displaying subtle character flaws for later use down the road but nope, best to just start again and sweep it under the rug.
Thatâs cause most of the Warcraft games came out long before they were born, up to the first few Xpacs of WoW even.
Too be fair, most people would blitz the dialogue and dropoff Deathwingâs bling without even knowing whatâs going on. And frankly the whole thing was blown out of proportion by peopleâs need to manufacture outrage these days.
I mean, you made a nice strawman here we can all spit atâŚbut over 100 posts in and Iâm not seeing any of this.
Itâs so silly to have a quest that revolves around enabling continued SA when there are so many other ways to highlight that you have to let bad things happen to people to preserve the completely fictional, completely in their control timeline that they wrote that donât involve that specifically. Like the still-existing quest where you make sure that Amber Kearnen gets assassinated.
They tweaked a single quest to make it so that the player character wasnât complicit in making SA happen for a geegaw and 25 blimblams with a lighthearted joke at the end. Thatâs not about âhurt feelingsâ, thatâs about having a modicum of human decency.
If you have a deep and driving need to explore the implications of doing awful things to defend the timeline, the Amber Kearnen quest is right there. Enjoy!
While I agree the original quest was tone deaf and should have been changed, Iâm willing to be charitable enough to say that this was nowhere near the thought process. Iâd more easily believe that they wanted to make it a quest simply because itâs one of the more poignant events in WoWâs history and Alexstraszaâs involvement in it makes it a natural candidate for time travel quests of this nature. I really donât think that any more thought than that was put into it. Which is certainly a bad thing, but I donât think there was ever any deliberate attempt to minimize SA.
And for what itâs worth, I donât think that a tone deaf quest going on to the PTR and then being changed in response to feedback before going live in any way necessitates any changes on Blizzardâs quest writing team. As ugly as this particular oversight was, it was resolved pretty quickly and itâs frankly just not that big of a deal.
defending blizzard are weâŚ
Why defend a company so bad that they got sued⌠from something that shouldnât even happenâŚ
Turned out everyone was using roids in the Tour de France.
Wonât someone please think of the Dev time it took to make a daily.
lmao
It wasnât just about dev time.
Im sorry that I show just abit of empathy for whoever came up with this quest idea, only for it to be forcibly changed.
Yeah, you just radiate empathy.
That happens a lot in game development. Iâm sure they are use to it.