Publishers are not famous for giving things away, least of all the blueprints to their best-known games. So when Electronic Arts announced, on 27 February 2025, that it had recovered the source code for four classic Command & Conquer titles and published it for anyone to study, modify and build upon, the strategy community reacted the way it usually reacts to an unexpected superweapon landing in its own base: first with disbelief, then with enormous enthusiasm. This was not a leak, a lapse or a legal grey area. It was the rights holder opening the vault on purpose, and doing preservation work that, until that week, the industry had mostly left to fans.
What EA actually released in February 2025
The February 2025 announcement covered four bodies of code. The headline pair was the original Command & Conquer of 1995, retroactively subtitled Tiberian Dawn, and its 1996 follow-up Command & Conquer: Red Alert. Joining them were Command & Conquer: Renegade, Westwood’s 2002 first-person shooter spin-off, and Command & Conquer: Generals from 2003, including its expansion Zero Hour. The code was published through EA’s official GitHub presence under version 3 of the GNU General Public License, with some additional terms attached — a detail worth noting, because it means the releases are genuinely open for community development rather than merely available to look at.
The word that mattered most in EA’s announcement was “recovered.” Five years earlier, in 2020, EA had already released source code connected to Tiberian Dawn and Red Alert alongside the Command & Conquer Remastered Collection. That earlier release was valuable, but it was the code behind the remaster’s engine components — material that had already been adapted for a modern reissue. The 2025 release went further back, presenting the fully recovered original source for the first two games, the product of archival digging rather than a by-product of a product launch. Renegade and Generals, meanwhile, had never had their source officially released at all.
The person who made it happen is a large part of the story. EA commissioned Luke Feenan, a veteran of the Command & Conquer community known by the handle CCHyper, who had previously served on the Community Council for the Remastered Collection and helped bring the Ultimate Collection to Steam in 2024. Given access to EA’s internal archive for the series, Feenan spent roughly a year researching and preparing the releases on the community’s behalf, working alongside producer Jim Vessella, the public face of the franchise’s revival since the remaster. It is difficult to think of another major publisher that has handed a trusted community member the keys to its archive and asked him to prepare its history for publication.
More than code: Workshop support and the modding pack
Source code was the headline, but it was not the whole announcement. EA also switched on Steam Workshop support across a wide slice of the series, covering Renegade, Generals and Zero Hour, Command & Conquer 3: Tiberium Wars and its expansion Kane’s Wrath, Red Alert 3 and Uprising, and Command & Conquer 4: Tiberian Twilight. The Mission Editor and World Builder tools were updated so creators could publish maps directly to the Workshop instead of scattering them across fan sites. Alongside that came a dedicated modding support pack gathering the source XML, schema, script, shader and map files for the games built on the SAGE engine — the technology that powered the series from Generals onward — plus archive footage from Renegade and Generals development that EA released at the same time.
Taken together, the package addressed the three things an ageing game needs to stay alive: the code to fix and port it, the tools to build for it, and a distribution channel where new work can actually find an audience. Modders had kept these games breathing for decades with reverse engineering and patience. February 2025 replaced a good deal of that guesswork with ground truth.
Why source code is the preservation prize
Game preservation usually deals in finished artefacts: cartridges, discs, executables, artwork, manuals. Those matter enormously, but a compiled game is a locked room. You can admire it, emulate the machine it ran on, and — with enough skill — pick the lock. Source code is the room’s architectural plan, wiring diagram and builder’s notebook combined. With it, a community can port a game to hardware its creators never imagined, repair bugs that have been frozen in place for thirty years, restore features that were cut for deadline reasons, and understand design decisions that the finished product only hints at.
The Command & Conquer code illustrates the point neatly. Generals was built on SAGE, an engine descended from the Westwood 3D technology created for Renegade — which means the 2025 releases let researchers trace an entire engine lineage in the open. The community had already demonstrated what it could do with partial access: projects built around the 2020 release produced clean, cross-platform versions of the classic games, and the long-running open-source effort to reimplement the early Westwood engines had kept Tiberian Dawn and Red Alert playable on modern systems for years. Full, official source turns that kind of work from archaeology into engineering.
How rare is this, really?
Very — and the exceptions prove the rule. The famous counter-example is id Software, which made a habit of open-sourcing its engines once their commercial life had passed: Wolfenstein 3D in 1995, Doom in 1997, and the Quake lineage thereafter, eventually under the GPL. That policy was considered eccentric for years, driven by John Carmack’s personal advocacy, and it came from a small, independent studio that owned its technology outright. For a publisher of EA’s size, holding decades of catalogue from an acquired studio — Westwood was bought in 1998 and closed in 2003 — the legal and archival friction is far greater. Rights must be audited, third-party components examined, and the code itself first has to be found. The conspicuous gaps in the 2025 release underline how fragile that process is: Tiberian Sun and Red Alert 2, two of the most beloved entries in the series, were not part of it, and commentators immediately began speculating about whether their code is lost or being held back. Nobody outside EA knows, which is precisely the problem source releases solve when they happen in time.
It is also worth separating what was given from what was not. The February 2025 release covered code, not the games’ commercial assets — the art, cinematics and audio that make up so much of Command & Conquer‘s identity remain EA’s property, and the games themselves are still sold, not given away. That distinction is not a catch; it is the workable middle ground that makes releases like this legally possible at all, and it still hands the community the one thing it could never manufacture for itself.
The view from here
Writing with the benefit of hindsight, the February 2025 announcement looks less like a one-off publicity gesture and more like the logical end of a strategy EA had been testing since the Remastered Collection: treat the community as a partner, give its most trusted members real access, and let a dormant series sustain itself. The franchise had no new mainline game on the horizon. What it had was thirty years of accumulated goodwill and an audience that had never actually left. The source release converted that goodwill into permanence. Whatever happens to stores, servers and operating systems from here, the foundations of Tiberian Dawn, Red Alert, Renegade and Generals now exist in the open, under a licence designed to keep them there. For game preservation, that is not just good news. It is the template.