download the latest release ·
join the discord ·
check out the youtube
forever compatible, for everyone
GulchCE is a fork of OpenCommunityEdition/OpenCE- the Halo: Combat Evolved decompilation project targeting Linux,
Windows, Android and web browsers.
No game data is included. You need your own copy of Halo: Combat Evolved for the original Xbox to get started.
Any fork compatible with OpenCE is also compatible with GulchCE. Crossplay galore!
Halo is a trademark of Microsoft. GulchCE is a fan project, not made or endorsed by Microsoft, Bungie, 343 Industries, or Halo Studios, and does not include any game assets or content.
- Download a release build for your platform. Debug builds are intended for troubleshooting and stop when an assertion fails.
- Start
halo.exeon Windows,haloon Linux, or the Android app. Browser players use the site's import prompt. - Select your Xbox Halo disc image (
.isoor.xiso) when prompted. GulchCE extracts the Xbox maps and starts the game. On Windows and Linux, you can also place the image beside the executable.
Xbox data goes in maps. Custom Edition and MCC content use their own folders:
| Content | Folder in the game data directory |
|---|---|
| Original Xbox maps | maps |
| Halo Custom Edition maps | custom_maps |
| MCC maps and packages | mcc_maps |
Keep these folders separate. Halo PC or MCC data does not replace the Xbox data needed to start GulchCE.
For installation, controls and platform requirements, see the Windows, Linux, Android or browser guide. Settings are available in the menus and config.toml.
GulchCE is one of several community forks of the Halo: Combat Evolved decompilation and OpenCE. Each has its own focus, and they borrow from each other. Some notable ones:
thelinkin3000/SlipstreamCE, by thelinkin3000: an OpenCE fork focused on mobile and console platforms, among them its own Vulkan renderer and dynamic lighting on mobile and console platforms, and MCC custom map support. SlipstreamCE's dynamic lighting is ported from GulchCE, and its MCC support builds on GulchCE's. If you're an Android player, this is the best place to experience OpenCE.
Watanoge/halo-content-evolved, by Watanoge: the Xbox game with Watanoge's own quality-of-life changes for the Switch, with a lot for the campaign, such as skulls and a randomizer.
BirchWoodGod/halo-ce-vita, by BirchWoodGod: the decompilation ported to the PlayStation Vita, now adding Halo 2 support and Forge. Its bots are SlipstreamCE's Birchwood bots.
GulchCE supports Halo 1 MCC maps, including Workshop multiplayer maps and campaign packages. Compatibility is experimental; some maps or scripted features may not work correctly.
- Install Halo: Combat Evolved through your copy of MCC on Steam.
- Subscribe to the Halo 1 Workshop maps or campaigns you want and let Steam finish downloading them.
- Start GulchCE and open the MCC map or campaign selector.
Steam Discovery and Campaign Missions are enabled by default. Existing configurations retain your previous choices. Find these settings under Settings > Online > Map Sharing > MCC Packages in Modern menus, or Settings > Network Setup > Map Sharing > MCC Packages in the other menu styles.
GulchCE reads installed Workshop packages directly. When a map needs MCC's shared base resources, it can also read them directly from your installed MCC copy. You do not normally need to extract or copy those resources yourself. Package-supplied resources take priority, and Steam does not need to stay open while you play.
If a newly downloaded package is missing, reopen the map list or restart GulchCE. If your Steam installation is not detected, set its installation or library folder in the existing [paths] section of config.toml:
[paths]
steam = 'C:\Steam'Download MCC's shared files and Halo 1 Workshop maps directly in GulchCE:
- Open Settings > Online > Steam Workshop in Modern menus, or Settings > Network Setup > Steam Workshop in the other menu styles.
- Sign in with a Steam account that owns Halo: The Master Chief Collection and Halo: Combat Evolved Anniversary, then complete Steam Guard approval if requested.
- Use MCC File Status to download the shared resources, then Browse Workshop to find and install Halo 1 maps or campaigns.
When you join an MCC game while signed in, GulchCE can install its Workshop package and missing shared resources directly from Steam. It checks the package against the host's copy; if it differs or the download fails, the existing host-download prompt remains available. See the Steam Workshop guide.
Manual installation remains a fallback: copy a complete Workshop package folder or ZIP from your PC. Quit GulchCE, long-press its launcher icon, choose Import MCC maps, then select Workshop package. Import required base resources using Singleplayer shared resources or Multiplayer shared resources. See the Android import guide.
Workshop packages are stored on your PC under steamapps/workshop/content/976730/<workshop ID>. Keep their maps, package resources, JSON metadata and artwork together.
Import your Xbox data first, then use Custom maps to import CE files or an MCC package folder. See the browser import guide for supported layouts and storage limits.
Copy the complete downloaded Workshop folder from steamapps/workshop/content/976730/<workshop ID> into mcc_maps. Keep its contents unchanged: GulchCE reads the nested maps, metadata and previews, showing the authored mod and level names instead of the numeric folder name. Steam Discovery is not required for local packages.
The manual method still works: create mcc_maps/MyCampaign and place .map files directly inside it, with any supplied bitmaps.map and sounds.map. Metadata and previews are optional; without them, the menu uses folder/map names and its placeholder picture. Do not mix resources from different packages.
If Steam Discovery is unavailable or disabled, required base resources can be copied from your MCC installation into these locations:
| MCC installation file | GulchCE destination |
|---|---|
halo1/maps/bitmaps.map |
mcc_maps/_shared/singleplayer/bitmaps.map |
halo1/maps/custom_edition/bitmaps.map |
mcc_maps/_shared/multiplayer/bitmaps.map |
halo1/maps/custom_edition/sounds.map |
mcc_maps/_shared/multiplayer/sounds.map |
These are MCC's resources, including its own custom_edition directory. Self-contained packages do not need shared resources. See the package layout guide for manual layouts and supported metadata.
- Modern, Stock and Classic PC: choose MCC Singleplayer or MCC Multiplayer, open the package and select a level.
- Xbox menus: use MCC Campaigns on the main menu for campaigns, or X — MCC Maps in the multiplayer map selector.
Campaign Missions uses the package's metadata for mission order and progression. Supported titles and previews appear automatically.
Copy your Custom Edition maps into custom_maps, together with bitmaps.map, sounds.map and loc.map from your Custom Edition installation. Select them under Custom Singleplayer or Custom Multiplayer.
The Gearbox multiplayer maps, such as Ice Fields and Death Island, can also be copied from your Custom Edition installation. They are not bundled with GulchCE. Maps that require OpenSauce are unsupported.
See the Custom Edition guide for format support and limitations.
- Join through the server browser or an invite link, or host a public or private game.
- Play campaign co-op or multiplayer across Windows, Linux, Android and browser builds with compatible network versions.
- Multiplayer supports up to 128 players, with up to four local players per device in split screen.
- Voice chat, host moderation, bots and additional gametypes are available in the game settings.
Use matching GulchCE builds when playing together. This development branch changes the network agreement and cannot join older OpenCE or GulchCE builds. GulchCE Standard disables the optional multiplayer shoulder camera; GulchCE Third Person uses a separate camera agreement and requires matching clients.
Older cores and checkpoints from before the saved-state layout change are incompatible. Start a new map or campaign session; the game does not migrate those saves. See the checkpoint guide.
The host's existing Map Sharing setting covers both Custom Edition maps and MCC packages. It is enabled by default. There is no separate Share MCC Packages option or manual package approval list to configure.
- Custom Edition: missing maps and required CE resource files can download from the game's players.
- MCC: Android players signed in with Steam can download Workshop packages directly from Steam. Otherwise, the joining player is offered a download from the host. Workshop packages can also offer a link to their Steam page, with a browser fallback on desktop.
- MCC base resources stay local: packages may depend on them, but those shared base files are not supplied by the host. Each player needs matching local resources, discovered from MCC on desktop, downloaded from Steam or imported on Android, or imported in the browser.
Downloaded MCC packages are validated before use. Download Maps controls whether a joining player accepts map downloads; transfers from the host ask for confirmation. Steam installs can update an existing Workshop package.
Run halo --server (halo.exe --server on Windows). Dedicated servers support Xbox, Custom Edition and MCC maps, including MCC campaign co-op. Use sv_maps to list available maps and their paths.
See the dedicated server guide for setup, rotations, administration and deployment. OpenCE also documents Zenith Hosting for managed dedicated servers.
Settings include display and frame-rate options, FOV, smooth motion, controller bindings, touch controls, menu styles and optional visual effects. The settings reference lists their defaults and platform availability.
Loose-tag mods go in mods and can be enabled or reordered from the menu. They apply to Xbox and Custom Edition maps; MCC packages use their own authored resources. See the mod guide.
Install Python, Ninja and the tools listed in your platform's guide, then run:
python configure.py --release
ninja windowsUse ninja linux, ninja android_apk or ninja web for the other platforms. Add --portable when configuring native builds intended for other computers. The Xbox SDK is not required.
Start with the code reader's guide, repository requirements and coding standards. Platform guides cover build options; the repository requirements list the regression checks.
Release downloads include SHA256SUMS for verification. Where signing is configured, verify SHA256SUMS.sig with tools/release_sign.sh verify SHA256SUMS using OpenSSL 3 and the release key.
GulchCE is maintained by Chester (@chestahh) and its contributors. It builds on OpenCE, including the work of Jonas Volman (@bnunu), MrBruh (@cybersecurity) and the OpenCE contributors.
The decompilation comes from bnunu/halo-1, a fork of punpckhdq/halo, and targets Xbox build 2342 (cachebeta.exe). Artwork credits are in AUTHORS.md; bot and Android feature credits are in the provenance guide.
Current revisions are licensed under AGPL-3.0-or-later, with no warranty. Earlier revisions and releases published under CC0 1.0 retain that licence. Contributions use AGPL-3.0-or-later; adapted GPL code retains its notices, including the GPL-3.0-only bot tactics. Third-party code, fonts and artwork retain their own licences and accompanying notices.
GulchCE is an unofficial fan project, not affiliated with or endorsed by Microsoft, Bungie or Halo Studios. Halo is a trademark of Microsoft Corporation. The project's licence does not grant rights to Halo or its game data.

