54 lines
3.2 KiB
Markdown
54 lines
3.2 KiB
Markdown
# Airfield extraction and map icons
|
|
|
|
The live Everon scenario no longer creates `everon-supply-2`, its guards, UAZ or
|
|
crate. The remaining supply cache and medical stash provide the two reachable
|
|
radio-intel sources. Mortar reserve/courier preparation uses the existing eastern
|
|
outpost, preserving its finite logistics without creating a replacement site.
|
|
|
|
As of 28 October 2026, extraction can use suitable clear ground anywhere on the
|
|
terrain. Original Everon randomizes its pickup with `RandomClear 1` and
|
|
`RequireAirfield 0`; its previous airport coordinate remains only a fallback
|
|
subject to the same landing-space and escape-boundary checks. Terrain-independent
|
|
placement also samples the entire terrain immediately, without an airport-first
|
|
pass or a dedicated airport-discovery wait.
|
|
|
|
Primary ground/overhead clearance and secondary transport space are checked
|
|
before accepting a candidate. Site creation rechecks the generated primary pad.
|
|
Aircraft damage and physics remain normal. Explicit authored airport-only pads
|
|
remain supported through `RequireAirfield 1`.
|
|
|
|
Exact discoveries use native wrapper images and matching glow images:
|
|
helicopter for extraction, radio for radio camps, artillery for mortar sites,
|
|
building for outposts, medical for medical supplies, and supplies for other caches.
|
|
The prison is now always hidden. Partial clues use a question mark. Icons are
|
|
applied after native marker initialization and reapplied when the map opens.
|
|
Partial markers use stable 500 m grid centres; all objective markers remain uneditable.
|
|
|
|
## Verification — 22 September 2026
|
|
|
|
The full repository check passed during implementation; the mortar-logistics
|
|
regression also passed after changing its preparation source. The final Core
|
|
Workbench `airfield-markers` fixture passed 12 assertions and completed without
|
|
script errors or VM exceptions. It checked the removed site, a settled usable
|
|
aircraft on the real pad, rejection of the old forest point and occupied pad,
|
|
two reachable intel sources, all six site icon selections, and native map opening.
|
|
|
|
Final local session: `/tmp/erri-airfield-markers6/logs/logs_2026-09-22_15-44-19`.
|
|
A direct capture of the private Workbench viewport visually confirmed the prison
|
|
lock replacing its circle. The other sites were outside that captured viewport;
|
|
the fixture checks their icon selections, not visual quality at every map zoom.
|
|
|
|
Existing RHS/WCS localization, stock resource-keyword and native map-UI resource
|
|
errors remain visible in the strict report. The runner recorded smoke completion
|
|
but returned failure because its immediate cleanup check encountered an exiting
|
|
`enfMain` process with an empty command line. A subsequent host-visible
|
|
`assert_prefix_idle` check confirmed the private prefix was idle. This is local
|
|
Workbench validation, not dedicated multiplayer acceptance or a clean strict
|
|
engine report. No server deployment or Workshop publication was performed.
|
|
|
|
Historical geometry-dependent smoke tests explicitly load `Tests/LegacySites.conf`;
|
|
production, `generated-sites`, `opening-tools` and `airfield-markers` use the live
|
|
scenario definitions.
|
|
|
|
The lock-icon screenshot below is historical; the subsequent [mortar and prison changes](mortar-intel-and-prison-map.md) removed that marker and restored question marks.
|