- Level
- Intermediate
- Before you start
- A Halo 3 multiplayer map. Field names are built into the Kit, so no Editing Kit install is needed. No loose tag files are changed in this exercise.
- You will make
- A duplicated weapon tag, placed in the level, with an independently edited magazine.
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.
Understand what a tag change affects
A placement says where an object is and which tag it uses. The weapon tag defines the weapon shared by every placement that references it. Editing the original assault rifle's magazine changes that weapon throughout this map. Duplicating it gives you an independent weapon definition.
Save as courtyard_tags. Open Tags and search for assault_rifle.weap in Find a tag. Check both the group and full path: a render model or sound with a similar name is a different tag.
Duplicate before editing
- Open the weapon tagSelect the assault rifle's weapon tag and inspect its preview. Use Find references to see which tags use it before making changes.
- Make a copyChoose Duplicate… and give the copy a unique path, such as
objects\weapons\kit\tutorial_rifle. Keep the weapon group. Wait for the map to reload with the new tag. - Find the magazineThe line above the fields says where their names come from. In the copy, use Find a field to search for
rounds loaded maximum. Open the magazines block and check that you are editing element 0 of your copied weapon. - Browse without moving dataIf the block has several elements, use the number or its Previous and Next chevrons to inspect them. The separate Up and Down controls reorder the block, so leave those alone while looking for a field.
- Set an obvious valueRecord the old value, type
7for rounds loaded maximum and confirm it. Do not change reserve-ammunition fields at the same time; you want one observable difference. - Place the copyReturn to Level. The duplicated object appears under New tags in the object browser. Place it on open ground and place a normal assault rifle beside it.
Test a newly created instance
Press F5 and pick up the copied weapon. Check its loaded magazine, then compare it with the ordinary rifle. A weapon already alive before the edit can keep its current ammunition: check a fresh pickup or a newly loaded map before assuming the tag edit failed.
Return to editing. Undo the value change and confirm that the field returns to its previous value, then redo it. Reopen the original weapon tag and confirm its magazine still has its original limit.
Know the limits of a duplicate
A tag duplicate copies its own blocks and data. It still references other tags, such as a model, projectile or sound. Editing one of those referenced tags can affect both weapons. Follow the reference, inspect Find references, and duplicate that referenced tag as well if you need it to differ.
Use the reference field's Change… picker to point your custom weapon at the intended tag. A matching group is necessary, but a resolving reference alone does not prove the resulting weapon behaves sensibly.
Save the definition and the placement
- Save the scenarioUse Ctrl+S. The copied tag, its value edit and its placement belong to this scenario.
- Compile and verifyCompile under a new package name and run File → Verify Map… on the compiled map. Resolve any broken reference before moving on.
- Check the packageOpen the compiled map, pick up a fresh custom rifle and check its magazine again. Check a normal rifle too. This tests both the change and its intended scope.
Try the edit on CE, Halo 2 or Reach
The Kit also names the fields of maps composed from the other games, which play in Halo 3's format. For a small follow-up exercise, open one of these maps, edit its existing weapon’s magazines element 0 and set rounds loaded maximum to 7. This changes every instance of that weapon in the map. Save it as a separate scenario, compile it and test the resulting package.
| Game and map | Find in Map Tags | Original capacity |
|---|---|---|
| Halo CE: Blood Gulch | halo1\weapons\assault rifle\assault rifle.weap | 60 |
| Halo 2: Lockout | halo2\objects\weapons\rifle\battle_rifle\battle_rifle.weap | 36 |
| Reach: Forge World | objects\weapons\rifle\dmr\dmr.weap | 15 |
Use a fresh weapon after loading the compiled map. Check the HUD ammunition, shots until empty and reload behavior. A display drawn on the weapon can use an authored animation or a scaled meter; it is not always a literal count after you change its capacity.
Loose source files are separate: File → Open Tag File… opens CE, Halo 2 and Reach weapon files too. Each is read with its own game's built-in definitions, so it can be opened from any folder. Work on a copy, search for the same named field and use Save Tag. Saving a loose file does not change an already compiled map; that map needs the edited source imported and compiled through the appropriate workflow.
If the field or object is missing
| Problem | Likely explanation |
|---|---|
| Some values show only an offset | No definition covers those bytes; the line above the fields says where the names come from. See how well the names fit. Do not guess what an unnamed value means. |
| Every rifle changed | You edited the original weapon, or your placed objects still use the original tag. Check the selected tab's full path and the placement's tag. |
| New tag is visible but not usable yet | Wait for the reload or choose Load into Game when shown. Growing tag data needs the map to load again. |
| The custom rifle looks identical | Expected: a magazine edit changes behavior, while the render model reference remains shared. |
Next step
Carry edits between maps with a Tag Set or replace a texture and sound. Reference: Tags, blocks.
