# Sly 2: Band of Thieves gets a matching decompilation, v1.0

> Sly 2: Band of Thieves has a matching decompilation v1.0 on GitHub. All 6,662 functions match the PS2 original byte for byte.

- Published: 2026-11-03T12:30:34Z
- Score: 9/10
- Tags: ps2, decomp, pc
- Port / platforms: PS2 -> PS2 (Decompilation)
- Web page: https://emu-radar.customfw.xyz/news/sly-2-band-of-thieves-matching-decomp-v1/
- Sources: https://github.com/Komasia/sly2-decomp/releases/tag/v1.0

The Sly 2: Band of Thieves decompilation project, [sly2-decomp](https://github.com/Komasia/sly2-decomp), shipped v1.0 on October 30, 2026. The README says all 6,662 functions now match the original PS2 game byte for byte.

A match means the team's C code, built with the same compiler settings, produces the same machine code as the disc. Every call and data address in a matched function is checked against the original. The project tracks this with a progress graph and a list of verified functions.

The repo holds no game data. You need your own disc. The target is the NTSC-U build, `SCUS_973.16`, and the README gives its SHA-1 (de2af92a54de71e33edc8a160c31c0337a95e6f5), so you can check your copy before you build anything. The build runs on Linux through `tools/wibo-i686`. The compilers come from decomp.me's collection, which the setup guide covers.

How to try it:

1. Read SETUP.md and have your disc ready.
2. Run `tools/setup_all.sh`. It fetches the compilers and tools and pulls the executable from your disc.
3. Install the Python packages with `pip install rabbitizer spimdisasm splat64`, and make sure PYTHONPATH includes rabbitizer.
4. Run `tools/progress.py` to rebuild every source, regenerate the match list, and print totals.

To check one file, use `tools/matchtool.py check FILE [func...]`.

Most functions still have address-based names like `func_XXXXXXXX`, and the types are rough. Naming can come later without affecting the match. The README does not describe a PC or other port, so this work gives you a clean, verified codebase for the PS2 game, not a way to run it somewhere new.
