5 Famous Video Game Disasters (And Why They Happened)

It's not entirely surprising that Anthem turned out this way, though. When Jason Schreier of Kotaku interviewed over a dozen developers who'd worked on the game, it came out that BioWare wasn't so much a studio as it was a tinderbox of bad management, technical misfires, and mental trauma.

Despite first being teased in 2012, Anthem didn't enter actual development until 2017. That's because for the longest time, no one knew what they wanted the game to be. Management meetings about things like the plot or mechanics would often end in a stalemate where nothing got decided. It wasn't until 18 months before Anthem was due to be released that BioWare decided to get its act together, which led to them asking a studio veteran to step in and do whatever it took to get the game out the door.

The technology that the team was using didn't help. As a subsidiary of EA, BioWare was asked to develop Anthem using Frostbite, an engine created by EA. The only problem was that no one at BioWare had any experience with Frostbite. As a result, the team soon found themselves having to cut content, because while they could eventually finagle Frostbite into doing its job, there wasn't enough time to do it with every single feature they'd envisaged.

With a working environment more hostile than anything they'd managed to program, it wasn't long before the team started breaking down. In the two years that Anthem was (properly) in development, BioWare saw dozens of employees -- some of whom had been with the company for decades -- resigning for greener pastures. Or at least pastures where everyone could agree that pastures should probably have some form of grass.

Some breakdowns were more literal than others. The harshness of the production cycle, the ineptitude of management, and the fact that (according to one developer) everyone was "so angry and sad all the time" resulted in several employees being diagnosed with depression and anxiety, while others wound up having to take doctor-mandated periods of "stress leave" (which was deducted from their vacation time, of course).

I actually cannot count the amount of 'stress casualties' we had ... a 'stress casualty' at BioWare means someone had such a mental breakdown from the stress they're just gone for one to three months. Some come back, some don't.

After Kotaku published its article detailing all these shenanigans, EA and BioWare responded by arguing that it was a mean-spirited attempt at tearing down the company's employees -- which is something that they know a great deal about, according to said employees.

The rush of players immediately overloaded the game's servers, causing widespread outages that lasted for weeks -- a situation compounded by the fact that the developers were still rolling out the game as planned, which only added more and more players into the increasingly frustrated mix. As it turns out, the developers had massively underestimated the popularity of their little project, and hadn't given much thought to building out their server capacity.

That's understandable. How were they meant to know that a free-to-play game based on one of pop culture's most enduring franchises might appeal to more than, what, 25 people? We almost feel like the bad guys for expecting too much of them. Anyway, it took several weeks before people were able to play the game reliably, after which point they breathed a sigh of relief, took it for a quick spin, and then went back to playing Overwatch.

Related: 5 Dark Turns Lurking In The Next Pokemon Go Expansion

One of the worst elements of Kinect Star Wars was "Galactic Dance-Off," a mode wherein you could dance along to franchise-themed parodies of current songs like "Hologram Girl" (a riff on "Hollaback Girl"), "Empire Today" ("Y.M.C.A"), "Blasterproof" ("Bulletproof"), and of course "I'm Han Solo" ("Ridin' Solo").

For a long, long time, we wondered who we had to blame for this mess. Was it George Lucas? Kathleen Kennedy? Rian Johnson? Those bloody Sith again? Um, no. It was the fault of the bean counters over at Microsoft:

Microsoft had had success with a Kinect dance game, they had licensed a number of songs for a different dance game, and then that game fell through. They had that license and they had all these songs, and they knew that that gameplay was something that worked well with the Kinect. So somebody at Microsoft made the decision that they were going to add a dance section into the game.

On the other hand, the existence of "We No Speak Huttese" kinda evens everything out.

Related: The Terrifying Next Step In Xbox Kinect Evolution