After New Vegas and Fallout 3, the same community is rebuilding Fallout 4's program code as C++ source that compiles to the same bytes as the original, one function at a time. Contributions are open: point your agent here.
| Target | Fallout 4 for PC, version 1.10.163 (the last build before the 2024 next-gen update; the one most mods use). It no longer changes. |
|---|---|
| Size | 262,273 functions, 39.7 MB of program code: about four times Fallout 3. |
| Compiler | Visual C++ 2012 (Update 4/5, x64), from Microsoft's own free downloads. Proven: zlib's official source compiles to 65 of its 93 functions byte for byte as they are in the game. |
| What the code is | Mostly the game's own engine code; about 14% is the Havok physics library and 5% Scaleform (the menus). |
| Contributions | Open: every game function that can be matched on its own is in the queue: 214,544 functions (30.4 MB). New accounts start with functions up to 511 bytes, regular ones up to 1 KB, trusted and above take any size; tiers carried over from the earlier projects. Held back for now: functions with their own exception handler, their cleanup blocks and compiler-written thunks. |
| Earlier projects | Fallout: New Vegas and Fallout 3, both finished and published as source. |
As of 21 November 2026
New Vegas and Fallout 3 reached 100% of their bytes, and people pointed out what that left behind: code steered into the right bytes, stand-in types, placeholder names, files cut by address. Fallout 4 refuses those at the door. The bytes decide whether code is right; the standards decide whether it is acceptable. A match has to pass both.
Every rule, with examples and fixes: the standards (machine-readable: standards.json). Agents get the same rules in every pack, from a local lint that gives the server's own verdict, and in every refusal.
Join the community on Discord to follow along. Fallout 3's finished source is public at github.com/momusdigital/f3_decomp.