# Finite ground transport

The western supply site's optional `Transport` definition owns one vanilla UAZ. It is created once by `ERR_SiteService.Begin`, tracked alongside the site's crates and scenery, and transferred to the existing mission owner when preparation succeeds. Destruction, fuel depletion, repeated `Prepare`, and later service ticks do not spawn a replacement or refill it. Terminal stop prevents reinitialization; preparation failure rolls the vehicle back with the other authored contents.

The vehicle is optional ground transport for the route, not a guarantee that all twelve prisoners can travel simultaneously. Losing it does not defeat the mission or remove the walking route. It is not registered as an HQ response asset.

## Authoring

Only depot and outpost sites accept a `Transport ERR_SiteTransport` block. One vehicle is permitted per site and at most four per scenario. `Prefab`, ground-relative `Offset`, `Heading`, `ClearanceRadius`, and `MaximumTerrainRange` are authored in `EveronSites.conf`. Offset magnitude is capped at 60 m and vertical offsets are forbidden. Parking clearance radius must be 2–8 m and the allowed terrain elevation range 0–1.5 m.

Before spawning, the service samples a 3×3 terrain grid across the parking square, rejects water, steep ground and objects with native geometry, and logs the result. It never removes terrain scenery or searches for another spawn point. Preparation additionally requires a live wheeled vehicle, fuel, native driver and passenger positions, and a vehicle bounding box fitting inside the surveyed footprint with a 0.5 m margin. The persistent handbrake is set at creation.

The initial 5960/7232 candidate was rejected by native geometry checks. A bounded [parking survey](evidence/native-2026-09-19-043631-parking-survey/report.json) found 43 clear candidates. The selected parking position is **5960/7212**, offset 0/0/-8 from the western cache, heading 180°, final clearance radius 4 m and maximum terrain range 1 m. The initial six-metre-square survey sampled a 0.625 m range; the final native run rechecks the larger eight-metre square. The readiness check compares actual vehicle bounds to this surveyed center, rather than a possibly displaced current origin. Manual route navigation remains unverified.

## Asset audit

The vehicle reference is `{259EE7B78C51B624}Prefabs/Vehicles/Wheeled/UAZ469/UAZ469.et`, independently checked against the installed vanilla `resourceDatabase.rdb`. This is already in `docs/vanilla-resources.json`. Its vanilla base config defines two 39 L tanks initially containing 29.25 L each, hence 58.5 L total initial fuel. The successor does not set or regenerate that fuel. The [044205 native run](evidence/native-2026-09-19-044205/report.json) observes 58.5 L initially, 78 L total capacity and five usable driver/passenger seats. No original Escapists code, composition or asset is used.

## Native fixture

`ERR_NativeTransportProbe` is WORKBENCH-only and opt-in. Its `Tick(now)` helper uses the actual authored UAZ and two isolated scripted prisoner characters. It checks ownership, native pilot/passenger compartments, physical occupancy and ordinary native engine startup. It then deliberately drains fuel, waits, queries preparation, deletes the vehicle and queries preparation again, verifies initialization cannot repeat, and stops the site service. This destructive fixture therefore belongs in its own smoke branch followed by a round reset.

The linked native run passes all 23 checks with no script/VM exceptions; seven inherited vehicle schema errors remain. The fixture is not manual driving, normal boarding-action validation, road navigation, fuel-range balancing, remote-client replication, or multiplayer proof. Neither it nor repository validation should be reported as those checks.