To be honest, it’s better to not promise anything that the player base will hold them to. Even if it runs past launch date. This is a level 10.0 magnitude problem IMO that will have people doing overtime to asses and fix. This is the one issue we as a community need to give blizzard a break on and not rush it so they do it right.
This is why I’m quite happy to remain a front end/client dev forever. Damage can still be done, but it’s much more limited, and because of App Store/Play Store review times there’s no point to midnight calls.
Maybe the server shard crashed or they merged part of some old data. Imagine losing levels and achieves, mounts, toys, xmogs - thats alot of stuff to lose.
haha! I too am now a front end dev. Happy with accessibility testing and css whispering. No one calls you at 3am because their image doesn’t have the right margin.
And man, those delays in review from app and play stores can be a godsend sometimes.
TL;DR for anyone out of the loop: Blizzard appears to have accidentally backed the Khadgar server up to some time in 2014 (WoD), so a huge amount of characters have had their progress between then and now completely wiped because that server was accidentally backed up to a point in time where none of that stuff existed yet. Players on that server are, justifiably, absolutely flipping out on Blizzard right now. That includes an 11/12M guild that was pushing Cutting Edge during the last weeks they possibly can.
I really, really want to know how the folks at Blizzard could mess something up this badly.
Shadowlands releases in a month and the prepatch releases in a week or two, by the way.
After hearing about other stuff breaking from previous realm connections, like people’s raid lockouts, etc., this is exactly why I didn’t want my realm connected (and thankful that it wasn’t). But man, this last connection was like the grand finale of peak brokenness.
Ok, so here it is. Khadgar finally found what he was looking for in Kara. You know, since he vanished for the expac and all. He came to the realization that the only logical way to remove the Sword of Sargeras from Azeroth and heal her wound was to reverse time. But you see, Khadgar is no bronze dragon, so he isn’t very good at time magic.
But he thought to himself, “There isn’t any time to get the bronze dracos. And they might not even listen since they like to “protect the true timeline” or something of the like. So I’ll just do it myself. How complicated can messing with time be anyways?”
And here we are. This explains everything, and why it only happened on his server! I know, I know. I’m a genious. Please save your applause for blizzard when they fix this mess and delete Khadgar from the game.
Coding happens. I can assure you, this is not super uncommon in the industry and internally. It just made it live this time.
I can also assure you that there are redundancies in place to guarantee that when something like this happens, data is not lost. So everyone in Khadgar should be fine eventually.
And from what I have gathered it’s not a simple roll back, it also duplicated, restored and overwrote some user access sometimes even back to MoP.
But again, I do have trust that Blizzard will figure it out AND that all the present data is backed up somewhere in the ether.
Bugs don’t have a schedule except their own my dude. It is what it is.