Allow off-airport extraction across terrains; record Workshop 0.0.124

docs/configuration.md

@@ -324,12 +324,16 @@ authoring fields, failure behavior and validation.
 
 The initial prison patrol contains 3–5 soldiers, chosen once during preparation from the selected enemy faction roster. An existing RTO is retained. If that roster has no large radio, one soldier is equipped with a physical manpack (US/USAF: AN/PRC-77; otherwise R-107M). Preparation waits for that radio to be present. The guards start at separate random clear positions 12–24 m around the prison and remain frozen until it is unlocked; other site squads keep their configured size.
 
-## Airfield extraction and site icons
+## Extraction landing zones and site icons
 
-Everon extraction uses the airfield pad at 4800.953 / 11487.412. Site authors set
-`RequireAirfield 1` and `AircraftOffset 0 0 0` on that extraction definition.
-Preparation checks airfield anchors, terrain and clearance before creating the
-aircraft, and refuses an invalid pad without relocating it elsewhere.
+Extraction searches for suitable clear ground across the terrain from the first
+attempt, on original Everon and on other terrains. It does not prioritize airports.
+Dry ground, slope, obstacle/overhead clearance, nearby rescue-fleet space and the
+prison's escape boundary still constrain placement. Terrain-generated scenarios
+also require reachable navigation at the landing zone and guard positions.
+Original Everon uses `RandomClear 1` and `RequireAirfield 0`; its old airport
+coordinate is only a validated fallback if the random search is exhausted.
+Scenario authors can still explicitly require an airfield for their own fixed pads.
 
 Identified sites use helicopter, radio, artillery, building, medical and supplies
 icons. Partial intel shows a question mark at an approximate position; the prison