jakub
6a667d8deb
Include the current addon, terrain integrations, tools, regression tests and recorded development evidence.
38 lines
2.2 KiB
Markdown
38 lines
2.2 KiB
Markdown
# Cessna dedicated-server check — 8 October 2026
|
|
|
|
Reforger 1.8.0.13, Cessna 172 1.0.0, Propeller Flight Core 1.0.18. Private Everon
|
|
server, loopback-only network namespace, separate profile and frozen source;
|
|
no Steam player profile, live server or published addon was changed.
|
|
|
|
The retained fixture advances HQ on the otherwise empty server, transitions to
|
|
the normal escaped phase and places three active opposing AI actors near the
|
|
runway. It does not manufacture sightings, reports, radio delivery or aircraft
|
|
motion. The patrol uses its production airport survey, native crew boarding,
|
|
engine start and PFC flight controls. After 120 seconds airborne, the fixture
|
|
destroys the aircraft through its damage manager, waits for the replacement to
|
|
take off, then changes its faction to check release and restoration of controls.
|
|
|
|
Results in `native-summary.log`:
|
|
|
|
- Native crew sighting reached HQ with the plane group as its source.
|
|
- Original plane took off from the airport and remained alive through the patrol.
|
|
- Replacement took off 108.1 seconds after destruction, including the minimum
|
|
60-second delay, additional clearance search and engine/ground takeoff time.
|
|
- Faction takeover retained the living aircraft and restored its original rates.
|
|
- Separate native compile without either plane addon passed.
|
|
- Menu structure/routing, setting validation, settings import/migration and HQ
|
|
registration checks passed; the development source bundle audit passed without
|
|
adding aircraft addon dependencies.
|
|
|
|
`result.json` contains source hashes and explicit test limitations. The native
|
|
snapshot matches the production sources listed there; its runway survey has one
|
|
additional diagnostic Print on rejected clearance, and the fixture is injected
|
|
as a separate script. `isolated-runner.py` records the local fixture setup; its
|
|
runtime, downloaded addon and RDB paths are machine-specific prerequisites.
|
|
|
|
This is **not** a clean full-mission or multiplayer playtest: two optional-site
|
|
initial guard preparations failed during the busy escaped-phase fixture. They
|
|
are retained in the summary rather than hidden. No connected human client was
|
|
used, so first-person visuals/audio and an actual player boarding takeover still
|
|
need normal gameplay validation.
|