# Named asset usage: pedestrians, gunners and backdrops

Investigated 20 November 2026 against the extracted European retail executable, SLES-03425. Evidence is static code/data tracing; no live game settings or disc images were changed for this investigation.

## Main finding: the skeleton is a retail Halloween-theme pedestrian

The retail **MERGED/DAY_MON.MRG** bank contains an embedded MISC.DOB with the skeleton-textured **GFX_PEDO2**. This is not just a skeleton found in a historical folder: a corresponding version exists in the selectable retail monster-theme bank.

The engine loads **GFX_PEDO** and **GFX_PEDO2** as two pedestrian mesh choices, and uses **PEDO_WALK** / **PEDO_RUN** animation resources. Its pedestrian draw path switches the active mesh between those two slots according to the pedestrian instance. The evidence supports two pedestrian variants, without assigning a gender solely from the model names.

The executable's bank selector reads active bonus flags and constructs **merged/{time}{theme}.mrg**:

| Active flag | Bank suffix | Menu label | Reward dispatch index |
| --- | --- | --- | --- |
| 0x2000 | _flw | FLOWER POWER THEME | 3 |
| 0x4000 | _mon | HALLOWEEN THEME | 5 |
| 0x8000 | _wat | AQUA THEME | 16 |

These labels come from MENU/XENGLISH.MTS, entries 67–69. The executable explicitly names that menu text resource. The release allowance table includes the three theme flags.

**When / where:** Halloween changes the pedestrian assets supplied to the normal city pedestrian system; it is a theme, rather than a skeleton tied to one secret coordinate. The code's reward chain selects index (current zero-based mission + 1). Index 5 enables the Halloween unlock bit. SCRIPT/05.SCB's aMissionSuccess event sets the reward flag through native 33 and contains the messages “You got a commendation” and “No commendation, you broke the suspect”. This statically links the Halloween unlock to a **mission 5 commendation**. Select the unlocked Halloween Theme through the bonus-items interface before loading a session so the _MON bank is chosen. That menu flow has not been replayed during this investigation.

The older MONSTER_OLD/MONSTERS_OLD versions in the catalogue are **legacy variants of a retail bonus-theme role**. Their surviving texture/UV differences do not establish that the whole skeleton design was unused. Flower and Aqua banks provide their own versions of the same pedestrian slots.

## GFX_SHOOTER: the player/car-mounted gunner role

The shared gunner constructor selects GFX_SHOOTER for selector 0, attaches it to an entity positioned using vehicle-defined mount coordinates, and uses the player **PISTOL_LEANOUT / PISTOL_SHOOT / PISTOL_RELOAD** animation family. Native script call 82 reaches this constructor. Mission setup and Free Patrol code call that interface; SCRIPT/VASM/01.SCS includes a player-vehicle setup call with selector 0.

**When / where:** the vehicle's weapon/gunner system, including the visible occupant leaning out to fire. Its static mesh is not a separate strange vehicle or a city prop. A catalogue render shows an unanimated local mesh; it does not reproduce its seated/lean-out pose or attachment to the car.

The unusual legacy versions remain candidates for older artwork or mesh revisions. The **role/name itself is definitely referenced by retail code**.

## GFX_PERP: the AI vehicle suspect/gunner role

Selector 1 in the same gunner initializer selects GFX_PERP. Its placement uses vehicle-configured occupant/window coordinates, and it follows the **AI_PISTOL_LEANOUT / AI_PISTOL_SHOOT** animation family. The generic AI-actor setup calls the shared gunner constructor with selector 1 when the actor has the relevant weapon/shooter configuration.

**When / where:** configured suspect/AI vehicles that have an armed occupant. It is part of the vehicle actor system, rather than the ordinary walking pedestrian pool. The catalogue's unanimated rendering can therefore look disjointed or unlike its in-game presentation.

## GFS_BACKDROP: the sky / distant-horizon mesh

The retail environment loader constructs **BACKDROP/{time}{weather}.DOB**, with time tokens 06, 09, 12, 15, 18, 21, 00 and weather tokens CLEAR, CLOUDY, RAINY, FLASH. It loads that bank, looks up **GFS_BACKDROP**, and attaches the resulting geometry to the environment scene. This loader is exposed through native script call 206.

Retail files including BACKDROP/12CLEAR.DOB and BACKDROP/06CLOUDY.DOB contain the same named role. The two catalogue occurrences—BACKDROP/00CLEAR.OLD and BACKDROP/06CLOUDY.OLD—are older versions of this background role. They are not evidence of an unused playable map.

**When / where:** the surrounding sky and distant skyline for the chosen time/weather combination. An outside orthographic model view looks odd because the geometry was built as background scenery viewed from the game scene, not as a standalone object to walk around.

## Reproducible evidence

- Trace-Named-Asset-Usage.py verifies the named strings, theme bits, menu labels, reward index mapping, and indexes script gunner/backdrop calls.
- named-asset-usage-evidence.json records executable hash, code addresses, bank paths and script call offsets.
- retail-halloween-GFX_PEDO2.jpg is the offline four-angle preview decoded from the retail DAY_MON bank, not from the historical HUD folder.

Important code locations:

| Evidence | Executable addresses |
| --- | --- |
| Pedestrian mesh initialisation | 0x800B6044–0x800B60A0 |
| Per-instance mesh switch | 0x800B6E64–0x800B6E84 |
| GFX_SHOOTER selection | 0x8006C790–0x8006C7DC |
| GFX_PERP selection | 0x8006C7E0–0x8006C84C |
| AI gunner construction | 0x80041D14–0x80041D2C |
| Environment bank and backdrop lookup | 0x8008C190–0x8008C230 |
| Theme bank selection | 0x800AD640–0x800AD6F0 |
| Commendation reward dispatch | 0x800AA5BC–0x800AA5E8 |
| Mission 5 reward → Halloween bit | table 0x800134A8, case 0x800A93FC |

The catalogue annotations now distinguish a legacy source variant from the known retail role. Actual runtime use of each historical source file remains unproven unless separately traced.
