A public GitHub repository for `adonis-singh/re4` claims a complete, byte-identical decompilation of the GameCube debug build `G4BE08` of *Resident Evil 4*. The project says its C/C++ build reproduces `main.dol` and all 114 REL overlays exactly, which are the game’s main executable and reloadable code modules.
The article opens with this repository, which identifies the Resident Evil 4 GameCube debug-build reconstruction discussed throughout the story.
The repository reports about 571,000 lines of source, 43,000 lines of headers, 1,083 objects, and 23,289 function symbols. It says the names come from the debug build’s `Bio4.sym` symbol files, while file boundaries were inferred from strings left in the binaries. That is why the result is useful to researchers even though it is not a simple restoration of lost source code.
The central verification is unusually strict: each unit is compiled with the original compilers and compared with the original bytes. The project reports that `ninja` finishes with 100% matching for the DOL and REL modules, and that its SHA-1 check prints 115 `OK` lines. In plain terms, the rebuilt machine code is being checked against the shipped code, not merely tested for similar behavior.
That does not mean every source line is a natural reconstruction. The README documents 578 `COMPILER-DIFF` markers used to reproduce compiler choices such as register allocation or instruction scheduling. Most are described as non-emitting constructs, while the remaining assembly is said to correspond to code the original developers also wrote in assembly. This distinction matters: byte identity validates the build output, not the readability or historical authenticity of every source spelling.
The project contains no game assets or code copied from the discs, and it requires users to supply their own images of the debug discs. It also states that the reconstructed game and SDK source remains the property of its respective owners, while the project’s own build scripts, tools, and documentation are released under CC0. The packet does not independently establish the legal status of the reconstruction, so the repository’s preservation framing should not be read as a legal conclusion.