And pre-paid mobile users can be angry over the Battle.net requirement.

Blizzard’s president, Mike Ybarra, posted on Twitter on Tuesday evening: “Unfortunately, we are experiencing a mass DDoS attack on our servers. Teams are working hard to mitigate/manage. It is causing a lot of drop/connection issues.” A few hours later, Aaron Keller, the game’s director, added, “We’re steadily making progress on server issues and stability, as well as working through a second DDoS attack. We’re all hands on deck and will continue to work throughout the night. Thank you for your patience – we’ll share more info as it becomes available.” So the launch was spotty.

Blizzard has published a list of known bugs and launch errors. The known launch issues are: “Some players who merged their PC and console accounts are seeing an “Unexpected Server Error”. Some cosmetics, items, and currency that players own are not showing up in their collections. Some players are experiencing server disconnects.”

The known bugs’ list is longer: Players who merged their PC and console accounts saw an Unexpected Server Error; several cosmetic items and currency items didn’t show up when players should have them; and several instances of players being disconnected from servers for no reason, which means they were eliminated from the game.

The list of known bugs is longer: “Prices for dynamic bundles in some Just For You sections aren’t populating. Using Alt + Tab [on PC] in fullscreen and windowed borderless can result in a black screen. The camera may be misplaced on the level when viewing your Highlights. Hero Unlock challenges may fail to progress in Total Mayhem. Workshop Green Screen and Workshop Island are loading incorrect maps and may break some existing codes. Numbani, Necropolis, Illios CTF, and Temple of Anubis are temporarily disabled. Echo plays Kiriko, Sojourn, and Junker Queen ultimate lines in English for non-English languages. Mitigating Bastion’s damage as many heroes will not grant proper credit for the System-Wide Malfunction season challenge.”

And this issue deserves a separate paragraph: “SMS protect – Using a number already in use on another account can leave the client in an unusable state. If you encounter this, close the title, log into the affected Battle.net account via web browser and change the number to one that is unique” However, those using a pre-paid number cannot help if the previous number holder has, say, cheated! Excluding innocent players because of it isn’t fair.

Source: WCCFTech