A mission is an information problem first
The developer describes a consistent outer loop. High Command sends an objective through the teleprinter; the Operator transfers useful details to the notebook, measures on the tactical map, calculates and fires, receives a newspaper after completion, and goes to sleep to begin the next assignment.
Inside that structure, target positions and objectives can vary. Replaying a mission does not guarantee that an old map plot remains valid.
Read the exact objective
Destroying something is not always the whole requirement. The chosen shell, friendly protection, sequence, time, or medal condition may matter. Keep the current order visible and distinguish mission completion from an optional performance goal.
Use a compact working record:
- confirmed friendly and Nest positions;
- the current target or reference points;
- fresh range, bearing, charge, elevation, and shell;
- optional medal constraints still in progress.
Close the operation correctly
The FAQ says the post-mission newspaper summarizes the operation and world events, and that sleeping advances to the next mission. Challenge scoring is recorded only after the mission is completed correctly and the newspaper is dismissed, so do not quit during that transition if a result has not appeared.
Patch notes have corrected mission and medal issues after launch. If an objective seems stuck, check the current build before assuming the solution itself is wrong.
Version note
The mission loop and procedural-objective framing come from official sources reviewed for version 1.0 (1663) on September 2, 2026. No fixed target coordinates are published because runs can differ.