This was supposed to be a TLDR, but then I started rambling… Sorry.
How it went down from my perspective;
5-1, I was leveling a char out in Searing Gorge, while watching some of the guild raid AQ20 - suddenly, everyone but 3(I believe it was) disconnected from the game, received the same error, and were immediately able to log back in.
I, luckily, was just slowly auto-ing a mob down (can be seen in Crash Report) in SG, while the raid members had just pulled the first pack in AQ20. Luckily only 1 member died, but we still lost a very geared Tank. Another guild on the server was moments from pulling a Corehound in MC - imagine the fallout from that one (:
Reading chat logs from minutes after the crash report should indicate a significant majority of the server had disconnected, incurring a number of deaths.
5-12 - Similar situation, spontaneous disconnect, affected a significant majority of online players at the time. Video footage posted above will show it not only affected those in instanced environments, but open world, across both continents. Chat logs from moments after the crash should indicate similarly, this affected many if not most.
This had larger repercussions, as we had just pulled General Drakkisath in UBRS. We lost 6 players, many of whom were quite geared (RIP Server first CTS) .
Luckily, again, for the other raiding guild on our server, they were again moments from pulling a boss - this time Bloodlord Mandokir - again, imagine the fallout if they had been mid pull for that one…
This appears to only be happening with increasing frequency on Skull Rock NA, but I’ve heard from others that an instance of this occurred on Stitches once within the past 2 weeks.
End of the day, look, we get it.
We signed up to deal with this BS. Well, not quite - we signed up to deal with death is death. We signed up to deal with occasional server INSTABILITY, resulting in server-side disconnection, personal disconnections, personal failures, bugs, etc. What we didn’t sign up for, was having patches to different versions of the game application, for some reason using shared core game resources, cause server-wide service drops. We’ve seen how the patches for SOD bleed over into Classic Era/Classic HC. We’ve had the Rune buffs appear on our characters, mobs that shouldn’t exist, exist… SpellID’s and Spell effects change with no notice as they are being prepped for - or worked on - for SOD.
We play this version of the game because we like this version of the game. You have sold it to us as this version of the game. The excuse of “Well, WoW was never made for HC” doesn’t cut it for the things we are experiencing. You sold us this version of the game, with the expectation that it would be that, and receive necessary support to deliver the product you said you would.
I don’t care about the dead character’s - I’ve had 2 now die to this HC:SOD resource mismatch, client incompatibility, memory failure, etc. What I DO care about, is hearing something - anything - to indicate you’re not ignoring it. We’re not the biggest playerbase of yours, but we are a damn loyal one. At this point, I daresay the loyalty is not to Blizzard, but to the vestiges of a game that the HC community cares deeply for. Don’t make us lose that too.
