Halo Reach Editing Kit
This page is incomplete! You can contribute information using GitHub issues or pull requests.
The Halo Reach Editing Kit (HREK) is the official set of tools for creating custom content for the MCC version of Halo Reach. Similarly to the mod tools for Halo 2 and 3 it is ultimately based on the old internal tools used by Bungie during the development of Halo Reach, with modifications made during the porting of the game to MCC and some changes to make them more user-friendly.
- Ensure you own Halo Reach on Steam, tools are only accessible if you own the Steam version.
- Download the tools using Steam, you might need to install Steam first.
- Follow the on screen prompts to download the tools.
- Once the tools are done downloading you can find them in your library in the tools section.
- Right click the entry for the mod tools, select the "Manage" context menu entry then select the "Browse local files" subentry.
- Run the
Extract (HREK).batfile - this will extract all the files required.
- If your operating system supports it you should enable file system compression for the
tags\soundsfolder. This is a workaround for high disk space usage caused by sound tags including zeroed out sound data.
- (Optional) Check out the guides hub to learn more about modding or install a launcher like Osoyoos if you don't like using the command line.
- Make sure you didn't update any stock tags, and if you did make a backup of those files.
Extract (HREK).batand replace all files.
Naturally there is multitude of changes compared to H3 as the engine underwent a major revision, this document endeavours to list the major ones.
- Bonobo takes the place of Guerilla as the kit's tag editor with a completely new UI that makes it easier than ever before to create and modify tags.
- Structures can no longer be created using ASS files, you need to use GR2 files.
- Resource sharing is currently not supported.
- Halo Reach custom maps require that EAC is turned off to load
- Halo Reach custom maps requires that the map info matches the map it is replacing to load. This means having the same campaign and map ID. These values can be found at the top of the scenario tag.
- Single threaded lightmapping is not supported, you need to use the multi-process solution. This can be run with only a single client if only using one core is desired.
- Sound playback and sound importing require the FSB files that come with MCC in order to function. Copy the FSB files from your Halo Reach MCC install.
- The mainmenu requires the mapinfo files that come with MCC in order to load levels. Otherwise you will need to use
init.txtor the developer console to load scenarios in the standalone build.
- All the stock tags do not contain import info so you will not be able to extract source assets that way.