- Level
- Beginner
- Before you start
- A saved multiplayer scenario. A second game instance or another player is needed to check joining. Each player needs their own required game content.
- You will make
- A verified package, a recoverable source project, and a checklist for a successful host-to-joiner test.
Shortcuts use Ctrl; Cmd also works on macOS, and Alt is Option. Keep the pointer over the viewport for editing shortcuts. Save before switching projects.
Know which file you are handling
| File or folder | Purpose | Keep it |
|---|---|---|
Kit Projects/<name>/ | Editable project: .rkscenario plus imported pictures or sounds beside it. | Back up the whole folder, together with any custom source dependencies. |
Mods/<name>/ | Playable package: map, metadata and any companion files. | Keep the whole package together when copying it. |
.rkmap | A recipe describing edits that another installation can rebuild. | Keep with the package; it is not the same as a scenario or a standalone map. |
.rktags | Reusable tag edits for application to compatible maps. | Optional authoring tool; it does not replace the package. |
These paths are relative to the player folder. Find that folder for your platform in How to play. An original installed map is never a compile destination.
Build the package
- Save firstSave your scenario with Ctrl+S. Use a distinct name such as
courtyard_release. Save and Compile are different operations; compiling is not a backup of the whole project. - Inspect the Compile panelIn Scene → Compile, check Package name and Compile for Reclaimer. On a compatible installed multiplayer base, leave the recipe option enabled. Read any reason it is unavailable.
- CompileSet the intended name in Scene → Compile → Package name, then press Ctrl+B. If Save As appears, confirm the name and choose Compile Map. Later compiles can start immediately using the panel's name; saving a scenario under a new name does not necessarily rename its package. Wait for the completed save report. Do not copy files while the map is still being written.
- Inspect what was producedFind
Mods/courtyard_release/. Keep the metadata, sound banks, Forge data and recipe media with the map. The Kit shows a compile report with tag origins and package size; use it to investigate unexpected additions. - Keep editing from the scenarioFor the next revision, reopen the scenario, edit, save and compile again. Opening a built package as a new base loses the original installed-map recipe workflow.
Verify the artifact you will share
Choose File → Verify Map…, then Verify the compiled map. If you are checking an older or copied build, use Verify a map file… and select that exact file. The verifier walks tag references, strings, resources and indices.
Read every error and warning. A double-click opens the relevant tag. Correct the source scenario and compile again when the problem came from your edits. Aim for No problems, while also understanding any warning you decide to retain.
Verification checks map structure. It cannot prove that a player can reach an objective, that a weapon is balanced, that a sound plays at the right event or that a friend can join. Check those in the saved map.
Test the saved map as a player
- Open the compiled package and repeat the tutorial's observable result: walk the route, use the teleporter, pick up the custom weapon, check the texture and trigger the script.
- Host the intended game type. The editor's Slayer playtest does not test objective scoring or team-specific placement.
- Restart the game on that package once. This catches edits that were visible only in the editor's live state.
- Keep the source scenario separate from the saved map you are inspecting so you know which result you are testing.
Check a host and a joiner
- Start the game separatelyClose the Kit after saving and open Project Reclaimer. Choose HOST GAME, then your map in the MAP row and the intended GAME TYPE. The Kit itself does not lead to the game's main menus.
- Allow the package to travelIn HOST SETTINGS → MODS, enable Share mod files. For a private check on one computer, use local hosting and direct connect; on a local network, set NETWORK to LAN and the game shows in the other PC's server browser. For a public session, follow the hosting guide.
- Join from the other sideUse the server browser or DIRECT CONNECT from the second game. When prompted, use DOWNLOAD & JOIN. The host's map and the joiner's reconstructed map must match.
- Compare the authored behaviorWalk the same route on both sides. Check the teleporter destination, custom weapon behavior and any imported media. A successful download alone does not check the content.
- Record requirementsList the game content and custom dependencies the map needs. A recipient must own the required content even when the download is only a small recipe.
Expect the right download size
A recipe can be much smaller than a whole map, but it is not always only a few kilobytes. Imported replacement pictures and audio add data. Source imports, new assets built with your tags folder, re-baked lighting and campaign maps can require the whole map. The Compile panel reports the applicable workflow.
A host shares a recipe only when the map still matches it. Hand-editing package files can invalidate that relationship. If a join fails with a mismatch, check the required installed content and rebuild from the saved scenario before changing unrelated settings.
Publish to the Steam Workshop
Once the package has passed the checks above, the Kit can upload it to the Master Chief Collection's Workshop itself. Steam must be running and signed in to an account that owns MCC.
- Take a pictureOpen the map and choose View → Picture Mode. Frame the map, choose the 16 : 9 or square frame and press Take Picture (Enter). The JPEG is saved in
Kit Picturesat a size the Workshop accepts. Esc leaves Picture Mode. - Open the publish windowChoose File → Publish to Steam Workshop… and pick your package from the Mods folder.
- Describe itEnter a title and description, choose the picture with Browse…, and add the Workshop's tags by name if you want any. The window says at once whether the picture fits: a PNG or JPEG under 1 MB that the game can show.
- Keep it private firstA first publish makes a new item, private unless you choose otherwise. Publish, check the item on your own Workshop page, and widen who may see it when you are ready.
- Update the same itemAfter a fix, compile under the same package name and publish again with a change note. The Kit remembers the item in
kit-workshop.jsonbeside the package, so keep that file with it.
Observable result: the item appears on your Workshop page with your picture, and a subscriber's game lists the map with the same picture.
Share objects or sounds, not a map
Two boxes in the Scene tab's Compile panel change what a package is for. Both compile the whole map, so neither takes a recipe.
- Tags only (content for other maps) makes a map of shared tags: it is in no list of maps to play, and every vehicle, weapon, equipment, scenery and crate it adds is offered to any other map, in Forge and in the Kit, each named after its tag. Put a mod's objects in one such map and its other maps, or anyone's, can place them. In Forge, turn the mod on among the object sources.
- Sounds inside the map moves the sounds the map plays from its package's own sound banks into the map file, so the map plays without bank files beside it. It is off by default, and isn't offered with Compile for Reclaimer. For a package you already have,
project-reclaimer --kit-tool hold-sounds PACKAGEdoes the same for Halo 3, ODST and Reach packages; add--sharedto keep what its maps share once, inshared.sounds.
Observable result: with Tags only, the package's map is missing from the map picker while its objects appear in another map's object browser under the mod's title.
Finish with a recoverable project
Back up the entire Kit Projects folder for the scenario. If it imports loose tags or source files, keep those inputs and note their locations in your own project notes. Copy the entire Mods package when sharing by folder; do not leave out its sound bank or Forge sidecar.
Hosting, sending a package folder and publishing to the Workshop are the supported paths. A scene that only moves, deletes and places Forge's objects can also be saved with File → Save as Forge Map…, which nobody has to download. Only distribute content you have the right to share, and keep the recipient's required game installation separate from your authoring files.
Keep learning
Return to the tutorial library, look up a control in the Kit reference, or follow dedicated-server mod setup.
