Reclaimer Kit · Lesson 3 of 11

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.

Level
Intermediate
Before you start
A multiplayer scenario. Re-baking needs your own Halo 3 Editing Kit tags folder, set in Preferences; everything else works without one.
You will make
A scene with a deliberate light source, a decal on the intended surface, and a saved lighting setup.

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 a scene to compare

Save a new scenario named courtyard_lighting. Choose one piece of cover or a doorway as a focal point. Keep the camera in a repeatable position and compare each change with Undo and Redo. A bright camera exposure can make a weak light hard to see.

There are three different tools here. Scene → World changes multiplayer map settings. The globe-shaped World tab edits the scenario's sky and atmosphere tags. A Scenario light is an individual placed light. Change one system at a time.

Place a scenario light

  1. Choose its positionPut the 3D cursor near your focal point with Shift+right-click. Use Add → Scenario light and frame the new light.
  2. Pick a visible light tagIn the light's panel, choose a suitable Light tag. The first palette entry can be faint; try another if there is no visible effect.
  3. Set its reachEnable Its own shape and choose Sphere for a simple local light. Set Reach so it touches the nearby surface. For a directed beam, use Frustum and rotate its forward direction toward the surface.
  4. Set when it lightsUse Lit for to choose runtime lighting, lightmaps, or both. Avoid Cinematics only for a normal gameplay light. Inspect the scene in its lit view.
  5. Separate placement from shared settingsA light's own shape changes this placement. Colour and Brightness under Its light tag affect every light using that tag. Duplicate the tag before changing those values if the other lights should keep their appearance.

Put a decal on the intended surface

Use Add → Decal at the cursor, then choose a Decal system in its panel. Move it onto a clear floor patch. At Pitch 0 it lies on a floor; rotate its orientation for a wall. Check it from the player's side of the surface.

The visible decal uses the decal system's size. Scaling its marker changes the square drawn by the editor, not the decal's size in the game. If you need another size, choose another decal system or deliberately edit its tag.

Keep the atmosphere readable

In Scene → World, try a modest Exposure or Look strength change. If the map has a sky, you can choose an installed map's Sky and adjust Sky height. A map with no sky cannot take one this way.

The World tab names the atmosphere fields, including fog and sun settings. Record the old value and make one small change. Walk from shadow to sunlight and check that players and exits remain readable. A game's own exposure or fog option can take precedence over the map setting.

Decide whether to bake

A scenario light can light the running game dynamically. Baking is a separate operation: File → Re-bake Lighting uses your tags folder and reloads the map. On an installed map, it adds the effect of eligible changed lights to the existing lighting; it does not replace the original bake with an identical new one.

In the Lighting dialog, choose Draft Low for a first check, then Bake. Wait for the bake and map reload before comparing or saving. If the Kit says it is still learning the Editing Kit fields, wait and choose Re-bake Lighting again. Save the scenario after a successful bake so it keeps the bake settings for later compiles.

A light set for the game alone is not a bake contribution. Inspect Lit for before baking. For a quick iteration, keep the dynamic version until the placement is right.

Re-baking with changed lights uses your local tags and makes this a whole-map package. Compile for Reclaimer will explain why a recipe is unavailable. Save a separate scenario before baking so you can retain the simpler version.

Check after saving

  • In a playtest, approach the light from both sides. Look at its reach, the visibility of nearby players and any unexpected influence on other lights.
  • Compile, reopen the compiled map and inspect the light and decal again. This checks the saved result rather than only its live preview.
  • If you baked, compare the saved lighting and check the compile panel's package choice. A different sky does not automatically re-light an existing BSP.

If the light is invisible, check the light tag, reach, shape direction, Lit for, Cinematics only and the viewport's lighting mode. If a decal is missing, check its orientation and projection onto the surface before changing its tag.

Next step

Paint surface detail. Reference: lights, decals, re-baking, reflections and cubemaps.