It triggers an error if you try to see Blizzard announcement in the forums…Did they removed it due to backlash?
It was the main thread for feedback regarding this awful implementation
4 Likes
It looks like you’re correct…it is gone. I couldn’t find it on the Blue Tracker or the forums
They’ve gotten a lot of feedback that the event should just cycle every 30 minutes, so if they’re getting ready to act on that, they probably took it down to update/repost it when the change is done.
3 Likes
First time I hear about that kind of action, usually they just add a blue comment or block a thread if required, then do a new thread.
2 Likes
Wouldn’t the servers break even more if they cycled the event every 30 minutes? The game is nearly unplayable in those zones as it is.
1 Like
is this real? so…every time something goes wrong they just remove their posts instead of apologizing and saying ‘‘we’ll do better’’ ?
guess its normal nowdays, not only for blizzard
2 Likes
They didn’t remove the Plunderstorm one if I remember correctly how bad was the Radiant Echoes thread 
If they activated it in all three zones at once, that would split the player base and hopefully reduce the lag.
6 Likes
Since the event is cycling between 3 “world servers,” I wouldn’t think so. It’s intended to speed up to “every 30 minutes” in two weeks anyhow.
If a thread gets too spicy, sometimes they’ll temporarily hide it while the moderators clean it up. So it might reappear in a bit.
(And that did happen to the Plunderstorm thread as I reacall.)
1 Like
or took it down bc they noticed they rushed the event and they think hey look events up and running and when its really hey look we made a bad event and need to think of a new event while this event is going on
They will probably change the event to be every 30 minutes, buff the currency drop my a marginal amount and say they listened to player feedback, and some will sing them praises, when most know it should have been that way from the start.
9 Likes
Thats assuming this event and everything wrong with it was not intentional. It was. No good real dev team would have made this event without being ordered to do so by a higher up.
doubt it bc that would mean week 3 the bosses would spawn all the time, week 3 is 30mins week 2 is 1 hour this week is 1h 30mins…unless they dod 30 this week 15 next week and maybe 5 final week
pretty much this right here
2 Likes
THey removed the initial Plunderstorm one after, just like this event it didn’t go exactly over as they though. They weren’t receiving the enormous applause they thought they’d receive. If I Remember correctly they did it twice, and when players started remarking like “Seriously, hiding negative remarks to make the event seem better?” They stopped removing it.
Gotta love companies attempting to hide negative criticism.
Edit: I honestly wouldn’t be surpised if we started to see the negative criticism threads, even like this one, being removed too. Then they’ll come out with a statement of “We wanted to consolidate the feedback of this, and having mulitple threads wasn’t conducive to this.”
7 Likes
im shocked there isnt more people posting about them increasing the boss HP making them take longer to kill now
1 Like
Yea, that fixes one issue. But silence on the actual bugs in Dragonblight that prevent the actual boss from spawning.
Or they would drop it to 30 minutes and leave it that way the rest of the event, which would of course get them saying they listened to player feedback, and get some singing them praises.
3 Likes
Probably because “the boss dies too quick” was a common complaint on Day 1, and I doubt the conspiracy corner wants to accidentally praise Blizz for addressing it.