Reclaimer Kit · Lesson 8 of 11

Build and inspect an AI encounter

Learn three workflows: a multiplayer AI spawner with its own health, behaviour and patrol route, a squad of your own on a multiplayer map with characters of any installed Halo, a team and a patrol route, and a mission squad whose starting locations, areas and objective explain its behavior.

Level
Advanced
Before you start
A multiplayer scenario for the first two exercises. For squad inspection, an installed Halo 3 mission such as Sierra 117. Campaign editing remains partial.
You will make
A configured multiplayer spawner, a patrolling squad that plays in the compiled map, a squad of another game's characters, plus a working understanding of a mission's squad → fire team → starting location and objective → task → area relationships.

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.

Choose the right AI workflow

A multiplayer map has two ways to get AI. Forge AI spawners in the object browser are the quickest: one object with its team, health, behaviour and patrol route, which Forge can place too. Squads in the AI tab give you more: your choice of character from any installed Halo, vehicles, several starting locations, a team, a patrol route, zones and objectives. Mission AI is authored in the same tab using squads, fire teams, zones and objectives. Placing a biped object is not the same as creating a squad with orders.

The mission part of this tutorial is an installed-map learning exercise. Campaign compilation is partial, and compiled missions have a known crash when some AI squads are placed. Do not treat successful editing in an installed mission as proof that a campaign mod is ready to share.

Make a small multiplayer encounter

  1. Save a separate projectOpen your multiplayer scenario and save as courtyard_ai. Choose a clear patch of walkable ground, away from the player start and from any kill volumes.
  2. Add one spawnerIn the object browser, choose Forge and find an AI Spawner. Place one of a kind the map offers. Avoid placing a large group before testing the first.
  3. Give it explicit behaviorIn the Object tab, review Team, Shoots at, Moves, Weapon, Returns and Place at start. Choose settings that let you observe movement and firing safely. While you edit, the spawner is drawn in its team's colour: grey for Enemy of all, white for Ally of all players.
  4. Tune its AIBelow, set Health and Shields and armor as a share of what its character has in its campaign, or tick Invulnerable. Under Behaviour, untick what it shouldn't do, such as Throws grenades or Enters vehicles.
  5. Give it a routePut the 3D cursor a short walk away and choose New route point; add two or three more. Choose Round and round or Back and forth under Walks its route. Its AI walks the route while it has nobody to fight. The Kit's own view places the AI without these settings: check them in a game on the compiled map.
  6. Play the encounterPress F5. Observe whether it appears where expected, can move around cover, targets the intended side and returns as configured.
  7. Save and compileReturn, save the scenario and compile it. Check the same behavior, health and route on the compiled map before increasing the encounter size.

Give a multiplayer map its own squad

A multiplayer map has no AI data of its own. The host of a game on your compiled map places its squads a moment after each round starts and works out where they can walk, so you only author the squad.

  1. Put the 3D cursor on open groundHold Shift and right-click a flat, walkable spot away from spawn points. New AI elements go to the cursor.
  2. Make the squadOpen the AI tab and choose New squad. On a map with no squads it makes one with a single fire team and one starting location at the cursor.
  3. Give it a characterSelect the fire team and use Character of a biped to make a character for a biped the map has: a Spartan or an Elite is on every multiplayer map. Then choose it as the fire team's Character, and set a Weapon and Count (normal).
  4. Choose sidesOn the squad, set Team to Enemy of everyone, Friendly to every player or a team colour. Set Shoots at and Respawn (seconds); 0 keeps the squad gone for the round once it dies.
  5. Lay a patrol routeMove the 3D cursor a short walk away on the same floor and choose New patrol point in the squad's Patrol route. Add two or three more. The points appear in the 3D view joined in walking order; drag one with the move gizmo or G, and press Delete to remove it.
  6. Look at it in the KitChoose Load into Game, then Place squad. Check that the actors stand on the ground with the weapon you chose. Erase squad removes them again.
  7. Compile and playSave the scenario, compile the map and host a game on the package. Watch the squad appear shortly after the round starts, walk its route round and round, and break off to fight according to its team and targets.

Zones are optional here. New zone in the Zones section makes one at the cursor with a first area, New firing position adds positions to it, and the squad can take it as its Initial zone. To make a squad advance, choose New objective, which gives the map its first objective, give its task the area and tick Goal, then set the squad's Initial objective and Initial task.

Bring in another game's soldiers

