spore-decomp

How it works

What "byte-exact" means

Spore's executable was built in 2008 with Visual C++ 2008 SP1 (and the Visual C++ Toolkit 2003 for its Havok and RenderWare code). This project rewrites each function as C++ and compiles it with those same compilers and options. A function counts only when its compiled bytes are identical to the shipped function's, apart from the addresses the linker fills in. Close does not count.

How a match is checked without the game

The repository contains no game code. For each retail function it keeps a fingerprint: its size, which byte positions hold addresses, and a SHA-256 hash of the remaining bytes. Every pull request runs the Byte-match check on GitHub, which compiles every function the change can affect and compares it with its fingerprint. It fails if anything that matched before stops matching.

Why bother

Byte-exact source is the strongest proof that a decompilation is right: it is the program, not an approximation of it. It is the foundation for preserving the game, understanding it, and eventually building it for other platforms.

What is not here

No game code, data or assets. Contributors use their own copy of the game locally to see instruction diffs; nothing derived from it is ever committed. The open-source libraries the game links (jpeg, libpng, OpenSSL, and EA's published EASTL and EAWebKit) are rebuilt from their published sources rather than decompiled.

Source, tools and every rule: github.com/NoahBPeterson/spore-decomp. Questions, or want to talk it through: join the Discord server.