Jonas VolmanandClaude Opus 5 7a3bbb9c87 Test the bsp3d plane designator sign bit with LONG_MIN
January's decals copy of the bsp3d_get_plane_from_designator inline branches on the sign bit (jns), matching the punpckhdq upstream spelling. Full build: decals::_bsp3d_get_plane_from_designator exact (112 padded), 0 regressions across all bsp3d.h consumers, parks clean.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-13 19:58:56 -07:00
2026-09-13 03:49:13 -07:00
2025-11-27 02:27:27 +00:00
2026-01-03 00:47:17 +00:00
2026-06-29 11:34:11 +01:00

Halo 1 decompilation Build Status Code Progress Data Progress

This is a work-in-progress decompilation of Halo: Combat Evolved build 2342 (cachebeta.exe, sha256 4cc87b45f721270392a96f1674ed2b5cd4a7bb4355faeab4531d1cf1884d9520).

Agent quick references

Build instructions

You must source the Halo 1 PAL debug build and the August 2001 Xbox SDK yourself. You also need ninja-build on your PATH.

Extract the XDK/xbox folder from the installer into the repository root such that xbox/{bin,include} are valid paths. Place cachebeta.exe from the Halo 1 build into your repository root. Navigate to the repository and run configure.py in the terminal.

Then, use ninja build to compile the game and report progress statistics, or open the cachebeta.sln VS2022 project under projects on Windows.

Where's all the type information?

We use debug symbols from later Halo games to help map structures, enums, type definitions, function signatures and some variable names. You should obtain a copy of the Halo CEA beta and run it through pdb-decompiler to obtain debug info for yourself. Note that CEA is based off of Halo PC and has its own modifications which make it not 100% accurate to the original Xbox title.

2026-10-27 19:00:41 +01:00
Languages
C 90.1%
Python 6.7%
JavaScript 1.3%
Java 0.6%
C++ 0.2%
Other 0.8%