User:Famous Hobo/sandbox
Development
The origins of Fallout 76 date back to 2013.[1] During the development of Fallout 4, Bethesda Game Studios began conceptualizing what a potential multiplayer game mode would look like.[1] The ideas presented were considered too large in scope, and were set aside in favor of the single-player campaign.[1] During this period, Jason Hasenbuhler of the recently formed BattleCry Studios in Austin, Texas, met with Bethesda executive producer Todd Howard.[1] Hasenbuhler noted that several developers at BattleCry had experience with large multiplayer games like Star Wars Galaxies, and asked Howard to let the studio work on a Fallout multiplayer game using the ideas proposed.[1] It was not until after the release of Fallout 4 in November 2015 that Bethesda greenlit the project. Bethesda had already begun work on downloadable content for Fallout 4 as well as preliminary work on Starfield, and felt a Fallout multiplayer game would help fill in the downtime between their games.[1] BattleCry had recently placed their upcoming free-to-play game BattleCry on indefinite hiatus, and agreed to Bethesda's request.[1]
Bethesda provided BattleCry with Fallout 4's Creation Engine, a game engine that had been exclusively used in single-player games.[2] The Creation Engine proved difficult to work with, as it was still using code written for The Elder Scrolls III: Morrowind in 2002, and any part of the map the player was not currently in would not be loaded.[2] BattleCry believed their best option to retrofit the engine with multiplayer capabilities was to implement the netcode used in older Quake games.[2] While BattleCry worked with the engine, a small team at Bethesda's main studio in Rockville, Maryland began brainstorming the premise for the game.[3] They decided the map needed to be larger to compensate for multiple players, and chose the Appalachian region of West Virginia as the setting.[3] The last two Fallout games developed by Bethesda were set in major cities along the East Coast of the United States, and the team wanted to instead explore a more rural location that would not have been targeted by nuclear warfare.[3] This meant the local flora and fauna would have largely survived and mutated, and forests could encompass parts of the map.[3]
Fallout 76 takes place just 25 years after the Great War, which affected some decisions regarding the gameplay and plot, the largest of which was the decision to not include human non-player characters (NPC).[4] A behind-the-scenes documentary about the game gave two reasons for the decision.[4] From a lore perspective, Bethesda reasoned it would take longer than 25 years for hostile factions to form and take control of the area, and from a gameplay perspective, the team wanted players to know that any human characters they ran across were in fact other players and not NPCs.[4] Bethesda compensated for the lack of gun-wielding enemies by creating a new type of ghoul enemy that still had some mental faculties and knew how use weapons.[4] In a 2022 retrospective article published by Kotaku, anonymous developers stated that nearly everyone at BattleCry disliked the decision to not include human NPCs, although Howard was insistent on their removal until after the game released.[5] Executives at Bethesda felt it would take a significant amount of time to update the engine for multiplayer capabilities, and decided that replacing NPCs with text-based storage devices and moments of environmental storytelling would convey the same level of narrative storytelling.[5]
Troubled development
The anonymous developers interviewed for the Kotaku article outlined the game's troubled development history.[5] One developer stated, "No one wanted to be on that project because it ate people. It destroyed people ... The amount of people who would go to that project, and then they would quit [Bethesda] was quite high."[5] To compensate for the turnover rate, some developers working on Starfield and the Arkane Austin game Redfall were moved onto Fallout 76.[5] One reason why the game struggled to retain workers was the lack of leadership.[5] Some members of BattleCry were led to believe Howard was in charge of the project, although he was in fact working on Starfield.[5] Howard would occasionally visit BattleCry but his involvement was deemed inadequate by the developers.[5] One developer stated he shot down any new ideas proposed by the design team, while another developer claimed he leaned too heavily into the "bigger is better" design philosophy with no thought given to how it would work.[5]
In general, Bethesda did not provide enough information about important aspects of the game, such as the maximum amount of players per server, or how griefing would be handled.[5] Those interviewed also claim there was a level of resentment toward BattleCry from the Rockville studio, particularly for Bethesda's decision to structure Fallout 76 as a live service game.[5] The free-to-play Fallout Shelter had grossed over $100 million in four years, and as a result, Bethesda took a greater interest in games that could continuously generate revenue after their release.[5] Emil Pagliarulo was singled out as a designer from the Rockville studio that ignored BattleCry.[5] One developer said, "[Pagliarulo] didn't seem to want to be involved with the product at all. He didn't want to have any contact with it ... or read anything that we put in front of him."[5] The issues of resentment were compounded as some members from the Rockville studio that were brought in to work on Fallout 76 were dismayed that they were working on a multiplayer game despite joining a studio that had exclusively produced single-player games.[5] One developer said, "[Bethesda] has a lack of respect for folks who are working on things that they consider theirs."[5]
Members of the game testing department were also interviewed for the Kotaku article, and shared similar stories about the game's development.[5] Testers were subject to significant crunch, and the exhaustive work took a toll on their mental health.[5] Testers dealt with what they described as "voluntold overtime", because if no one volunteered for weekend overtime hours, then everyone within the department would be called in.[5] Peer pressure became commonplace among testers, as those who did not complain about the crunch had increased odds of being converted to full-time employees instead of contract workers.[5] When these issues were brought up to the studio's parent company ZeniMax Media, it was either ignored or outright denied.[5] Testers claimed their breaks were timed, and some testers went as far as to claim they were followed into restrooms by what they described as "chronic snitches".[5]
Nearly every build for Fallout 76 during its development suffered from glitches, most of which stemmed from the Creation Engine.[5] When asked what parts of the game were subject to glitches, one developer said, "Tongue in cheek: the whole game. In general, every major bug in 76 [that appeared at launch] was known by [quality assurance]."[5] The engine was poorly optimized, and simply updating to a new build could potentially break the game.[5] Game testers were forbidden from discussing problems found in the game directly to the developers, and instead had to bring up any issues with the quality assurance department.[5] This in turn delayed work on game-breaking glitches for sometimes months.[5] Developers assumed Fallout 76's would be delayed, but Bethesda and BattleCry worked on tight schedules, and would not delay any preset deadlines.[5]
References
- ^ a b c d e f g Noclip 2018, 2:32-4:47.
- ^ a b c Noclip 2018, 5:19-7:10.
- ^ a b c d Noclip 2018, 7:48-9:31.
- ^ a b c d Noclip 2018, 11:44-12:55.
- ^ a b c d e f g h i j k l m n o p q r s t u v w x y z aa ab Jiang, Sisi (June 8, 2022). "The Human Toll Of Fallout 76's Disastrous Launch". Kotaku. Retrieved October 3, 2024.
Sources
- The Making of Fallout 76 - Noclip Documentary. Noclip. June 12, 2018 – via Youtube.