10 Times Publishers Sabotaged Their Own Video Games

5. Forcing Every Studio To Use Frostbite - EA

I'm... noticing a trend here. But hey, there's a reason why EA have been voted the worst company - like, ever - a whole bunch of times. Seriously, go stick an EA logo on Star Wars' Emperor and see if it looks out of place. Go on! We do it all the time, and frankly I've never felt better.

EA's rep has flip-flopped so much over the last five years, but arguably the biggest contributor to their decade of controversies has been the company's insistence that every studio use the Frostbite engine.

When used properly, and by those familiar with its intricacies, Frostbite can look phenomenal. That's fairly evident in pretty much every game helmed by DICE, who created the engine all the way back in 2008 with Battlefield: Bad Company. But sadly for those studios less accustomed to its quirks, using Frostbite can quickly turn into a nightmare.

At the start of the decade, EA demanded that all its studios switch to Frostbite, as pretty much every studio was utilising their own separate engines. Problems quickly began to emerge, as Frostbite was mainly designed for FPS and multiplayer games. BioWare in particular found themselves repeatedly frustrated by the engine, with Dragon Age: Inquisition supposedly a nightmare to work on and both Mass Effect: Andromeda and Anthem experiencing widespread bugs upon their respective launches.