Start here
These tutorials turn the Kit reference into small projects with observable results. Each gives you prerequisites, numbered operations, a check of the saved result and a way to diagnose common failures. Work from your own scenario and use a separate name for each experiment.
New to the Kit? Complete Your first map first. It covers opening the app, camera movement, adding an object, saving and compiling. Then start with the blockout lesson below. The installed maps are inputs; your scenarios and packages are separate outputs.
These guides focus on Halo 3 multiplayer, the established editing workflow. The AI lesson labels its installed-mission exercise separately. The Kit reference lists campaign limits and other incomplete workflows. Having an editing control does not mean every compiled campaign or cross-game combination is supported.
Choose a learning path
| Your goal | Work through | Files needed |
|---|---|---|
| Build a multiplayer space | Blockout → Gameplay → Lighting → Detail → Sharing | MCC Halo 3 maps. Lighting bakes are optional and need your tags folder. Publishing to the Workshop needs Steam running. |
| Customize behavior and media | Weapon tags → Textures and sounds → Reusable Tag Sets | Field names are built in; no Editing Kit install is needed. Use your own media for imports. |
| Author events and encounters | HaloScript → AI encounters → Saved-map checks | A multiplayer scenario; an installed mission for squad inspection. Other games' characters need those games installed. |
| Let an assistant do the repetitive work | AI encounters → AI assistants | An MCP client on the same computer, such as Claude Code. |
The tutorials
Build a playable blockout
Make a small route with cover and a raised platform, then save a reusable piece. Learn the editing loop before adding detail.
Set up multiplayer gameplay
Connect two parts of a level with a teleporter, place useful pickups, and check how a chosen game type uses the map.
Light and dress a scene
Give an existing route a clear focal point with a scenario light, a decal and restrained atmosphere changes. Learn what needs a bake.
Paint surface detail
Use the decorator brush and its spread options for small foliage and ground detail, then check that the saved map contains your strokes.
Change a weapon without changing every copy
Learn the difference between an object placement and its shared tag. Make a seven-round rifle and keep an ordinary rifle beside it for comparison.
Replace a texture and a sound
Bring your own picture and recording into existing assets. Follow one visible texture and one audible sound through preview, save and compile.
Write and test HaloScript
Start with a command you can call on demand, then connect a named trigger volume to a one-time event. Keep compile errors separate from runtime behavior.
Build and inspect an AI encounter
Learn three workflows: a multiplayer AI spawner with its own health, behaviour and route, a patrolling squad of your own with characters of any installed Halo, and a mission squad whose starting locations, areas and objective explain its behavior.
Reuse tag edits across maps
Save one controlled weapon edit as a Tag Set, apply it to another map, and read the report before compiling.
Compile, verify and share your map
Take a saved scenario through a checked package and a real join, then publish it to the Steam Workshop. Keep the work file, the playable map and the download recipe straight.
Work the Kit with an AI assistant
Turn on the Kit's assistant server, connect an assistant such as Claude Code, and have it stage and playtest an AI battle, every edit one you can undo.
Use the same editing loop
- Save an experimentGive the scenario its own name before trying a new system. Keep imported media and source dependencies with your project.
- Make one observable changeUse a small route, a distinctive texture, a seven-round magazine or a printed script message. Change one cause at a time.
- Check when it reaches the gameA transform can be live; growing a tag needs a reload; a new marker must reach a rebuilt map. See What shows when.
- Test as a playerUse F5 to check the live setup, then open the compiled package and check the saved behavior. Host the intended game type when testing objective rules.
- Verify and shareVerify the compiled map, keep the complete package, and check a joiner before assuming a recipe or imported asset works on another installation.
Coming from Sapien, Guerilla or Tool?
The learning progression is inspired by the classic Editing Kit: place objects, set up encounters, edit tags, compile scripts, build and test. These are original Reclaimer tutorials. The buttons and shortcuts below belong to the Kit; Sapien's hotkeys are not interchangeable with them.
| Classic tool or concept | In the Reclaimer Kit |
|---|---|
| Sapien hierarchy and properties | Level workspace, outliner and Object/Scene/AI tabs. |
| Sapien camera and player simulation | Viewport navigation, F5 playtest, then F5 to return. |
| Guerilla tag editing | Tags workspace. Distinguish map tags, tags-only map sessions and loose tag files. |
| Tool imports and map builds | Assets, File → Import Tags and Compile Map. |
| Scenario source versus playable cache | Save Scenario keeps your editable work; Compile Map writes a playable package. |
| Editing Kit scenarios and tags of any game | Link each kit's tags folder in Edit → Preferences, then File → Open Scenario and File → Open Tag. See the reference. |
| Forge maps | File → Open Forge Map and File → Save as Forge Map, for scenes of Forge's objects alone. |
For background on the official tools, read c20's Sapien reference, AI spawning tutorial, pathfinding guide and objective guide. They explain shared authoring concepts and document Sapien's own interface. No c20 text or assets are bundled here.
When a step fails
Check the selected workspace, active item and exact tag path first. Then check whether a reload, compile or different game type is required. Use the troubleshooting reference and View → Info Log for reports that have left the status bar.
For a useful bug report, state your Kit version, platform, base map, the last successful step, the step that failed and the visible error. Describe the expected saved-map behavior. Keep original game files and your personal profile out of anything you share.
