Findings

All available recovered source from old Roblox clients, including partial and unfinished functions. Browse individual sources on the Clients page or download the full collection below.

Download all available sources
Includes exact matches and partial sources. Updated with each findings publication.

Download findings ZIP

What these files are

Each .cpp file is a recovered function or work-in-progress candidate. A 100% score means a byte-identical match; partial sources still differ from the original binary and may be incomplete or incorrect. Available sources are published regardless of score.

Files live under a client folder such as src/2008-06/. Comments at the top preserve compiler version, flags, library, and match provenance so results can be checked later.

Source-linked functions on the Clients page also link to their original source file or release archive when provenance is available. Match harnesses remain available beside those links; archive links show the original file path to find inside the download.

Why names look random

Names like 00546900.cpp are hexadecimal function addresses from the original executable. Address naming avoids inventing fake Roblox names and keeps every result traceable to its exact client location.

Many original symbols are stripped. Until a PDB, MAP, or reliable community name appears, random address names are more honest than guesses. Same address + same client means same recovered function.

How matching works

1 · Build candidates Compile leaked, community, and open-source code with period-correct MSVC.

2 · Fingerprint bytes Compare compiler output against each client function.

3 · Save proof Write matching source and compiler metadata beside the function.

4 · Review Analyze, classify, and improve names as new evidence arrives.

What happens at 100%

“100% matched” means every detected function has a source-backed match. It does not mean the project is instantly buildable.

Next work: reintegrate files into modules and classes, replace address names with verified symbols, merge duplicate code across clients, restore missing headers/build scripts, resolve dependencies, then compile and test a reconstructed client.

Until that work is complete, findings ZIP is a forensic corpus: useful for research, comparison, and continued decompilation.

Keep findings separate

The findings repository is intentionally separate from RoConstruct. Main project downloads stay lightweight; researchers can download the large ZIP only when they need recovered source.

Browse findings repository → · See source provenance →