{"id":1916,"date":"2017-10-09T09:47:00","date_gmt":"2017-10-09T09:47:00","guid":{"rendered":"http:\/\/www.gamasutra.com\/view\/news\/307191"},"modified":"2017-10-09T09:47:00","modified_gmt":"2017-10-09T09:47:00","slug":"classic-postmortem-xcom-enemy-unknown-which-turns-5-today","status":"publish","type":"post","link":"https:\/\/sickgaming.net\/blog\/2017\/10\/09\/classic-postmortem-xcom-enemy-unknown-which-turns-5-today\/","title":{"rendered":"Classic Postmortem: XCOM: Enemy Unknown, which turns 5 today"},"content":{"rendered":"

In honor of the 5th anniversary of the release of the brilliant\u00a0<\/em>XCOM: Enemy Unkown<\/a>, we present this classic postmortem, which first appeared in the January 2013 issue of Game Developer magazine.<\/em><\/strong><\/p>\n

The game was a “reimagining” by Firaxis<\/a> of the classic 1994 strategy title\u00a0<\/em>UFO: Enemy Unkown, as well as a reboot of the XCOM series. It was a smashing success, earning numerous awards and GOTY accolades.<\/em><\/strong><\/p>\n

This in-depth look at what went right and what went wrong during development was written by\u00a0Garth DeAngelis<\/a>, who was the lead producer and a level designer on<\/em> XCOM: Enemy Unknown.<\/em><\/strong><\/p>\n

There may have been wounds, but somehow, the XCOM: Enemy Unknown<\/em> development team evaded permanent death.<\/p>\n

In 1994, Microprose released a special PC game called UFO: Enemy Unknown<\/em>. The turn-based strategy title accumulated a devoted fanbase for its unique take on high-level management against an alien invasion blended with boots-on-the-ground, intimate combat controlling individual soldiers. Fast-forward almost two decades, and Firaxis Games has released XCOM: Enemy Unknown<\/em>, a reimagining of Julian Gollop\u2019s original design.<\/p>\n

The road to completing XCOM<\/em> was an arduous one. We made many of the same mistakes that other devs have made (and documented in previous Game Developer postmortems): feature creep, communication shortfalls, not enough time, not enough people\u2026 If you\u2019re a game developer, you know the story. But through it all, the entire team remained resolute, and in October 2012, against all odds, the development team managed to save Earth<\/del> ship XCOM<\/em> on PC, Xbox 360, and PlayStation 3.<\/p>\n

\"\"<\/p>\n

Lead designer Jake Solomon planted a small seed within the creative walls of Firaxis Games in 2004. As the self-proclaimed \u201cbiggest fan of the original X-COM\u201d and as a designer\/programmer working directly with Sid Meier, it made sense to spark discussion regarding resuscitating one of the greatest strategy titles of all time. After shipping Civilization Revolution<\/em>, the stars began to align, and the rebuilding of XCOM<\/em> became a reality.<\/p>\n

Before any code was written or any art completed, Jake defined core pillars that would act as the foundation for pillars that would act as the foundation for designing the rest of the game. All facets of game development had clearly evolved since 1994, from game and narrative design to user interface, but Jake remained adamant that certain high-level elements from the original remain holy. These inspirations included maintaining a turn-based combat system, which seemed risky in the modern age of frenetic first-person shooters and real-time action games.<\/p>\n

The game would also preserve the symbiotic relationship between the micro combat layer and a macro, grand strategic mode, where the player runs and builds their own secret headquarters to counter the simulated alien invasion. Fans of the original game understood the appeal of these interdependent systems, but to those unfamiliar with the XCOM<\/em> franchise, this was a foreign game structure, and that equaled potential big risk.<\/p>\n

Other smaller pillars included: updating systems such as the fog of war and how visibility would be communicated to the player in a 3D environment; fully destructible environments, a satisfying staple from UFO: Enemy Unknown<\/em>, but a potential challenge in a game of this scope; reintroducing players to permanent death, and the fact that when it comes to XCOM<\/em> soldiers, there are no such things as extra lives; and recreating the tense atmosphere from the original.<\/p>\n

It was critical to place the player in a world they recognized\u2014in settings they may recall from their own neighborhood or city\u2014and then introduce a menagerie of new and classic aliens into these usually safe environments. This led to an unnerving despair that XCOM<\/em> fans are all too familiar with. Collectively, these pillars provided the foundation for a challenging experience that presented true consequences, just like UFO: Enemy Unknown<\/em>.<\/p>\n

\"\"<\/p>\n

Firaxis underwent a pitch process that previously had not been attempted with past projects, but then again, we were pitching what was essentially a new IP as a big-budget endeavor, so we needed to make a major splash.<\/p>\n

Getting the green light to remake an antiquated turn-based strategy game would be a challenge, and simply verbalizing what made XCOM<\/em> so special and ripe for a rebirth wouldn\u2019t be enough. The team needed something that would make everyone understand why we were so passionate about undertaking this project\u2014something beyond a static presentation.<\/p>\n

Jake began working with project art director Greg Foertsch and a small band of artists to create a gameplay previsualization. Over the course of multiple months, Greg and his team ate, breathed, and slept UFO: Enemy Unknown<\/em>, ultimately planning a storyboarded sequence that would illustrate how Firaxis\u2019s take on the XCOM universe would not only look, but also how it would play.<\/p>\n

On Fridays, Jake would sit in a room with the team while they immersed themselves in the original game, becoming familiar with its nuances and big concepts alike. This collaboration led to a compelling previsualization that not only got the development team on the same page, but also communicated to nondevelopers the potential for a classic turn-based experience to be reborn as something cutting edge, distinctive, and thrilling in the modern age of video games.<\/p>\n

\"\"<\/p>\n

Even before beginning work on XCOM<\/em> , we heard it all before: Games had become too easy. The development (or marketing) buzzword \u201caccessible\u201d translated to \u201cdumbing down,\u201d the idea that developers would take an otherwise deep, rich, and satisfying game and distill its intricacies to its barest form so the entirety of the world could understand, buy, and play said game.<\/p>\n

It sounds hyperbolic, but I\u2019ve seen games with easy modes that literally played themselves, making failure impossible, so this stigma against accessibility wasn\u2019t without merit! Making a game \u201cfor the masses\u201d could be the ultimate transgression, especially for a complex game with a hardcore past, and we anticipated that XCOM<\/em> fans would be skeptical that our work would hold up to those who fell in love with the original.<\/p>\n

While UFO: Enemy Unknown<\/em> may have been magnificent, it was also a unique beast when it came to beginning a new game. We often joked that the diehards who mastered the game independently belonged in an elite club, because by today\u2019s standards the learning curve was like climbing Mt. Everest.<\/p>\n

As soon as you fire up the original, you\u2019re placed in a Geoscape with the Earth silently looming, and various options to explore within your base\u2014including reading (unexplained) financial reports, approving manufacturing requests (without any context as to what those would mean later on), and examining a blueprint (which hinted at the possibility for base expansion), for example\u2014the player is given no direction.<\/p>\n

Even going on your first combat mission can be a bit of a mystery (and when you do first step off the Skyranger, the game will kill off a few of your soldiers before you even see your first alien\u2014welcome to XCOM<\/em>!). While many fans on the team found this learning curve to be a part of the game\u2019s charm and wore it as a badge of honor, we ultimately knew that, in 2012, we needed to enable gamers to experience the truly fun elements without overly testing their patience. But neither could we bear to dumb XCOM<\/em> down.<\/p>\n

\"\"<\/p>\n

We were on a mission to flip\u00a0the perception on streamlining, to remove the stigma that accessibility equaled a dirty word. We wanted anyone to be able to give XCOM<\/em> a whirl without expecting them to become fluent\u00a0in the game\u2019s many systems on their own accord. At the same time, we needed to preserve all of the richness, depth, and challenge ingrained in the core pillars. If someone wanted to walk away from the experience due to the game\u2019s challenge, we were okay with that; but we didn\u2019t want to alienate anyone simply due to a lack of information.<\/p>\n

To accomplish this, we built an optional, integrated tutorial that peeled off the components of XCOM<\/em> one layer at a time. It was important to keep this hour-and-a-half experience optional, as experienced players could save Earth again without the tutorial force-fed to them (and we also knew some players, even in 2012, would want that old-school badge of honor by skipping the tutorial altogether, which is somewhat appropriate for certain types of X-COM fans).<\/p>\n

The introduction to the game wasn\u2019t the only area we redesigned. Jake and the design team refined low-level mechanics from the original, such as removing Time Units and capping the squad loadout at six. Both of these changes were the result of internal playtesting over the course of many months, with the development team finding a combat \u201csweet spot\u201d with respect to approximate time spent on a map and number of decisions made per turn (we found, depending on map size, battles should average 20 minutes, not to exceed 50 minutes on the absolute longest missions). Six units also made every decision vitally important, promoting group tactics with no moves feeling like unnecessary filler.<\/p>\n

This \u201cnew era of accessible\u201d mindset also helped the design and user interface teams build a platform-agnostic experience. This is an element that could have gone horribly wrong (and did have its inherent challenges, detailed later), but the team did an admirable job of crafting a historically PC experience for consoles as well. We knew games like XCOM<\/em> weren\u2019t traditionally available on Xbox 360 and PlayStation 3, but we\u2019re extremely happy we could provide the same experience (without compromising features or \u201cdumbing down\u201d the console versions) across all platforms.<\/p>\n

\"\"<\/p>\n

The developers at Firaxis are extremely professional, with each discipline playing the hero role at some point and overcoming monumental obstacles throughout development. From the audio group to the animation and narrative team, they were continually course-adjusting due to dependencies, yet still producing incredible content to polish the game.<\/p>\n

On the engineering front, months of changing design had to be technically supported in many complex situations. Systems were built, iterated upon, and some were even discarded after determining a new direction was needed. For example, over the course of a few milestones in midproduction, design asked for sightlines to be drawn from every game unit, soldier, and alien alike, so it was clear what each unit could see.<\/p>\n

Our graphics engineering team and artists diligently worked to make this system digestible, but unfortunately, it was tough for the player to determine what was going on amidst the plethora of multicolored lines. After months of trying to get sightlines to work, we eventually realized that the strongest solution was to remove them.<\/p>\n

There were plenty of other challenging systems to decipher: the building visibility system underwent various ceiling, wall, and floor rule changes; destruction fidelity fluctuated through a shaky toughness system; and the fog of war was a full 3D cloud early in production, which proved to be a nightmare for both graphics engineering and performance.<\/p>\n

Additionally, each gameplay layer (combat and strategy) received drastic overhauls after months of playtesting. In all of these cases, initial engineering efforts had to ultimately be thrown out. To the team\u2019s credit, they understood the nature of iterative design and admirably continued to put in the time needed to make the game a better experience.<\/p>\n

\"\"<\/p>\n

In addition, the engineers banded together in a Herculean effort to fix thousands of bugs in postproduction. XCOM<\/em> is a large, system-driven game with many procedural elements. This meant that many bugs were not only difficult to reproduce, but challenging to even find! Together, engineering raised the bar of the final player experience by squashing these bugs feverishly. Obviously, we couldn\u2019t find and fix every bug, but we\u2019re proud of the effort given in the race to the finish\u00a0line.<\/p>\n

The art and content teams also worked minor miracles. A primary example was the game\u2019s levels. We all love maps and levels, and want more of them; but they are a nexus of many different disciplines somehow crafting the same sculpture all together, and this requires tight coordination and lots of time. Firaxis had never created a level-driven game before (with a strategy system still on top of it, no less), so we had to learn how to build a pipeline that would let us efficiently design and build level assets.<\/p>\n

This specifically required an inordinate amount of collaboration between level design and level art, weeks of gameplay testing and feedback per map, and an extreme amount of content creation (we needed to have approximately enough maps for two full playthroughs). In the end, our modestly sized level team ended up exceeding the original goal of 70 unique maps.<\/p>\n

Beyond levels, there was still an entire headquarters to build on the strategy layer, with dozens of expandable rooms that could be hand-placed by the player. After making various isometric prototypes, we realized the base wasn\u2019t nearly as gripping as we\u2019d like; something was missing.<\/p>\n

Lead technical and HQ artist Dave Black pitched the \u201cant farm,\u201d a diorama-style side view that instantly connected with the entire team. This was an entirely new process as well, but Dave and the art team concurrently exceeded expectations on headquarters while finalizing\u00a0all of the combat maps.<\/p>\n

\"\"<\/p>\n

We\u2019ve heard countless horror stories about publisher-developer relations, with publishers stifling creativity, dictating direction, or creating impossible deadlines\u2014but our partnership with 2K Games was not one of those horror stories. While there was give-and-take from both sides (as in any relationship), we were overwhelmingly happy with 2K Games\u2019s support\u2014especially considering no major publishers have funded a large-scale, multiplatform, turn-based strategy game in recent memory.<\/p>\n

2K believed in our vision and greenlit the project, something we\u2019re not so sure would have happened elsewhere. The 2K Product Development group believed in the potential for a reimagined XCOM<\/em> and also understood that taking risk was necessary. We were ecstatic to learn we would be given this opportunity.<\/p>\n

Furthermore, 2K trusted in us as a studio to own the creative direction of the title. While they provided in-depth milestone feedback, every item was up for discussion, and they ultimately trusted in our design vision. 2K also provided us with additional resources to build an integrated tutorial, something that became critical late and ballooned beyond our initial resource estimations. This type of support proved invaluable to finish\u00a0the game.<\/p>\n

\"\"<\/p>\n

Also, 2K\u2019s public relations team was instrumental in raising the awareness for XCOM<\/em>. They took the time to understand the vision and value of the project, and allowed the team leads to directly and candidly communicate that vision to the player base. PR worked diligently to uncover many valuable opportunities for the game, including a cover reveal with Game Informer magazine and various demo presentations to targeted press.<\/p>\n

These presentations planted the seed in our most passionate advocates\u2014the press\u2014to pass along what they liked (or disliked) about the game\u2019s potential. There was also a strong working relationship between PR and the development team, leading to joint initiatives like the \u201cJake Solomon Undercover\u201d video and exciting panel discussions like PAX\u2019s \u201c1000 Stupid Ideas on the Road to Glory.\u201d<\/p>\n

[embedded content]<\/p>\n

XCOM<\/em> required constant design iteration, with some features being implemented beyond Alpha. It may sound clich\u00e9, but Firaxis has always lived by the mantra \u201cFind the Fun,\u201d and the company takes that very seriously. Sometimes, fun can be a challenge to find, especially in a product that is unlike any other we\u2019ve built before. XCOM<\/em> boasts two interdependent systems that could almost be standalone games, and discovering that special synergy between the two was the key to unlocking the magic within the XCOM<\/em> universe.<\/p>\n

Trying to focus concurrently on both gameplay layers was challenging. We spent various milestones on certain features that didn\u2019t progress as we\u2019d hoped. By midproduction, the strategic layer was a turn-based card system for various months, and it stagnated while the team focused on improving combat. Ultimately, the strategy layer was molded into the version we\u2019re satisfied with, but it was neglected for too long and required a late Half-Life<\/em>-inspired Cabal process to get there.<\/p>\n

We (myself, Solomon, and other members of the dev team as necessary) would meet every morning, every day, until each component of the strategy layer had a concrete game plan and a clear implementation schedule. Additionally, the tutorial and narrative, critical components of the game, couldn\u2019t be pushed to final\u00a0until the design was locked. And since the design tentpoles ran late, the narrative team (including animators, writers, and audio) came under immense pressure to finalize\u00a0high-quality cinematics in an extremely short timeframe.<\/p>\n

\"\"<\/p>\n

The extra design time helped make the game as good as it could possibly be from a gameplay perspective, but it\u2019s worth asking whether we could have made tough calls on certain systems earlier in the schedule. This is one of game development\u2019s largest challenges: Holding a game\u2019s design to immovable deadlines can be stifling to the iterative and tricky-to-quantify creative process.<\/p>\n

Shipping an unpolished combat game with a completely disconnected strategy layer would have spelled disaster for the future of XCOM<\/em>, so we kept the process malleable much later into the schedule, allowing the team to find the answers through discovery and experimentation.<\/p>\n

Practices like the design cabal helped the team focus on areas of the game that weren\u2019t fun, but in a perfect world, we would have locked down as many high-risk systems as possible as preproduction wrapped up. We did ultimately cut content, but the bulk of our wishlist shipped in the final\u00a0product, which was great for the game but taxing on the team.<\/p>\n

\"\"<\/p>\n

By Alpha, only a few systems needed to be implemented, but a new challenge was looming around the corner: the bug database. Before Alpha, the team had a good sense of the state of the game and which systems were most playable, but it was difficult to quantify the true workload until QA began fully testing the game for a few weeks. The reported bug count rapidly multiplied like termites silently infesting the framework of an otherwise beautiful house.<\/p>\n

Initially, we weren\u2019t quite sure what to expect, but as the picture became clearer, we knew we were in for an inordinate effort to keep pace with the influx of bugs. There were concerns about the amount of work needed to fix the game relative to the engineers on the team. We had a ship date to hit and we wanted to get our dedicated engineers help.<\/p>\n

But the mythical man-month is a very true concept. While our publisher was generous with additional resources to assist toward the end of production, we found that a flood of external helpers had undesired consequences. Knock-on bugs due to unfamiliarity with the codebase, content that needed to be fixed by internal artists, and communications inherent in outsourcing relationships all led to an extreme amount of overhead that ultimately fell onto the laps of internal team members who were already responsible for an aggressive workload.<\/p>\n

Outsourcing challenges also hit the content-creation team during production. Communicating with an external cinematic team overseas led to a staggered communication channel. Since there were dozens of unanticipated clerical issues just to get their tools up to speed with ours (no fault of theirs), it was extremely challenging to troubleshoot any setbacks. Also, providing creative feedback to most external partners often led to significant delays due to the remote feedback loop and misinterpretations of feedback via email.<\/p>\n

\"\"<\/p>\n

Once we were late into production, the leadership team wanted to maximize each developer\u2019s working hours by being judicious regarding meeting requests, even amongst ourselves. Process-driven meetings were reduced along with costly, 20-plus-person large-scale meetings. We still maintained informal but intimate one-on-one reviews with each discipline\u2019s lead, which was intended to be more focused and fruitful per developer. While the leadership team and some team members appreciated this, others were understandably yearning for additional official communication channels.<\/p>\n

Also, team members wanted quicker information on the high-level changes to the design of the game, but with our lead designer doubling as a gameplay engineer, he would often be tied up with coding. Finally, cross-discipline groups (like level design and level art, and feature-specific teams) surely could have benefited from a more formalized stand-up process, which we implemented toward the end of production.<\/p>\n

Moving forward, the leadership team knows it needs to strike an appropriate balance between optimal information flow and excessive meeting time, hedging toward more opportunities for formal communication.<\/p>\n

\"\"<\/p>\n

Not only was the game structure of XCOM<\/em> unlike anything the studio had built before, this was also the first time we\u2019ve had to concurrently develop versions for three different platforms. It turned out managing all three was a massive amount of work.<\/p>\n

Design-wise, the team knew there would be feature parity between PC and consoles; the only difference would be the control scheme. While the design and UI team did an admirable job on this front, there were continuous challenges throughout development to accommodate multiplatform user interface design, specifically tied to this genre. The team had to ensure all tactical commands were accessible via gamepad, and this involved quite a bit more than accommodating a point-and-shoot mechanic.<\/p>\n

The movement system, mapping a system to support dozens of contextual abilities, and crafting a uniform Shot HUD were just a few areas that took time to master across the board. While this specific instance arguably didn\u2019t go \u201cwrong,\u201d it is a small example of the multiplatform challenges faced daily.<\/p>\n

\"\"<\/p>\n

The system-specific optimizations needed for each platform were significantly more difficult, particularly for the consoles. Understanding the console constraints for items like number of maps, audio files, texture budget, and animation sizes was a continual process between engineering and the specific disciplines. There were also severe, system-specific bugs, technical requirements, and crashes that ate up much of our senior engineers\u2019 time.<\/p>\n

Our systems engineering team was a very talented duo, but they didn\u2019t have a dedicated platform engineer, which meant that they had to partner on all of these complex issues across the board. While they worked together effectively, they simply had too much work on their plates: universal systemic issues, art optimization requests, and other general and technical requirement bugs, just to name a few major workloads.<\/p>\n

Our lead engineer assisted on the most difficult issues when he was free from putting out other fires, and another internal systems engineer joined the cause late in the project to own the Xbox 360 technical certification requirements, but these were solutions that emerged late in development.<\/p>\n

\"\"<\/p>\n

We\u2019re not proud about the fact that we had to crunch to finish XCOM<\/em>. We have a dedicated and passionate team, and all team members put in serious extra hours at some point for the good of the project. For many, the malleable structure of the game led to frustration as we were knee-deep in the trenches. Certain dependencies were continually pushed (especially impacting audio, effects, cinematics, and user interface) and the lack of testing on late gameplay systems led to a heavy bug load for the engineers.<\/p>\n

On the art side, the content creators had production crunches to finish all maps. As said before, this was the first time we created a game of this structure, and the first time we had to iterate so much on the process itself. While we improved certain inefficiencies throughout production, we simply couldn\u2019t accurately predict how much time we\u2019d need to make the game the way we wanted to make it.<\/p>\n

\"\"<\/p>\n

In the end, we avoided permadeath. And after all of the extra hours, the thousands of bugs fixed, the hundreds of level playtests dissecting every piece of cover, the dozens (hundreds?) of gameplay prototypes and healthy debate that accompanied each new system, through every team meal, and in the wake of every hopeful or concerned hallway discussion, in the end, the XCOM<\/em> development team emerged victorious.<\/p>\n

We shipped the project within weeks of our original target release date, earned a near-90 Metacritic from video game journalists, garnered hundreds of game accolades, and won 13 Overall Game of the Year awards. Most importantly, a wildly creative and cross-discipline team banded together to contribute to the unlikely revitalization of a classic game, capturing the magic of X-COM for a new generation of gamers and hardcore fans of the original alike.<\/p>\n","protected":false},"excerpt":{"rendered":"

In honor of the 5th anniversary of the release of the brilliant\u00a0XCOM: Enemy Unkown, we present this classic postmortem, which first appeared in the January 2013 issue of Game Developer magazine. The game was a “reimagining” by Firaxis of the classic 1994 strategy title\u00a0UFO: Enemy Unkown, as well as a reboot of the XCOM series. […]<\/p>\n","protected":false},"author":2,"featured_media":1917,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[20],"tags":[],"class_list":["post-1916","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news"],"_links":{"self":[{"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/posts\/1916","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/comments?post=1916"}],"version-history":[{"count":0,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/posts\/1916\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/media\/1917"}],"wp:attachment":[{"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/media?parent=1916"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/categories?post=1916"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/tags?post=1916"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}