| 1 | ---- |
| 2 | [[foldercontrol]] |
| 3 | |
| 4 | [[folder:#-B]] |
| 5 | * ''VideoGame/FiftyCentBloodOnTheSand'' started life as a tie-in for a TV series based on Creator/RobertLudlum's ''Covert-One'' novels but the show was scrapped and so was the game's original incarnation, which was also set in a Middle Eastern locale. Vivendi had the licence to make games based on Fiddy's likeness and stage persona, and offered Swordfish to develop a sequel to ''Bulletproof'', much to the shock of the team. Not wanting to leave the ''Covert-One'' work to waste, they retooled the project into an absurd, over-the-top romp of a rapper and his posse staging a concert in a ''war zone'' of all places, fighting his way through just to get a diamond-encrusted skull he was promised as compensation. Even with the shift in tone in place, Swordfish had to muddle through with development, particularly when 50 Cent's son insisted on helicopter sequences and the rapper himself wanting to have vehicle chases thrown in, something which Swordfish had to implement despite it being a total headache to code and incorporate. Vivendi then merged with Activision, and the game was left in limbo again when it was not included in the [=IPs=] Activision acquired during the merger. Creator/{{THQ}} finally picked up the rights to the game, with Swordfish folding around that time. |
| 6 | * The much-anticipated mystery game ''1666'', that was being developed by Patrice Desilets of ''Franchise/AssassinsCreed'' and ''VideoGame/PrinceOfPersiaTheSandsOfTime'' fame, has been delayed due to conflicts between Patrice and Creator/{{Ubisoft}} due to Ubisoft acquiring the rights to the game after THQ's bankruptcy. Since Patrice had left Ubisoft for THQ due to creative differences, Ubisoft wasted no time in firing Patrice over "creative differences". However, as [[ScrewedByTheNetwork one final act of spite]], Ubisoft did not outright cancel ''1666'', since that would revert ownership of the rights back to Patrice. Instead, they put development "on hold" indefinitely just so they can keep the title out of Patrice's hands. Patrice pursued legal action to force Ubisoft to release the property (which eventually did happen, though what will happen next is anyone's guess). |
| 7 | * While prior games in the ''VideoGame/AceCombat'' series had relatively smooth productions, ''VideoGame/AceCombat7SkiesUnknown'' had serious troubles that nearly killed the project and the series. |
| 8 | ** [[https://twinfinite.net/2019/03/ace-combat-7-heartfelt-story/ As]] [[https://twinfinite.net/2019/03/ace-combat-7-best-launch-saved/ explained]] by Producer Kazutoki Kono, the concept of the game sat on the shelf for two years due as Creator/BandaiNamcoEntertainment focused on the free-to-play business model of ''VideoGame/AceCombatInfinity''. After ''7'' was finally given the go-ahead, the project was restarted after the game's announcement at [=PlayStation=] Experience 2015. Kono was dismayed at the lack of progress or a clear design goal and felt that the game was "boring", all of which led to several delays. |
| 9 | ** Bandai Namco grew restless with the chronic ScheduleSlip and production troubles. Multiple attempts to have Kono removed from the development team were made, and Kono was eventually confronted by executives who were considering cancelling the game and shelving the series. Kono convinced them to let the game's development continue, a process that reduced Kono to tears. |
| 10 | ** It was only in late 2017 that the game began to take shape, with the team expanding and Manabu Shimomoto joining as a second producer. The team worked in a frenzy to complete the game, breaking through the game's VR troubles as well as redoing work on various elements to a higher standard of quality. When ''Ace Combat 7'' released in January 2019, it was met with a level of critical acclaim and commercial success the series hadn't seen since the Platform/PlayStation2 era, selling 500,000 units [[https://twitter.com/BandaiNamcoSEA/status/1099927006412763137 in Asia]] during its first month. By August 2021, the game had become the best-selling installment in the series with over 3 millions copies sold worldwide, vindicating Kono's struggle. |
| 11 | * ''VideoGame/TheAct'', an InteractiveMovie arcade game with hand-drawn animation from ex-Creator/{{Disney}} animators, was cancelled when its location test failed, and publisher interest never materialized. Developer Cecropia [[CreatorKiller closed]] [[http://www.bizjournals.com/boston/blog/mass-high-tech/2008/06/while-the-local-gaming-space-rises-cecropia.html afterwards.]] Only a handful of conversion kits and dedicated cabinets exist. The game's sole port to iOS devices was delisted from the App Store in 2015 when third-party company React Entertainment shut down. |
| 12 | * ''VideoGame/Action52'', an unlicensed 1991 [[Platform/NintendoEntertainmentSystem NES]] compilation of 52 games on a single cart, became one of the most infamous games of its decade due to this. Vince Perri, head of Active Enterprises, hired 4 college students and gave them only '''three months''' to make the compilation, a laughably short timespan for a single game let alone dozens. Despite this, Perri was so confident in the game that he announced it at CES with plans for a portable game system and multimedia franchise based on ''Action 52'' title ''The Cheetahmen''. The final product dashed away such ambitions, as it contained extremely basic games [[ObviousBeta plagued with technical issues]] as they had no time for bug testing. In fact, some games would crash when trying to start rendering them unplayable. Critics and consumers alike were viciously negative (especially as its price point was $200 USD), and Active Enterprises would close down in 1993. |
| 13 | * The Amiga adaptation of ''Anime/{{AKIRA}}'' is considered one of the worst games ever released on Amiga computers. [[http://www.hardcoregaming101.net/akira-amiga/ One intrepid writer for games]] set out to find out exactly how the game wound up so dismal, and the small handful of members of the development team that he managed to make contact with recounted how they worked well into the night to try to bugfix the game and how their bosses were completely incompetent. Attempts to contact said bosses were met with demands for the writer to "FUCK OFF". |
| 14 | * ''VideoGame/AlanWake'', as detailed by [[https://www.youtube.com/watch?v=AoHkGDu0_Hw this War Stories video]] from Ars Technica, was an unusually rough production for Creator/RemedyEntertainment that took six years of development. |
| 15 | ** Having finished work on the ''VideoGame/MaxPayne'' series and parting ways with Rockstar Games, Remedy decided that their next title would be an open-world SurvivalHorror game, where the player would spend the in-game daytime preparing for combat against shadow enemies at night. Remedy immediately encountered problems; the studio had never developed an open-world title before, and Remedy's small team (roughly 55 full-time developers) were woefully understaffed for the demands. Not wanting to hire more developers for the sake of one project, Remedy spent a year building technology to expedite the process of building the game world. |
| 16 | ** Showing off the game with a next-generation technological demo at E3 2005, Remedy quickly generated interest from publishers and by 2006 found a partnership with Microsoft, who won Remedy over by allowing Remedy to retain ultimate control over the ''Alan Wake'' property. Despite the impressive demo, Remedy had only began prototyping gameplay with Microsoft's partnership. |
| 17 | ** With the game now in full development, Remedy slowly realized the fundamental design of the game had critical issues. The open-world structure clashed against Remedy's attempts to write a storyline, while various gameplay elements were not proving to be engaging. Three years into development, the game had fallen so far out of the public eye that it was assumed to be {{Vaporware}}, and was missing internal milestones, creating tension between Remedy and Microsoft. |
| 18 | ** Having decided the game's structure was fundamentally unworkable, Remedy effectively suspended development on the game for two months while the lead developers formed a "sauna" group to internally {{Retool}} the game's story and design. By the end of the process, the game was now a linear psychological action thriller and the open-world was cut down into traditional levels. While less ambitious and requiring content to be cut, development resumed at a brisk pace. |
| 19 | ** But with the game having slipped to 2010, Microsoft began imposing their will on the game in what Remedy's Sam Lake described as a "too many cooks" situation. This included canceling the Windows PC version of the game as Microsoft's gaming division had shifted away from Windows in favor of the Xbox consoles. ''Alan Wake'' released in May 2010 to positive reviews, but initial sales were weak due to releasing next to ''VideoGame/RedDeadRedemption''. The game eventually turned a profit thanks to steady sales, strong word-of-mouth from fans, and a Windows PC port in 2012. |
| 20 | * ''VideoGame/AlienResurrection'': While [[Film/AlienResurrection the film's]] production was calmer than its predecessors, the production of its video game tie-in is another story, as documented by WebVideo/MattMcMuscles [[https://www.youtube.com/watch?v=8GLxPjX0L2M&t= here]]. |
| 21 | ** Fox Interative contracted Argonaut Games to produce an ''Franchise/{{Alien}}'' game during the development of ''VideoGame/{{Croc}}'' but gave them no directive beyond that. Assuming it was for a prospective ''Franchise/AlienVsPredator'' title, Argonaut developed a prototype whose engine was based on the recent game ''VideoGame/{{Loaded}}''. Fox was impressed with the prototype and greenlit the game, which they clarified was a tie-in to the upcoming film. They also assigned Argonaut to develop an in-movie game, ''Atom Zone'', which they finished in three days. Fox soon announced the game would debut on PC, [=PlayStation=] and Sega Saturn in time for the film's November 1997 premiere. |
| 22 | ** Once production on the real-world game began, Fox sent Argonaut relevant production materials for inspiration. The task of watching hours upon hours of dailies proved tedious for the production staff. It didn't help that the film was rewritten constantly, which made it difficult to produce something faithful to it. |
| 23 | ** By the end of 1996, and with 60 percent of the game done, Argonaut realized their ''Loaded'' engine was outdated next to the newly released ''Franchise/TombRaider'' and retooled it into a 3D third-person shooter. At least thirty percent of the staff [[ScrewThisImOuttaHere quit the project]], which was then pushed back to Spring 1998. |
| 24 | ** Things got worse when Argonaut was given an early screening of the film. They were not impressed. They were especially disappointed that ''Atom Zone'' had only eight seconds of screentime. Nevertheless, they continued production, albeit with lowering morale. Fox continued to promote the game, whose release date was getting delayed again and again, while its Saturn and PC ports were canceled. |
| 25 | ** It didn't help that the 3D engine was difficult to work with. While the ''Loaded'' engine allowed up to 100 enemies to appear on-screen, the ''Tomb Raider'' engine only allowed for three. These enemies had only basic "walk-in and attack" patterns. They also dealt with a limited draw distance and a camera system that made it impossible to ''not'' see new foes coming. Argonaut solved these problems by turning the game into a FirstPersonShooter, which limited players' [=POVs=], and therefore, made enemies scarier. This meant things like fully voiced cutscenes had to be scrapped, but it meant the game didn't have to be restarted from scratch either. |
| 26 | ** When the game finally made it to stores in Fall 2000, three years after the film, it was met with mixed reviews. Gamespot, in particular, took umbridge with [[ItWillNeverCatchOn its unconventional Dual Analog control system]], which would be adopted by the FPS genre down the line. Nowadays, it's been VindicatedByHistory as [[SugarWiki/NoProblemWithLicensedGames being better than its associated film]]. |
| 27 | * ''VideoGame/AliensColonialMarines'' spent six years in DevelopmentHell, and it shows in the finished product. Reportedly, the game's sorry state involved [[http://kotaku.com/5984068/how-aliens-colonial-marines-fell-apart a clusterfrak]] [[http://kotaku.com/5986694/from-dream-to-disaster-the-story-of-aliens-colonial-marines of epic proportions]] on the part of publisher Creator/{{Sega}} and developer Creator/GearboxSoftware alike. |
| 28 | ** 20th Century Fox had tried to get production rolling for many years, beginning with an aborted attempt by Check Six Games (which was intended to be released for the [=PS2=] at one point) in 2001, and culminating in their hiring of Creator/GearboxSoftware in 2006. |
| 29 | ** However, production was very slow for the first four years, and there were a lot of "cooks in the kitchen" with different ideas about where to take the franchise. Allegedly, Gearbox was using money Sega paid them to work on other projects, including ''{{VideoGame/Borderlands 2}}'' after the first game became a surprise hit. They eventually farmed out the game to [=TimeGate=] Studios (makers of ''{{VideoGame/Section 8}}'' and the non-canon ''[[VideoGame/FirstEncounterAssaultRecon F.E.A.R.]]'' expansion packs) so that they could meet their obligations to Sega. |
| 30 | ** The first indication that something was wrong happened when [=TimeGate=] got their hands on Gearbox's assets for the game. What they found was a hodgepodge of barely functional code that clearly wasn't the result of four years' worth of work, forcing [=TimeGate=] to scrap most of it and rebuild the game from scratch. Complicating this was the fact that the script had not been finalized yet, so content was continually being scrapped or changed due to last minute story changes. The creative process was also hampered since [=TimeGate=] had to pass all decisions through both Sega and Gearbox for approval, leading to multiple conflicts. Finally, Gearbox and [=TimeGate=] had wildly different design philosophies, with Gearbox being more content with delaying games to ensure quality, while [=TimeGate=] being more concerned with shipping games as quickly as possible. |
| 31 | ** During this time, an [[https://www.youtube.com/watch?v=2fHv4wQJfSY amazing-looking teaser reel]] was released at E3 2011 showcasing sections from the Hadley's Hope stages, helping to get people pumped for when the game came out. [[NeverTrustATrailer This video was made of nothing but lies.]] The demo was cut together using pre-release code running at a higher framerate than the finished game, polished to a greater extent, and featured gameplay elements and setpieces that were not present in the final product. Furthermore, the demo was a prelude to another series of delays, as the release was eventually pushed to February 2013. |
| 32 | ** By 2012, most of their replacement assets were still incomplete. Sega was becoming impatient with the game's progress, to the point that they could threaten legal action for contract breaching. Gearbox had to step up, try again from an incomplete product, and rush the game out the door despite knowing it was in no condition to hit the market in order to get their contract fulfilled and avoid the aforementioned legal action. [[https://www.youtube.com/watch?v=aBHkricvocs This retrospective]] by [=YouTuber=] DK makes the argument that a large number of game mechanics and setpieces were cribbed wholesale from ''VideoGame/FEAR2ProjectOrigin'' by design director John Mulkey, who also helmed design on the latter title. |
| 33 | ** After the game's critical drubbing, a planned Platform/WiiU port was scrapped, and Sega and Gearbox were hit with a class-action lawsuit for knowingly misrepresenting the levels, graphics, and AI in previews and press demos, as well as restricting reviews until after the game's release. Sega agreed to [[http://www.destructoid.com/sega-agrees-to-settle-in-aliens-colonial-marines-lawsuit-279556.phtml a $1.25 million settlement]], but not before [[http://www.destructoid.com/sega-outs-gearbox-for-lying-in-aliens-colonial-marines-case-280655.phtml accusing Gearbox]] of lying to them as well by presenting the demo as indicative of their progress. |
| 34 | ** Years later, it was revealed by modders digging around in the game's code that one of its most infamous flaws, in which enemies would appear to dance around without ever attacking, was caused by a [[https://www.polygon.com/2018/7/15/17574248/aliens-colonial-marines-fixing-code-typo-ai-xenomorphs one letter typo]] on the word "tether" in one line of code, without which the enemies would have no idea where they were or what they were supposed to be doing. |
| 35 | * [[http://www.polygon.com/2016/2/1/10889756/ant-simulator-eteeski-strippers-liquor-allegations- Two]] [[http://www.gameinformer.com/b/news/archive/2016/02/01/ant-simulator-business-partners-respond-devs-claims-100-percent-bull.aspx conflicting]] accounts exist over the indie game ''Ant Simulator''[='=]s troubled development and eventual cancellation: |
| 36 | ** One developer, Erik Tereshinski, [[https://www.youtube.com/watch?v=2IWl29BNawg alleged]] his friends/business partners Tyler Monce and Devon Staley spending most of the Kickstarter and investment money on "liquor, restaurants, bars, and even strippers." Other claims included: Monce was incompetent with submitting the game to Sony for a software development kit; Staley lied regarding conversations with Sony; Monce and Staley overspent on setting up an office in the basement of Staley's mother's home. |
| 37 | ** Monce and Staley [[http://www.gameinformer.com/b/news/archive/2016/02/01/ant-simulator-business-partners-respond-devs-claims-100-percent-bull.aspx claim]] Tereshinski [[SmallNameBigEgo egotistically]] monopolized their company's bank accounts, social media accounts and website. They also accused him of embezzlement and have considered pursuing legal action. |
| 38 | * Development on ''[[VideoGame/Anthem2019 Anthem]]'' was characterized by near-constant upheaval up to a few months before its release, as detailed in [[https://kotaku.com/how-biowares-anthem-went-wrong-1833731964 this article]] by Jason Schreier for ''Kotaku'', who described its development as "a story of indecision and mismanagement" that characterized the troubled state that Creator/BioWare was in at the time. |
| 39 | ** First teased in 2012 and originally known under the codename "Dylan" before it was titled ''Beyond'', the game spent years in pre-production. The team wanted to break away from their traditional role-playing formula and quickly settled on the idea of an online multiplayer action game set on a hostile "[[TheBermudaTriangle Bermuda Triangle]] in space" alien world, with the {{Player Character}}s piloting suits of flying PoweredArmor and a Hard Science Fiction approach that was said to be "less ''Film/IronMan'' and more NASA". Development suffered a blow when Casey Hudson, the ''Franchise/MassEffect'' creative director who was slated to take on that role in ''Beyond'', left the company in 2014. Hudson played a major role in development on the games he worked on, and without him the team felt directionless. Regardless, morale on the ''Beyond'' team was high, especially compared to the Montreal team behind ''VideoGame/MassEffectAndromeda'', which was in a state of internal crisis. |
| 40 | ** [[TemptingFate Very quickly]], the same problems that plagued development on ''Andromeda'' hit ''Beyond''. Many [=BioWare=] employees blamed the creative leadership team for the turmoil, as they seemed to be designing the game by committee and agreeing on little in the way of a coherent vision. Ideas for the gameplay, setting, and lore of the game were frequently brought up, worked on, abandonned and then brought up later on without a leadership to give them clear directions. An internal mandate was made forbidding examining or even ''discussing'' the similar game ''VideoGame/{{Destiny}}''. While this was done so that in theory Creator/BioWare would avoid even subconsciously [[FollowTheLeader mimicking]] ''Destiny'', it also prevented them from learning what it did right and wrong, especially as various changes made ''Beyond'' resemble ''Destiny'' anyway. Several developers expressed concerns that ''Beyond'' was repeating the same development mistakes as ''Andromeda'' and ''VideoGame/DragonAgeInquisition'', but were brushed off by management. |
| 41 | ** Their ambitions also faced technical limitations. Just as with a slew of other EA projects, the proprietary Frostbite MediaNotes/GameEngine proved to be a nightmare for the team to work with, forcing them to cut back their ambitious SurvivalSandbox plans for the game. [=BioWare=] staff with experience working with Frostbite were often shuffled over by EA to work on the ''VideoGame/FIFASoccer'' series and salvaging ''Andromeda'', leaving the studio understaffed. [=BioWare=]'s internal policy of not sharing technology between projects resulted in the team effectively redoing work that had already been done for ''Andromeda'' and ''Inquisition''. After the Montreal studio that worked on ''Andromeda'' was shut down, most of its staff was moved over to work on ''Beyond'', giving the team a much-needed boost to its workforce. |
| 42 | ** It was just in time as EA executive Patrick Söderlund, highly disappointed by progress on ''Beyond'', demanded they put together a more impressive demo build in six weeks -- one that led [=BioWare=] to reintroduce flying to the game, a feature that had been heavily debated by the team. This demo wowed Söderlund and became the basis for the game's reveal at [=E3 2017=]. Just days before the reveal, EA forced [=BioWare=] to change the title from ''Beyond'' to ''Anthem'' as they couldn't secure the trademark for ''Beyond'', a change that disappointed many on the team. |
| 43 | ** [=BioWare=]'s Austin, Texas studio was also called in as reinforcements - and they quickly clashed with the main team in Edmonton, Alberta. Edmonton saw itself as [=BioWare=]'s "A-team" and the Austin team as a bunch of upstarts, while the Austin team was bitter that their input was being dismissed, especially since they had experience working on an online game in the form of ''VideoGame/StarWarsTheOldRepublic'' and [[IgnoredExpert had gone through many of the same problems]]. Production sprawled into further chaos as 2018 approached, and EA would only delay the game until March 2019 at it marked the end of the fiscal year. The troubles began to take a toll on other projects within [=BioWare=]'s walls, with a version of ''Franchise/DragonAge 4'' codenamed '[[WorkingTitle Joplin]]' scrapped to reassign its team to assist with ''Anthem''. |
| 44 | ** The arrival of Mark Darrah as the game's executive producer is credited as a major turning point in the game's troubled history; he gave clear direction to the development team, committing them to getting the game released even if it meant that they had to cut features that had been profiled in previews or leave {{Plot Hole}}s due to last-second story changes. The final year of development happened at a breakneck pace, and the team was hit with crunch time so brutal that some employees suffered mental breakdowns and were given "stress leave" for the sake of their mental health; many wound up quitting due to burnout. Casey Hudson also rejoined the project during its final months. Even with Darrah and Hudson's efforts, it was clear to everybody that the game would be effectively unfinished at release. |
| 45 | ** ''Anthem'' was released in February 2019 to rocky reviews and poor sales. Its Metacritic scores across all three platforms sit in the 50s and 60s - numbers generally considered disastrous for a big-budget title. Many people who left the studio described development on ''Anthem'' as a symbol of everything that had been going wrong at [=BioWare=] for years by that point, in particular its over-reliance on "[=BioWare=] Magic", i.e. crunch time that would pull a troubled production together in the last few months. [=BioWare=] [[http://blog.bioware.com/2019/04/02/anthem-game-development/ replied to Schreier's article]] a mere 15 minutes after the article went live, accusing the gaming press of writing articles that 'tear down the industry'. This reply was not taken kindly by fans or the press, especially as the story was surrounded by reports of brutal crunch conditions and employee mistreatment throughout the industry. Creator/ElectronicArts would [[https://www.businessinsider.com/electronic-arts-laying-off-350-employees-2019-3 lay off 350 employees]] a few weeks after the release of ''Anthem'', likely in reaction to the game's poor critical and sales performance. |
| 46 | ** The troubles continued post-launch, as support of ''Anthem'' was not any better with an inconsistent update schedule and a litany of bugged content that lead to a hemorrhaging player base. The 90-day roadmap was delayed indefinitely at the end of April 2019, and some [=PS4=] owners reported that the game would crash and '''brick their consoles''', due to some crashes permanently corrupting [=PS4=] databases. The further updates to ''Anthem'' reduced drop rates of Legendary gear against player requests, and the much anticipated Cataclysm expansion was eventually released in August 2019, a full ''3 months'' behind its original release date; even then the Cataclysm event failed to reinvigorate ''Anthem'' in the public conscience, and [=BioWare=] announced they would [[https://www.eurogamer.net/articles/2019-09-17-bioware-ditching-anthems-original-post-launch-content-plans-to-focus-on-core-issues cancel their post-release plans]] in favor of focusing on the game's core issues. It was estimated that by May 2019, the number of concurrent players on the Xbox One alone [[https://comicbook.com/gaming/2019/05/26/anthem-ps4-xbox-pc-player-count/ numbered less than 2,500]]. |
| 47 | ** One year after the game's initial launch, Bioware announced that the studio was holding off seasonal updates in favor of massive rework titled "Anthem Next". However, Darrah and Hudson would retire from Bioware in the same year, leaving "Anthem Next" without any leadership and only a skeletal crew. Making matters worse is the UsefulNotes/COVID19Pandemic hampering development by forcing the small team to work remotely. Although the team provided a demo for EA, the publisher ultimately cancelled the overhaul in February 2021 and transferred the remaining ''Anthem'' developers to work on other Bioware [=IPs=]. The tumultuous development of ''Anthem'' and its subsequently disappointing reception also convinced EA to remove mandatory multiplayer elements planned for ''Dragon Age 4''. |
| 48 | * ''VideoGame/{{Apocalypse}}'' contains a full list of credits for the version of the game that Creator/{{Activision}} tried to develop internally but eventually gave up on and had Neversoft rebuild from the ground up. |
| 49 | * ''VideoGame/{{ARMA}} III'''s development eventually led to a somewhat-infamous incident where two members of the dev team were arrested in Greece and held for over 4 months under charges of espionage. Greek officials asserted that they were taking pictures of Greek military facilities as research for the game's setting, while the devs retorted that they were simply on vacation and that the planning and designs for the setting were already finished by then. |
| 50 | * ''VideoGame/BatmanDarkTomorrow'' went through hell during development. The ambitious project sought to see Batman travel an open world Gotham with usage of his legendary vehicles. Initially it was meant to be a Gamecube exclusive before pivoting into adding the Xbox and Playstation 2 (the latter quietly cancelled early on). But things went completely off the rails as explained by former Hot Gen dev Dave Vout via the web series ''Wha Happun?'' by WebVideo/MattMcMuscles: |
| 51 | ** The first bit of trouble came from producer Yuki Takafumi, who was producing his first video game after coming off numerous TV and movies. It was quite obvious that the CGI cutscenes and music were beautifully done, but nothing had been addressed concerning the gameplay side of things. |
| 52 | ** Vout found himself in a culture where he had to sell ideas to the board team and get every member to agree to each one just so his team could help finish the Gamecube version before jumping onto the ports. At the same time, his team investigated the code and learned that it was running on a ''Platform/GameBoyAdvance emulator''. Vout surmises that the team was originally meant to make a GBA port but was moved to making a Gamecube game and they decided to do things like this to get it running. |
| 53 | ** There was also a massive case of culture clash between the Japanese company Kemco and DC Comics with Scott Peterson recalling one instance of the Kemco developers suggesting that Batman would distract guards by ''pulling out a boombox and playing salsa music''. Essentially speaking, they had no idea what Batman's character was or how his various series function. |
| 54 | ** Outside of a comic tie-in, Kemco had ''no money'' [[InvisibleAdvertising to push for a marketing campaign]] and hoped good word of mouth would save the game, which it obviously did not. In the end, Kemco would find themselves scaling back massively and making simple mobile RPG games while Hot Gen would ultimately collapse soon after. |
| 55 | * ''Battlecruiser 3000 A.D.'' In 1989, Derek Smart had the idea for a grand, sweeping game set on a large ship cruising a realistically large galaxy. Players could choose how they wanted to experience it, from either the strategic level commanding fleets of ships in interstellar campaigns, to just [[FirstPersonShooter shooting it out]] on a planetary surface with a blaster. Three years later it was a gaming magazine's cover story as "the last game you'll ever want." |
| 56 | ** Smart posted regular, lengthy updates on multiple online forums. This got him in his first bit of trouble. He claimed at one point that he'd figured out how to make the opposing [[ArtificialIntelligence AIs]] use neural nets, a potential quantum leap in not only gaming but computing as a whole. Many developers and programmers were skeptical, and Smart's updates soon engendered one of the longest-running {{flame war}}s in UsefulNotes/{{Usenet}} history due to his penchant for writing lengthy and confrontational replies, then lengthy and confrontational rebuttals to the lengthy and confrontational responses those replies got. Some people say that the feud between Smart and his critics might as well have been the real game, since at least most people could play it. |
| 57 | ** Offline, his personality was having the same effect on his backers. He went through several before landing at a small, relatively new company called Creator/TakeTwoInteractive. They got tired of his antics and, in 1996, called one of Smart's frequent bluffs by actually releasing the game. [[ObviousBeta The buggy, unfinished result]] of seven years of hype, development, and online acrimony got the expected horrible reviews. |
| 58 | ** Smart immediately went online blaming Take-Two. He was just as incorrigible with the company's executives. During one of the fights he had with management there, he started trashing the company's office, reportedly completely destroying a Coke machine at one point (an account he denies). |
| 59 | ** Smart has released some later versions as freeware. The flame wars are probably still going on ''somewhere'' on the Internet. And given his interest in the development of ''VideoGame/StarCitizen'', a game that he feels is a similarly troubled production, they likely won't end anytime soon. |
| 60 | * According to [[https://www.youtube.com/watch?v=2MKtgP7cHEk interviews and information gathered by]] Tom Henderson, ''VideoGame/Battlefield2042'' and its problematic reception was the result of ExecutiveMeddling by EA and management troubles at EA DICE reaching a breaking point. |
| 61 | ** The troubles for ''2042'' began far earlier, as numerous DICE directors, producers, and engineers started leaving the company after the release of ''VideoGame/Battlefield1'', frustrated by EA pushing for ''Battlefield'' to FollowTheLeader and become a BattleRoyaleGame like ''VideoGame/{{Fortnite}}''. This exodus caused a "brain-drain" at the studio, with inexperienced developers now left to grapple with the mounting issues facing the franchise, and post-release support for ''Battlefield V'' ended prematurely due to lacklustre sales and volatile player reception, |
| 62 | ** DICE was now left not only with the task of developing a new ''Battlefield'', which EA ordered to "copy what's popular", but addressing the increasingly outdated technology of the Frostbite game engine. With senior engineers who had made the engine no longer available, DICE was now struggling with Frostbite in the same way that [[VideoGame/MassEffectAndromeda many]] [[VideoGame/Anthem2019 other]] [[VideoGame/{{Ragtag}} projects]] under the umbrella of EA already had. What was predicted to be a six month task instead took '''eighteen''' months, roughly half of the development time. |
| 63 | ** Even with the success of ''VideoGame/ApexLegends'' giving EA its much-coveted Battle Royale title, concerns about its longevity made them continue their plan to make ''2042'' another BR title as insurance. The onset of the UsefulNotes/COVID19Pandemic forced DICE to implement work-from-home policies, which had a profound impact on development as communication troubles and supply shortages for high-end PC parts bottlenecked futher development on the game. |
| 64 | ** With ''VideoGame/CallOfDuty Warzone'' being a runaway success for Activision and ''Apex Legends'' having stablized into a persistant money-maker for EA by the middle of 2020, EA now wanted ''2042'' to offer a more traditional ''Battlefield'' experience on top of its BR game mode, which became 'Hazard Zone' in the final release. This late shift in direction caused further turmoil, as developers were now scrambling to make content beyond the scope of what had been planned. And combined with issues with the engine overhaul, the game was in crisis from a technical standpoint. |
| 65 | ** Even with Creator/CriterionGames dropping their intended 2021 ''VideoGame/NeedForSpeed'' title to help development, DICE still begged for additional help from the team of Frostbite technical staff within EA to get the game to a playable state. Even with their efforts, the Technical Play Test on August 2021 was a disaster, as the sheer amount of issues on display cast dark clouds upon the game. Despite reassurances to the public and a slight delay, it was known internally that the game would be making a rough landing on its release date. When it released on November 19, 2021, the game was riddled with performance issues and bugs, even more than the notorious launch of ''VideoGame/Battlefield4'', while many players who toughed out the issues considered the game to be thin in content and had fundamental design problems. Even the positive critic reviews it received were muted compared to prior games in the series. |
| 66 | ** Pains continued even after the release, as old features like voice chat and scoreboard had been removed in the name of addressing player toxicity -- which led to DICE developers being harassed away from the ''Battlefield'' sub-reddit, [[NotHelpingYourCase ironically justifying the decision to cut such features]]. The player count of ''2042'' dropped dramatically within the months following release, to the point where ''Battlefields'' ''1'', ''4'' and ''V'' were drawing more players daily, as DICE pushed further patches or updates to later dates. In December 2021, EA [[https://www.theverge.com/2021/12/2/22814517/ea-battlefield-vince-zampella-apex-legends-respawn-boss-ceo-shakeup appointed Vince Zampella]] of [[VideoGame/{{Titanfall}} Respawn]] [[VideoGame/ApexLegends Entertainment]] to oversee the future of the franchise, while DICE GM Oskar Gabrielson departed the company. |
| 67 | * The development of ''Beast's Fury'' -- an indie 2-D fighting game with a cast of anthropomorphic animals -- was rightly described by [[http://archive.is/g07R1 this article]] as a "sideshow circus". A former developer of the project [[https://www.youtube.com/watch?v=vYSiIRG3IIo has also discussed its issues at length]]. |
| 68 | ** In 2013, Australian game developer Rhyan Stevens sought to capitalize on the fame of the 2-D fighter ''VideoGame/{{Skullgirls}}'' [[StartMyOwn with his own game]]. His company, Beast Fury Studios, partnered with Montreal-based flash and mobile game developer Evil Dog Productions. Despite [[ToughActToFollow the high bar set by]] ''[[ToughActToFollow Skullgirls]]'', development began confidently. |
| 69 | ** Inspired by ''Skullgirls''' successful Indiegogo campaign, Stevens [[StartMyOwn created his own]]. Two back-to-back failed campaigns later, he returned with ''[[ThirdTimesTheCharm a third one.]]'' It raised over $20,000--mainly thanks to endorsement by Platform/{{YouTube}} personalities [[LetsPlay/TheOnlineWarrior Maximilian Dood]] and [[WebVideo/GameGrumps Egoraptor]]; they were touted as guest characters if stretch goals were met. Neither was funded, but several other characters were. |
| 70 | ** Stevens' projections for the animation costs were ''so'' inaccurate, his team couldn't finish the first two characters. After [[https://www.facebook.com/BeastsFuryGame/posts/810800969016456 admitting this]], he created [[https://www.kickstarter.com/projects/beastsfurygame/keep-beasts-fury-going/ a fourth campaign]] with more realistic stretch goals. The campaign raised over $47,000, which funded the first two characters. |
| 71 | ** [[SkewedPriorities The campaign money was blown on visual gimmicks over gameplay]], including cinematics, 3-D models and art for unfinished characters. Not helping were the ''Franchise/MortalKombat''-esque [[FinishingMove finishing moves]]; by design, they had different animations when performed on all current ''and'' future members of the roster.[[note]] In contrast, ''Skullgirls'' reused animations and avoided gimmicky mechanics with little impact on gameplay in order to lower costs.[[/note]] |
| 72 | ** Worse, Stevens had a skeletal team of only two part-time animators. His next Kickstarter campaign to expand the roster improved nothing, despite making twice its goal. The animators themselves were [[https://twitter.com/sorcererlance/status/685188410672205824 allegedly]] overworked, verbally abused, and barely paid by Stevens. |
| 73 | ** [[https://ibijau.tumblr.com/post/136895458483#notes The voice actors also got the shaft]]. Stevens allegedly fired one character's voice actor, ''and'' his replacement, when they asked to be paid. He later came crawling back for the original voice actor, who agreed to be rehired only after being paid first. However, Stevens sampled "demo recordings" and passed them off as final audio so that he didn't have to pay. |
| 74 | ** Egregiously, a sequel and animated short film were planned...while ''the first demo'' languished in a two-year DevelopmentHell. Lead designer Andrew Fein, a professional ''Franchise/StreetFighter'' player, was inexperienced in game design and mostly added whatever (bad) ideas Stevens wanted to the game. Upon release in 2015, the demo was a [[ObviousBeta buggy, unbalanced mess]]. Entire updates were dedicated to adding purely cosmetic elements. |
| 75 | ** Aya, the designer of the doujin fighting game ''MONSTER'', joined the project as a consultant. However, he decided to take a chance after seeing the project's crowdfunding successes. At Fein's request, Aya fully redesigned ''Beast's Fury''. Stevens never signed Aya's contract, and was hostile when approached about payment two and a half months later. Aya would learn that Stevens also owed money to Fein and Evil Dog lead programmer Marco Arsenault. |
| 76 | ** Stevens' behavior drove off several potential investors, including Creator/WayForwardTechnologies.[[note]] When interviewed, Aya declined to elaborate on what Stevens did to make [=WayForward=] bow out.[[/note]] Allegedly, one deal involved Stevens not being the team leader. |
| 77 | ** One investor wanted a complete prototype as soon as possible. However, Stevens either lied or miscommunicated to Aya that they wanted it done ''in two weeks''. Arsenault refused to give Stevens the original engine's source code, so Stevens convinced Aya to reschedule his eye surgery and create the prototype from scratch. Many sleepless nights later, Aya sent the completed prototype to the investor, and was livid upon learning about Stevens' deception. |
| 78 | ** [[CantTakeCriticism Criticism was either ignored or met with animosity]] by Stevens and Arsenaut. They squandered [[http://skullheart.com/index.php?threads/beasts-fury-kickstarter-is-live.6714/ their]] [[http://skullheart.com/index.php?threads/beasts-fury-updates-discussion.6723/ attempts]] to gain the ''Skullgirls'' community's support and sparked [[https://youtu.be/DslNQQ-Xmdc?t=572 further derision]] after clashing with ''Skullheart'' forum users, [[http://skullheart.com/index.php?threads/beasts-fury-kickstarter-is-live.6714/page-4#post-126307 stalking and harassing naysayers on social media]], and rejecting developer Mike "Z" Zaimont's advice and offer to provide them ''the Skullgirls game engine''. |
| 79 | ** Aya bailed and discussed his poor experience in a [=FurAffinity=] interview with ex-''Beast's Fury'' artist [=RockawayCarter=]. Stevens hassled Aya for his design -- despite that he never signed Aya's contact to be legally entitled to it -- and tried to stop the interview. When this failed, he made his own [=FurAffinity=] interview to refute Aya's points. |
| 80 | ** The campaign backers never received their rewards. To quell the complaints, Stevens allegedly convinced one of his biggest supporters, who was terminally-ill, to lie on social media about receiving her wooden arcade stick, with Stevens promising to send her his arcade stick in return. He never did and ghosted her. |
| 81 | ** UsefulNotes/{{Furry|Fandom}} artist Adam Wan, who designed ''Beast Fury''[='=]s GUI, was accused by the fandom of being a bully and a sexual predator. Stevens and Evil Dog quietly deleted all mention of his name. Until [[https://www.dropbox.com/s/ctamabcwjxucdu1/logmidwayofBoF.txt?dl=0 an Internet chat log]] later confirmed Wan's involvement, [[GoneHorriblyWrong fans interpreted the damage control as deliberately hiding information]]. |
| 82 | ** [[https://www.indiegogo.com/projects/support-beast-s-fury-fighting-game#/story A last-ditch Indiegogo campaign]] with a massive $185,000 goal emerged in May 2015. [[https://mobile.twitter.com/jwonggg/status/607665192688742400 Promotion]] was solicited from professional fighting game player Justin Wong. As a testament to all the bridges burned, it only grossed $1,620 (which, thanks to "flexible funding", was still pocketed). Stevens [[ScrewThisImOuttaHere left the project]], and on January 2016 announced [[https://pbs.twimg.com/media/CYIUwSNWwAA286O.png in a now-deleted FurAffinity post]] that ''Beast's Fury'' was cancelled. |
| 83 | ** Beast Fury Studios [[CreatorKiller shut down]], and Evil Dog removed most references to the game from their official website. Stevens did [[https://archive.ph/Opagw another FurAffinity interview]] in an attempt to save face, and sought work elsewhere in the game industry, but [[http://archive.is/kG7H0 a conga line of voice actors and animators]] publicly alleged him of poor leadership and stiffing their pay. Some onlookers regard the train wreck as how ''not'' to make a fighting game. |
| 84 | * ''Videogame/BendyAndTheInkMachine'''s development for Chapter 1 started off not too bad, but became a huge problem during the making of Chapter 2. According to a Patreon post, The Meatly describes how the decision to release Chapter 2 within two months "almost killed us," and his and his co-creator's health suffered as a result of working so hard on the game. And the night before the launch date the game broke completely, refusing to run at all. The problem was rectified before ScheduleSlip could occur, but it was a very close call. |
| 85 | * ''VideoGame/BeyondGoodAndEvil2'' was initially teased in May 2008, with a short trailer showcasing a new graphics engine. Director Michel Ancel would later state that the game was only in pre-production and had not yet been greenlit, though a gameplay trailer would be leaked the following year. What would follow was a constant series of missteps, false starts, and very long waits between updates as the game underwent radio silence once again. |
| 86 | ** [[https://www.youtube.com/watch?v=C9VPnI34dPw A cinematic trailer at E3 2017]] was met with a lot of enthusiasm, and updates from 2018 seemed to showcase a new direction for the sequel. However, this enthusiasm began fading rapidly when the public started getting less and less information about the game. [[https://www.youtube.com/watch?v=aB0Tm6xTdSM The E3 2018 trailer]] was the most recent thing anyone had heard about the game when the world entered TheNewTwenties, which meant it rapidly fell off the radar for the gaming world at large. |
| 87 | ** In 2020, following original director Michel Ancel's retirement from game development, many members of the ''Beyond Good and Evil 2'' development team came forward to accuse Michel Ancel of mismanaging the game and holding up progress due to him dividing his attention away from the game by also directing ''Wild'' at the same time[[note]]Which has also reportedly been cancelled.[[/note]], having a penchant for frequently throwing out work and changing up game and story elements on a whim, and generally being unhelpful and even verbally abusive towards his staff. Ancel's retirement caught the team off guard, and the years afterward saw several other staff leave the project as it struggled to find a solid creative direction after Ancel's departure. In July 2021, Ubisoft ensured fans that development was "progressing well", but with Ancel leaving under very bad circumstances, fans were skeptical. |
| 88 | ** By late 2022, ''Beyond Good & Evil 2'' had broken the record for the longest development period for a video game in history, surpassing even the infamous ''VideoGame/DukeNukemForever''. It ended that year with no progress announced, although [[https://www.thegamer.com/beyond-good-and-evil-2-reportedly-being-playtested-in-early-development/ a minor source confirmed the game was being playtested]]. In January 2023, [[https://www.thegamer.com/ubisoft-still-making-beyond-good-and-evil-2-despite-cancellations/ Ubisoft assured fans that the game was still coming]], but by February, [[https://kotaku.com/beyond-good-evil-2-ubisoft-montpellier-assassins-creed-1850164420 several]] [[https://www.youtube.com/watch?v=7oche63hzg4 outlets]] revealed that the title has been undergoing various issues (unclear creative direction, staff burnout and high attrition rates, etc.) that kept it from entering full production. And then the next time the game made headlines in game journalism in July 2023, it was for the unexpected death of their then-latest creative director Emile Morel at age 40, only a few months after taking over from the previous creator director. It got to the point that shortly after the reveal of ''VideoGame/StarWarsOutlaws'', a false rumor circulated that ''Beyond Good & Evil 2'' had been scrapped and reworked into ''Outlaws'' going by its similarities to ''BG&E 1'' (despite having different developers). |
| 89 | * Team Alpha, the maker of the popular ''Alphabirth'' GameMod for ''VideoGame/TheBindingOfIsaac'', wound up being destroyed by their work on its third edition, as outlined in [[https://modteamalpha.tumblr.com/post/165080542066/a-critical-look-at-ab this blog post]] from the head of the mod team. Most of the problems stemmed from the new application programming interface (or API) introduced with the official expansion ''Afterbirth+''. While it was intended to be mod-friendly, it instead suffered from clunky programming and design that made modding work far more difficult. Fixes were slow in the pipeline, especially for modding tools, and ''Binding of Isaac'' developer Nicalis was slow in communicating. While the mod was released, the burnout suffered by the team caused them to hang it up afterwards. |
| 90 | * ''Blacksite: VideoGame/Area51'' suffered from a very rushed development cycle, due in part to Midway's insistence on having all of its future projects use the Unreal Engine 3, which was still experimental, and them making hail mary shots in the hopes that any of them would be successful. The situation had gotten bad to the point that Harvey Smith (who was working on his own game) had to be called in to intervene on the game's development. Needless to say, the game was released in a buggy state and to a poor critical and commercial performance. As Smith himself puts it: |
| 91 | -->"That project was so fucked up. I wasn't particularly interested in the IP, and it took eight months to get one thing working. With a year to go, the game was disastrously off tails. It went straight from alpha to final." |
| 92 | * The Creator/NightdiveStudios remaster of the ''VideoGame/BladeRunner'' AdventureGame [[https://www.eurogamer.net/articles/2020-10-22-replicating-blade-runner-why-the-adventure-game-classic-is-so-tough-to-remaster ran into trouble]], first because the game's source code and data were lost at some point between the release of the game and developer Creator/WestwoodStudios' acquisition by Creator/ElectronicArts, and then because it could not reuse any code from the [=ScummVM=]-based rerelease of the game on Platform/GOGDotCom as a result of [=ScummVM=] being licensed under the GPL and thus preventing anything using it or its code from being released on consoles [[labelnote:why?]]The GPL terms' require that any API used by a GPL project must itself be licensed under the GPL, and thus require its source code to either be available to the public or be available upon request, which is not allowed by the rules imposed by console makers regarding their [=APIs=][[/labelnote]]. An attempt to negotiate a separate license for [=ScummVM=]'s work on ''Blade Runner'' fell through. The result was that Nightdive were forced to repeat the work of [=ScummVM=]'s developers and reverse-engineer the whole game themselves. Among the difficulties in doing so were in untangling the efforts made to compress the game to fit in the limitations of computers of the time, which include using separate character models for ''individual frames of animation'' to reduce the amount of model data needed in memory at a time, making remastering the character models more difficult than if a single model were used per character. |
| 93 | * The partnership between Silicon Knights and Crystal Dynamics (with Creator/{{Activision}} involved on Crystal Dynamics' side) on the development of ''[[VideoGame/LegacyOfKain Blood Omen: Legacy of Kain]]'' and a proposed, canceled sequel degenerated into a pileup of legal screwovers and ExecutiveMeddling on ownership and content of the IP -- with Crystal Dynamics winning and bridges burned. [[https://web.archive.org/web/20121216013606/http://www.gog.com/forum/general/release_legacy_of_kain_blood_omen_2/post24 Because of this, don't expect]] [[ScrewedByTheLawyers to see a re-release]] of the first ''Blood Omen'' in the near future, although it ''is'' available on the [=PlayStation=] Store as a download for Platform/PlayStation3 and Platform/PlayStationPortable. A port of the PC version would finally arrive on GOG in 2021, though. |
| 94 | * ''VideoGame/BodyHarvest'' was originally slated to be a launch title for the Platform/Nintendo64. However, during development, publisher Nintendo took issue with the game's violent themes and thus dropped out of the project altogether. The game was presumed vaporware until Creator/GremlinInteractive and Midway Games picked it up and released it in October 1998... more than two years after it was originally slated to be released! According to Rusel [=DeMaria=]'s video game history book, the real reason ''Body Harvest'' fell through was because of DMA Design's and Nintendo's different ideas (DMA's free-form/mission play similar to ''GTA'' vs. role-playing elements that Nintendo wanted), and the game ended up being not as great as could have been after Nintendo didn't decide to publish it. |
| 95 | * ''[[VideoGame/{{Bubsy}} Bubsy 3D]]''[='=]s status as one of the most infamous video games of all time was a result of its terrible production. After the release of ''Bubsy 2'' almost killed the franchise, lead designer Michael Berlyn wanted to take the series in a new direction by taking the titular bobcat to [[VideoGame3DLeap the third dimension]]. The development was a challenge due to Berlyn and Eidetic's inexperience with the software required for 3D environments. After the release of ''Videogame/SuperMario64'', Berlyn became worried. Thinking that the game would be outshined by Mario, Berlyn and Eidetic tried making the game more complex, but due to the deadline getting closer, it was already too late. When the game came out, it was indeed outdone by not only Mario, but also newcomer ''[[VideoGame/CrashBandicoot1996 Crash Bandicoot]]'' released on [[Platform/PlayStation the same console]]. The ''Bubsy'' franchise laid dormant for twenty years (with a Platform/SegaSaturn port scrapped), until a new team released ''Bubsy: The Woolies Strike Back'' for the [=PS4=] and PC in 2017. |
| 96 | * ''VideoGame/TheBureauXCOMDeclassified'', as chronicled in the ''Polygon'' article [[http://www.polygon.com/features/2013/8/19/4614410/xcom-the-bureau-development-2006-2013 "The Many Faces of The Bureau"]], spent seven years in DevelopmentHell and faced long periods of uncertainty, not helped by constant criticism and bad PR: |
| 97 | ** During 2005-06, Take-Two Interactive bought up a number of developers and rebranded them as a singular entity called 2K Games. Take-Two bought the rights to the X-COM franchise from Atari and planned to kick things into high gear with a new installment of the franchise. Irrational Games was renamed "2K Boston" and, together with another Irrational regional studio renamed "2K Australia", began to draw up concepts for a new game. However, none of the concepts got past the drawing board with the exception of a multiplayer prototype (which was later scrapped). |
| 98 | ** After the success of ''VideoGame/{{BioShock|1}}'', 2K Boston gave up interest on the proposed ''X-COM'' title and development became a joint venture between 2K Australia and 2K Marin in California. After ''VideoGame/BioShock2'' (which had been farmed out to 2K Marin) shipped in 2010, the two studios still hadn't come up with a workable pitch for the next ''X-COM'', but they were helped by 2K Australia creative director Jonathan Pelling, who got some traction with a pitch titled "X-COM: Enemy Unknown" (after the international name for the very first game in the series) that was intended to take place in the 1950s. 2K decided to rush into production and use the Marin staff as support so the game could be finished and ready for release by 2011. |
| 99 | ** What followed was a communication breakdown between Marin and Australia. The Marin team was already divided into teams working on DLC for ''[=BioShock=] 2'' and development of a new IP in addition to the ''X-COM'' project, while 2K Australia was working on the single-player campaign while Marin worked on the multiplayer component. The two studios were merged into a single unit (as Marin) and the game was officially announced (as "''XCOM''" without the hyphen), but this didn't ease tensions between the two studios. |
| 100 | ** Once it became clear that the game wouldn't meet its original ship date, the multiplayer component was scrapped yet again and the teams were forced to rush to get a prototype ready for E3 2010. The Marin team took the lead on development of the single-player campaign, but the directives from the Australia branch were confusing and vague. The teams attempted to work out their differences by swapping small groups of programmers between the studios, but many staff quit in response. |
| 101 | ** A hastily thrown-together vertical slice [[https://www.youtube.com/watch?v=JdVb4UnqO7A shown at E3 2010]] was met with mixed reactions from the press. In the months after, several high-profile employees departed the studio and the project was rebooted. Firaxis had also begun work on what would eventually become ''VideoGame/XCOMEnemyUnknown'', which was more traditional and grounded in the franchise's strategy roots. |
| 102 | ** The Marin team dropped development of their new IP and continued tossing out more pitches and ideas for ''XCOM'' while development continued. The game slowly morphed from a first-person shooter to a third-person tactical game, and Marin took over lead development duties. It was given another ship date -- March 6, 2012, the date that ''VideoGame/MassEffect3'' was set to launch. The Marin team continued to rework the game and had voice actors come in to record lines (only to re-record it a year later with new actors). In October 2011, the main branch of 2K (reeling from the long development cycles being taken for ''XCOM'' and ''VideoGame/BioshockInfinite'') pulled 2K Australia from the project and instituted a mandatory "crunch" development period for the Marin team. This caused morale to drop and the March 6 release date to be scrapped. |
| 103 | ** 2012 saw more setbacks for the team, including the departure of creative director Jordan Thomas (to work on ''Infinite''), the official announcement of ''Enemy Unknown'' (which received far more praise) and screens from the game that leaked online. However, the Marin team pulled together under the direction of design director Zak [=McClendon=] and started including classic enemies from the earlier games after the critical success of ''Enemy Unknown'' (and after 2K had previously told the team not to use said enemies like the Sectoids). It finally hit its development deadlines and was rebranded as ''The Bureau: XCOM Declassified'' before being released in August 2013. |
| 104 | [[/folder]] |
| 105 | |
| 106 | [[folder:C-E]] |
| 107 | * ''VideoGame/CallOfDuty'' |
| 108 | ** The development of ''VideoGame/CallOfDuty Finest Hour'' proved to be problematic [[https://www.gamasutra.com/view/feature/130125/call_of_duty_the_lawsuit.php?page=1 on multiple fronts]]: Even before production started, developer Spark Unlimited became embroilled in a nasty lawsuit with Creator/ElectronicArts: the company's founders had worked on the ''VideoGame/MedalOfHonor'' series and poached many of the staff behind ''VideoGame/MedalOfHonorFrontline'', causing EA to retaliate by accusing (not baselessly) the exilees of having stolen resources and helped Spark Unlimited on company time. The development itself also had its share of troubles: despite Creator/{{Activision}} insisting otherwise, the developers decided to use Renderware for the game, which caused many problems down the line as it was incompatible with Spark's custom object database, becoming increasingly slow and crash-prone as development progressed. A poor tool chain made it difficult to troubleshoot bugs. Spark Unlimited's game development philosophy was also at odd with Activision: while EA's philosophy was to focus on making the levels and focus on technological polish at the end of development, Activision expected a polished core game far earlier. As the developers missed every milestone and went greatly overbudget, Activision salvaged the game by lending a large team of internal engineers to assist development and outsource large chunks of the game and development of the Xbox and Gamecube versions. While ''Finest Hour'' ended up being a financial success, lack of faith in Spark's management and an underwhelming pitch for a sequel caused Activision to end their contract with Spark Unlimited, spawning ''another'' lawsuit as Spark felt the company was trying to weasel out of the agreed royalties. |
| 109 | ** During the development of ''[[VideoGame/CallOfDutyModernWarfare3 Modern Warfare 3]]'', the long-brewing conflict between publisher Activision and lead elements of studio Infinity Ward finally came to a head[[note]]Infinity Ward wasn't happy with Activision assigning Treyarch as a B-team to develop mainline games in the series, sneaking in a TakeThat at Treyarch's ''Call of Duty 3'' in the end credits of ''4''. Rumors also flew around that Infinity Ward wanted to move on to an original IP after the success of ''4'' but was pressured to make more ''Modern Warfare'' games instead[[/note]]. Activision fired the Infinity Ward's studio heads Jason West and Vince Zampella over royalties involving ''Modern Warfare 2'' and allegations that West and Zampella were communicating with rival publisher Electronic Arts in a plan to jump ship. In response, a large portion of Infinity Ward's staff ended up leaving or being forced out, forcing Activision to bring in Sledgehammer Games to finish development of the title. Infamously, one of the disgruntled employees leaked the complete plot of the single player campaign almost a year before release, which was widely published by the gaming press. West, Zampella and several departed Infinity Ward staff would then form the studio Respawn Entertainment, which would later be acquired by Electronic Arts, and a lawsuit over the royalties was [[https://venturebeat.com/games/activision-settles-lawsuit-with-former-infinity-ward-heads-west-and-zampella/ settled just before going to court.]]. |
| 110 | ** ''VideoGame/CallOfDutyBlackOpsColdWar'' experienced a rough development with studio turnover and bad timing. Originally the game was to be co-developed by Raven Software and Sledgehammer Games with a 3 year development period aiming for a 2020 release. However, Sledgehammer Games co-founders Michael Condrey and Glen Schofield left the company in early 2018, leading to the studio hemorrhaging employees. A 2019 [[https://kotaku.com/sources-call-of-duty-2020-in-upheaval-as-treyarch-take-1834858368 Kotaku article]] then revealed that Treyarch studios replaced Sledgehammer owing to the studio's tensions with Raven. The game also had the unfortunate luck of coinciding with the [[UsefulNotes/COVID19Pandemic Coronavirus pandemic]] lockdown orders and the launch of [[MediaNotes/TheNinthGenerationOfConsoleVideoGames the Ninth Console Generation]], forcing developers to port to multiple platforms with fewer resources available. On top of all that, Raven and Treyarch had to make their title share gameplay progression with the standalone Battle Royale game ''Warzone'' even though that game was built on a different engine. The rough development cycle also adversely affected the marketing with the traditional Spring reveal trailer being delayed to ''August''. When the game was released in November 2020, the final product showed signs of corners being cut as it had numerous bugs and having only 8 launch maps compared to the standard 12+ in previous titles. |
| 111 | ** Just like its previous namesake, ''VideoGame/CallOfDutyModernWarfareIII'' faced a hectic production. Originally conceived as an expansion for ''VideoGame/CallOfDutyModernWarfareII'' by Sledgehammer Games, due to another ''Call of Duty'' game in development being delayed, the team were forced by Activision to instead retool the game to make it a full-fledged sequel in just a year and a half in time to meet the franchise's yearly quota, which was half the time it took to make a regular ''Call of Duty'' game. Crunch time was apparent, with many employees working nights and weekends just to get the game out on time. But the game's single player campaign suffered the most; the original plot was thrown out and retooled tremendously, and the resulting story campaign was met with negative reviews by critics and fans for its short length, Open Combat Missions that recycled maps from ''Warzone'', and overuse of cutscenes. |
| 112 | * Shortly after the release of the critically disappointing ''VideoGame/CastlevaniaLordsOfShadow2'' in 2014, several anonymous sources came forward to shed light on the game's troubled production. Said sources ended up being from various employees of the game's developer, [=MercurySteam=], claiming that development on the game had been a "degree of 'hell'". |
| 113 | ** Most of the blame was placed on [=MercurySteam=]'s leader, Enric Álvarez. Outside of his seemingly friendly demeanor in the public media, in actuality [[SmallNameBigEgo his ego had grown]] since the success of the first ''VideoGame/CastlevaniaLordsOfShadow'', and he completely undermined and overlooked his programmers, designers and artists, running development based on his own personal criteria. As such, employees were often forced to include game features and mechanics into the final game that they didn't even like (such as the stealth sequences). |
| 114 | ** There was also a great degree of distrust between him and his employees, with the communication so poor that they were only informed about the game's features not from Álvarez himself, but rather from ''the press''. This treatment was the final straw for José Luis Vaello, the Art Director for the first game, who ended up leaving [=MercurySteam=] to join another developer. Once work on the game had finished, [=MercurySteam=] laid off over 35 people- and more were to be expected. |
| 115 | ** [=MercurySteam=]'s primary game engine was coded by only two people, and since Álvarez was prone to hovering over and monitoring his employees, killing ideas that he didn't like left and right, it was never updated, reducing the development down to a very sluggish pace. In response to the game's poor reception, Álvarez [[ArtistDisillusionment claimed that the reviewer's gripes had no merits and that they weren't doing their jobs properly]]. Additionally, he seemed to deny the complaints of his employees, [[https://mobile.twitter.com/Enric_Alvarez/status/439658992621875200 as a post on his Twitter page showed]]. |
| 116 | * The Kickstarter-funded, motion-controlled sword-fighting game ''Clang'', developed by Subutai Production and sci-fi author Creator/NealStephenson, received over $500,000 in donations. Then Subutai revealed that they had exhausted ''all'' of it when searching for publishers, none of which showed interest. Livid campaign backers were refunded two years later. Stephenson discussed ''Clang''[='=]s cancellation [[https://www.kickstarter.com/projects/260688528/clang/posts/989911 here]]. |
| 117 | * Another Kickstarter failure: ''Code Hero'', [[GameWithinaGame a game coined as being able to teach players how to make games]]. It nearly doubled its $100,000 goal in January 2012. Developer Primer Labs missed two release deadlines and barely updated their website. Cue complaints from campaign backers over never receiving their rewards. Designer Alex Peake [[http://www.ign.com/articles/2012/12/14/code-hero-dev-responds-to-kickstarter-complaints quelled those threatening legal action]], but it was revealed that the $100,000 had only covered game costs up to October; afterwards, most of the developers had become ''volunteers''. Since 2012, Primer Labs' Facebook and Twitter pages are inactive. |
| 118 | * ''VideoGame/ColossalKaijuCombat'' was a 2015 Kickstarter funded game by Sunstone Games that was meant to be a large, ambitious fighting game where players could fight using their own, backer-created Kaiju monsters with the playstyle of the Pipeworks Franchise/{{Godzilla}} fighting games. The project reached its goal and nothing came of it. Some backers were already suspicious of the game, since it showed no original gameplay footage. On November 23, 2016, the project's development was revealed to be suspended indefinitely (game development purgatory) thanks to [[DiedDuringProduction the unexpected death of Sunstone's environment artist, Ron Clayborn]], which halted production on the game. Without an environment artist, game developers can't work on a game, [[{{Vaporware}} and thus the game was never released]], much to the dismay of the backers. |
| 119 | * In 2019, ''VideoGame/CookingMama: Cookstar'' was revealed for the Nintendo Switch, released in March 2020 and immediately delisted from the Nintendo [=eShop=] and recalled from stores. Speculation and rumors ran rampant until ''Cooking Mama'' creators Office Create came forward with the full story. The property was licensed out to another publisher (Planet Entertainment) and developer (1st Playable Productions), but when the developers were asked to fix ''Cookstar'''s problems after a poor gameplay demonstration, Planet not only released the game anyway (breaching their contract), but also commissioned and promoted a [=PlayStation=] 4 port of ''Cookstar'' (also without Office Create's authorization). As for the game itself, the release was an ObviousBeta plagued by awful motion controls, [[ItsEasySoItSucks repetitive and unchallenging gameplay]] and an inferior depiction of the Mama. On top of all that, the game was so badly optimized that it caused players' Nintendo Switch consoles to overheat, which spawned rumors that it had a Bitcoin miner embedded (spurred by an odd claim in an PR release that the game would leverage cryptocurrency, which turned out to be meaningless buzzwords meant to entice investors). In the end, Office Create [[CreatorBacklash profusely apologized]] for the game, removed the game from digital storefronts, and sued Planet Entertainment over the whole debacle. The courts ruled in favor of Office Create, and in November 2022, ''Cookstar'', which by that point was completely [[OvershadowedByControversy defined by the controversy surrounding it and had cast a heavy shadow over the franchise itself]], was withdrawn from circulation from physical and digital storefronts for good. |
| 120 | * ''VideoGame/CounterStrike: Condition Zero'' was passed between multiple developers, had its development restarted several times and suffered from chronic ScheduleSlip. |
| 121 | ** The concept of the game was born when Rogue Entertainment, who was out of work and in financial trouble after EA canned their Playstation 2 port of ''VideoGame/AmericanMcGeesAlice'', was contacted by Valve CEO Gabe Newell, who pitched the idea of a single-player focused game using the gameplay of Counter-Strike. Both parties reached an agreement for the game to start production in April 2001. Rogue quickly went into crunch to have material presentable in time for E3 2001 but one month after development started, Lead Producer Jim Molinets unexpectedly left Rogue. While Rogue insisted that his departure would not impact the project, Valve felt "betrayed" and had serious doubts over Rogue's stability, pulling the plug in May 2001. This served to accelerate Rogue's collapse and left Rogue employees infuriated by the sudden cancellation. Employees wasted little time [[https://www.shacknews.com/article/14041/more-on-rogue-valve-fallout leaking details]] of the negotiations as well as a number of early screenshots of the game. Rogue would be acquired by United Developers later in the year. |
| 122 | ** After pulling the game away from Rogue, Creator/GearboxSoftware reached an agreement with Valve, following their work on the ''VideoGame/HalfLife'' expansions, to pick up development of ''Condition Zero''. As development entered 2002, Gearbox and Valve butted heads over the direction of the project - Gearbox had created an arcade-style campaign of mostly disconnected levels and challenges while Valve wanted a connected, story-driven campaign akin to ''Half-Life'', forcing Gearbox to toss out a good deal of work while direction shifted. Work continued with this new direction well into 2002, but with Gearbox lacking enthusiasm for the project and the company also working on PC ports of ''VideoGame/{{Nightfire}}'' and ''VideoGame/HaloCombatEvolved'', Gearbox pulled out of ''Condition Zero'' by July 2002. |
| 123 | ** The game then fell into the hands of Ritual Entertainment, who (like Rogue) had been out of work after a cancelled port from EA and needed a project. Ritual also agreed to produce an Xbox port of the original ''Counter-Strike''. But in June 2003 Ritual ran into financial troubles after finishing ''VideoGame/StarTrekEliteForce II'' and were forced to lay off members of the ''Condition Zero'' team. While Ritual completed development of ''Condition Zero'', Valve was deeply unhappy about the quality of the game and a handful of outlets who received review copies were unkind in their reviews. Valve retracted the game's immediate release and - without informing Ritual - assigned Turtle Rock Studios to finish ''Condition Zero'', scrapping Ritual's single-player in favor of skirmishes against bots. Ritual's Xbox port was released in November 2003 to positive reviews, but ''Condition Zero'' released in March 2004 to mediocre reviews that considered the game outdated as ''VideoGame/HalfLife2'' and ''Counter-Strike Source'' were mere months away from their own release. Ritual's single-player portion of the game would be included as ''Deleted Scenes''. |
| 124 | * ''VideoGame/CrashTwinsanity'' suffered through this. Deadlines not being met, scrapped concepts, the pressure of Universal needing the game out, and too many ambitious ideas led to about a third of the game's original ideas being cut. The final product, while still regarded as a good game, shows the lamented development cycle in many areas. However, the dev team have been kind enough over the years to explain and show off various parts of the game that got cut, even supplying cut voiced dialogue and storyboards, all of which can be found online. |
| 125 | * Given the wildly ambitious scope of the project, it probably should come as no surprise that ''VideoGame/{{Cuphead}}'' went through this. A run 'n' gun game that painstakingly reproduced the art, animation, and sound of 1930s cartoons by [[Creator/MaxAndDaveFleischer Fleischer Bros.]] and similar animation companies, while also packing over three dozen varied boss battles; produced by a small indie studio of very limited staff on hand. As one would expect, it took a long and hard 7 years before the game became what it is today, and the development cost was so big that the Moldenhauer brothers, the game's creators, had to ''mortgage their house'' to get through it. It worked though -- the game sold over a million copies in two weeks, and received tons of acclaim and a handful of awards for its presentation. |
| 126 | * ''VideoGame/Cyberpunk2077'' was one of the most hyped video games of all time. Upon its release, however, it became notorious for being an ObviousBeta on next-gen platforms and the catastrophic PortingDisaster it received on Platform/PlayStation4 and Platform/XboxOne. [[https://www.nytimes.com/2020/12/19/style/cyberpunk-2077-video-game-disaster.html This article]] by Mike Isaac and Kellen Browning for ''The New York Times'', along with [[https://www.bloomberg.com/news/articles/2021-01-16/cyberpunk-2077-what-caused-the-video-game-s-disastrous-rollout Jason Schreier's investigation]] for ''Bloomberg'', tells a grim tale of [[Creator/CDProjekt CD Projekt RED]]'s unchecked ambition and severe mismanagement resulting in a BrokenPedestal moment for what had previously been one of gaming’s most beloved companies. |
| 127 | ** CD Projekt RED, hot off the success of 2011's ''VideoGame/TheWitcher2AssassinsOfKings'', announced an adaptation of the tabletop game ''TabletopGame/{{Cyberpunk}}'' the following year, but production didn't really get rolling until the blockbuster success of 2015's ''VideoGame/TheWitcher3WildHunt'' propelled the Warsaw-based studio to triple-A developer and publisher thanks to their ownership of the digital games store GOG. That success and their pro-consumer policies dramatically increased the hype around ''Cyberpunk'', as fans of the ''Witcher'' games expected it to be a larger and deeper role-playing experience than any of the ''Witcher'' games had been. |
| 128 | ** While a small team had been quietly working on base concepts for the game during the development of ''Wild Hunt'', the completion of that game’s final downloadable expansion saw the ''Wild Hunt'' team joining up with the ''Cyberpunk'' team… and immediately clashing with them. The veterans behind the ''Witcher'' titles had very different ideas for what ''Cyberpunk'' should be, and disliked that ''Cyberpunk'''s gameplay was similar to ''Wild Hunt''. The clashes led to studio head Adam Badowski taking over the project and several lead developers walking away from the company, as development was effectively rebooted. |
| 129 | ** CD Projekt was keen on exceeding expectations. The first gameplay reveal at E3 2018 showed a vast array of role-playing options, a massive and deep world, and advanced graphics, all of which appeared to eclipse that of ''Wild Hunt''. While the presentation drew wide praise, the entirety of the presentation had been created specifically for E3 and had no basis in the game’s actual progress, taking vital months away from development and setting unrealistic expectations. The hype machine shifted into overdrive in 2019 at the announcement that Creator/KeanuReeves, riding high on a CareerResurrection from the ''Franchise/JohnWick'' films, would be providing the [[InkSuitActor likeness and voice]] of major supporting character Johnny Silverhand. Reeves was also present to announce the game’s release date of April 2020. |
| 130 | ** Back in Warsaw, however, employees at CD Projekt RED were quietly panicking over the 2020 release frame. They saw obvious signs of feature creep as the studio's management had made increasingly grandiose promises they had no way of meeting with the timeframe they were given, with one manager dismissing concerns with "We'll figure it out along the way". The release date of 2020 was at least in part from hoping to “double dip” consumers by getting the game out before next-generation consoles released, then forcing consumers to buy the game again on the latest hardware. |
| 131 | ** Despite having increased the size of the team to over 500 people for the game, they were still considered grossly understaffed, and the company's inexperience with handling a large team further impacted work. There were also troubles between the native Polish employees and foreign expats brought in for work, with the expats frequently feeling disrespected (for example, Polish developers would suddenly start speaking Polish amongst them during meetings with non-Polish speaking expats present, despite company policy to hold all meetings in English). Against the backdrop of these troubles, management forced [[https://www.bloomberg.com/news/articles/2020-09-29/cyberpunk-2077-publisher-orders-6-day-weeks-ahead-of-game-debut a long period of brutal crunch time]] in order to get the game finished by its planned April 2020 release date, despite having [[LyingCreator publicly promised that no crunch would happen]]. This lead to numerous departures from longtime engineering staff due to overwork, as well as backlash when the crunch conditions were made public. |
| 132 | ** As 2019 ended, management realized that there was no possible way the game would be ready in time even as the team cut content, and in January 2020, with just three months before release, they announced that they were pushing it back to September. In June, they pushed it back to November as the UsefulNotes/COVID19Pandemic severely impacted communication and workrate, and in October, after the game had been announced as having "gone gold", they pushed it back ''again'' to December as the team scrambled to fix severe bugs. By this point, next-generation consoles had already hit stores, scuttling the "double dip" plans -- which would likely have been torpedoed anyway by the fact that the next-gen consoles turned out to be fully back-compatible with their predecessors, most publishers made next-gen versions of their games available for free, and the few that ''did'' charge extra for next-gen upgrades were almost invariably met with heavy backlash -- and splitting the team's efforts between the new consoles and the prior generation. |
| 133 | ** Meanwhile, [=QuanticLab=], the Romanian QA company that CDPR contracted to play-test the game, was botching things on their end, too, at least according to [[https://www.youtube.com/watch?v=FEarLGfqhvo documents leaked]] by a whistleblower to the [=YouTube=] channel Upper Echelon Gamers. According to the allegations, [=QuanticLab=] flat-out lied to CDPR about the size and experience of the team, claiming to have far more testers than they actually had and that senior staff would be working on testing. Furthermore, they pushed testers to meet a daily quota of bugs discovered, which had the effect of causing CDPR to be inundated with reports of minor, comparatively irrelevant issues that distracted them from working on the serious [[GameBreakingBug Game-Breaking Bugs]]. |
| 134 | ** Despite the hype, the reveal of crunch conditions and the constant delays served as red flags as they went directly against many PR statements made by CDPR. More red flags raised in the immediate lead-up to release, as [[https://www.polygon.com/2020/12/4/22058784/cyberpunk-2077-marketing-cd-projekt-red-transphobia LGBTQI+ groups took exception]] to the game’s treatment of trans characters, and the release build [[https://www.gameinformer.com/2020/12/07/cyberpunk-2077-epileptic-psa contained sequences that consistently caused seizures]]. It was known within the studio that, while the PC, Platform/PlayStation5 and Platform/XboxSeriesXAndS versions were buggy but functional, the [=PS4=] and Xbox One versions were nearly unplayable. The game would be shipping regardless. CD Projekt RED only allowed reviewers to play the PC version in controlled conditions to mitigate the issues. |
| 135 | ** While many of the initial reviews were positive, console gamers, the vast majority of whom were using the [=PS4=] and Xbox One due to supply shortages of next-gen consoles, were in for an unpleasant shock when they got a nigh-unplayable version of the game. Overnight, social media was flooded with reports and [[MemeticMutation memes]] about the slew of bugs, performance issues, and rampant crashing. While much of the negativity was directed at the game’s technical state, the more critical console reviews also targeted the gameplay and story, which, while generally considered solid, wasn’t as ambitious as the marketing promised, as well as the obvious signs of cut content. |
| 136 | ** The backlash was so overwhelming that Sony [[https://www.playstation.com/en-us/cyberpunk-2077-refunds/ ripped the game down from its digital store]] and began offering refunds. Microsoft and CD Projekt RED themselves also began offering refunds soon after, and employees at CD Projekt RED [[https://www.bloomberg.com/news/articles/2020-12-18/cyberpunk-game-maker-faces-hostile-staff-after-failed-launch got into heated arguments with executives]] over the poor state of the game and the [[BrokenAesop hypocritical attitude toward the game’s anti-corporate and anti-capitalist themes]]. Two months after launch, [[https://www.theverge.com/2021/2/10/22276664/cyberpunk-witcher-hackers-auction-source-code-ransomware-attack CD Projekt RED was hit by a cyberattack]] that claimed to have stolen ''Cyberpunk'''s source code among others, which [[https://twitter.com/CyberpunkGame/status/1364607741680115717 delayed patches for the game]]. |
| 137 | * ''VideoGame/{{Daikatana}}'', as chronicled in [[http://replay.waybackmachine.org/20000619155817/http://www.gamespot.com/features/btg-daikatana/index.html "Knee Deep in a Dream"]]. |
| 138 | ** Despite the success he'd enjoyed with ''VideoGame/{{Doom}}'' and its progeny at id Software, John Romero was unhappy with his job because he felt his vision as a designer took a back seat to the company's technological considerations. When his idea to split the company into separate divisions devoted to design and technology was nixed by the founders, he threatened to leave and [[StartMyOwn start his own company instead]], and was eventually let go. |
| 139 | ** Carrying out his threat, he and id cofounder Tom Hall started what became Creator/IonStorm at the end of 1996, where "Design is Law." On the strength of their names and accomplishments, the company was able to raise millions. Some of this was spent on high-cost real estate, renting office space in the top floors of a Dallas skyscraper, featuring the Ion Storm logo carved into terrazzo in the lobby because, Romero said, he had always wanted to work in flashier offices at id. But all did not go well from that auspicious start. |
| 140 | ** Romero's dream game, ''Daikatana'', would be the sort of FirstPersonShooter he had pioneered, but with two sidekicks and multiple levels in four different time periods across a 4,000-year period. He told the media it would be available within a year, since the plan was to build it on the ''VideoGame/{{Quake}}'' engine. As you might expect, such an optimistic prospect was just asking for trouble. |
| 141 | ** First, Ion Storm had some internal warring because the ''Daikatana'' team felt the development of ''Dominion: Storm Over Gift 3'' was stealing resources and staff, which ultimately hurt that game and forced the abandonment of the other early titles Ion Storm meant to bring out. |
| 142 | ** Then, they tried to move from the old ''VideoGame/{{Quake}}'' engine to the ''VideoGame/QuakeII'' one, a process [[PortingDisaster much more complicated and time-consuming]] than they thought. In June of 1997, they made it official — ''Daikatana'' would not be shipping that year. That didn't stop the company from taking out ads that cheekily promised "[[PreAssKickingOneLiner John Romero's about to make you his bitch]]", alienating some gamers and ramping up expectations for others. Romero has since apologized for the campaign and tried to distance himself from it; others involved say he was much more enthusiastic at the time. |
| 143 | ** [[ThePeterPrinciple Romero's prowess as a designer and programmer, despite his experience at well-managed id, did not transfer to management or leadership skills]]. His development team quit on him en masse to start their own company because they were so fed up with the lack of direction they were getting. To maintain goodwill with potential competitors, Romero avoided hiring away any of their programmers, instead hiring amateur programmers whose homebrewed levels for id's games had been the most downloaded — a fact which, another Ion Storm executive admitted later, told them nothing about what it was like to work with this person or what their work habits were. During the development of the game, the staff changed completely three times. |
| 144 | ** This turnover had a chaotic impact on the game code, with fragments inserted here and there by different people who had never communicated. Demos made from this increasingly buggy mess failed to impress at industry events. Communications between all the people working on the game did not get any better: one artist submitted the infamous "1,300-pixel arrow", a texture file for a crossbow bolt that was inexplicably 1300 pixels by 960 pixels. [[note]] For reference, the most common resolution for gaming -- i.e. the resolution that the ''entire game'' output at -- at the time was 1024 by 768 pixels, something which would largely remain the case until the late 2000s.[[/note]] When Romero hired his then-girlfriend, Stevie Case, to work on level design, he nearly triggered another full-staff walkout. |
| 145 | ** The programmers who ''were'' working had some unexpected physical problems with the skyscraper office space. Some of them were under skylights where, around midday in the Texas sun, they would get too hot to work, and even if they didn't the light was too distracting. People were covering their cubicles in blankets to get their work done. |
| 146 | ** Ion Storm missed ''Daikatana''[='=]s 1997 ship date, and its 1998 ship date, and its 1999 ship date. It became a punchline within the industry, as [[Webcomic/PennyArcade one webcomic]] memorably demonstrated. Eidos, Ion Storm's parent company, finally had to step in and straighten things out. And as things were finally turning out, id released the ''Quake III'' game engine. Recalling how much fun they had had three years earlier upgrading to its predecessor, Ion Storm understandably opted ''not'' to do it again, meaning the game they had poured so much design effort into would be [[TechnologyMarchesOn technologically behind]] from the moment it was released. |
| 147 | ** The game ended up [[{{Vaporware}} delayed]] so much that, by the time it came out in 2000, it was seriously outclassed by competing games like ''VideoGame/HalfLife'', ''VideoGame/SystemShock2'', and the soon-to-be-released ''VideoGame/DeusEx''. The resulting product ended up being a complete bust and [[CreatorKiller ended the fame and career]] of Creator/JohnRomero, who, before ''Daikatana'', was a superstar developer on par with Creator/SidMeier and Creator/TimSchafer thanks to his work on ''VideoGame/{{Doom}}'' and ''VideoGame/{{Quake}}''. |
| 148 | * The cancelled Comicbook/{{Daredevil}} game owes its nonexistence to this trope, as [[https://www.youtube.com/watch?v=MF8AEtKXwEA this video]] would explain. In a nutshell... |
| 149 | ** 5,000 Ft, a game studio located in Reno, Nevada, wanted to [[StartMyOwn make a game of their own]] after assisting [[Creator/The3DOCompany 3DO]] with their ''VideoGame/ArmyMen'' series for the [[Platform/PlayStation PS1]]. After being bought by publisher Encore, Encore proceeded to buy out a few licenses to several Marvel products, such as ComicBook/CaptainAmerica, and of course, Daredevil. |
| 150 | ** 5,000 Ft thought of doing a Daredevil game for the [=PS2=] because of their interest in the character. They presented their ideas to Encore, which consisted of a linear third person brawler that was heavily tied into the comics. The game was meant to be a series of vignettes based around famous Daredevil stories as a way to celebrate the character’s legacy. After a week of creating a workable prototype for Encore, the game was greenlit for production under the name ''Daredevil''. [[Creator/MarvelComics Marvel]] themselves became heavily involved with the game’s development, at first being very easygoing with 5,000 Ft such as giving the writers full creative control over the story of the game. |
| 151 | ** Creator/SonyPictures then called upon former 5,000 Ft president, Tim Page, to inform him of the then upcoming Film/{{Daredevil}} movie. Because of this coincidence, Encore decided to port the game to PC and Xbox alongside its original [=PS2=] port. This forced both [[Creator/MicrosoftStudios Microsoft]] and Creator/{{Sony}} to watch over development of the game. |
| 152 | ** After meeting with Sony, 5,000 Ft was forced to increase the budget and scale of their game. The game became an open world action game that was meant to be a lot more combat focused. The game was then given a deadline: February 2003, around the time the movie came out. Microsoft, in contrast, was much more laid back in their approach to the game, allowing the developers to do whatever they wanted. Both cases of contradicting philosophies caused friction during development. |
| 153 | ** If that wasn’t bad enough, Marvel’s ideas for the game contrasted even more with Sony’s ideas. While Marvel wanted a game that was more faithful to the comic, Sony wanted a game that was more experimental. Marvel would constantly shoot down any ideas presented by Sony, such as a grinding mechanic [[FollowTheLeader inspired by]] the ''VideoGame/TonyHawksProSkater'' series. |
| 154 | ** The game had some conflicts with the engine. 5,000 Ft wanted to use the new Renderware engine, used in games such as ''VideoGame/GrandTheftAutoIII''. Encore, however, [[ExecutiveMeddling didn’t want to use it,]] not wanting to pay engine fees. 5,000 Ft ended up having to use the base of Renderware’s technology, and build upon it, creating their own engine in the process. |
| 155 | ** Due to the release of [[VideoGame/SpiderManTheMovie the first Spiderman Game]], 5,000 Ft not only wanted to [[FollowTheLeader copy that game]], but also outdo it, giving Daredevil a swinging mechanic that allowed his billy club to grapple onto buildings, loads of people for Daredevil to interact with, and a new, cutting edge mechanic called The Shadow World, which allowed the player to see the game from Daredevil’s perspective (the precursor to [[VideoGame/BatmanArkhamSeries detective mode]]). |
| 156 | ** At this point, the game grew into a giant, bloated mess that ended up causing problems for 5,000 Ft’s development team. Tensions started rising up, with multiple developers and staff members, including one of their most skilled engineers, leaving. Their replacements ended up being nowhere near as talented. What’s worse, drug problems ran rampant among the staff. Multiple developers started showing up to work intoxicated, with one of the engineers doing drugs during his lunch break. 5,000 Ft then attempted to make Encore give them full creative control over the final product, which resulted in the studio dividing itself due to several staff members’ growing ambitions and conflicting ideas. |
| 157 | ** By now, the engine had started taking its toll, struggling to handle the game’s graphical fidelity and scope, which ended up causing a weak framerate. After multiple edits and cuts of certain levels, 5,000 Ft decided to cut the game’s overworld entirely, turning the game into [[ResetButton a linear third person brawler]] that had almost none of the features 5,000 Ft had promised. The new linear and tight level design caused the aforementioned grappling and Shadow World mechanics to become useless. |
| 158 | ** Because of the engine’s limitations and the upcoming deadline getting closer and closer, 5,000 Ft had to rely on help from many different studios such as Creator/ElectronicArts in order to get the engine working properly. By now, the game had missed its February 2003 deadline, resulting in the game getting pushed to the summer. |
| 159 | ** The game, now going under ''Daredevil: The Man Without Fear'', was now almost fully complete, with a new story and overworld created. Unfortunately, during 5,000 Ft’s now six month development time, a large chunk of the staff left, resulting in control of the project being given towards their hired consultants, who ended up cancelling production of the game because of Marvel’s refusal to release it. |
| 160 | ** In the end, ''Daredevil: The Man Without Fear'' was shelved thanks to 5,000 Ft leaning more closely with Sony’s ideas rather than Marvel’s, who pulled the license from 5,000 Ft. An attempt to make another IP using the same engine and mechanics ended up not happening. 5,000 Ft sunk into third party obscurity until [[CreatorKiller their demise in 2012.]] |
| 161 | * ''VideoGame/DarkSoulsII'' suffered through a large bit of behind-the-scenes trouble, as detailed in an [[http://peterbarnard1984.tumblr.com/post/113163062955/dark-souls-2-design-works-translation interview with director Yu Tanimura]], explaining why the final game is significantly different from the first ''Dark Souls''. The original director was kicked off the project for as-yet undisclosed reasons halfway through development, and the game was essentially restarted from scratch with a hard deadline to ship the game. The new director had to salvage what he could and re-purpose it into what became the final product, meaning that large numbers of areas (most notably a transition between Earthen Peak and Iron Keep) and the ''entire original plot'' had to be scrapped. It didn't help either that their planned graphical upgrade to the engine failed when they discovered that the [=PS3=] and Xbox versions could only run the game in ''single-digit'' FPS, forcing them to drastically downgrade the graphics to make it playable. While still a very good game, it definitely bears the scars of its turbulent development, and is usually [[ContestedSequel considered weaker]] than the other ''Souls'' games by many fans for that reason. |
| 162 | * ''The Day Before'' was originally announced in 2021 as a new, open-world ZombieApocalypse survival MMO by Russian game studio Fntastic, quickly becoming a hotly-anticipated title (becoming the most wishlisted game on Steam almost immediately following its announcement), but ended up experiencing a multitude of behind-the-scenes troubles and scuffles with the public that resulted in a cataclysmic launch: |
| 163 | ** Following a steady release of various gameplay trailers throughout 2021, Fntastic set up a release date of June 2022. However, just a month shy of the date, it was announced that [[ReleaseDateChange the game would be delayed to March 2023]] in order to upgrade its engine from Unreal Engine 4 to 5, ostensibly to boost its open world technology. This sudden announcement provoked disappointment as well as suspicion as such a fundamental shift in development isn't at all normal for a project of ''The Day Before'''s scope, ambition, and schedule, and this would be the first of several incidents that left many questioning the game's integrity. |
| 164 | ** Fntastic received further heat in June 2022 when it was reported that the game was being developed almost entirely by unpaid workers, something that the company ended up confirming and defending in a public statement on grounds that ''all'' their employees were "volunteers", believing that it wasn't necessary to pay them as part of their "volunteer culture". Not only did this draw immense scrutiny for being worker exploitation, this raised even more suspicion as to whether or not Fntastic could even afford to develop the game, especially concerning for something as expensive and requiring maintenance as an MMO. |
| 165 | ** Early 2023 saw Fntastic enter a trademark dispute over the title ''The Day Before'' (from a holder in Korea with trademark rights in regions including the US, EU, and Russia), resulting in the game's Steam page being briefly taken down, along with an announcement of [[ReleaseDateChange another delay]], this time to November 2023. However, Fntastic [[https://www.ign.com/articles/the-day-before-devs-say-delay-was-planned-before-trademark-dispute would end up relaying in a statement to IGN]] that this most recent ReleaseDateChange was planned even without this legal dispute, provoking even more fan revolt, with many accusing Fntastic of lying about progress of their development and calling the game a scam. |
| 166 | ** Facing increasing public controversy, Fntastic began making public pledges to be more transparent about the game's progress and to combat disinformation of the game being a scam, including a public commitment that the November 2023 release date would be set and final. However, with this came with a further revelation that they had no marketing team and that all their resources went into game development (lightly muddied by their earlier confirmation that their workers were unpaid volunteers), provoking further concerns that them acting on damage control was only stretching progress even further. [[DiggingYourselfDeeper Not helping matters]] was how the game did end up experiencing yet more last-minute delays, this time with the PC version launching on December 2023, and only in Early Access. Meanwhile, the expected console releases on the [=PlayStation=] 5 and Xbox Series X and S were delayed indefinitely. |
| 167 | ** The Early Access launch date finally arrived, only for it to be met with a disastrous response as it was discovered that [[NeverTrustATrailer virtually nothing about the game was as advertised]] -- instead of an open-world zombie MMO, ''The Day Before'' was effectively a half-baked [[LooterShooter extraction shooter]] with almost no zombies in it whatsoever, filled with AI-generated art and stock assets (the entire city environment turning out to be an Unreal store asset), [[ObviousBeta as well as server instability and many, many bugs]]. The overwhelming backlash -- from social media, to Steam reviews (the game quickly becoming one of the worst-reviewed games on the platform), to the game's own official Discord server (which quickly became locked from complaints of angry customers demanding refunds) -- led to Fntastic announcing a mere four days later that both ''The Day Before'' [[CreatorKiller and the company as a whole were folding]] due to having "failed financially," with the game becoming delisted almost immediately. |
| 168 | * ''VideoGame/DeadIsland2'' was originally to be developed by Techland (who had worked on the previous installments), but they had a falling out with Deep Silver that led to them going independent and releasing a SpiritualSuccessor in the form of ''VideoGame/DyingLight'', so the game was handed over to Yager Studios (who had just finished ''VideoGame/SpecOpsTheLine''). A trailer was unveiled at E3 2014, with plans to release the game in 2015. However, relations between Deep Silver and Yager quickly broke down in the following year, and the game was transferred to Sumo Digital in 2016. After three more years, the game was transferred again to Dambuster Studios in 2019. Then it was finally unveiled again at Gamescom 2022 with a release date of February 3rd 2023, before getting one last delay to April of that year, and after [[SavedFromDevelopmentHell eleven grueling years]] the game would finally release to mixed-to-positive reception not unlike its predecessor. |
| 169 | * The iconic ''VideoGame/DeadOrAlive'' series might be dead in the water thanks to the troubled production of ''VideoGame/DeadOrAlive6'': |
| 170 | ** Coming off of the hight of ''VideoGame/DeadOrAlive5'', Yohei Shimbori, director for most of the series, started work on the next chapter of the franchise. He wanted to break away from ''[=DOA=]''[='s=] infamous reliance on sexy female fighters and make the next chapter more in line with other competitive fighting games. As well, the new engine being worked on would be used to give the characters a more realisitic stance with added damage, additions and physics. |
| 171 | ** June 2018 saw the release of the first teaser trailer for the game, showing off the new aspects. Fans, however, saw something different - the costuming and tone had decidedly changed. The trailer was designed to be more serious, reframe the DOA tournament as a serious martial arts tournament and mostly dumping the heavy sexual nature. Of note was the ''de facto'' main character Kasumi, who abandoned her iconic ''gi'' top and thigh-highs for a full leather black and blue outfit. |
| 172 | ** Later that same summer, another trailer showcasing two male characters was released and the creators began doing the interview scene. Shimbori explained that the game's change in tone was meant to help the franchise get into the emerging e-sports scene, something fighting games aren't really known for really taking off in. That meant the game's iconic sex appeal had to be deemphasized. Shimbori tried to walk this back during the Tokyo Game Show 2018, claiming that the trailers were only what they had to work with at the moment and they wanted to show off what the new engine could do. Despite this, many fans didn't buy it and continued to lambbast the game's more puritan nature, going so far as to note a Eurogamer interview done earlier, where Shimbori blamed the ''DOA Xtreme'' entries for its more sexual nature. |
| 173 | ** The game arrived on March 1, 2019 to a lukewarm reception - hardcore fighter players still saw the game's mechanics as simplistic even after the supposed changes while the hardcore fans of the franchise were slighted at the fact that the game's iconic skimpy outfits were shoved aside various lists to be grinded away while the more conservative outfits were front in center. |
| 174 | ** Worst of all were the game's more predatory purchases. Season Passes were nothing more than just character costumes going as high as over $90 and then there was the Platinum Passes, which were used for hair color changes. That was the last straw for gamers and Koei Tecmo as the Passes were done away with and support ended in April 2020, barely over a year after the game released. |
| 175 | * As [[https://www.youtube.com/watch?v=6glExmQadfY this video]] by Liam Robertson explains, the ''VideoGame/DeadRising'' series, from the third game onward, endured a series of these that eventually led to [[CreatorKiller the collapse of Capcom's Vancouver studio]] and [[FranchiseKiller the death of the series]]. |
| 176 | ** To start, after their successful work on ''VideoGame/DeadRising2'', Blue Castle Games was bought out by series publisher Creator/{{Capcom}} to become Capcom Vancouver. Unfortunately, around this time their original IP ''Brazil'', a survival game set in an alien-infested Rio de Janeiro, saw its own production fall apart after two years of work due to CreativeDifferences within the staff over fundamental gameplay elements, particularly the pacing. With production on ''Brazil'' going nowhere, Capcom shut it down in 2012 and put the studio to work on ''VideoGame/DeadRising3''. |
| 177 | ** ''Dead Rising 3'' was already suffering a troubled production when Capcom Vancouver was brought in, beset as it was by technical issues. The Platform/PlayStation3 version, owing to that console's infamously exotic and complex hardware, suffered the bulk of the problems, especially given the game's lofty WideOpenSandbox ambitions compared to its predecessors. As a result, when Microsoft showed up with an offer to make the game an Platform/XboxOne exclusive, Capcom jumped at the chance to cancel the troubled [=PS3=] version and focus their resources, especially with the added Microsoft money, more powerful hardware to work with, and another year to work on the game before the Xbox One launched. Unfortunately, this forced Capcom Vancouver to cancel ''another'' original IP, an open-world sci-fi action RPG called ''New Frontier'' that many people who worked on it described as a "proto-''VideoGame/{{Destiny}}''". |
| 178 | ** ''VideoGame/DeadRising4'''s mixed reception owes much to its troubled history, as [[https://www.youtube.com/watch?v=6FztJTSrqB8 recapped]] by WebVideo/MattMcMuscles. |
| 179 | *** Capcom Vancouver, disillusioned with the increasingly DenserAndWackier tone of the series and desperate to try something new, began work on a DarkerAndEdgier reboot inspired by ''VideoGame/TheLastOfUs'' codenamed "Climber", with Microsoft, eager to compete with Sony's KillerApp and now increasingly involved with the series, supporting the shift. They had not received permission from Capcom Japan for such a departure, as Capcom Japan trusted Vancouver enough to be able to produce a game without their constant oversight, but Vancouver expected Capcom Japan to be pleased when they presented their new direction. Instead, Capcom Japan's executives were reportedly ''furious'' at the changes, which they felt took away everything that made ''Dead Rising'' unique and made it into a cookie-cutter zombie horror game, and they fired the responsible devs (including several of the lead developers on ''Dead Rising 3'') and demanded the rest throw out their work to make a more traditional ''Dead Rising'' game. |
| 180 | *** With six months of work rendered useless, minimal budget, hemorrhaging of key developers, a general sense of aimlessness without them, [[ChristmasRushed fast-approaching deadlines from Microsoft]], and studio morale running low, the game's development cascaded into a disastrous crunch where many series mainstays (most infamously the time limit, MultipleEndings, and [[BossBattle psychopath battles]]) were cut, the [[PoweredArmor exosuit]] and [[EliteZombie evo zombies]] were added at Microsoft's insistence despite most of the developers hating them, and attempts to polish the gameplay, story, and technical aspects were constantly fought against because of internal conflicts or there simply being no time. About 40% of the Vancouver studio, including many series veterans, left during 2014, and many people who worked on the game said that [[ThisIsGonnaSuck they knew it was going to be bad]]. The game released in 2016 to mediocre reviews and disastrous sales that, in the long term, tanked both Capcom Vancouver and the series. |
| 181 | ** Before it dissolved, however, Capcom Vancouver was gearing up for ''Dead Rising 5'', which proved to be TheLastStraw for Capcom. |
| 182 | *** Seeking to get as far away from the horror-show experience of working on the fourth game as possible, the team for this title was composed entirely of fresh blood and led by a former Creator/CrystalDynamics executive, and it was to run on Unreal Engine 4 instead of Capcom's proprietary Forge engine. Unreal 4 was not particularly well-optimized for either large open worlds or the series' trademark hordes of hundreds of zombies on screen at once, which led to a focus on smaller semi-open environments like the first two games as well as battle with smaller numbers of tougher zombies. Its plot would have been an {{interquel}} set between the second and third games, with Chuck and Katey Greene from the second game as co-protagonists in a Mexican city searching for Zombrex medicine to suppress Katey's [[ZombieInfectee infection]], with the plot inspired by films like ''Film/{{Sicario}}''. |
| 183 | *** Even before the failure of ''Dead Rising 4'', however, the project was entering troubled waters in 2016 with a shift in design director, with the new one, who had previously worked on the ''Franchise/AssassinsCreed'' series, implementing a [[LeParkour parkour-inspired building climbing]] mechanic, changing up the combo weapon system, and trying to go back to the open-world design of the prior two games -- all decisions that divided the team. (On the parkour, some developers questioned why they were implementing a system that's all about ''avoiding'' zombies in a series dedicated to giving players creative ways to kill them.) Creative disputes led to firings of more key developers, [[HistoryRepeats just like]] on ''Dead Rising 4'', and the game underwent another creative shift to a semi-linear SoulsLikeRPG, a move that, just like the Climber build of ''Dead Rising 4'', was rejected by Capcom Japan in 2018 despite Sony showing interest, leading again to layoffs and a shift to a more traditional series style. |
| 184 | *** Six months after that, Capcom, fed up with spending time and money with little to show for it and feeling that the Vancouver studio had [[IgnoredAesop learned nothing]] from the problems that occurred making ''Dead Rising 4'', cut its losses and shut down the Vancouver studio, canceling ''Dead Rising 5'' with it. Many former employees describe it as a MercyKill given how dysfunctional the studio was. |
| 185 | * ''Descent to Undermountain'' was Creator/InterplayEntertainment's attempt to make a cheaply produced mega hit by quickly developing a game that utilized their ''TabletopGame/DungeonsAndDragons'' license and their newly developed fully 3D engine that was used in their extremely successful title, ''VideoGame/{{Descent}}''. However, Interplay's judgment was blinded by greed and they wanted to rush the game out quickly without taking into account what it would actually take to ship a game in their planned six month timeframe. This made the development cycle much more difficult than it should have been. |
| 186 | ** Instead of assigning a development studio to work on the game like usual, Interplay decided to set up an independent contracting program that would utilize Interplay's own employees as well as outside talent. This arrangement proved to be chaotic and the team never even had an assigned project manager. |
| 187 | ** The engine used for ''Descent'' proved to be ill suited for an RPG that involved melee combat. The giant collision meshes in particular proved very difficult to work with as they had to be downscaled significantly to better fit the gameplay requirements. |
| 188 | ** By December 1997, the game that was supposed to take six months of four developers' time had been three years in the making and gone six times over the budget. Despite being woefully unfinished, Interplay believed that they could still profit from the game if they released it before 1998 due to the immense hype surrounding it. As a result, the unfinished four player multiplayer was left out of the game and the game itself would release in an ObviousBeta state. |
| 189 | ** The game's release was followed by an immense HypeBacklash, Creator/ChrisAvellone who worked on the project [[OldShame still regrets his involvement in it]], and its failure also played a role in driving Interplay's finances to the point that it was in bankruptcy court in 1998. The game would be mostly forgotten by the turn of the millennium and is nowadays mostly remembered from an EasterEgg in ''VideoGame/Fallout2'', where [[CreatorBacklash Interplay themselves admit that the game was crap]]. |
| 190 | * ''VideoGame/DeusEx'' was Creator/IonStorm's big success story but it wasn't less troubled for it, with lead director Warren Spector giving a detailed post-mortem in the November 2000 issue of ''Game Developer Magazine'' about the challenges and mistakes of its production. |
| 191 | ** Warren Spector struggled for years to get the concept (initially titled ''Troubleshooter'') off the ground, with Origin Systems rejecting it and Creator/LookingGlassStudios unable to find funding. Spector nearly took a contract with Creator/ElectronicArts in 1997 when Creator/JohnRomero, having recently helped to establish Ion Storm, offered Spector the chance to make his game at Ion Storm without any limitations. Spector gladly accepted, quickly starting pre-production in Austin, Texas with a small team of former Looking Glass staff. |
| 192 | ** Spector's team was soon bolstered by former Origin Systems employees, including ''VideoGame/UltimaIX'' lead designer Robert White, as part of a walk-out due to EA's ExecutiveMeddling at Origin, but problems soon arose as White's team had a very different design ethos. This led Spector to split developers into two camps with White leading a "traditional roleplaying group" against an "immersive simulation group" led by Harvey Smith, hoping that a FriendlyRivalry would bring the best out of both. Instead, the two groups clashed over '''everything''', with just the idea of a set name for the player character nearly inciting a "holy war". Spector ultimately merged the two groups into a single team with Harvey Smith as the lone design lead, and later regarded the two groups decision as a costly blunder. |
| 193 | ** There were also troubles regarding art assets and engine choice. Early in development, assets were outsourced to Ion Storm's Dallas offices who seemed disinterested in the game, leading Spector to beg for a dedicated art team which he eventually got. As for the engine, the team licensed the Unreal engine and had to spend over half a year learning it, cautiously programming role-playing features like skill systems and dialogue trees for an engine built around shooting. |
| 194 | ** Meanwhile, the Dallas branch of Ion Storm was under fire. Their real-time strategy game ''Dominions: Storm Over Gift 3'' had released to negative reviews and was utterly crushed by ''VideoGame/StarCraft'' in sales[[note]]most estimates for the sales of ''Storm Over Gift 3'' are around twenty thousand copies, though a [=GameSpy=] retrospective put it at less than ten thousand copies[[/note]], Tom Hall's ''VideoGame/{{Anachronox}}'' and John Romero's ''VideoGame/{{Daikatana}}'' were punching bags in the gaming press for their protracted developments and confrontational marketing, also casting doubts on ''Deus Ex'', and private emails were leaked to the public. The bad press hurt morale and made it nigh-impossible for Ion Storm to hire more developers. Ultimately, the Austin team adapted a "we'll show them" mentality to continue work on the game. |
| 195 | ** As private prototype tests were held in 1999, the feedback was dire. Game systems were criticized for lacking tension while the realistic level design wasn't creating compelling gameplay. Realizing a "less is more" approach was needed, the team began toning down their ambitions and refocused their efforts, cutting their design document in half and trimming many locations from the story to allow the team to focus their efforts on what worked. |
| 196 | ** And even as the game finally began to take shape, Creator/EidosInteractive (who had made a publishing deal with Ion Storm) grew increasingly concerned with the turbulence within Ion Storm's walls. Spector claimed that Eidos repeatedly pressured him to make the game a conventional shooter, while Romero claimed years later that he had to step in late in development to stop Eidos from canceling the game entirely. |
| 197 | * ''VideoGame/DeusExInvisibleWar'' suffered from a myriad of development problems whose end product ultimately led it [[CreatorKiller sinking]] Creator/WarrenSpector's [[CreatorKiller reputation]] and the [[GenreKiller immersive sim genre]]. The engine the game was built on, a heavily modified version of the Unreal Engine 2 dubbed the "Flesh Engine" was capable of great visuals, but it was a technical nightmare to work with. Disaster happened when the lead engine coder left partway through the project and left no documentation behind, leaving the rest of the team scrambling to fix critical engine issues. Further complicating the development was Eidos forcing Ion Storm Austin to also develop it for the Xbox in tandem with the PC, and the Xbox proved less powerful than the developers anticipated. This, combined with the aforementioned engine issues, forced the developers to significantly cut down levels and take extreme measures to try and save on memory usage, such as shutting down the entire game and restarting it on every loading screen. These problems also affected the development of ''VideoGame/ThiefDeadlyShadows'', which was developed concurrently with ''Invisible War'' and used the same engine. When the game finally was released, it performed ultimately poorly compared to the previous installment both critically and commercially and [[FranchiseKiller led to Eidos cancelling future installments]] and retooling the only in-development installment [[VideoGame/ProjectSnowblind as its own game]] to distance itself from the franchise whose reputation was now marred by ''Insivible War'''s failure. |
| 198 | * ''VideoGame/DevilMayCry2'' became an outstanding example of a SophomoreSlump due to a chaotic and rushed development. Details are still scarce about what happened before Hideaki Itsuno came on board as director; he only joined halfway through the project, and the original director is unknown to this day. According to the ''Devil May Cry: 3-1-4-2 Graphic Arts'' book, Itsuno arrived to see that little progress had been done on the game, with many basic gameplay elements undecided and no plot outline written. With the game only six months away from release and Capcom unwilling to push the deadline back, Itsuno and the team scrambled to put together a game that was at least functional. The end result was commercially successful, but took a beating in the reviews for its undercooked gameplay and bland level design. Capcom themselves see it as an OldShame; ''VideoGame/ViewtifulJoe'' pokes fun at it and ''VideoGame/DevilMayCry5'''s "History of [=DMC=]" video only offers a brief glance at the game. Itsuno would bounce back with ''VideoGame/DevilMayCry3DantesAwakening'', which addressed many of the second game's flaws and was released to critical acclaim, though it failed to outsell ''2'' due to consumer wariness. |
| 199 | * ''VideoGame/DMCDevilMayCry'' was an attempt to reboot the ''VideoGame/DevilMayCry'' series to give it greater worldwide appeal, but it suffered heavily from controversy and development troubles. |
| 200 | ** The idea of rebooting the series came from Capcom's disappointment by the sale numbers of ''VideoGame/DevilMayCry4'' and a push by Creator/KeijiInafune to "westernize" game development at the company. Wanting to hand the series to a developer in the west, Capcom approached Creator/NinjaTheory, who were fresh off of their success with ''VideoGame/HeavenlySword'' and the AcclaimedFlop ''VideoGame/EnslavedOdysseyToTheWest'' to take up the series. Ninja Theory gladly accepted the offer, but their initial concepts were rejected by Capcom as being too close to the original games. Encouraged by Capcom, they pursued a radically different aesthetic inspired by street culture and works like ''Film/FightClub'' and ''Series/{{Dexter}}''. |
| 201 | ** When the game was first debuted at the 2010 Tokyo Game Show, it impressed critics with its visual flair but left fans of the original games confused and angry at the radical changes from the original series, the most glaring was the changes made to the series' iconic protagonist, Dante. NT director Tameem Antoniades infamously [[http://kronecker-delta.tumblr.com/post/163118817114/the-most-serious-part-of-the-devil-may-cry-series lashed out]] at the complaints in interviews and NT art director Alessandro Taini compared Dante's ''[=DMC4=]'' design to ''Film/BrokebackMountain'' and ''Film/BatmanAndRobin'' in a [[https://youtu.be/b_Pz8WiEW4U?t=103 GDC presentation,]] which drew accusations of homophobia. As a result, Ninja Theory formed a mutually antagonistic relationship with ''DMC'' fans, even though many of the choices that got them heat had been at Capcom's behest. [[https://www.polygon.com/2013/1/30/3931784/capcom-devs-describe-the-long-distance-romance-with-ninja-theory-that Communication and culture issues]] between Ninja Theory and Capcom meant that [=DMC4=] director Hideaki Itsuno was brought in to advise Ninja Theory on gameplay and visual designs, leading the game to take more elements from the original series than initially intended. |
| 202 | ** Upon release, the game suffered a textbook example of CriticalDissonance. Professional reviewers gave nigh-universally positive reviews, while fans of the original series were deeply displeased with the simplified gameplay mechanics, DarkerAndEdgier tone and [[TakeThat perceived jabs]] toward the older games. The high review scores did not translate to commercial success however, and the game only managed half the sales of ''[=DMC4=]''. In the end, Capcom would UnReboot the series with ''VideoGame/DevilMayCry5'', ignoring ''[=DmC=]'' plot points and outright saying that ''[=DmC=]'' was ExiledFromContinuity in interviews. Ninja Theory also thankfully managed to escape the game's shadow, returning to developing original properties and managing to self-publish the critically-acclaimed hit ''VideoGame/HellbladeSenuasSacrifice'' in 2017. |
| 203 | * Both ''VideoGame/{{Destiny}}'' and [[VideoGame/Destiny2 its sequel]] went through much turmoil owing to conflicts between the development team and senior leadership at both Creator/{{Bungie}} and Creator/{{Activision}}. |
| 204 | ** ''Destiny'': There was a lot of difficulty and conflict over exactly what kind of game they were trying to make, the core idea was a hybrid between the mechanics of a FirstPersonShooter with the infrastructure of an MassivelyMultiplayerOnlineRolePlayingGame. They did not always agree on the best way to do that. |
| 205 | *** When Joseph Staten revealed the story plans for the base game release to the higher ups they declared it too complex and linear, desiring a more open world approach, leading to most of the material to be dropped and Staten eventually left. Some of that material has filtered into later DLC and the lore, but this was the core reason the first year of the game was so underwhelming with its story as the focus was on refining the gameplay mechanics and WorldBuilding to a sharp point. |
| 206 | *** Marty O'Donnell took on an ambitious composing project to create unique musical environments called "Music of the Spheres," complete with getting Music/PaulMcCartney involved, but Activision rejected his ideas for a soundtrack release, and the gameplay reveal was made using other licensed music. This conflict eventually lead to O'Donnell being fired, he successfully sued them for wrongful termination and lost income for profit-sharing and stock options. By the time the game was launched Bungie ended up losing two of the most prominent members of the ''Franchise/{{Halo}}'' crew. |
| 207 | ** ''Destiny 2''. According to Jason Schreier, the game underwent a complete reboot in production about sixteen months from release when Luke Smith took over as Game Director. Apparently, many of the current woes that the fandom is expressing (Mainly the Eververse) can be traced back to this decision. For anyone who thinks that this sounds familiar, that's because [[HistoryRepeats the exact same thing happened to the first game.]] |
| 208 | *** People who have paid visits to the actual headquarters of Bungie have discovered that there is a strong internal disagreement with many of the negatively-received aspects of the game. No one knows the full extent of this, but given the wording of these accounts, at best, it's AHouseDivided, at worst, you could count the amount of people who genuinely like said aspects on one hand, namely the directors. |
| 209 | *** During the Season of the Drifter near the end of Year 2, Activision and Bungie officially parted ways on game development, after having a difficult relationship from the start of the franchise. Rumors imply that Bungie threw a party to celebrate. Year 3 and the release of Shadowkeep was Bungie making the game closer to what they wanted it to be, but the overhaul on PC was massive as they had to switch from the Battle.Net client to Steam. |
| 210 | ** A [[https://www.ign.com/articles/bungie-report-battle-soul-work-culture-harassment-crunch 2021 report]] by [=IGN=] revealed that Bungie suffered from a chaotic and sexist work culture that negatively impacted the development on Destiny with the narrative team suffering the worst. According to one writer, a woman of color known in the article as Cookie Hiponia, women were denied promotion unless they "got good" at the game, their reports of sexist abuse were aside by [=HR=] as just jokes and many writers suffered from stress-related health problems caused by working 80-100 hours per week with Hiponia herself developing a gastrointestinal disorder required surgery. On top of the hostile workplace, the writers were scapegoated by members of the ''Destiny'' fanbase, who weren't aware of the development problems and blamed the team for storytelling pitfalls that they had little control over. Only after threats of developers quitting ''en masse'' did Bungie finally fire the problematic leads and overhauled the studio structure. |
| 211 | %%* ''VideoGame/DigimonSurvive'' was first announced in 2018 and slated for release in the next year. However, the game ended up being delayed three years in a row as well as having the developers & engine changed halfway through before releasing in summer 2022. |
| 212 | * The development of ''VideoGame/{{Doom}}'' went generally smoothly, but its infamous [[Platform/ThreeDOInteractiveMultiplayer 3DO]] port was something else. It was produced by a company called Art Data Interactive, who's CEO Randy Scott paid for the license by asking for donations from his Church. He beleived that all one had to do to port a game to another platform was to recompile its code, and that new weapons could be added just by importing new art assets. This led to programmer Rebecca "Burger Becky" Heineman, who had joined under the impression she just needed to polish a complete game for release as Scott repeatedly claimed the game was 90% done, having to develop ''the entire thing, on her own, in ten weeks,'' which forced her to live in her office to finish it on time. |
| 213 | ** All Scott did during this time was butting heads with Heineman, demanding more additions to the game and still convinced programming wasn't nessacery. The only thing that Scott actively contributed to the final product was the soundtrack since the 3DO has a dedicated sound driver that was incompatible with the 3DO's sound font (he was able to record every track in the game with his garage band). |
| 214 | ** It appears that Art Data attempted to create FullMotionVideo cutscenes for the port, if [[https://twitter.com/burgerbecky/status/675578504352673793 this still photo]] from Heineman and others [[https://www.doomworld.com/vb/post/1375471 dug up]] by fans are any indication. The result was SoBadItsGood, which is likely why it wasn't added to the final game. |
| 215 | ** Heineman lost about a week of development time dealing with flaws in the console's development tools and quirks of its operating system; for most games this would have been only a minor inconvenience, but with such a short development timescale, it was all the more damaging. And even if she'd had more time to optimize the code, the console's CPU was too weak for it to even match the resolution or frame-rate of the Atari Jaguar or Sega [=32X=] ports, hence why it runs in such a small gameplay window. |
| 216 | ** In the end, Scott was actively ''mad'' at Becky for not putting all of the content he wanted into the game, ''still'' under the belief that programming was not necessary. Randy Scott vanished from the industry after Art Data Interactive immediately went under after Scott pressed ''way'' more copies than would feasibly ever sell. |
| 217 | ** Nine years later, Heineman [[https://github.com/Olde-Skuul/doom3do released the source code alongside her story of its production and a wish that she had time to polish her work before release]]. In addition, she's more than happy to recall the story to those interested in [[https://www.youtube.com/watch?v=rBbIil2HPSU her livestreams]] [[https://www.youtube.com/watch?v=y_do6lL7ueQ&t=2134s and convention appearances]]. |
| 218 | * 2016's ''VideoGame/Doom2016'' had a hard time getting finished. |
| 219 | ** As covered in the [[https://www.youtube.com/watch?v=PS6SBnccxMA DOOM Resurrected documentary]], the game started life as ''Doom 4''. Creator/IdSoftware originally built the game as a much more scripted, cinematic experience in the style of ''VideoGame/CallOfDuty'', but [[http://kotaku.com/five-years-and-nothing-to-show-how-doom-4-got-off-trac-468097062 development suffered a number of restarts and employees leaving, with poor management and direction being blamed for the lack of progress]]. When screenshots and concept art leaked out in 2008, fans were deeply upset at its derivative FollowTheLeader nature and feared it would become an even bigger OddballInTheSeries than ''VideoGame/Doom3'', which came out years prior. Id realized the direction of the project was a poor fit for ''Doom'', and rebooted the project with Zenimax's blessing. |
| 220 | ** Even then, it was a rough road; its Quakecon 2014 debut was behind closed doors with no footage allowed, and its E3 2015 showing was met cautiously by the fanbase. Id was forced to outsource the multiplayer as they scrambled to finalize and polish the single-player elements. Bethesda chose to heavily promote the multiplayer in its marketing, which left fans restless about the state of the single-player and only got worse when the multiplayer open beta was slammed for its lack of features and ''Franchise/{{Halo}}''-style weapon loadout system. Bethesda [[NotScreenedForCritics withheld review copies]] in response, which accordingly sunk expectations to rock-bottom. |
| 221 | ** However, when the game finally released, it was greeted warmly by both fans and critics with the single-player in particular being praised as a quality GenreThrowback, though its multiplayer was and still remains a [[BrokenBase divisive element]]. |
| 222 | * ''VideoGame/DragonAgeII'' was a victim of an especially rushed development cycle, as the success of ''VideoGame/DragonAgeOrigins'' resulted in EA demanding that [=BioWare=] were to make a full sequel to within 18 months of the ''Origins''[='s=] launch. In comparison, the pre-production on ''Origins'' had been 18 months ''alone'', while the development cycle had been clocking in at about 5 years. Under these circumstances, [=BioWare=] scrambled to quickly put a team and did a rushed bit of pre-production, where it was decided to take the planned minor SpinOff game ''Dragon Age: Exodus'' and turn it into an [[WhatCouldHaveBeen uplifted side story]] by retooling it into being a sequel. According to some sources, the game then ended up spending as little as ''8-9 months'' in active development before it was pushed out the gate to meet EA's deadline. |
| 223 | * ''VideoGame/DragonAgeInquisition'' suffered from a messy and hectic development. |
| 224 | ** Initially planned to be an expansion to ''VideoGame/DragonAgeII'', the colder-than-expected reception to that game led to [=BioWare=] scrapping those plans and turning ''Inquisition'' into a full sequel. This had ripple effects through development, as the team had difficulty committing to decisions on gameplay mechanics and story. This led to the game [[http://kotaku.com/dragon-age-inquisition-used-to-be-a-way-different-game-1684304172 significantly shifting]] from its PAX 2013 demo, and a number of story and gameplay elements would be cut from the game. |
| 225 | ** Technical issues plagued the game during development. EA mandated the use of DICE's Frostbite MediaNotes/GameEngine that had been developed for the ''VideoGame/{{Battlefield}}'' series. Frostbite has become notorious for its CripplingOverspecialization toward FirstPersonShooter games, offering no concessions toward other genres, and would come to plague the development of other games under EA's umbrella. Combined with the team failing to make design decisions early in development, the final months were defined by a harsh period of crunch time. |
| 226 | ** While the game was ultimately a success - enough that several outlets gave it their Game of the Year awards - some at the company would later state that the game's success convinced [=BioWare=]'s management that indecision and crunch periods were an acceptable reality of modern game development, leading to the troubles faced by ''VideoGame/{{Anthem}}''. |
| 227 | * ''VideoGame/DragonQuestXI'' was one of the first games announced for the Platform/NintendoSwitch. Its development went smoothly and it released on Platform/PlayStation4 and Platform/Nintendo3DS without trouble, but the game's Switch version was [[ScheduleSlip delayed by two years]] because ''XI'' was initially developed on a version of Unreal Engine 4 that the Switch did not support, and Creator/SquareEnix had to spend a fair chunk of time updating the engine to a newer version. To compensate for the delay, the Switch version became an UpdatedRerelease with new story chapters and several new features, which was eventually re-released on [=PS4=], Xbox One and PC. |
| 228 | * The saga of ''VideoGame/DukeNukemForever'' is one of gaming's most infamous examples of a production GoneHorriblyWrong, becoming a byword for {{Vaporware}} through its 14-year development. |
| 229 | ** The long DevelopmentHell for Creator/ThreeDRealms began in 1997 after ''VideoGame/DukeNukem3D'' proved to be a smash hit. ''Forever'' was originally intended to be a 2D platformer, but was scrapped and rebuilt to be a FirstPersonShooter sequel to ''3D''. The game was first announced in 1997 and made a point to use the latest in technology, with 3D Realms licensing Creator/IdSoftware's [[VideoGame/QuakeII iDTech 2]] engine at an exorbitant cost - roughly $500,000[[note]]to put this in perspective, the licensing costs for powerful game engines late in the next decade, like Unreal Engine 3, didn't cost that much[[/note]]. While the game's showing at E3 1998 impressed many, 3D Realms co-founder George Broussard was concerned that the game would be overshadowed by the likes of ''VideoGame/{{Unreal}}'' and ''VideoGame/HalfLife''. The team made a unanimous decision to switch to the ''Unreal'' engine, a decision that required scrapping the work they had done up to that point. |
| 230 | ** The game would miss release dates for the next few years, and public appearances of the game ceased amid publisher troubles before the game landed with Take-Two. ''Forever'' would reemerge at E3 2001, becoming the talk of the show with its advanced graphics and interactivity. The team was elated at the response, but the game would once again fade from the public eye; the release date now being "When it's done.", which became the subject of mockery and MemeticMutation. |
| 231 | ** Many who worked on the game blame the delays on Broussard, whose perfectionism and desire to upstage the competition led to the game constantly shifting as new technologies and gameplay innovations inevitably arrived, with no end goal in sight. The company's outdated mentality toward game development was also an issue, as it used small teams and a management structure that was inefficient and understaffed for the demands of a big-budget title. |
| 232 | ** As the game was funded entirely by 3D Realms, the game was effectively immune to ExecutiveMeddling by publishers, which led to tensions between Take-Two and 3D Realms over the lack of progress. In response to Take-Two CEO Jeffrey Lapin claiming that the game would cost the company $5.5 million of its earnings in 2003, Broussard publicly stated that "Take-Two needs to STFU" (yes, he [[https://money.cnn.com/2003/06/11/commentary/game_over/column_gaming/ really did say this]] in an online forum that year). Broussard would make several other statements against Take-Two, his ProtectionFromEditors rendering him immune to retaliation. |
| 233 | ** With development dragging on through the mid-2000s, the team became restless with the constant delays and being paid via deferred income; [[ScrewThisImOuttaHere many began walking out]]. By late 2006, Broussard began to take the idea of finishing the game seriously and the company would bring in new hires in 2007, most notably Brian Hook as project lead, who was the first to push back against Broussard's demands. At one point, Creator/BenCroshaw was approached by Hook to write the game's script, but Broussard shot down Croshaw's irony-drenched draft as disrespectful. Media began to be released once again, starting with a small trailer in late 2007 and in-game footage appearing on ''The Jace Hall Show'' in 2008. |
| 234 | ** But funds finally began to dry up. 3D Realms, having spent over $20 million of its own money on ''Forever'', approached Take-Two for an additional $6 million to complete the game. Both parties have conflicting accounts about the exact counter-offer made, but Broussard rejected the offer and 3D Realms ceased development in May of 2009, laying off the development staff. Take-Two filed a lawsuit against 3D Realms for failing to complete the game, which would be settled out of court in 2010. While internal development at 3D Realms had ceased, work continued by ex-employees under Triptych Games. |
| 235 | ** With the PC version of the game nearly complete, 3D Realms contacted Creator/GearboxSoftware to assist development and create console ports. Gearbox CEO Randy Pitchford - a former 3D Realms employee who had worked on ''Duke 3D'' - convinced 2K Games that Gearbox and Triptych could finally complete the game. The near-final version of ''Forever'' made a surprise showing at the Penny Arcade Expo of 2010 with a playable public demo. It was the first time the game had been shown to the public since E3 2001. The reveal of a playable demo reignited interest in the game, setting the internet abuzz with the news while hours-long lines formed for the demo. |
| 236 | ** A new release date was finally set: May 3, 2011. [[RunningGag Fittingly]], this date would be pushed back one last time to June 2011. Unfortunately, the game's release finally saw the [[HypeBacklash hype bubble pop]] after being deflated and revived constantly. Reviews were mixed-to-negative, with critics unimpressed with its gameplay and attacking the game's 90s attitudes as crass and unacceptable. Fans were somewhat more positive, though many were displeased with the game [[FollowTheLeader borrowing elements]] from ''Franchise/{{Halo}}'' and ''VideoGame/HalfLife'' instead of being a true GenreThrowback. |
| 237 | ** While the development nightmare was finally over, the aftershocks continued to echo for years. Gearbox and 3D Realms would tangle in legal disputes over the ownership of the ''Duke Nukem'' property, with 3D Realms eventually conceding to Gearbox. The game appears to have been a FranchiseKiller for Duke; his only appearances since ''Forever'' have been Gearbox's UpdatedRerelease of ''VideoGame/{{Bulletstorm}}'' and the ''World Tour'' re-release of ''Duke 3D''. 3D Realms managed to remain in business but [[CreatorKiller have fallen irreparably far from their glory days]], having backed away from development to publish retro indie titles such as ''VideoGame/IonFury''. |
| 238 | * In a partnership with Creator/{{Nintendo}}, Creator/SiliconKnights' ''VideoGame/EternalDarkness'' started development on the Platform/{{Nintendo 64}} -- and neared completion before Silicon Knights were asked to throw away everything and rebuild the game from scratch on the [=GameCube=] for launch.[[note]]A situation that isn't unique to just Silicon Knights; see also ''VideoGame/StarFoxAdventures'' by Rare, coincidentally another developer that would end up suffering from having their ties to Nintendo cut...[[/note]] Additionally, in its [=GameCube=] incarnation, there were some internal concerns on the Middle Eastern areas [[DistancedFromCurrentEvents due to 9/11]], causing a delay. Altogether though, the development of the [=GameCube=] version (as well as that of ''The Twin Snakes'') were far less catastrophic due to the constant supervision of none other than Shigeru Miyamoto and Satoru Iwata (no word if Silicon Knights' workplace conditions under Nintendo were as difficult as those of Retro Studios' concurrently). |
| 239 | * The infamous ''VideoGame/ETTheExtraTerrestrial'' for the Platform/{{Atari 2600}}, which was so [[ChristmasRushed rushed]] that it ended up being made just in six weeks. It was made by a single person, Howard Scott Warshaw, and programming for 2600 was notoriously idiosyncratic, so it's actually a minor miracle that the game is playable at all. The game was enormously hyped by the Atari's marketing department, who were [[ThisIsGoingToBeHuge so confident that the game would be successful]] that they manufactured over 4 million cartridges. Instead, it catastrophically failed to live up to expectations, with many people calling it one of the worst games ever made. The game's failure played a huge role in triggering MediaNotes/TheGreatVideoGameCrashOf1983. It led to [[http://en.wikipedia.org/wiki/Atari_video_game_burial Atari secretly burying tons of unsold cartridges in a secure New Mexico landfill]], which were later excavated in 2014. |
| 240 | [[/folder]] |
| 241 | |
| 242 | [[folder:F-H]] |
| 243 | * As explained in [[http://www.eurogamer.net/articles/2016-05-12-lionhead-the-inside-story this article]] from Eurogamer, development on the ''VideoGame/{{Fable}}'' games was a long series of Troubled Productions that [[CreatorKiller slowly destroyed]] Creator/LionheadStudios. |
| 244 | ** After the success of ''VideoGame/BlackAndWhite'', Lionhead made a decision that Creator/PeterMolyneux felt in hindsight to be a bad idea: it brought on two smaller developers, Big Blue Box and Intrepid, as satellite studios, leading to Lionhead turning into a quite large and bloated company. Big Blue Box began work on what would become ''Fable'', which attracted the attention of Microsoft, which was looking for a KillerApp for their new Platform/{{Xbox}} console and liked what they saw. They immediately stepped in to publish and fund ''Fable'', and all seemed to be going well. |
| 245 | ** Unfortunately, Lionhead's plan to raise money by having the company float on the stock market backfired spectacularly after 9/11 and the resulting crash in the stock market. Leaking money, the company absorbed Big Blue Box and Intrepid, canceling the latter's caveman survival game ''B.C.'' and its own internal "Project Dimitri" (which the ''Black & White'' dev team had been working on before being shifted to ''Fable'') in order to meet its commitment to Microsoft. All the while, ''Fable'' grew more ambitious than initially planned, the result of Molyneux's penchant for constantly thinking of new features to add (some of which his developers resisted), turning into by far the biggest game that anybody involved on it had ever worked on. |
| 246 | ** When it was ultimately released, ''Fable'' had all the hallmarks of a Lionhead game: a lovely WideOpenSandbox that was absolutely packed with features, characters, monsters, and ways for the player to experiment, but not much of a cohesive story tying it all together, a critical element for a console RolePlayingGame. The long, drawn-out production also meant that, while the game looked good by the standards of an Xbox launch title, at the time of its 2004 release other games had long since passed it by. Many Lionhead veterans maintain that it was Microsoft's support that had saved ''Fable'' and ensured it was any good at all, and that Lionhead was in way over its head making such an ambitious RPG. |
| 247 | ** After ''Fable'', Lionhead grew large and bloated, with over three hundred employees at one point in 2005 working on such games as a ''Fable'' expansion, ''Fable II'', ''VideoGame/TheMovies'', ''Black & White 2'', and more. Molyneux later admitted that the company's resources and his attention were drawn too thin, especially when ''The Movies'' and ''Black & White 2'' underperformed in sales and left Lionhead in financial trouble. |
| 248 | ** In 2006, Microsoft purchased Lionhead, hoping to secure ''Fable'' as a flagship RPG franchise for the Platform/{{Xbox 360}}. The deal was based on an earnout, and to secure the rest of the money, Lionhead not only had to make ''Fable II'', but they also had to release ''Fable III'' by the end of 2010. Microsoft's involvement marked a change in the culture at Lionhead; the "boys' club" culture that had dominated the company in its early years would no longer fly, and while many grumbled at the increasingly uptight, HR-focused nature of the new Lionhead, most employees agreed that Microsoft's management was for the better. The company redirected its resources towards ''Fable II'', and even though development required heavy crunch towards the end to get the game finished on time, as well as butting heads with Microsoft over some of the content and marketing, the game came out in 2008 to much fanfare. |
| 249 | ** Now, Lionhead had just eighteen months to make ''Fable III''... time that was clearly not enough, especially not with the design changes Molyneux had planned, some of which (like the "Road to Rule" feature) he only announced late in the development cycle. ''Fable III'' launched in 2010, and while it received positive reviews, critics noted its [[ObviousBeta technical problems]] and undercooked story and compared it unfavorably to the previous game. Problems continued to hit Lionhead with their experiences working with Microsoft's Kinect motion control system. One game they were working on, ''Milo & Kate'', fell apart due to both the reduced technical specs of the Kinect and fear that the game would be [[PaedoHunt used by pedophiles as a 'grooming simulator']], while ''Fable: The Journey'' received mixed reviews, with many critics again citing the technological limitations of the Kinect. After the departure of several veteran developers, Molyneux left Lionhead and formed an independent studio, allegedly because of his disillusionment with being unable to make games at Lionhead that weren't sequels to ''Fable'' (a game that, having originated at Big Blue Box outside of his purview, he wasn't so personally connected to in the first place). |
| 250 | ** The final straw for Lionhead was ''Fable Legends'', the most troubled production of them all. The remaining Lionhead developers wished to work on a proper ''Fable IV'', but Microsoft, launching the Platform/XboxOne at the time, was keen on the idea of 'games as a service', and wanted to make a multiplayer ''Fable'' and rejected Lionhead's single-player game. The developers were incensed by Microsoft's ExecutiveVeto, but had little room to push back given Microsoft's ownership of the studio. And so they got to work making ''Fable Legends'', which was stymied by constant ExecutiveMeddling designed to shoehorn the game into Microsoft's constantly evolving brand strategy, as well as by Lionhead's inexperience at making multiplayer games and designing for competitive balance. Up to $75 million was spent on ''Fable Legends'' according to some sources. As development continued to drag on with little to show for it, few developers were surprised when, in 2016, Microsoft cut its losses and closed down Lionhead, canceling ''Fable Legends'' in the process. |
| 251 | * ''Faith and a .45'', a cooperative ThirdPersonShooter set in TheGreatDepression, fell victim to this. Though it was mainly external factors and ExecutiveMeddling that killed both the game and its developer, Creator/DeadlineGames. |
| 252 | ** According to a [[https://vimeo.com/48436052 post-mortem]] by lead developer Søren Lundgaard, the project originally started as a ''Film/BonnieAndClyde'' video game, directly based on the historical OutlawCouple. While publishers were receptive to the idea, they also demanded the game not use innocents or police officers as enemies, which flew in the face of the concept and forced the developers to spend years reworking the premise. |
| 253 | ** Eventually, the project became ''Faith and a .45'', which now featured {{Expy}}ies of Bonnie and Clyde running from John [[MeaningfulName Mammon]], an [[CorruptCorporateExecutive oil baron]] who had bought out part of the United States. Deadline proceeded to pitch the game to a number of publishers, but the game was repeatedly rejected with the reason being "Old West games [[ItWillNeverCatchOn don't sell]]". Demoralized and confused by this response, the developers realized that publishers had no idea what to do with a game set during TheGreatDepression, and as few games had covered the setting before, it was treated as a western game in the eyes of publishers, which were seen as poor sellers. There were also doubts about the game's focus on a romantically-involved couple not going over with shooter audiences, as RatedMForManly shooters such as ''VideoGame/GearsOfWar'' and ''VideoGame/ArmyOfTwo'' were the hot sellers of the genre. |
| 254 | ** In an attempt to get publishers to take on the game, Deadline revealed it to the public with a number of screenshots and trailers, most of which can be seen [[https://www.unseen64.net/2009/08/08/faith-and-a-45-xbox-360-ps3-cancelled/ in this Unseen64 article]]. While the initial publicity and positive reception was a major boost for the developers, publishers remained unconvinced and uninterested in the game. In a last-ditch attempt to sell the concept, Deadline repitched the game in an AfterTheEnd setting akin to ''VideoGame/{{Fallout}}''. This was also brushed off by publishers, who by now had made clear that they wanted nothing to do with the game regardless of its setting. |
| 255 | ** Unable to secure funding for ''Faith and a .45'' or any other in-development games, which included a sequel to ''VideoGame/TotalOverdose'', Deadline filed for bankruptcy in 2009 following the financial failure of ''VideoGame/WatchmenTheEndIsNigh'', and closed down shortly after. |
| 256 | * While ''VideoGame/{{Fez}}'' emerged as an "underdog darling of the indie game scene" and went on to attain critical acclaim, it was highly-publicized for the five-year DevelopmentHell Phil Fish and his company, Polytron, had faced. The documentary ''Film/IndieGameTheMovie'' highlights just a few of their struggles. |
| 257 | ** During ''Fez''[='=]s prototyping phase, Fish opened Polytron as a startup company through means of a Canadian government loan. However, they began to run out of money, and the loan wasn't renewed for the game's production phase. Polytron also lost funding from the organization supporting them[[note]](which preceded the Indie Fund)[[/note]] when their producer, Jason [=DeGroot=], left the company. Fish -- contemplating cancelling ''Fez'' outright at this point -- was forced to borrow money from friends and family for three months in order to keep Polytron open. To his luck, Québécois developer and publisher Trapdoor offered their support in exchange for a portion of ''Fez''[='=]s earnings--a turn of events [[http://www.gamasutra.com/view/feature/134934/the_making_of_fez_the_breaking_of_.php?print=1 which Fish himself believed to have saved the game]]. |
| 258 | ** Fish was embroiled in a legal dispute with [=DeGroot=], who was yet to sign his side of a final separation deal; because of this, [=DeGroot=] had the ability to potentially block Polytron from presenting anything at 2011 [=PAX=] East. The situation left Fish suffering anxiety attacks as Polytron was getting ready for the Penny Arcade Expo. Fortunately, his new partner, Ken Schachter, met with and came to an agreement with [=DeGroot=], settling the problem once and for all. |
| 259 | ** At the Expo itself, last minute changes to the build caused ''Fez'' to hang up or crash, to which Fish would have to restart the game. This turned out to be a minor issue, however, as player reception remained positive. His confidence regained, Fish went back to work on the game. ''Fez'' was submitted for certification in February 2012 [[http://kotaku.com/5845288/oh-by-the-way-fez-is-delayed-again after a few delays]], before getting released exclusively to Xbox Live Arcade on April 13, 2012. |
| 260 | ** Months later, Polytron and Microsoft clashed when the former released a patch which, while fixing some technical issues, had introduced a new one that corrupted the saved games for one percent of users. Polytron withdrew the patch, only to reinstate it later after finding Microsoft's fee for subsequent patch releases unfeasible; the latter eventually announced that they would no longer be charging for patches, and Fish [[https://www.polygon.com/2013/6/27/4471162/phil-fish-slams-microsoft-over-lack-of-support-for-fez went on to criticize Microsoft]] for mishandling ''Fez''[='=]s release, citing poor advertising and little promotion or publicity. |
| 261 | ** ''Fez 2'' was announced in June 2013. However, after an argument with game journalist Marcus Beer, Fish [[https://www.polygon.com/2013/7/27/4563350/fez-2-canceled-phil-fish-confirms angrily cancelled the game]] and [[ScrewThisImOuttaHere left the industry]]. This bit of news surprised the rest of Polytron, and ever since then are loath to discuss upcoming projects (besides ports). On account of what happened, Fish himself became a persona non grata among portions of the gaming community. Fingers were still crossed that ''Fez 2'' would see the light of day, but those hopes were quashed when Fish [[http://www.gamerevolution.com/news/phil-fish-selling-polytron-and-rights-to-fez-27879 sold the rights to Fez and Polytron]] after his personal information was hacked[[note]](over his support of the controversial ''VideoGame/DepressionQuest'')[[/note]]. |
| 262 | * ''Franchise/FinalFantasy'': |
| 263 | ** Midway through development of ''VideoGame/FinalFantasyII'', the development staff moved to Sacramento, California to finish the game, since the work visa of lead programmer Nasir Gebelli (who is Iranian-American) had expired. |
| 264 | ** ''VideoGame/FinalFantasyXIII'' was envisioned as the starting point for a "ten year project" of games [[TheVerse sharing a common mythos]] (a la the ''VideoGame/IvaliceAlliance'') called the ''Franchise/FabulaNovaCrystallisFinalFantasy''. Unfortunately the project was plagued with issues mostly stemming from ''XIII'' being the first ''Franchise/FinalFantasy'' game produced for the [[MediaNotes/TheSeventhGenerationOfConsoleVideoGames seventh generation]]. The vast majority of time and effort was spent on the creation of the Crystal Tools engine, which was envisioned as the engine Creator/SquareEnix would use on ''all'' of their future seventh generation games. Meanwhile, the development team could not agree on a creative vision for the game: the [[https://www.youtube.com/watch?v=IkcscpaqvTQ E3 2006 trailer]] felt more like a concept movie, and the extravagant SummonMagic was purely the art team's idea. The resulting game was commercially successful and scored well with critics but was also controversial for having a linear storytelling style similar to earlier titles like ''VideoGame/FinalFantasyX'' during a time when open world games were becoming popular. |
| 265 | ** ''VideoGame/FinalFantasyXV'' was announced in 2006 as ''Final Fantasy Versus XIII'', a Platform/PlayStation3 exclusive. The game spent four years in pre-production due to the protracted development of the Crystal Tools engine, which gave director Creator/TetsuyaNomura time to work on three ''Franchise/KingdomHearts'' games (''[[VideoGame/KingdomHearts358DaysOver2 358/2 Days]]'', ''[[VideoGame/KingdomHeartsCoded coded]]'' and ''[[VideoGame/KingdomHeartsBirthBySleep Birth by Sleep]]'') and a remake of ''VideoGame/KingdomHeartsChainOfMemories''. Unfortunately, Crystal Tools was unable to handle the open environments of ''Versus XIII'', which caused Square Enix to order ''another'' purpose-built engine: [[https://en.wikipedia.org/wiki/Luminous_Engine the Luminous Engine]]. Frustrated, Nomura's team moved to internally-built code with only the graphics supported by Luminous.\ |
| 266 | When ''Versus XIII'' was about to enter full production, Square Enix got an early look at the Platform/PlayStation4 and Platform/XboxOne, which threatened to render ''Versus XIII'' obsolete before release. Even after blowing so many resources on two purpose-built engines, SQEX president Yoichi Wada MisBlamed Nomura for the development trouble; he ordered ''Versus XIII'' retooled into the next mainline ''Final Fantasy'' and assigned the developers of ''VideoGame/FinalFantasyType0'' to replace Nomura's team. ''Type-0'' director Hajime Tabata was made co-director with the long-term goal of [[ReassignedToAntarctica making Nomura leave the project]] — which succeeded.\ |
| 267 | Unfortunately, development proved even more chaotic under Tabata. The battle system changed countless times; the script was heavily rewritten even months before release; and the dev team took so much fan feedback that the game's release was delayed by two months. While the game was still critically and commercially successful, development of ''XV'' proved so exhausting that Hajime Tabata quit Square Enix in 2018, and the second of two DLC waves was cancelled and relegated to a book. |
| 268 | ** ''VideoGame/FinalFantasyXIV'' had a very troubled production from the beginning, a production so troubled, they literally pulled a RocksFallEveryoneDies ending to revive it. [[https://www.youtube.com/watch?v=Xs0yQKI7Yw4&ab_channel=Noclip-VideoGameDocumentaries This video series]] describes what happened, but Cliff Notes: |
| 269 | *** Coming off of the success of ''VideoGame/FinalFantasyXI'', Square Enix got to work on creating a sequel to it for PC and Playstation 3. In a case of TooManyCooksSpoilTheSoup, various teams were created to craft the various worlds and systems for the game. What no one realized (except maybe the localization the QA teams) was that all of these systems were individually amazing, but were a total mess when combined. Background pieces had as many graphics and polygons as a character, the UI was confusing, crafting was slow and tedious, movement was a hassle, and the game ran extremely slowly on all but the most powerful hardware at the time. As the game came together, the developers started to realize that ''maybe'' they were doing something wrong, but many of them were too stubborn to adjust and kept going. When the game was finally released, despite people noting things in the beta that were wrong, the game was savaged by players and critics alike because of its design flaws. |
| 270 | *** As this was going on, Naoki "Yoshi-P" Yoshida, who had worked on the ''Dragon Quest'' series but had no experience in ''Final Fantasy'', had been approached by ''FF XIV'' team members to help and petitioned to let him join the team. Yoshida felt, at the time, that Square Enix was caught up in a pattern of arrogance that needed to be shot down. However, as Yoshida and his new team prepared to work on the game, he realized the game in its current state could not be fixed. He approached the bigwigs at Square Enix with two plans. Plan A: keep patching the game and try to make it the best it could, knowing it would never be the best and the Online branding would be tarnished. Plan B: patch the game and make an entirely new one behind the scenes to replace the old one. Plan B was implimented in order to salvage the game. |
| 271 | *** During development of this new game, the 2011 Sendai Earthquake and Tsunami struck, and Yoshida made the decision to power down the servers to help alleviate the pressure caused by the damage. When they returned power, Yoshida recieved letters of thanks for keeping the game going as people were able to connect through the game. However, it prompted him to replace the primal Leviathan with Good King Moggle Mog XII, but it was decided to keep the game running during this time. In the following months, patches were released that added auto-attack, removed the fatigue system, brought in Chocobo mounts, introduced famous faces like Hildebrand Manderville... and a strange red star in the sky. On October 11, 2011, ''A Realm Reborn'' was announced with benefits made for new players who stuck with the game during the time this was all happening. In the last months of 2012, final patches were made to set up the final basic systems for 2.0 and set the stage for the end. |
| 272 | *** On November 11st, 2012, after a week of insane monster spawns outside city hubs, the game finally reached its end, playing the "End of an Era" trailer before the servers were shut off. Nine months later, ''A Realm Reborn'' was launched, rescuing a game that heavily floundered upon released, and becoming one of the most iconic games in MMO history. The fact that Yoshida and his team were able to turn a massive failure into such a success is considered one of the biggest AuthorsSavingThrow attempts in video game history, but it had a ''very'' rough road getting there. |
| 273 | * ''VideoGame/{{Firefall}}'', a team-based hybrid of an {{MMORPG}} and a FirstPersonShooter, was announced in 2010 as a potential e-Sports contender with a heavy focus on [=PvP=]. However, as explained in [[http://www.gamefront.com/no-win-situation-the-troubled-history-of-firefall-and-red-5-studios-part-1/ this GameFront article]], over the course of its development things went downhill fast. As of this writing, the game is still in development, but studio Red 5 has laid off a sizable chunk of its workforce, putting its future in doubt. |
| 274 | ** Frequent changes in direction from Red 5 studio founder Mark Kern, the studio's horizontal structure making it hard to coordinate efforts, and Kern's hot temper, absenteeism, and attempts to dictate the production all led to wasted work and what former employees described as a once-pleasant, tight-knit work environment slowly turning toxic. The original focus on [=PvP=] also faded as Kern lost interest in e-Sports, culminating in the game's beta dropping [=PvP=] altogether in 2014, despite all the work that had been put into the [=PvP=] side of the game. |
| 275 | ** There was also Stage 5 TV, a Platform/YouTube channel designed to promote ''Firefall''. Kern and Red 5 spent lavishly on Stage 5, with highly produced short films and reality-style shows shot with very expensive (over $40,000 each) 4k-resolution video cameras, along with a studio, a Mercedes-Benz Sprinter van, and other equipment.[[note]]For comparison, most professional, high-end Platform/YouTube videos are shot with cameras that cost in the low four figures, with budgets typically ranging from $1,000 to $5,000.[[/note]] Kern would greenlight short films left and right, throwing money at projects that often turned out to be either very low quality or having little to do with games at all, and not the sort of thing that Red 5 wanted to showcase. Stage 5 quickly became a money sink that diverted resources away from ''Firefall'', before being scaled back drastically in 2013. |
| 276 | ** Red 5 finally decided to pull the plug entirely on July 2017. At this point, most of the playerbase agreed that it was only a matter of time. |
| 277 | * Creator/{{Atari}}'s ''VideoGame/{{Firefox}}'' arcade game was [[http://www.jmargolin.com/firefox/firefox.htm plagued with problems]] from start to finish. The success of ''VideoGame/DragonsLair'' prompted management to demand the game be ready in a few months, so it could appear at the October 1983 AMOA show in New Orleans. Experienced designers and engineers balked at the schedule; the role of project engineer fell on a new hire who had claimed to be a programmer, hardware engineer, and systems developer, yet who had never designed an arcade game before. The game used three boards designed by different groups, and a laserdisc player that had never been tested in an arcade environment. The incomplete game was rushed to the AMOA show in Nolan Bushnell's private jet, but despite the assurances of the project engineer, remained a dormant shell for the entire show. The project engineer quit afterward; Jed Margolin was cajoled into the project, working 12-hour shifts for three weeks straight to resolve numerous engineering issues, including a new raster monitor that tended to explode when it did not receive a sync signal. The final insult came after the game was released; its high price and declining demand for laserdisc games resulted in ''Firefox'' being a flop right out of the gate. |
| 278 | * ''VideoGame/FugaMelodiesOfSteel'' was Creator/CyberConnect2's first venture into indie game development and publishing, and as they stated over different articles on Famitsu, so many things went wrong that it's a miracle the game didn't crash and burn on release. This included an extremely understaffed team that had ''no programmers'' at the start (everyone else was working on the licensed anime-endorsed games), the project going over-budget and passed projected development time due to certain features being added last minute, the team confusing wholesale and retail price causing the game's pricing to be out of sync across multiple regions and systems, and, somehow, the development team ''forgot'' to contact Sony, Microsoft, and Nintendo for their respective consoles' development kits. '''''[[EpicFail At the end of Fuga's development cycle]]'''''. |
| 279 | * While ''VideoGame/{{Fortnite}}'''s Battle Royale mode had a smooth and quick development process thanks to piggybacking on existing assets and code, the same could not be said for the core ''Save the World'' mode. It took at least six years to make and was the first game to use Unreal Engine 4, which wasn't finished at the time and slowed production down as a result. Creator/EpicGames was also looking into using the games as a service model and reached out to various MMORPG game designers and Chinese conglomerate Tencent, who had experience with the model, for help. This led to many senior employees at Epic Games, including lead designer Creator/CliffBleszinski, leaving the company. Darren Sugg, one of the MMORPG game designers hired by Epic Games, then had to pick up the slack Bleszinski left behind when he left. |
| 280 | * ''VideoGame/{{Gex}}'', as discussed by programmer Gregg Tavares [[http://games.greggman.com/game/gex/ here]]. The development team was inexperienced, overworked to the point of doing 12 to 16 hours a day, understaffed and rushed to finish the game for Christmas. A lot of content was cut due to time and manpower constraints, and lead designer Justin Knorr was fired after hiding an insulting message in the game that included Crystal Dynamics co-founder Madeline Canepa's actual phone number. |
| 281 | * ''VideoGame/GhostbustersTheVideoGame'', while not as fraught with development difficulties as the films, had to deal with a set of problems of its own, including struggles to handle the game's internal development engine, problems securing actors for roles and cost overruns resulting in Vivendi Studios slashing the project's budget anywhere from 25-40%. To note, the producers had to work around Bill Murray's infamous silence related to which projects he was confirmed to be working on by lobbying his brother, Brian-Doyle Murray, who they cast in the game as the Mayor of New York ([[TheOtherDarrin replacing David Marguiles]]) and eventually asked him to tell Bill about the project. Additionally, just as the game was finishing production, it was left in developmental limbo as a result of the Activision[=/=]Vivendi merger, but was bought by Atari several months later. Despite that, the game was a critical success, and sold one million units by July 2009. |
| 282 | * ''VideoGame/GoldenAxe'' was planned to have a 3D remake in the style of ''VideoGame/CastleOfIllusion'', but according to a [[https://archive.is/x4ZWC developer on the Golden Axe revival project]] it was a nightmare to make. Crunch hours, [[ExecutiveMeddling the suits not knowing what to do with the thing,]] and health issues plagued the project and Sega ultimately pulled the plug on it. The cancellation of the ''Golden Axe'' remake played a hand in SEGA Studios Australia [[CreatorKiller closing their doors.]] However, it wasn't a total waste as Sega cleaned up a prototype and released it for free on Steam as ''[[https://store.steampowered.com/app/1368460/Golden_Axed_A_Cancelled_Prototype/ Golden Axed]]''. That said, [[CreatorBacklash its release is a sore spot for those who DID work on the prototype,]] and the developers weren't contacted by Sega (allegedly) about it being released on Steam. |
| 283 | * ''VideoGame/GoldeneyeRogueAgent'': According to screenwriter Danny Bilson in a [[https://www.youtube.com/watch?v=f0xA0oLoeYA video]] and [[https://soundcloud.com/raycevick/sets/test?utm_source=clipboard&utm_medium=text&utm_campaign=social_sharing interview]] with Lucas Raycevick, the game was "our dream that became kind of a nightmare" thanks to this trope. |
| 284 | ** The concept started when Bilson and writing partner Paul [=DeMeo=], having written prior ''Franchise/JamesBond'' games [[VideoGame/AgentUnderFire under]] [[VideoGame/{{Nightfire}} the]] [[VideoGame/EverythingOrNothing flag]] of Creator/ElectronicArts, pitched a ''Bond'' game where the player would be [[VillainProtagonist a rogue MI6 agent]] playing both sides in a "gang war" between ''Bond'' villains [[Film/DrNo Dr. No]] and [[Film/{{Goldfinger}} Auric Goldfinger]]. Despite certain restrictions coming down from EON and MGM regarding the pitch, it quickly entered pre-production at EA Los Angeles. |
| 285 | ** Just as quickly, troubles descended down on the project. [[ExecutiveMeddling EA mandated]] that it needed a quick turnaround, as EA was intent on keeping its ''Bond'' games to a yearly release cycle and had ''VideoGame/DoubleOhSevenFromRussiaWithLove'' lined up for 2005. EA LA manager John Batter named the game ''Goldeneye: Rogue Agent'' for marketing reasons, despite the game [[InNameOnly having no relation]] to [[Film/{{Goldeneye}} the film]] or [[VideoGame/GoldenEye1997 the game]] of the same name[[note]]The game would ultimately include a paper-thin justification by having the protagonist lose an eye and have it be replaced a golden prosthetic and thus be given the nickname "[=GoldenEye=]".[[/note]]. Bilson took particular exception to this, noting that the name would bring unfair comparisons. |
| 286 | ** EA Los Angeles attempted to overhaul its technology during development. The game engine they used had come under fire for its dated graphics in ''VideoGame/MedalOfHonorRisingSun'', pressuring the studio to take action. With EA demanding that ''Rogue Agent'' be released within nine months, EA LA found themselves gutting the concept in order to make it work within the confines of their in-progress engine upgrade and the strict deadline imposed by EA. Bilson was dismayed as communication between the creatives and the development team grew "out of sync", and virtually all the storylines and ambitious setpieces he had drawn up was cut in the mad dash to present a shippable product. |
| 287 | ** The game also had knock-on effects with ''VideoGame/TimesplittersFuturePerfect'', developed by former Rare veterans at Free Radical, as EA slashed the marketing budget for ''Future Perfect'' in favour of ''Rogue Agent''. ''Future Perfect'' became an AcclaimedFlop while ''Rogue Agent'' was panned for its repetitive gameplay. Bilson, having already grown disillusioned with how EA was handling the business side of games he had worked on, decided that ''Rogue Agent'' was the last straw and walked away from the company. Bilson would be hired as a creative executive at Creator/{{THQ}} during its final years before returning to screenwriting with ''Film/Da5Bloods'' in 2020. |
| 288 | * ''Greed Monger'' was a Kickstarter game by Electronic Crow Games that was meant to be a Free-to-Play [[MassivelyMultiplayerOnlineRolePlayingGame MMO RPG]] with a focus on crafting, economics, and politics that allowed the player to do whatever they wanted. While the project made almost four times its original funding goal, it ended up suffering due to terrible behind the scenes problems and never actually released. Where to begin? |
| 289 | ** The game was thought of by [[RenaissanceMan Web designer/Mortgage consulter/Club promoter/Voice actor/DJ competitor/Jujitsu competitor/Head of his own marketing SEO company]] Jason Appleton, who wanted to get into game design. After many months of zero progress, backers became suspicious and impatient. Looking at the development pictures, backers wondered where their money was going to, especially since Appleton stated in a video that he already had the budget for not only the video game, but also a server farm. |
| 290 | ** Enter James Proctor, the game's sole programmer. Proctor was a UsefulNotes/{{Unity}} developer best known on the Unity forums as a guy who [[AttentionDeficitCreatorDisorder creates loads of games every five minutes that he never ends up finishing.]] Appleton hired Proctor because of his love for programing, thinking that ''Greed Monger'' will get finished quickly and safely when in fact, the opposite happened. |
| 291 | ** What backers ended up seeing was a game that had no original assets or models ''at all''. All the money that the backers spent ended up being used by Proctor to buy Unity store-bought assets, essentially turning the game into an overly expensive [[UsefulNotes/{{Shovelware}} asset flip]]. Three years later, photos were shown to backers in order to calm them down and show that the game was progressing. Instead, it caused a lot of animosity thanks to the game looking just plain awful. It was then revealed on the Unity forums that Proctor quit the project because he hated working with Appleton, since not only was Proctor not getting paid until the final product was released, but if he were to ever quit development, Appleton would sue him. Worse, Proctor was almost about to lose his life thanks to all the stress both Appleton and the project were putting on him. Proctor didn't have a contract to prove any of this. Instead, he had his and Appleton's Skype conversation. |
| 292 | ** "But wait!" you say, "How could Proctor pay for things like taxes, rent, and electricity if he was working on the game for years without pay?" Well, it was later revealed that Proctor suffered from depression, and that he couldn't leave his house without having a panic attack if he were to see a large crowd. Because of this, Proctor was getting disability checks from the government. Yup, the game was actually being funded by tax payers, while the backers' money was spent on already made assets from the Unity Store. |
| 293 | ** The project ended with ''Greed Monger'' never getting released, Proctor quitting the project, and Appleton leaving the project with the remaining Kickstarter money, having gone silent, though Proctor randomly shows off the build for the game from time to time, and most likely will never be able to finish it. |
| 294 | * The arcade ShootEmUp ''G-Stream G2020'' has a [[http://shmuplations.com/triangleservice/ unique development history]]. The game was the brainchild of former Konami employee Toshiaki Fujino, who had struggled with self-doubt and unemployment and was about to leave the game industry entirely until he saw an employment ad from an obscure and rather shady Korean company named Oriental Soft, which specifically asked for someone interested in developing an arcade shoot'em up. As Fujino badly wanted to make such a game, he immediately took the job but the problems would not end there: Oriental Soft would not pay him or composer Hiroshi Tanabe (a.k.a. Naoto) for most of development, and the game ran on hardware that was flimsy and woefully outdated for 2001; in particular, the board only had 3MB of audio memory available for music, only enough for about 30 seconds of background soundtrack. The story would have an happy ending though, as after completing the game, Fujino and Naoto left Oriental Soft and founded their own company Creator/TriangleService, which would continue making arcade shoot'em ups, and eventually get the right to rerelease ''G-Stream G2020'' alongside their other games, which they did under the new title of ''VideoGame/DeltaZeal''. |
| 295 | * Creator/ValveSoftware's landmark ''VideoGame/HalfLife'' series is known as a benchmark for revolutionizing gaming with each new major installment, so it's no surprise that actually producing them is a very uphill battle: |
| 296 | ** As covered by ''The Final Hours of Half-Life'', ''VideoGame/HalfLife1'' was so ambitious that most publishers rejected the game, and Valve was forced to cancel other projects to focus their efforts. Initially given a release date of November 1997, Valve repeatedly delayed the game after playtesters were finding it unfun and incohesive, with the setpiece design coming from the team placing every possible idea in a demo level out of desperation. 1998 was a year of brutal crunch development as the game was effectively rebuilt from the ground up, with developers pulling all-nighters on the regular and [[https://www.gamedeveloper.com/design/the-cabal-valve-s-design-process-for-creating-i-half-life-i- relying on internal committies]] named "cabals" to manage design aspects. Roughly two months before the release, [[https://www.gamedeveloper.com/design/valve-explains-why-we-ll-never-see-the-full-history-of-i-half-life-i-s-development the source code control system]] of Valve "exploded", resulting in a catastrophic loss of data and forcing the team to recover game code from various employee computers to complete development. |
| 297 | ** ''VideoGame/HalfLife2'' spent five years in development, and had a number of setbacks and challenges that impeded work. Aside from spending close to a year on a single gameplay trailer (which had to be reworked over and over because Gabe Newell and Jay Stelly were unimpressed by it), the project was originally given a release date of September 30, 2003, despite the dev team knowing that there was no way they would be able to make the deadline because near-final maps and minor storylines had been thrown out. The problems were then compounded by a delay announced ''on the week before the game was to be released'', and making matters worse, [[ContentLeak an incomplete build of the game along with the source code for the game engine was stolen from Valve and released online a week afterward]]. This triggered a massive backlash over Valve lying to the fans over the release date and the stolen build showing that the E3 demos were heavily scripted. It took another year before the game was released, though it was met with resounding critical praise and commercial success. The original storyline and scrapped gameplay elements can be seen [[http://combineoverwiki.net/wiki/Development_of_Half-Life_2 here]]. |
| 298 | ** ''VideoGame/HalfLifeAlyx'' was built on an even more troubled path, this time not because of strict deadlines, but there being effectively ''no'' deadlines, and Valve losing much of its steam ([[Platform/{{Steam}} so to speak]]) since the start of the 2010s. According to the documentary ''The Final Hours of Half-Life: Alyx'', Valve began focusing on the successor to their in-house Source engine -- simply called "Source 2" -- following ''Half-Life 2: Episode 2'', but the unexpected complications that extended its development resulted in many planned projects being [[DevelopmentHell stillborn]], including [[{{Vaporware}} the legendarily ill-fated]] ''[[{{Vaporware}} Half-Life 3]]''. Combined with the studio's organizational style visibly turning on itself[[labelnote:Explanation]]Valve famously works on a quasi-anarchic model where developers assign themselves to whatever self-directed projects they and their teams are most interested in, which worked for starting new ideas, but relied entirely on collaborative momentum for projects to actually be completed[[/labelnote]], virtually no projects were getting finished. It wasn't until they began their pursuit in VR technology and smaller concept projects like ''VideoGame/TheLab'' around 2016 (which reintroduced their need for strict deadlines to coincide with the release of the Valve Index) did they finally buckle down in pursuing a new landmark project simply hinging around "''Half-Life'', but VR". From there on, the usual Valve process of reiteration and refinement began taking hold again for the next several years, and ''VideoGame/HalfLifeAlyx'' was finally released in 2020, [[SequelGap 13 years after the previous]] ''VideoGame/HalfLife'', and to critical acclaim and [[KillerApp commercial success]]. |
| 299 | * ''Franchise/{{Halo}}'' |
| 300 | ** The final iteration of ''VideoGame/HaloCombatEvolved'' that we know today was developed in just nine months, a consequence of Microsoft acquiring the title as an early Platform/{{Xbox}} exclusive. This resulted in a very contentious developer-publisher relationship, as Creator/{{Bungie}} struggled to work with Microsoft as a publisher, and was often suspicious of their intentions for the game. From the perspective of Microsoft's Franchise Division, they had an immense interest in ensuring the game would be a KillerApp for the Platform/{{Xbox}}, and saw Bungie's reluctance to cooperate as immature. The biggest episode in this conflict surrounds the tie-in novel, ''Literature/HaloTheFallOfReach''. Microsoft commissioned author Eric Nylund to write it with the intention that it would be the starting point for a multi-media expanded universe, and gave him just seven weeks to write the book. Four weeks in, Bungie attempted to have the work cancelled because they envisioned ''Halo'' as a standalone work and did not wish to give its universe or characters a definitive backstory. The Franchise Division's Eric Trautmann managed to negotiate the book's continued existence, in exchange for assisting Bungie in completing the game's script, which was heavily behind schedule. As a result, Trautmann and his writers had to write a bulk of the game's dialogue with only a basic outline of what was happening in each level. For example, the infamous "[[CaptainObvious This cave is not a natural formation]]" quote was the result of a writer only having outdated concept art to use as reference. Ultimately, ''Halo: Combat Evolved'' would win commercial and critical acclaim, become the KillerApp for the fledgling Xbox, and spawned a massive franchise and expanded universe that continues to grow to this day. The Bungie-Microsoft relationship would get less dysfunctional, but the conflicting visions for the franchise would remain an issue for the remainder of Bungie's stewardship. |
| 301 | ** ''Videogame/{{Halo 2}}''. As detailed [[http://www.eurogamer.net/articles/better-than-halo-the-making-of-halo-2-article here]], Creator/{{Bungie}} did not want to just retread on ''Videogame/HaloCombatEvolved'' and would indulge in SequelEscalation. They built a new engine that pushed the Xbox to the limits, created an impressive trailer, and then discovered the console couldn't actually handle the tech, meaning they had to restart from scratch after 18 months of work. The planned sprawling levels had to be scaled down considerably, the storyline was cut down (leading to a [[NoEnding rushed ending]] that served as a shameless SequelHook) and trying to [[ChristmasRushed reach the November 2004 deadline]] meant the developers had to discard almost everything planned along the way. It became a KillerApp, particularly for groundbreaking online console multiplayer, but everyone agreed the single player campaign required more polish, and Bungie felt the game was not as good as they planned (thus much more effort was put into ''Videogame/{{Halo 3}}''). |
| 302 | ** ''VideoGame/HaloInfinite'', according to [[https://www.bloomberg.com/news/articles/2021-12-08/how-microsoft-s-halo-infinite-went-from-disaster-to-triumph this report]]. Originally intended for Platform/XboxOne and Windows, the game switched to becoming a 2020 launch title for the Xbox One's successor, the Platform/XboxSeriesXAndS. Besides having to create multiple compatible ports, studio Creator/ThreeFourThreeIndustries faced many challenges including working from home during a pandemic, adjusting to a new open world design and transitioning to a new game engine. Yet the biggest problem was the high developer turnover with senior leads leaving and contractors, who made up most of the development team, resigning after 18 months of work per company policy. Development did turn a corner when Joseph Staten, the original cinematic director at Bungie, came onboard and used his experience to address the flawed studio decisions and poor developer morale. It also helps that Microsoft delayed the game's release by a year to avoid releasing an unpolished game that would further tarnish the franchise (and to also coincide with the 20th anniversary of the first game). Ultimately ''Infinite'' was released to positive reception in 2021 and became one of the biggest launch success for the Xbox Series X|S though there were still sign of troublesome development as staple series elements like campaign co-op and Forge mode were absent at launch. |
| 303 | *** Post-launch support for ''Infinite'' was similarly troublesome. In the lead up to the game's release, 343 and Xbox touted that the game would have years of support including expansions to the campaign and multiplayer. As with pre-launch development, the live-service was continuously hampered by the tech and manpower issues, resulting in delayed content releases and the scrapping of promised features like split-screen co-op and additional story missions. However, the biggest setback to the live-service happened in 2023 when Microsoft would layoff dozens of 343 staff members and Staten himself would leave Microsoft, leaving a skeleton crew in its place. Despite 343's continuous work and some successes like the release of Forge mode and a strong competitive scene, ''Infinite'' never quite recovered from the drop-off in players and hardly has a presence in mainstream gaming discourse. |
| 304 | * ''Highlander - The Last of the [=MacLeods=]'', according to [[https://disqus.com/home/discussion/thespoonyexperiment/highlander_8211_the_last_of_the_macleods/ a comment]] on [[WebVideo/TheSpoonyExperiment Spoony's]] review of the game, had a terrible production. |
| 305 | ** Lore Design, the makers of the game, were just a bunch of inexperienced 24-year-old ''Film/{{Highlander}}'' fans wanting to make a game. Problems had already arisen when the folks at Lore Design were forced to make a game based on ''WesternAnimation/HighlanderTheAnimatedSeries'', which they all despised. No one except the boss of Lore Design knew where the budget for the game was coming from. |
| 306 | ** Coding for the Atari Jaguar CD was a nightmare, since because the Jaguar CD wouldn't allow Lore Design to use an already built engine like the one used for ''VideoGame/{{Quake}}'', they had to code everything by scratch. |
| 307 | ** The composer for the game, Paul C, had a miserable time making the music. He could only come up with 2-second loops that didn't go anywhere. The team would have been able to allow longer music tracks by writing a small wavetable synthesis engine, but that would have taken up more space in the RAM and CPU, which would have led to a decrease in the graphics. |
| 308 | ** The game development caused the developers to drink heavily, which might have influenced some of the more weirder parts of the game. |
| 309 | ** When the game was released, it sold poorly thanks to the Atari Jaguar CD's atrocious hardware not allowing its games to be played at all (including this one). As a result, Lore Design closed its doors shortly after the game shipped. |
| 310 | * ''VideoGame/{{Homefront}}'' was subject to a lengthy, excruciating production for developer Kaos Studios, according to the fittingly-titled ''Polygon'' article [[http://www.polygon.com/2012/11/1/3560318/homefront-kaos-studios-thq "Death March"]]. |
| 311 | ** Before exchanging hands with Creator/ElectronicArts and ultimately Creator/{{THQ}} to become Kaos Studios, Trauma Studios was known for ''VideoGame/Battlefield1942''[='=]s ''Desert Combat'' mod. After developing their first game, ''VideoGame/FrontlinesFuelOfWar'', in 2008, lead developer [=Frank DeLise=] left Kaos, taking its respected work culture with him and throwing the company into crisis. |
| 312 | ** As part of a new greenlighting policy, THQ critiqued prototypes before authorizing game development. Impressed with ''Homefront''[='=]s pitch demo, they ordered Kaos to prepare a demo for E3 2009. What followed was 18 months of resource-eating labor on a five-minute-long demo. |
| 313 | ** Because the game's vision statement was open-ended, ''[[TooManyCooksSpoilTheSoup every]]'' [[TooManyCooksSpoilTheSoup designer proposed hundreds of ideas]], resulting in plenty of design inconsistencies. |
| 314 | ** Employees were frustrated with [=DeLise=]'s replacement, Dave Schulman, who made them accommodate THQ's endless design requests. He tried fostering a relationship with THQ to limit ExecutiveMeddling, like Kaos enjoyed under [=DeLise=]. Thanks to a corporate reshuffling, however, THQ's new leadership instead fought with Schulman over his company management and responses to publisher directives. |
| 315 | ** Not helping was a damning audit of ''Homefront'', which revealed that Kaos' vision was impossible, and that they had little to show despite being a multimillion-dollar production. Schulman departed Kaos and was replaced by creative director Dave Votypka. |
| 316 | ** Danny Bilson, THQ's vice president of core games, took the reins when Votypka couldn't multitask. Some ex-employees describe Bilson as arrogant, but most agree that he was inconsistent: his ideas suddenly pitched ''Homefront'' as a ''VideoGame/CallOfDuty'' rival--a goal Kaos and THQ agreed was lofty, yet pursued anyway. |
| 317 | ** By late 2009 and early 2010, the game was ''still'' unfinished. Several of EA's veteran shooter developers joined, along with David Broadhurst as Kaos' new production lead. Initiating a seven-month crunch cycle on the team, Broadhurst allegedly rode several employees hard and publicly rebuked them in front of coworkers. His leadership, while criticized, is still often credited as the reason for ''Homefront''[='=]s completion. |
| 318 | ** Bilson's [[https://twitter.com/DannyBilson/status/24991583564730370 sardonic Twitter comment]] about Kaos' crunch cycle angered developers, who then aired grievances against THQ and Kaos. Votypka was forced to play damage control. |
| 319 | ** The final year of development was a nightmare, if the frosty reception to Votypka's speech at Kaos' 2010 holiday party was any sign. Morale was low, and a good chunk of personnel quit - either due to physical and mental exhaustion, or accepting jobs offered to them by other game studios out of pity for what they had gone through at Kaos. |
| 320 | ** ''Homefront'' ultimately received a mixed critical reception and undershot Kaos's expectations. After a large stock drop in March 2011, THQ confirmed three months later that [[CreatorKiller Kaos was shutting down]]. |
| 321 | * And production on the sequel, ''VideoGame/HomefrontTheRevolution'', had to deal with the fallout from the last game on top of its own new problems, to the point where the end credits opened with [[http://kotaku.com/new-homefront-has-a-very-unusual-message-in-the-credits-1777459692 a message]] from game director Halit Zala concerning it. It took until 2016 for the game to finally come out, upon which it received mixed reviews. To quote the linked Kotaku article: |
| 322 | -->"Even this first-hand explanation sells the chaos short. First, the developers of the original ''Homefront'' closed. Then the series was moved to THQ Montreal, then Crytek UK. Then publisher THQ closed, and Creator/DeepSilver picked up the tab. Then Creator/{{Crytek}} UK ran into financial issues, which led to many involved in the game’s development — [[http://kotaku.com/sources-crytek-still-facing-issues-as-homefront-direct-1603582673 including Hasit Zala himself]] — to walk out. *deep breath* ''Then'' Deep Silver’s parent company Koch Media stepped in, bought the property, set up a new studio and delayed the game from 2015 to 2016. Zala returned to head up development once more. So when he says 'the path has not always been a smooth one', [[{{Understatement}} he’s not kidding]]!" |
| 323 | * VideoGame/{{Hiveswap}}, the video game set in the ''Homestuck'' universe has had an extensive an quite rocky development along the way with it still despite being announced and started development almost 12 years ago still is on the horizon. |
| 324 | ** Despite breaking its kickstarter fund by a wide margin, with 2.4 Million dollars being raised for the project which was [[ScheduleSlip slated for a summer 2014 release, multiple delays followed.]] The main developers, The Odd Gentlemen, were subsequently dropped due to budgeting issues and unclear guidance from writers. This forced Hiveswap to be developed by the publishing company then on forward, What Pumkin in their new New York offices worked on Hiveswap until its eventual shutdown in favor for a different team that could work remotely in 2015. This new team, decided to ditch the one before 3D visuals of Hiveswap and code leading to years of work and money being lost. Hiveswap was finally released in 2017, but before release was decided the game would be split into episodic games instead of one giant game, due to an easier workload and to follow the structure of the original webcomic. Around this time "Homestuck: Beyond Canon" started its own run which depended on its own Patreon page to keep the lights on, which What Pumpkin started siphoning money out of to continue Hiveswap Act: 2 development, which finally released in 2020. Despite all this, Hiveswap Act: 3 has had nothing spoken about it besides some concept art and confirmed its being developed, with the final act 4 and Hiveswap's sequel series "HauntSwitch" also being confirmed to be coming all the way back to the original kickstarter. |
| 325 | * ''[=H1Z1=]'' was a zombie-themed MMO by Creator/DaybreakGameCompany that originally released on Steam Early Access in January 2015, but its ongoing development ended up transforming into an extremely complicated mess for a variety of reasons, from conflicting vision for the game's direction, to technical setbacks, to frequent exchanges of hand. As a condensed summary: |
| 326 | ** The game titled ''[=H1Z1=]'' -- while facing major server problems early on -- was ultimately a modest Early Access success, though in February 2016, it was announced that the game would become split into two separate titles with their own development teams for ongoing support: ''[=H1Z1=]: Just Survive'' (focusing on the MMO and survival elements) and ''[=H1Z1=]: King of the Kill'' (a BattleRoyaleGame). This naturally induced a huge fission of the existing playerbase, with attention by players and developers ultimately favoring ''King of the Kill''. By August 2018, the survival game -- [[PostReleaseRetitle which had been retitled]] to simply ''Just Survive'' in 2017 -- was shut down due to low player numbers. |
| 327 | ** During the initial announcement of the split, it was also announced that there would be console ports alongside the games' official release, slated for September 20, 2016. However, by the time that month rolled around, it was announced that the console ports were put on pause in order to focus on the PC version, and then just a week before the release date, news came that the game was still deemed "incomplete" and would remain in Early Access development until further notice. |
| 328 | ** ''[=H1Z1=]: King of the Kill'' attained a spike in positive attention around 2017 following the rise of ''VideoGame/PlayerUnknownsBattlegrounds'' and later ''VideoGame/{{Fortnite}}''[[note]](In an odd twist of fate, Daybreak initially brought on Brendan "[=PlayerUnknown=]" Greene -- back when he was simply known for producing a popular battle royale mod in ''VideoGame/DayZ'' -- as a consultant for ''King of the Kill'', but following this period, he was later picked up by (what was then named) Bluehole Games to produce ''VideoGame/PlayerUnknownsBattlegrounds'')[[/note]], but soon found itself unable to keep up with the competition of them and other battle royale titles. By the time of its eventual release from Early Access in February 2018 (as well as a Platform/PlayStation4 release in August 2018), Daybreak had been struggling with deciding on and implementing features to give itself an edge from other titles, from suddenly announcing then adding in an "Auto Royale" game mode based on VehicularCombat, to the game initially launching with a $20 price tag, only to be reverted to a free-to-play a mere week later. The game's title was also in flux, with Daybreak periodically ditching the ''King of the Kill'' subtitle and [[PostReleaseRetitle just referring to the game once again as]] ''[=H1Z1=]''. |
| 329 | ** During this development period, Daybreak was undergoing chaos from various acquisitions and restructuring: after being independent since 2015, the studio received an investment from holding company [=NantWorks=] in 2018, causing Daybreak to undergo several rounds of layoffs between 2018-2019, with it being announced in March 2019 that Daybreak would be split into three separate divisions. In this shuffle, ''[=H1Z1=]: King of the Kill'' [[PostReleaseRetitle was rebranded yet again]] to ''Z1 Battle Royale'', with its new developer division being [=NantG=] Mobile, who -- in a bizarre turn of events -- reverted the game's form to a patch from ''2017'', undoing two years worth of work to the combat, movement, graphics, and other game mechanics in the title. |
| 330 | ** In April 2019 -- a mere ''one month'' after taking the wheel -- [=NantG=] Mobile returned the game back to Daybreak, citing confusion from both development parties as having severely impeded the title's progress. This presented issues for Daybreak in trying to revert [=NantG=]'s reversal of their progress, and ultimately, they were forced to source their [=PS4=] port of their game (which had become greatly asynchronous from the PC version that that point) and sought to integrate console-specific content for the PC version. Reportedly, [=NantG=] had provided a season's worth of old content, but this never saw the light of day. |
| 331 | ** The game's final update came in the form of a bug fix in February 2020. In December of the same year, it was announced that Daybreak was being bought out by Swedish holding company Enad Global 7, and in April 2021, then-CEO Robin Flodin announced that they were going through the game's codebase and were interested in adding new life back into the game. This ended up being the last news of the game's development, with Flodin being replaced by Ji Ham (formerly Daybreak's CEO) in August 2021. No updates to the game have been made since, with North American servers [[DefunctOnlineVideoGames becoming defunct]] on June 2023 without announcement (though European servers still remain). |
| 332 | [[/folder]] |
| 333 | |
| 334 | [[folder:I-K]] |
| 335 | * ''Indie Game Battle'' was a hella ambitious project; a ''VideoGame/SuperSmashBros'' clone starring characters from indie games. Unfortunately, [[https://steamcommunity.com/profiles/76561198044494288/recommended/407620/ as several]] [[https://steamcommunity.com/id/Bas-Makes-Games/recommended/407620/ former devs]] [[https://pbs.twimg.com/media/DJC0Z0sWAAABNiN?format=jpg&name=small have testified]], the lead developer Felix Kjolner failed to learn anything from the disastrous story of fellow fighting game ''Beast's Fury'' and tore the project down with his own unstable ego. |
| 336 | ** When the game first previewed, it was [[TaintedByThePreview roundly mocked]] for its cheap appearance and underwhelming roster, with generic-looking nobodies far outnumbering the few recognizable characters such as The Kid from ''VideoGame/IWannaBeTheGuy'' and WebAnimation/SaladFingers (who wasn't even technically a videogame character, being a Platform/{{Newgrounds}} web series). Many people learned of the game's existence from CausticCritic Creator/JimSterling's [[https://www.youtube.com/watch?v=9N62MQh6zpg video]], which certainly didn't help its image. |
| 337 | ** The devs struggled in obtaining the licenses for the "heavy hitters" in the indie industry: [=Edmund McMillen=] said no to using [[VideoGame/TheBindingOfIsaac Isaac]], Yacht Club said they'd rather have VideoGame/ShovelKnight in ''Smash'' [[note]] which he was, albeit as an Assist Trophy there rather than fully playable as he would be here, which [[StealthInsult really shows what they thought of the game]] that they considered this a better outcome[[/note]], [[VideoGame/{{Undertale}} Toby Fox]] wouldn't even give the courtesy of a reply, and nobody was willing to cough up the license fee to obtain [[VideoGame/FreedomPlanet Lilac]]. |
| 338 | ** Still, the game began to show some promise, improving in graphical quality as well as managing to secure a surprising number of fighters such as Zee Tee from ''VideoGame/{{Eversion}}'', Captain Viridian from ''VideoGame/{{VVVVVV}}'', The Batter from ''VideoGame/{{OFF}}'', a goat from ''VideoGame/GoatSimulator'', and Dust from ''VideoGame/DustAnElysianTail''. However, it became clear that Kjolner was apparently so desperate to pad out the roster that he was not only including characters from "indies-to-be" that weren't yet released (some of which were later straight-up cancelled), but also characters from ''games that hadn't even started production''. Him actually beginning work on these games only made things worse, as he increasingly neglected ''Indie Game Battle'' in favor of his own work. |
| 339 | ** People working with Kjolner were treated poorly: Kjolner reacted terribly to criticism and would often spite developers he had butted heads with by stalling work on their characters, deliberately making their characters play worse, and "forgetting" to credit them for their contributions. He would also send his yes-men to spam fake positive reviews as well as harass and [[https://i.imgur.com/TnQ0nRe.png mass downvote]] anyone who made negative ones. |
| 340 | ** Gaming website Opium Pulses agreed to feature ''Indie Game Battle'' on their store page in exchange for their mascot Opius becoming a character, a deal in which Kjolner never upheld his end of the bargain, essentially conning the site into giving him free advertising. |
| 341 | ** As the criticism wore him down Kjolner's ego went out of control. He started kicking out several longtime developers (such as [=BountyXSnipe=], [=StarTurbo=], and Ryan Silberman, who had all been working with him for years) and banning them from his Discord channel, often making up fake reasons for said bans and [[UnPerson removing any characters or stages they had contributed to the game in the process]]. If anyone stuck up for said developers, they would also be banned, as would anyone who happened to be friends with people who had been previously banned. |
| 342 | *** Silberman's treatment deserves special mention. Kjolner and his yes-men ripped on ''Missileman'' (Silberman's game) constantly, nagging Silberman to change the game to their desires and regularly threatening to remove Missileman as a character if demands weren't met. After booting Silberman from the project, Kjolner later lied to Silberman that the fans had voted for Missileman to be removed when no such thing had happened. For the rest of the game's history and ''to this very day'', Kjolner and his yes-men treat Silberman as a Boogeyman-figure out to sabotage the (nonexistent) game. |
| 343 | ** When the game was finally cancelled in 2017 it had barely changed from its Early-Access debut in 2015, with no extra modes added and several characters unfinished, unbalanced, unimplemented, or removed. Kjolner showed he had learned absolutely nothing by [[http://steamcommunity.com/gid/103582791439864952/announcements/detail/1439319410146120258 blaming the game's state on "the haters"]] while posting [[https://imgur.com/ysAMy3K articles slandering his former coworkers]] and holding a last-minute sale to squeeze what little money he could before the game fell into obscurity. |
| 344 | * This trope can affect gaming hardware as well as software. The best known example goes back to the early days of home video gaming: the Keyboard Component to Creator/{{Mattel}}'s Platform/{{Intellivision}}. |
| 345 | ** Starting in 1980, the back of the Intellivision box had given a third of its space to a large promotion for the Keyboard Component. The console itself was really the Master Component of what was to be fully functional home computer with a secondary processor, 64K of RAM, a built-in cassette drive and a connection for a thermal-printer cable ([[TechnologyMarchesOn all of which would have sounded impressive at that time]]). Just buy it, play the games, [[{{Vaporware}} and wait]]. This could have easily justified buying an Intellivision over the cheaper Atari 2600, especially for parents not wanting the expense of buying both a video-game console ''and'' a home computer. |
| 346 | ** However, behind the scenes the engineers responsible weren't as confident as the marketing department[[note]]Which of course ''rarely'' happens[[/note]]. Their prototypes were neither reliable nor reasonably cost-efficient to make. The ship date of the KC kept getting pushed back, to the point that Jay Leno got his biggest laugh at the company's 1981 Christmas party when he said that the three biggest lies were "the check is in the mail, I'll still respect you in the morning, and the Keyboard will be out in the spring". |
| 347 | ** By that time, the executives had grown concerned enough that they secretly established another group of programmers within the company to come up with a more scaled-down version of the KC, perhaps limited to the function of teaching kids BASIC programming. It was codenamed the LUCKI, or Low User-Cost Keyboard Interface, and its creators kept their work a secret out of (justifiable) fear that the main KC group would use their influence in the company to kill the LUCKI project if they learned of its existence. |
| 348 | ** Mattel's executives weren't the only ones having concerns, and acting on them. Customers who'd waited almost two years for the KC began to complain to the Federal Trade Commission, accusing Mattel of defrauding them. After enough of these complaints, and further stalling from Mattel, the FTC said that if they didn't make their latest promised ship date with the KC they would be fined $10,000 ''a day'' until they did. |
| 349 | ** It was still nowhere near ready. To appease the FTC, the company put about 4,000 of the latest prototype on shelves in selected test markets. Some sold, but the overall results were not encouraging. |
| 350 | ** After almost three years, the Keyboard Component was officially cancelled late in 1982 -- the ultimate death knell being brought about largely in part by the release of the Platform/Commodore64, whose specifications rendered the Keyboard Component utterly obsolete, and at a much lower price to boot. The FTC dropped the mounting fines when Mattel agreed to offer a full refund to anyone who ''had'' purchased one of the limited production runs. Those who wanted to keep them had to sign a full waiver promising not to seek any support or later refund from Mattel (in-house, the KC saw some limited later use when modified versions proved to be ideal development boards). A few are still out there somewhere. |
| 351 | ** As a consolation prize, the company brought out LUCKI, now formally named the Entertainment Computer System. While you could write and save programs to its (much-simpler) cassette drive (at a time when floppy disks were displacing tapes as the preferred storage medium), making it technically a computer, it only offered an additional 2K of RAM, putting it ''far'' behind any ''real'' PC on the market at that time. It was further the ECS's bad luck to hit the market in the spring, as MediaNotes/TheGreatVideoGameCrashOf1983 was becoming an undeniable reality. Mattel went from aggressively hiring programmers to laying them off in one two-week period that spring; it further decided to switch its Intellivision focus from hardware to software, leaving the ECS with little marketing push behind it. The KC-ECS debacle played no small part in Mattel's decision to [[CreatorKiller discontinue Intellivision]] a year later. |
| 352 | * ''VideoGame/JaggedAlliance 3'' had a development that spanned two decades and the collapse of multiple developers. |
| 353 | ** After Creator/SirTech ceased development operations in 2003, the series ended up in the hands of Strategy First and Russian developer [=MiST=] Land South (later GFI Russia). ''[[VideoGame3DLeap Jagged Alliance 3D]]'' became mired as the two parties clashed over the game's direction, with GFI allegedly pushing for the removal of the strategic layer and turn-based combat system. In 2006, Strategy First pulled the series from them as ''3D'' was still not ready for release after two full years in development. GFI Russia would salvage the work done on ''3D'' [[DivorcedInstallment and release it as]] ''Hired Guns: The Jagged Edge''. It would be one of the last games GFI Russia would release. |
| 354 | ** Strategy First then handed the game to Russian companies Akella and F3games with a tentative release date of late 2008, but it was pushed back to 2010. While Project Manager Andrew Kazakov [[https://web.archive.org/web/20071207173351/http://www.jacenter.pl/readarticle.php?article_id=194 blamed Strategy First demanding graphical improvements]] for the delay, the 2008 financial crisis was particularly brutal to the Russian economy and likely had consequences on the game. Development fell silent in 2009 as Strategy First was also rocked by financial issues, and German site games-on-net reported that Akella had ceased development amid ongoing layoffs and unpaid work disputes. |
| 355 | ** Early in 2010, German outfit [=bitComposer=] picked the series up from Strategy First with plans to develop the third game, but news on the project fell silent shortly after. It is likely that the lukewarm receptions of ''Jagged Alliance: Back in Action'' and ''Jagged Alliance Online'' scared [=bitComposer=] off from continuing development on the third game. |
| 356 | ** In 2015, Creator/THQNordic announced that it had acquired the series but made no immediate plans. In 2021, they finally announced that the game was back in development with Bulgarian studio [[VideoGame/{{Tropico}} Haemimont]] [[VideoGame/VictorVran Games]], with a trailer showing pre-alpha gameplay footage. Unlike the prior attempts, this one wasn't stopped by troubles and it was finally released in July 2023. |
| 357 | * Development of the Platform/NintendoEntertainmentSystem port of ''Jim Power: The Lost Dimension'' was set back when licensed developer Piko Interactive tried to contact the original creator for approval, only to be met with two years of silence. Upon learning that the creator had died around the time they initially tried to contact him, Piko themselves worked to fully acquire the ''Jim Power'' IP before the game's development went back on track. |
| 358 | * ''VideoGame/JurassicParkTrespasser'': As explained in an [[http://www.gamasutra.com/view/feature/3339/postmortem_dreamworks_.php online feature]] and [[https://www.youtube.com/watch?v=k6A3SaRr26M this video]] about this [[ObviousBeta infamously botched]] 1998 FPS, ''Trespasser'' had a host of design and logistical problems that caused its design team to hastily scale it back from their initial goals. |
| 359 | ** Intended as an ambitious and immersive first-person game with groundbreaking AI and realistic physics, mismanagement plagued the game's design team from the start. The team was inexperienced and had little in the way of design documentation for the project. Issues with the engine and toolset constantly dragged down the speed of development, and the team found there were serious issues with the game's AI and physics system. |
| 360 | ** The plan to have friendly and hostile dinosaurs that dynamically reacted to the player was largely abandoned because the creatures' AI couldn't internally decide what mood to pick. The melee weapons didn't work due to issues with the physics system, so they had all their mass removed making them useless. Textures were largely scaled back because of compatibility issues between the software-based rendering and the early 3D video cards of the time. A botched licensing deal meant they couldn't use Music/JohnWilliams' iconic music in the game, so they had to create their own. The continuously delayed release and broken technical state caused the game to be dead on arrival when released, but it would inspire elements of later games such as ''VideoGame/HalfLife2'' and ''VideoGame/PeterJacksonsKingKong'' |
| 361 | * ''VisualNovel/KatawaShoujo'' is a {{freeware}} visual novel created by amateurs. It spent many years in DevelopmentHell, lost many writers, and went through several phases until it was finally released. |
| 362 | * ''VideoGame/KidIcarus1986'': Designer and artist Toru Osawa spent most of the game's development [[http://www.nintendoworldreport.com/feature/29565 working on it alone]], while the rest of Nintendo R&D1's development staff was focused on ''VideoGame/Metroid1''. After the ''Metroid'' team completed that game and returned from vacation, ''Kid Icarus'' entered three straight months of crunch and constant all-nighters in order to meet the December deadline, with Osawa even foregoing his honeymoon in the process. The game was completed a mere three days before release, with there being no time to even add a credits roll for the original Japanese FDS version. |
| 363 | * ''Franchise/TheKingOfFighters'': While most of the franchise as a whole's developments were mostly smooth sailing, some weren't, to put it lightly: |
| 364 | ** ''VideoGame/TheKingOfFighters2001'' was heavily impacted by Creator/{{SNK}} going bankrupt midway through development, forcing a skeleton crew to partner up with the South Korean company Eolith who then [[ExecutiveMeddling made many, most of them poorly received, changes to the plot and character arcs]]. The result stumbled out [[{{Sequelitis}} as one of the more negatively received mainline installments]]. |
| 365 | ** ''VideoGame/TheKingOfFightersXII'' suffered from the one-two punch of SNK Playmore [[ArtShiftedSequel deciding to completely overhaul the graphics]], which ate into a lot of the game's time and budget (it was estimated that it took 16-17 months just to complete one sprite sheet) and [[ChristmasRushed setting a strict deadline for 2009]], the [[MilestoneCelebration 15th anniversary of the series]]. Once that deadline came around, they was forced to release what they had -- which got near-universally lambasted for [[ObviousBeta being obviously unfinished]]. |
| 366 | * ''VideoGame/KingsQuestMaskOfEternity'': Right out of the starting gate, the game was to become a Action-Adventure RPG, similar to Creator/{{Sierra}}'s own ''VideoGame/QuestForGlory'' series, which was suggested by Sierra employee Mark Seibert to fill in the large empty maps of the game in-between puzzles. |
| 367 | ** This ran into [[http://www.sierragamers.com/aspx/m/634063/bbs/Topic.13499.530202 stiff opposition]] from sister company Creator/DavidsonAndAssociates, creators of the ''VideoGame/MathBlaster'' series. Founders Bob and Jan Davidson, both devout Christians, were appalled at how the game was straying from the ''VideoGame/KingsQuest'' series' ThouShaltNotKill roots. This only compounded their pre-existing disgust with Sierra over the ''VideoGame/LeisureSuitLarry'' games and ''VideoGame/{{Phantasmagoria}}'', the latter of which had been designed by Roberta Williams, co-chair of Sierra and the writer and designer of ''Mask of Eternity''. The Davidsons coerced CUC Software, the company that owned both Sierra and Davidson & Associates at the time, into giving them permission to make their own Christian-friendly version of ''Mask of Eternity'', which would remove any and all violence and combat, ironically making it more like a standard ''King's Quest'' game. |
| 368 | ** Upon hearing this news, Williams felt like she was losing control over ''her'' game. She became adamant about her needing to work on it, and almost threatened to quit the game altogether. This changed when Davidson & Associates went out of business, meaning their version of the game was canceled. With their deadline steadily approaching, Roberta bounced back full force and helped salvage what was left of their game, but it wasn't good enough as it ended up being the last game she would ever work on, and would be one of the last adventure games made by Sierra. |
| 369 | * ''VideoGame/KingdomsOfAmalurReckoning'' is a particularly extreme example. The game as it was showed great promise, and in fact ended up selling over a million copies, but due to either extreme overconfidence or extreme shortsightedness, developer 38 Studios borrowed money left and right from the state of Rhode Island, ultimately racking up a ''75 million dollar'' debt. They were apparently confident that they would be able to pay back all the loans with the game's sales, as well as the sales of an then-planned MMO, but it then turned out that the game would have had to sell 3 million copies just to ''break even''. Long story short, 38's financial situation imploded, they went bankrupt, and all their assets, including the ''Amalur'' IP, were seized by the State of Rhode Island. |
| 370 | ** The head of that company was famous Boston Red Sox pitcher Curt Schilling, who traded heavily on his celebrity in convincing Rhode Island to suspend their own funding rules to loan his company more money. Not that RI necessarily needed convincing; the state at the time had one of the five highest unemployment rate in America; the promise of a major high-tech firm bolstering their economy must have been very easy to get excited about. RI's long rivalry with Massachusetts may also have played a role: here was one of Boston's star sons offering to bring his business to Providence. |
| 371 | ** The ''New York Times'' did [[http://www.nytimes.com/2013/04/21/business/curt-schilling-rhode-island-and-the-fall-of-38-studios.html a long story]] about this. RI governor Lincoln Chafee had not endeared himself to Schilling when, as a candidate while the state was doing the deal, he dared to repeat insinuations that Schilling had put red paint on his sock himself rather than actually bleeding during the most famous game of his career. While he tried to make up after he was elected, Schilling still resents that. |
| 372 | ** Schilling was probably out of his depth with his ambitious plans for the game. A complex multilevel PVE game is challenging to develop even for an established game maker with a success of exactly that type. He hired Creator/RASalvatore to create a 10,000-year backstory for the game, for which Salvatore has yet to get paid any of the $2 million he's owed. One of 38's original executives said he had tried to convince Schilling to develop and release the game in stages, rather than "trying to build a skyscraper on the side and then stand it up." |
| 373 | ** Schilling paid very generous salaries... by his estimate, the average pay at 38 was $86,000. The company went so far as to pick up the mortgage payments on its employees' unsold Boston-area homes if they moved closer to Providence. And since the state had made the investment to create jobs, 38 ultimately hired 400 people — a lot for a new game developer with only one title out. |
| 374 | ** In the end, everybody got hurt. Over three hundred people were let go from the jobs Rhode Island wanted so badly. Schilling claims to have lost his fortune from his baseball career, and had to auction the bloody sock. Schilling would take a position at ESPN as sports analyst until he was fired in 2016 for unacceptable conduct. Chafee announced [[http://www.providencejournal.com/breaking-news/content/20130904-r.i.-governor-chafee-will-not-seek-re-election.ece he would not run for another term]]. The state launched a criminal investigation into Schilling and 38 Games on suspicion of fraud, though [[https://www.eurogamer.net/articles/2016-09-23-four-years-later-the-kingdoms-of-amalur-court-case-comes-to-an-end the investigation found no criminal acts]]. The parties involved ultimately came to out-of-court settlements. |
| 375 | [[/folder]] |
| 376 | |
| 377 | [[folder:L-M]] |
| 378 | * ''VideoGame/{{Lair}}'' went through a variety of issues during development, [[https://www.polygon.com/features/2018/1/17/16886514/lair-what-went-wrong including but not limited to]] the following: the ill-advised decision to scrap all of Factor 5's previous development tools for the making of the game (which was called the single biggest mistake on the project by Factor 5's Julien Eggebrecht), Factor 5 greatly underestimating the work needed to optimize the game for the Playstation 3 hardware, the game's lead designer (and Factor 5 president) going through a rough patch in his life and growing increasingly irritable and emotional at the rest of the team, conflict over the game's direction (with Julien Eggebretch wanting a very fast-paced game more in the style of the developer's previous work on ''Rogue Squadron'' and others wanting a slower-paced experience that would better showcase the [=PS3=] hardware), a buggy and crash-prone level editor, feature creep... and most infamously, Sony's decision to impose [[ExecutiveMeddling a motion control-only scheme]] to promote the Sixaxis when the ''VideoGame/{{Warhawk}}'' team refused to do likewise in their own game, and the company's poor attempt at damage control when the controls predictably became the most contentious aspect of the game. |
| 379 | * [[http://hardcoregaming101.net/lastactionhero/lastactionhero.htm Two]] [[http://www.mobygames.com/game/snes/last-action-hero developers]] claim this happened to the infamous ''VideoGame/LastActionHero'' licensed game. After the planning stage, word from a lawyer came that Creator/ArnoldSchwarzenegger did not want to be "associated with violence" due to his then-recent involvement in family friendly comedies, and that the game could not feature him using firearms, completely ruining the original concept. This led to the game being hastily retooled as the deadline was fixed with no chance for extension. Communication with the legal department was exceptionally slow, leading to the developers being clueless on even basic questions such as whether or not Arnold's character ''could even punch anything'', and the development of the PC version ground to an halt after the graphic artist refused to do work because of an unrelated payment issue with the publisher. |
| 380 | * ''VideoGame/TheLastOfUsPartII'' was the highly anticipated follow-up to one of the [[VideoGame/TheLastOfUs most acclaimed titles of all time]], but became one of the most controversial titles of 2020 in part due to the management issues of Creator/NaughtyDog and a massive ContentLeak spoiling the game's major plot twists months in advance. |
| 381 | ** The marketing of the game was the first to attract attention, as marketing focused heavily on brutally realistic human-on-human violence and on Ellie's romantic relationship with a woman; The former was called out by some critics as snuff film-like (not helped when director Neil Druckmann [[https://www.gamesradar.com/we-dont-use-the-word-fun-says-the-last-of-us-2-director-neil-druckmann/ admitted]] that the team watched "uncomfortable" videos to ensure the violence was as realistic as possible), while the latter attracted a score of homophobic commentators who accused the studio of "pushing an agenda". Repeated delays also hit the game; Initially set for February 21, 2020, it slipped to May 29, 2020 before being [[https://twitter.com/PlayStation/status/1245773000592384001 delayed indefinitely]] that year due to the UsefulNotes/COVID19Pandemic. |
| 382 | ** In March 2020, [[https://kotaku.com/as-naughty-dog-crunches-on-the-last-of-us-ii-developer-1842289962 Jason Schreier]] did a report on the intense crunch conditions that had become commonplace at the studio, pointing out that the rate of turnover was high enough that of the twenty non-gameplay leads of ''VideoGame/Uncharted4AThiefsEnd'', 70% had left. Script changes were causing problems late into development; playtesters were finding characters unlikable while Naughty Dog's tradition of not using managers meant that developers were working on art assets for weeks at a time, only to find a change in the script had made their work irrelevant. Both factors were resulting in the long development time and constant delays that had marked production. |
| 383 | ** Shortly after the report went public, former Naughty Dog employee Jonathan Cooper [[https://www.tweaktown.com/news/71212/naughty-dog-is-no-longer-the-best-animator-hospitalized-from-crunch/index.html claimed]] that Naughty Dog's reputation is so bad in Los Angeles that the studio found it "nigh-impossible" to hire game animators, forcing them to hire workers from the film industry. At least one employee was so overworked during the creation of the September 2019 demo that they had to be hospitalized - an occurrence that was not uncommon at the studio during crunch. By Cooper's estimation, development took over a year later than it should have due to the high turnover. Poorly redacted court documents submitted as part of Sony's court battles with Microsoft over their buyout of Activision-Blizzard in 2023 [[https://www.ign.com/articles/the-last-of-us-2-and-horizon-forbidden-wests-budgets-revealed-ftc-documents revealed that the troubles swelled the game's budget to over $200 million]], making it one of the most expensive games ever made. |
| 384 | ** Things got worse in April of 2020 when a massive ContentLeak occurred through a data breach attack on Naughty Dog's servers. The leak was posted onto a [=YouTube=] channel that contained cutscene and gameplay footage from a near-final development build of the game, spoiling several major plot points (including and '''especially''' [[spoiler:the [[CruelAndUnusualDeath brutal and horrific]] [[TheHeroDies death of Joel]], the protagonist of the first game]]). These plot points were met with derision by a large portion of the fanbase and were quickly subjected to MemeticMutation across the internet, while various alt-right figures attempted to stir further outrage with transphobic and misogynistic fabrications. Within a day of the leak, Sony and Naughty Dog [[https://blog.us.playstation.com/2020/04/27/release-date-updates-for-the-last-of-us-part-ii-ghost-of-tsushima/ suddenly announced]] that the game would release on June 19, 2020, likely in an attempt to mitigate the impact of spoilers.. |
| 385 | ** In an attempt to stem the tide of spoilers flowing out from the leak, Sony and Naughty Dog used a third-party company (MUSO) to send waves of DMCA's targeting not just reuploads of the leaked content, but also anything so much as discussing or referencing the leak. This caused numerous [=YouTube=] channels to rack up copyright strikes for merely stating that the leak had occurred with no discussion of the content at all, and Sony's ''own Tweet'' advertising the game was hit with a DMCA. This heavy-handed attempt at damage control only served to [[StreisandEffect drive more of the unaware to look into the leaks]], and further fueled resentment against both Sony and Naughty Dog. |
| 386 | ** When the game finally released in June 2020, critics greeted it with open arms. Many gave perfect scores and some went as far as comparing it to highly regarded classic works of cinema such as ''Film/CitizenKane'' and ''Film/SchindlersList'', but others such as Polygon and Kotaku were more reserved in their praise, leveling criticism at the story's pacing and characters. Fan reception was mixed to say the least, with some agreeing with the praise and others outraged, and the work's Metacritic page was subjected to a bombardment of negative user reviews (many of which were from members of the alt-right angry over the game prominently featuring multiple [=LGBT=] characters and people of color). HypeBacklash and the reports of harsh crunch may have also contributed to the outrage, while the ongoing COVID-19 pandemic and widespread social unrest caused some to dismiss it [[AngstAversion for its excessively bleak tone]] [[RealitySubtext in an already depressing and tragic year]]. Nevertheless, it quickly become [[https://twitter.com/MatPiscatella/status/1284109173601366016?s=19 one of the best-selling games of 2020]] and swept The Game Awards in 2020, winning seven awards including Game of the Year. |
| 387 | * ''VideoGame/TheLegendOfHeroesTrailsInTheSky'' was a knockout hit in Japan and [[http://kotaku.com/the-curse-of-kiseki-how-one-of-japans-biggest-rpgs-bar-1740055631 a porting nightmare in the United States]]. Over three million characters of Japanese text, deathmarch hours, subcontracting difficulties, incompatible formats, and Falcom threatening to pull out resulted in ''[[http://www.carpefulgur.com/drakblog/?p=53 a suicide attempt]]'' and a great deal of lost weight among those working on it. Fortunately, the story seems to have had a happy ending so far. Falcom would ultimately become fed up with how long [=XSeed=]'s translations for the series took and stripped the localization rights of both the series ''and'' ''Ys'' from them in favor of NISA, who promised quicker translations of the same quality. |
| 388 | * ''VideoGame/LegoStarWars: The Skywalker Saga'' faced serious complications in its development, starting with the fact that it was made in the midst of the COVID-19 pandemic and that determined how much work could actually be done, with many developers working remotely for a considerable part of the development cycle. The game also was made on a completely different engine than the others, which likely led to further bugs and issues that needed to be resolved. These elements necessitated various delays in order to fix things. And this is on top of other, years-long issues at TT Games [[https://www.polygon.com/features/22891555/lego-star-wars-the-skywalker-saga-has-led-to-extensive-crunch-at-tt-games including extensive crunch time.]] |
| 389 | * ''VideoGame/TheLegendOfZeldaSkywardSword'' owes its late arrival in the Platform/{{Wii}}'s lifespan and smaller world compared to then-recent ''Franchise/TheLegendOfZelda'' games (especially ''VideoGame/TheLegendOfZeldaTwilightPrincess'') to a troubled development cycle on account of difficulties with the Wii [=MotionPlus=] accessory. Pre-development began in 2006 soon after ''Twilight Princess'', but during this phase Creator/ShigeruMiyamoto [[https://www.vg247.com/miyamoto-skyward-swords-development-more-like-three-years noted]] that some on the team didn't want to make a new ''Zelda'' game due to a lack of interesting ideas and an unwillingness from anyone to direct the game. This came to an end when Hidemaro Fujibayashi[[note]]A longtime director of many of the handheld ''Zelda'' games starting with the ''[[VideoGame/TheLegendOfZeldaOracleGames Oracle]]'' duology[[/note]] [[https://iwataasks.nintendo.com/interviews/wii/zelda-skyward-sword/0/0 proposed his idea]] to use the in-development [=MotionPlus=] accessory to realize fully motion-controlled swordfighting, which would earn him the director's seat on his first home console ''Zelda''. However, the team found the accessory to be very "unruly", finding it hard to work with and the mood of the team becoming "very nasty" at one point. Creator/EijiAonuma eventually decided to give up and abandon the [=MotionPlus=], but the release of ''VideoGame/WiiSportsResort'' (the first game to use the accessory) and pressure from others within Nintendo forced the team to return to it. This left the team with only a year and a half to actually develop the game, and there were debates about the game's direction during development as well. At the time of its release near the end of 2011, the game had taken the longest of any ''The Legend of Zelda'' game up to that point to go from planning to release. The released game would be a critical success, but would sell the lowest of the [=3D=] ''Zelda'' games (albeit still multiple millions), and would be extremely controversial in the fanbase for its linear structure, heavy backtracking, and handholding companion and hint system. |
| 390 | * The Platform/SegaSaturn game for ''Manga/MagicKnightRayearth'' was initially listed as one of the first games for the system. It didn't show up in the U.S. until three years after the Japanese release and ''six months'' after support for the system came to an end, effectively being the last North American Saturn game. What caused this game from Creator/WorkingDesigns to fall this far down? Numerous problems, including: |
| 391 | ** The usual need to translate and dub the voice bits from Japanese to English. |
| 392 | ** The computer holding the data for the game crashing, forcing them to rebuild pieces of it. |
| 393 | ** A fight between WD and Sega over what to name the main heroines (Sega had realized ''Rayearth'' was a good enough series to franchise to the States. However, as it was common at the time, [[DubNameChange they wanted to give them English names]]. Both Sega and WD had different names for the girls before they both threw their arms into the air and left them Hikaru, Umi and Fuu.) |
| 394 | ** And after it was all done, then-current Sega head honcho Bernie Stolar's draconian policy against third party developers kicked in, leaving them high and dry until the Saturn was dead in the water. |
| 395 | * ''Marvel'' aka ''Marvel: Chaos'', the cancelled Franchise/MarvelUniverse fighting game from Creator/ElectronicArts, was plagued with problems from Day 1: |
| 396 | ** The creative team initially wanted to use an analog control style, similar to the company's successful ''Fight Night'' and ''[[VideoGame/DefJamSeries Def Jam]]'' series. Unfortunately, while an analog control scheme worked well for games about boxing or street fighting, it quickly proved insufficient for a game featuring a wide range of superpowered attacks. |
| 397 | ** EA was interested in a more realistic visual style, with Comicbook/SpiderMan sporting a very scrawny physique to highlight his youthfulness, Comicbook/{{Wolverine}} appearing even more bestial and disheveled than usual, Comicbook/DoctorDoom wearing a tank-like suit of PoweredArmor, and Comicbook/TheIncredibleHulk having a bulkier, almost overweight appearance. Marvel strongly objected to these creative liberties, forcing EA to go with more traditional designs instead. |
| 398 | ** One of the major selling points for the game was that unlike past fighting games such as the ''VideoGame/MarvelVsCapcom'' series or ''VideoGame/XMenNextDimension'', ''Marvel'' would take place in a sprawling, open world environment that could be interacted with. Characters could cause damage to the surrounding city, and use objects like cars and street signs as weapons. While groundbreaking in theory, the idea proved horrendously challenging to implement, with the main problem being that huge arenas made it difficult for the characters to get close enough to each other to ''actually fight''. |
| 399 | -->'''Michael Mendheim''': When you are in a big play environment, and say you have the Thing over here and Beast over there, and they're two blocks away — they're just kind of running towards each other on a street. It wasn't very compelling. |
| 400 | ** Another idea was that the environments would feature interactive crowds of civilians who could participate in the fight. For instance, if one player rescued some civilians, the civilians might repay the favor by attacking the player's opponent. Similarly, causing damage to the surrounding area could provoke attacks from the police or military. It quickly proved difficult to actually include as many bystanders as the developers wanted, and the creative team soon realized that the AI required for such a feature would be incredibly complex. Some members of the team also found the idea distracting, especially given how fighting games are known for being fast-paced and tense. The concept was ultimately scrapped. |
| 401 | ** Because of the success of ''Fight Night 3'', the employees at EA Chicago were feeling very confident and adventurous, which meant that very few people involved with ''Marvel'' were willing to make decisions to limit the scope of the game, despite it rapidly becoming obvious that many of the original ideas were completely unfeasible in practice. |
| 402 | ** The game lacked any sort of story mode to explain ''why'' any of these characters were fighting each other, and plans to include a plot based on ''Comicbook/WorldWarHulk'' or a Skrull invasion proved fruitless. While the fighting system was improving, the staff admitted that they hadn't yet come up with any sort of motivation to move the players from one battle to the next. |
| 403 | ** Adding to the existing problems was that EA Chicago had then-recently moved into a brand new studio in an expensive downtown neighborhood, which greatly increased overhead costs. This, combined with a massive staff increase and the failure of ''Def Jam: Icon'', greatly hurt EA Chicago's profitability in the eyes of its parent company. Around this same time, EA also began cutting back on the number of licensed games it produced, beginning with them dropping the ''Def Jam'' franchise. A combination of these factors led to EA closing its Chicago branch and cancelling ''Marvel'', ending the company's partnership with Marvel Entertainment. |
| 404 | * According to [[https://www.youtube.com/watch?v=3kanICweLFM this video]], ''VideoGame/MarvelVsCapcomInfinite'' went through all sorts of tribulations: |
| 405 | ** Capcom [[ExecutiveMeddling slashed the game's intended budget]] in half, which caused a major downgrade in [[SpecialEffectsFailure model quality, cutscene animation and gameplay features]], and the other half went into ''VideoGame/StreetFighterV'' DLC. |
| 406 | ** To cut costs, the developers had to reuse the Capcom characters' models from ''VideoGame/MarvelVsCapcom3'' and older games they were in, which meant that the ''[=MvC3=]'' models had to be reshaded to fit in with ''Infinite''[='=]s art style and engine. This quickly led to criticism from fans and reviewers, as many of the cartoonish and exaggerated older models didn't mesh well with the more realistic, movie-inspired visual design of ''Infinite''. |
| 407 | ** Marvel gave some ExecutiveMeddling of their own, refusing the use of ComicBook/XMen and ComicBook/FantasticFour characters because their film rights were controlled by Creator/TwentiethCenturyFox at the time. The absence of fan favorites like ComicBook/{{Wolverine}}, ComicBook/{{Magneto}}, ComicBook/{{Storm|MarvelComics}} and ComicBook/DoctorDoom did not go unnoticed, and got major fan backlash and bad publicity. |
| 408 | ** All of this caused Capcom employees to become [[CreatorBacklash extremely disappointed in the product]], while the higher-ups wouldn't have any concerns with the game until fans started reacting really negatively to the graphics and models on social media (in particular Chun-Li's model, which ended up being reworked on before the game shipped, to better reception). The higher-ups also forced ComicBook/BlackPanther and VideoGame/MonsterHunter to become paid DLC characters, despite having already been completed and meant for the final game (with both characters showing up fully voiced in the story mode). |
| 409 | ** As a result of the game selling below expectations, planned DLC support was pulled after only one season. According to rumors, the premature cancellation meant that new characters who were already being worked on by the staff, such as [[Comicbook/MsMarvel2014 Ms. Marvel]], [[VideoGame/StreetFighterIII Gill]], Comicbook/StarLord and [[VideoGame/AsurasWrath Asura]], ended up being scrapped. Data mining subsequent revealed that a total of 61 characters were planned, with only 36 ever actually making it into the game. |
| 410 | * Believe it or not, a freaking ''baseball game'' fell victim to this trope! ''Major League Baseball Featuring Ken Griffey Jr.'', a spiritual successor to ''Ken Griffey Jr.'s Winning Run'' on the Super NES, was supposed to be released in late-1996. However, the game was delayed left and right before finally being released in May of 1998. By which time its graphics and gameplay were ultimately surpassed by Acclaim's ''All Star Baseball 99''. |
| 411 | * While it didn't apparently face the time crunch and staff conflicts other entries on this page did, the development of the Platform/NeoGeo launch title ''VideoGame/MagicianLord'' was hectic, as detailed in [[https://www.youtube.com/watch?v=wIWKJhRtdco a video]] by the French [=YouTube=] show ''Retro Games Test''. As the game developed alongside the Neo Geo hardware itself, features were constantly in flux and the developers wound up having to scale down their ambitious plans for dozens of transformations and advanced graphical effects due to the pressure to release the game alongside the system's launch and hardware features like zoom and rotation being cut to save costs. Another issue was when the game was location-tested and ADK found out that the game was far too easy, and thus unprofitable as an arcade game, as the large maze-like levels and generous health allotment meant players were able to survive for much longer than the average arcade game. As this was a few weeks before release, the developers responded by cutting the player's lifebar by half and haphazardly removing large chunks of the levels (the last-minute nature of the change is exemplified by the fact, that using a double jump exploits, players can go out of bound in the first level and find unused graphics for the original "large" version of the level and stand on invisible platforms that had their graphics removed but not the collision detection). This change ended up working perhaps a little too well, as the final release is a shining example of NintendoHard and an ADK employee was only able to one-credit it more than a year after release. In the end, ''Magician Lord'' [[VindicatedByCable flopped in the arcades but saw better sales on the home console]] and became something of a CultClassic among early adopters of the Neo Geo. |
| 412 | * The lead-up to the development of ''VideoGame/MarioPlusRabbidsKingdomBattle'' was [[https://www.eurogamer.net/articles/2018-01-11-the-pitch-that-convinced-miyamoto-to-back-mario-rabbids not the smoothest]]. Ubisoft wanted to revitalize the ''Rabbids'' franchise after a strings of poorly-received games and tasked Ubisoft Milan's newly-promoted creative director Davide Soliani to create a pitch for a new ''Rabbids'' game that could potentially be shown to Nintendo. However, as Ubisoft Milan was already busy with assisting the development of ''VideoGame/GhostReconWildlands'', Soliani was only given a tiny team of designers and they had to hire a junior programmer with no experience in video games to code the prototype - which turned out to be timely when management told him they would show a prototype to ''Creator/ShigeruMiyamoto'' in three weeks and a half. After Miyamoto responded positively to it, the team's resources were increased slightly for the purpose of making a second prototype over the next three months, but some employees had to split their work between it and ''Ghost Recon'' and Davide Soliani was so overworked that he went to the hospital as he was fearing having an heart attack (after being told there was nothing wrong with him but that he had to chill for the sake of his health, Soliani would promptly go back to work). Fortunately, it seems development on the actual game was far smoother, sans a period of diminished morale caused not by actual production woes but poor response on the internet to [[ContentLeak leaked documents]] about the title. |
| 413 | * ''VideoGame/MartianGothicUnification'', a SurvivalHorror game developed by Creative Reality, suffered from this according to [[https://web.archive.org/web/20160822202458/http://retroactionmagazine.com/retroactionextra/stephen-marley-talks-martian-gothic an interview]] with director Stephen Marley. In short, the ambitious scope of the project proved too much for the seven-person team and their tight deadlines. Numerous scenes and gameplay elements, including puzzle hints and the final boss fight, were cut for time. ExecutiveMeddling demanded that the PC and Playstation versions be identical in content, which prevented the PC version from receiving additional content. The casting agency also went against the wishes of the developers and cast a white voice actor for a black character, despite having reassured the team they would not do so. The game received mixed reviews and underperformed in sales, and Marley expressed regret over how the final product turned out. |
| 414 | * ''VideoGame/MassEffect3'' suffered a hectic development that had serious implications for [=BioWare=] going forward. |
| 415 | ** Like ''VideoGame/DragonAge2'', the team was given only 18 months of development time as Creator/ElectronicArts was eager to capitalize on [=BioWare=]'s [[VideoGame/MassEffect1 string]] [[VideoGame/MassEffect2 of]] [[VideoGame/DragonAgeOrigins successes]] immediately. While EA was eventually convinced to delay the game by three months to March 2012, the team was crunching around the clock regardless. A plot script [[ContentLeak mistakenly included in the August 2011 public demo]] confirms the team had to cut significant amounts of content to make their deadline, while Geoff Keighley's ''The Final Hours of Mass Effect 3'' shows that the endings were so rushed that the lead writer was hastily writing them down on napkins during lunch breaks. On release, the rushed endings ignited a fan backlash so intense that it led [=BioWare=] to quickly produce a free Extended Cut DLC to address it, which according to former [=BioWare=] developers interviewed in [[https://www.youtube.com/watch?v=nhtgjmkcht8 this video]] from People Make Games, led to '''even more''' crunch development for the exhausted team. |
| 416 | ** While the game was overall among the company's biggest successes in terms of sales and the Extended Cut quelled the worst of the fan backlash, [=BioWare=]'s [[VideoGame/DragonAgeInquisition next]] [[VideoGame/MassEffectAndromeda three]] [[VideoGame/Anthem2019 games]] would have productions just as troubled or even more troubled than ''Mass Effect 3'' despite having more development time. [=BioWare=] co-founders Ray Muzyka and Greg Zeschuk retired from the industry shortly after the game's release, with Zeschuk alluding to EA's growing influence over the company as a factor during his retirement speech. The ending backlash was also one of several controversies to hit EA that led to the resignation of EA CEO John Riccitello in 2013. |
| 417 | * As detailed in [[https://kotaku.com/the-story-behind-mass-effect-andromedas-troubled-five-1795886428 this article]], most of the problems that made ''VideoGame/MassEffectAndromeda'' fall short of its high expectations can be traced back to its turbulent development history, most of which can in turn be attributed to [[ExecutiveMeddling the mandated use]] of the Frostbite engine. While a very powerful engine and the mandate was intended to simplify development across Electronic Arts' various studios, it simply wasn't designed for building [=RPGs=] and thus lacked many features considered crucial for this genre. Figuring out how to build a ''Franchise/MassEffect'' game on Frostbite tied up so many resources that for a long time it wasn't even clear how ''ME:A'''s gameplay would look. The team realized that their ideas, like a free-roaming procedural system, were too ambitious to handle, throwing out years of effort. A lot of components (motion capture, facial animations, etc.) were outsourced to dozens of studios all over the world, many of which couldn't work efficiently because they also didn't know which direction the game was going. Throughout the course of development, multiple members of the team disliked the game's main plot of the Council's races travelling to a foreign galaxy to carve out a new home as many felt it glorified imperial colonialism (this is somewhat acknowledged in the game), but their concerns were either curtly shut down or ignored entirely. Of the five years the game was in development, only the final 18 months were spent on actually building the game. It was a small miracle ''ME:A'' was released in largely working condition at all. |
| 418 | * ''Mega Man Universe'' was announced as a side-scrolling ''Franchise/MegaMan'' spin-off with a level editor. It was cancelled after a murderer's row of [[https://www.rockman-corner.com/2021/08/how-overambition-and-mismanagement.html production troubles]], mostly chalked up to poor management by Creator/KeijiInafune. |
| 419 | ** The game was announced at the New York Comic-Con in July 2010 without a concept in stone. Internally, it juggled between a ''VideoGame/MegaMan2'' remake and a level creation platform (like ''VideoGame/SuperMarioMaker'' after it), until Keiji Inafune settled on the latter. Inafune ultimately envisioned ''Universe'' as an ambitious DLC-driven live service game with new officially-released levels and tons of OfficialFanSubmittedContent, to the point he no longer saw a need for "traditional" ''Mega Man'' games. |
| 420 | ** Unfortunately, a playable demo at New York Comic-Con [[TaintedByThePreview failed to impress]]. Whoever played it was let down by the subpar graphics and controls, and most fans were left ''livid'' by the sudden ArtShift towards a style influenced by Creator/CartoonNetwork shows. However, Inafune's mind was made up, and the new art style stayed while the dev team focused on graphical fidelity. |
| 421 | ** As ''Universe''[='=]s scope grew to include a two-player co-op mode, Inafune had the game outsourced to a third-party studio. Unfortunately, to save costs, he chose a studio that had '''no''' experience with home consoles or online networking; as a result, the online co-op didn't work at all. |
| 422 | ** In October 2010, Inafune announced he was leaving Capcom. ''Universe''[='=]s development became completely disorganized, without a real director to call the shots (but with help from producer Akiko Ito). With a Spring 2011 release window set in stone, the studio dropped the co-op mode, but was still unprepared to handle ''Universe''[='=]s ambitious scope. |
| 423 | ** Capcom tried to salvage what remained of the game by reassigning development to Capcom's in-house studios and changing platforms to [[MobilePhoneGame iPhone and iPad]], scrapping the level editor, and leaning even more heavily into its origins as a ''Mega Man 2'' remake. Even ''that'' didn't work, and ''Universe'' was officially [[https://web.archive.org/web/20110331060908/https://www.capcom.co.jp/megaman_universe/ cancelled in March 31, 2011]]. |
| 424 | * ''VideoGame/MetalGearSolid2SonsOfLiberty'' suffered a rushed development in order to try getting the game out in time for [[MeaningfulReleaseDate the Chinese Year of the Snake]]. But the biggest problem was the September 11th attacks happening just '''three''' days before the game's intended release date. The fact that the game's climax involved Lower Manhattan in New York City getting devastated and appearances of the World Trade Center (which ironically went untouched in the original script) caused the game to be delayed by a few months. The climax had to be hastily edited [[DistancedFromCurrentEvents to avoid controversy]], contributing to the infamous GainaxEnding. |
| 425 | * ''VideoGame/MetalGearSolidVThePhantomPain'' was intended to be series creator Creator/HideoKojima's masterpiece, but it also marked the end of an era, as it was his final project for Creator/{{Konami}} due to a contentious production. |
| 426 | ** Despite the game's auspicious reveal (with the main game being announced only by its subtitle and helmed by a "Moby Dick Studios", a fake name for Kojima Productions), the project faced controversy immediately when it came to light that long-time Solid Snake/Big Boss voice actor Creator/DavidHayter was unceremoniously fired in favor of actor Creator/KieferSutherland (who also provided facial capture for the Big Boss character). While it was suggested that Kojima did so in order to avoid paying a higher salary for Hayter, the latter contends that he was never approached about the issue and still harbors resentment. |
| 427 | ** In March 2015, it came to light that Konami restructured their corporate offices, with Kojima apparently out of the company as a permanent employee and his production studio intended to be disbanded at the end of ''Phantom Pain's'' production. This was followed by Kojima's name and company being removed from all marketing materials, including the final cover art for the game and future releases of ''Ground Zeroes'' and ''The Legacy Collection''. Over the next few months, several people (including voice actress/singer Donna Burke, composer Rika Muranaka and Creator/AkioOtsuka, Snake's Japanese voice actor) publicly spoke out against Konami for their poor treatment of Kojima. This also resulted in the cancellation of ''VideoGame/SilentHills''. |
| 428 | ** In April 2015, an online movement began to express questions about the likeness of a doctor featured in one of the trailers to real-life neurosurgeon Sergio Canavero, who was believed to be part of a viral marketing campaign for the game. In response, Canavero denied any involvement with the project and decided to sue Konami for an unauthorized use of his likeness. |
| 429 | ** Several months later, the Japanese newspaper Nikkei put out [[https://asia.nikkei.com/magazine/20150813-THE-SCARS-OF-WORLD-WAR-ll/Tech-Science/Gamers-dismayed-as-Konami-cuts-off-developers?n_cid=NARAN012 a damning exposé]] on the circumstances behind the game's development. It was reported that Kojima became a pariah because ''The Phantom Pain'' was delayed, leading to its production budget exceeding $80 million USD by April 2015. It was also revealed that Konami's executives had refocused their efforts towards mobile games; pachinko machines; and health spas, and had an iron grip over Kojima Productions — now renamed "Production Development No. 8". Employees were reportedly [[SinisterSurveillance monitored on social media and on emails]], publicly shamed if their lunch breaks went on too long, and [[ReassignedToAntarctica demoted to menial tasks]] for perceived mistakes. |
| 430 | ** When the game finally came out, it was immediately bombarded with universal acclaim... with the exception of a notoriously DisappointingLastLevel, with several promised features not coming to fruition, the game's TwistEnding revealed suddenly and out of context, and the game's TrueFinalBoss deleted and reduced to unfinished cutscene footage as a special edition Blu-Ray extra. A third chapter of the game appears to have been cut when it became apparent that the game was not going to break even for Konami. It's rumored that the game has become a CreatorKiller for Konami's AAA game production, though the company has publicly denied this. |
| 431 | * ''VideoGame/MetalSlug'': |
| 432 | ** ''Metal Slug 5'' was originally being developed by Noise Factory (who handled ''4'') and was almost done, until SNK took over late in development and revamped the entire thing. Unfortunately, they were also forced to rush the game out prematurely in order to begin development of ''6'' for the upcoming Atomiswave arcade board, and as a result, a lot of stuff got cut out such as a large turtle-like mech and the native zapped by lightning at the beginning acting as the final boss on a levitating, laser-blasting pillar. All the stuff that was left out can be found [[http://randomhoohaas.flyingomelette.com/msmia/ here]]. For what it's worth, some of them do eventually get their time to shine in the mobile games ''VideoGame/MetalSlugDefense'' and ''[[VideoGame/MetalSlugAttack Attack]]''. |
| 433 | ** A GBA port of the first ''Metal Slug'' was also being made, but was criticized during development demos for poor implementation and was eventually cancelled due to memory limitations alongside planned ports of ''2'' and ''3''[[note]]That, and the fact that ''[[CompilationRerelease Metal Slug Anthology]]'' was also being released probably didn't help matters.[[/note]]. |
| 434 | * ''Franchise/{{Metroid}}'': |
| 435 | ** The development of ''VideoGame/MetroidPrime'' (as detailed in [[https://www.polygon.com/2018/5/29/17386066/the-rocky-story-of-retro-studios-before-metroid-prime this article by Polygon]]) was an absolute mess. Even foregoing Creator/RetroStudios's troubled beginnings that prompted a frustrated Creator/{{Nintendo}} and Creator/ShigeruMiyamoto to throw out everything they were working on and lay off multiple employees, ''Prime 1'''s development was a stressful time. At a certain point, the Japanese crew was spending most of their year in America overseeing the game, while Retro staffers would spend that same year pulling all-nighters, working 80-100 hours a week and nourishing themselves on [[ChocolateFrostedSugarBombs atomic fireball candy]] ([[http://wii.ign.com/articles/101/1016511p4.html going through a total of 72 gallons worth]]). In the words of one artist: "I think it took us almost six months to do the first level that Nintendo approved, then we had less than a year to do the rest of the game." While the end result remains one of the most critically acclaimed and commercially successful entries in the franchise, the aforementioned work conditions and the aftermath of studio heads hogging the bulk of royalty payments to themselves still led to some staff jumping ship, forcing Nintendo to step in once again to replace company head Steve Barcia with Michael Kelbaugh. And this is even without mentioning how the founder of Retro Studios, Jeff Spangenberg, was doing absolutely nothing in terms of development or even general management, instead preferring to spend his time partying and running a porn website ''on computers that Nintendo paid for''. Needless to say, when Nintendo found out about Spangenberg's escapades, they bought out his share of the company and force him to resign. |
| 436 | ** ''VideoGame/MetroidDread'' was considered {{Vaporware}} for almost sixteen years. While never officially announced until 2021, the game's existence was leaked to the press shortly after it started development in 2005 for the Platform/NintendoDS. However, it would be cancelled quickly after due to series producer Yoshio Sakamoto being displeased with the technical power of the hardware. Development would begin anew in 2008 (presumably for the handheld's more powerful [=DSi=] revision), but was once again cancelled for the same reason. It wasn't until Sakamoto worked with Creator/MercurySteam to develop ''VideoGame/MetroidSamusReturns'' that ''Dread'' was revived, with the positive reception of ''Samus Returns'' and his own satisfaction with their work inspiring him to revisit the concept once again. Unfortunately, once the game restarted development in 2018, it suffered a number of production woes. [[https://www.anaitgames.com/articulos/mercurysteam-empleados-condiciones-trabajo This article]] details the production problems, with an English translation [[https://famiboards.com/threads/metroid-dread-dev-issues-cut-content-salary-punishments-and-more-at-mercurysteam.424/#post-27194 here]]. In short, many of the employees at [=MercurySteam=] were undervalued by higher-ups and [[WeHaveReserves treated as expendable drones]] [[GeorgeJetsonJobSecurity that were fired for the]] [[DisproportionateRetribution slimmest of infractions]]. This led to more than 50 staff members [[UncreditedRole not receiving proper credit]] for the finished game, due to [=MercurySteam=]'s policies only crediting those who worked for at least 25% of development time. Mismanagement of the project also resulted in tons of content needing to be scrapped to meet deadlines, though said decision was also thankfully the result of both Nintendo and [=MercurySteam=] adamantly refusing to force staff to crunch to make up for lost time (which employees viewed as a godsend for their physical and mental health). Despite the poor working environment, just like ''Prime'', ''Metroid Dread'' quickly became one of the most successful games in the franchise. |
| 437 | * ''VideoGame/MightyNo9'' was originally meant as a spiritual successor to the Classic ''Franchise/MegaMan'' franchise by series co-creator and main producer Creator/KeijiInafune. However, a combination of big promises, a slashed budget, and a desire for it to ''immediately'' become a franchise as large as ''Mega Man'' led to a slow and troubled development. None of this was helped by one of these big promises being to bring the game to ''all ten major gaming platforms'' of the time. After multiple delays, most versions were released in mid-2016; on top of the game being critically lambasted, the launch was plagued with multiple counts of backers receiving broken keys or receiving DLC keys instead of the game, and the Platform/WiiU version was buggy enough to cause the console to crash. Inafune [[http://kotaku.com/mighty-no-9-s-designer-says-i-will-own-all-the-proble-1782382706 accepted responsibility for the disappointing final product,]] citing the promise of developing so many versions at once as a death knell. With that in mind, the developers were also unable to complete all these versions; the Vita and 3DS versions would never see completion, being quietly (but unofficially) cancelled. |
| 438 | * The Platform/Nintendo64 adaptation of the 1996 ''Film/MissionImpossible'' film. The game was originally slated to be released in late-1996. However, constant ExecutiveMeddling (resulting in the game switching development teams midway through development) and problems fitting such an at-the-time ambitious game onto a small cartridge resulted in the game not seeing release until mid-1998 in North America. The final game actually wasn't half bad. However, its long development history definitely showed with its dated graphics, buggy programming, and somewhat underdeveloped gameplay. The impending release of the competing ''VideoGame/MetalGearSolid'' that same year certainly didn't help matters. |
| 439 | * Trevor Roberts, creator of the AnalogHorror web story ''WebOriginal/MysteryFleshPitNationalPark'', was [[https://kotaku.com/kickstarter-survival-horror-pc-mystery-flesh-pit-1849829127 brutally honest]] about why a planned SurvivalHorror video game adaptation ultimately [[{{Vaporware}} fell apart]]. In short, he underestimated just how much work goes into making a video game and wasn't sure he could maintain his standard of quality, especially since working on a game meant collaborating with an entire studio on his creative vision, a studio whose ambitions went far beyond what he originally had planned. Fearing that the game would have been "a rushed and inferior gaming experience at best, and an unmitigated disaster at worst," he pulled the plug just a week after announcing it and focused on adapting his story into a tabletop game instead. |
| 440 | [[/folder]] |
http://tvtropes.org/pmwiki/context.php
FollowingContext TroubledProduction / VideoGames0ToM
Go To
- Show Spoilers
- Night Vision
- Sticky Header
- Wide Load
