It was very disappointing to be able to enter this one dungeon and to realize that I’ve now had my enjoyment of the story spoiled by Blizzard, itself.
Why would you make this dungeon available if you know for sure that we haven’t yet reached this part of the story?
Terrible.
The worst thing is that you don’t even care enough about your own game to catch huge mistakes such as this.
EDIT: So, anyways. If you haven’t yet done that dungeon. Don’t look into it if you want to enjoy the story. It cuts to an event that hasn’t yet happened in-game.
They announced this experiment the same day the patch was announced and asked for feedback.
I have avoided trying the dungeon because I knew it took place after the raid. I know who the final boss is, so I really understand why I’m avoiding it now.
I’m on the fence about it. I dislike that so many major story moments are locked inside raids and then dungeons are given the scraps. It feels cool for a dungeon story to be important…but…you also get this problem we’re having right now.
The middle ground is probably for story important dungeons to be released during mid season minor patches instead of along with a major patch - even if that means the Mythic+ rotation jumps to 9 dungeons.
Yeah this was the first thing I noticed Wednesday when doing a quick m0 clear up with guildies.
I don’t expect much from wow’s story pacing but wow. Time gating the story is bad enough but this disconnected mess ontop of it all allowing you to experience what’s most likely the very next chapter early and disjointed with no clue on what is even happening?
I don’t understand why they spent so much time to create such a wonderful story, only to crap all over it by revealing the ending when you’ve just met these characters… and are hopeful as to what may happen with them.
What is the harm in holding 1 dungeon back until AFTER we reach that part of the story?
I honestly thought I missed some quests when I entered the dungeon. I was quite upset at myself. Didn’t even think for a moment Blizz did that intentionally…WOW…I have no other words…
This is a lazy response and you are unjustly defending Blizz. No one forced them to put that part of the story into a dungeon. It could have been in some part of the raid or even a cinematic, or heck, even part of the MSQs.
Take Floodgate for example. That’s an entire side plot. Renzik is involved and he was involved since the very beginning. We’re just stopping Darkfuse doing Darkfuse things. No spoilers, nothing.
There’s absolutely no reason this couldn’t have also been a side story instead of bombarding us with spoilers even before the first pull. In fact I can’t think of another dungeon where things are just flat out spoiled outside of “Murozond dies eventually”. Except even then no one knows when.
This isn’t a time gating issue. It’s a “we weren’t thinking about this at all” issue.
I’m just saying it how it is. When Blizzard messes up, I have no problem saying it. This isn’t one of those times.
You see, your mistake is that you’re thinking that Dungeons are subordinate to Raids, so the Dungeon story has to come before the Raid or not at all, so that the Raid can be the end of the story.
That was once true, but now with M+ Dungeons are just as valid as end-game content as Raids.
Blizzard is trying to do something different and end the story on a dungeon instead. And they decided, due to last season’s backlash against timegating, to not wait to release the dungeon.
Maybe they should have waited 1 week. Maybe not. I don’t know.
What I do know is that Blizzard warned that the Dungeon happened after the Raid. If you didn’t want absolutely any clues of what happens in the Raid, then it was up to you to wait and not spoil yourself.
It’s like complaining that a book was spoiled for you because you opened the last page and read it lol