A squad's character can come from another map or another game you have installed. Compile Map brings it in from its mission with its body, weapons and behaviour, so it fights as in its own campaign. Players who join need that game installed.

  1. Offer the game's objectsFor Halo: Reach's characters, tick Halo: Reach's objects under the object browser's sources: the map loads again with them, and your edits come back. Halo 3: ODST's, Halo 2's and Halo: CE's characters only need their game installed.
  2. Pick a characterSelect the fire team and open Characters of Halo: Reach, Characters of Halo 3: ODST, Characters of Halo 2, Characters of Halo: CE or, for Halo 3's missions, Characters of other maps. Search by name, such as elite, and choose one. It joins the palette as (of its map, merged in as the map compiles); make it the fire team's Character.
  3. Give it a vehicle, if you likeWith Reach's objects on, Vehicle of another map adds one of Reach's vehicles, such as its Warthog or Revenant, to the vehicle palette. Set it as the fire team's Vehicle. A character drives it where its own campaign has it drive one.
  4. Compile and playThe Kit's own view places nobody of another map's character until the map is compiled. Compile, host a game on the package, and watch the squad: Halo: CE's Grunts flee when their leader dies and its Elites berserk, as in CE.

The quick way. Forge AI spawners of every installed game are in the object browser too: tick a game's objects and search for, say, Elite (Reach). Leave a Reach spawner's Weapon on Its own.

Read a mission squad

Open the installed Sierra 117 mission in a separate session, saving your multiplayer project first. In the AI tab, select one of the map's existing squads. Inspect its fire team and starting locations before changing anything. Use this model:

ElementIts job
SquadNames the group and assigns its team, initial zone, objective and task.
Fire teamChooses character, equipment and count; it contains starting locations.
Starting locationPlaces a potential spawn and can override the fire team's character, weapons or vehicle.
Zone → area → firing positionGroups positions the AI may use. Firing positions are candidate destinations; they are not the navigation mesh.
Objective → task → areasDecides which squads may use which areas under the task's conditions and limits.

Try a controlled squad edit

  1. Pick a simple existing squadChoose one on the loaded BSP that already has a character, weapon and valid starting locations. Record its current fields. Avoid changing a mission-critical squad's identity or removing its elements.
  2. Inspect one fire teamReview Count (normal), Character and Weapon. Select a starting location and frame its marker in the viewport. Check the ground beneath it.
  3. Place and erasePlace squad spawns the selected squad now. Erase squad removes its actors; it does not delete its authored definition. Mission scripts can place squads independently, so keep this separate from normal mission progression.
  4. Test one changeChange a simple existing value such as the normal count, erase the squad and place it again. Check the resulting actors. Undo the edit afterward if you only wanted to inspect it.
  5. Reload structural changesNew or removed squads, fire teams, starting locations, areas and tasks change the scenario's structure. Use Load into Game or Play when required; seeing a new tree row is not proof that the runtime has it yet.

Understand why a squad stands still

Inspect the squad's Initial zone, Initial objective and Initial task. In the Objectives tree, select that task and inspect its Areas, priority, filters and squad/body limits. Follow an area into the Zones tree and look at its firing positions with Overlays → AI firing positions.

For an isolated authoring experiment, use New area inside an existing zone, then New firing position on walkable ground. Assign the intended area to the task and load structural edits into the game. The actor still needs valid navigation between positions: placing dots on the other side of an impassable gap does not create a route.

The Kit can add a zone with New zone but does not remove one. Jump, climb and well hints need rebuilt level pathfinding before the AI can use them; saving a hint alone is insufficient. Keep the base mission's zone setup while learning.

Check behavior, not just actor count

  • For multiplayer, check spawning, target selection, movement and the configured return behavior in both a playtest and the saved map.
  • For a squad of your own, check it on the compiled map: that it appears after the round starts, completes its route and respawns after the time you set. A squad of another game's characters plays only on the compiled map. If its AI stop part of the way, the walkable area the host worked out has a gap there: keep the route on one level and move the points.
  • For mission inspection, confirm you are on a loaded BSP and that the selected squad has a valid character, weapon, count and starting location.
  • If actors stand still, inspect task areas and reachable firing positions before changing their weapons or adding more actors.
  • Do not delete squads or reorder scenario markers casually. Existing scripts can refer to their positions in the authored lists.

Save mission experiments under a new scenario name, keeping the installed map intact. Read campaign limits before compiling or sharing them.

Next step

Connect a condition to a scripted event. Reference: AI tab, Forge AI. For the classic tools, c20 has complementary AI spawning, pathfinding and objective guides. Their interface instructions are for Sapien.