Liberation is documented by the official completion achievement Enforce the Liberation and gold award Exemplary Service. The safe approach is to let current orders define what liberation requires rather than projecting a preferred target or narrative outcome onto the map.
2950790, Windows public 1.0, checked 2026-08-09. Exact targets, branches, and medal thresholds remain spoiler-sensitive current-run evidence.Build an objective ledger
Number each teleprinter page and write its active verb, target, protected context, and required effect. A later order can supersede an earlier one. Mark completed stages, but do not discard them until the newspaper confirms the operation.
This ledger prevents firing at an obsolete target after a new dispatch arrives.
Mark protected context first
Before locating an enemy target, plot friendly observers, protected areas, and reference points. If intelligence creates two candidate intersections, use the next report or recon rather than choosing the one that seems narratively obvious.
Draw the final firing line from the Nest only after target selection. A spotter bearing is evidence, not gun bearing.
Match effect to the current order
Read shell and ability descriptions in the live console. Destructive, smoke, illumination, chemical, or leaflet roles are not interchangeable. Choose the effect requested and consider nearby friendlies.
Create a complete firing card and compare actual powder, elevation, barrel, and arming state. An accurate impact with no progression should trigger an effect/state review before an aiming correction.
Handle changing intelligence
When another dispatch arrives, label the old solution stale if target position, Nest origin, objective effect, or restrictions changed. Recalculate even if the new point looks close. Preserve both plots for after-action analysis.
If the operation seems stuck, search for unread paper, an unacknowledged effect, or the normal newspaper/sleep transition. Do not repeatedly fire at the last location without new evidence.
Keep narrative conclusions separate
Community searches about saving locations, friendlies, and switching sides show strong interest, but a single Liberation action may not determine a city ending. Record the full campaign choice sequence before claiming causation.
Use Endings only when ready for stronger spoilers. For a first run, follow the orders and accept the documented result.
Verify Exemplary Service
After ordinary completion, capture all medal names and hints. Test one suspected service criterion per replay: resource discipline, assistance, accuracy, timing, or objective choices. The Steam achievement confirms gold-on-all-medals, not the individual thresholds.
Allow the newspaper and save transition to finish. If the award fails after visible gold, separate in-game medal evidence from Steam synchronization.
Diagnose unexpected results
For a miss, classify direction, range, effect, or gun state. For a “wrong” newspaper, confirm the operation version, all dispatches, and complete campaign choices. For mission-entry failure after a crash, update to PATCH 1.0 (1558) or later public content and verify files.
Report exact stage, last order, shot card, result, and patch. Avoid resetting a whole profile based on one uncertain outcome.
Run a spoiler-safe comparison
If you want to compare Liberation choices, name alternatives neutrally—Route A and Route B—until the final result is recorded. Keep targeting mechanics identical where possible. This prevents a public help note from revealing an ending and prevents a different miss or requisition from being mistaken for a narrative branch.
After both runs, compare dispatch wording, protected/friendly state, newspaper, medals, and city achievement. A difference is evidence of correlation; repeat or find an independent complete run before declaring the tested action necessary. If there is no difference, keep that negative result because it rules out a popular assumption. Report a true progression bug separately from a disliked narrative outcome: one means the mission fails to advance despite satisfied state, while the other means it advanced to a result the operator did not expect.
Keep the successful baseline record after starting a branch test. It provides a known completion route and protects troubleshooting from guesswork when a later experiment changes several campaign states.