Final Harvest is anchored by Reap the Final Harvest and gold award Night’s Precision. As a late operation, it can carry campaign outcome context. This guide stays spoiler-safe: follow the current dispatch, preserve choices, and do not replace the finale with an unmarked coordinate list.
2950790, Windows public 1.0, checked 2026-08-09. Exact finale stages, targets, choices, endings, and medal thresholds require strongly labeled complete-run evidence.Preserve the campaign record before entering
Write the major choices and unusual target/effect decisions from earlier operations. Confirm Steam Cloud has synchronized normally and the public build is current. Do not experiment with unknown save files before a finale.
If researching endings, begin with a complete route log rather than only the last mission.
Keep the final dispatch ledger
Number every message, active target, required effect, restriction, and completed response. Late narrative language can be important; copy it before interpreting it. Mark whether a decision was explicit, implicit through firing, or merely suspected.
Use spoiler-free labels in shared notes until the reader opts into exact choices.
Build every shot from current evidence
Plot observers, references, friendlies/protected areas, and targets. Draw from the Nest after target confirmation. Calculate for actual shell/powder and record barrel/arming.
Do not use a finale walkthrough’s coordinate unless its AppID, patch, mission stage, and prior choices match. Even then, understand the evidence so a changed state can be diagnosed.
Allow the finale to respond
After each effect, wait for teleprinter, map, result, or newspaper. Do not fire a prepared second barrel across a narrative transition. A changed objective invalidates its card.
At completion, capture the newspaper, city outcome, medals, and Steam notifications. Dismiss normally and allow saving.
Distinguish completion, gold, and ending
Reap the Final Harvest confirms operation completion. Night’s Precision confirms all gold medals for this operation. The four city achievements are campaign outcomes. One notification does not substitute for the other two layers.
Use Endings for controlled route comparison and Gold Medals for isolated threshold testing.
Research Night’s Precision
Complete a baseline, photograph each medal hint, and change one factor per replay. Night setting or the word precision may suggest themes but are not exact rules. Test accuracy, assistance, resource use, timing, effect, and choices independently.
Record the entire final sequence and patch. Reproduce any combined gold route before calling all steps necessary.
Recover safely from finale trouble
For mission-entry failure after a crash, update to PATCH 1.0 (1558) or later public content and verify files. Preserve Cloud data. For a “wrong ending,” review the whole campaign log rather than repeatedly changing only the last shot.
A strong report includes prior choice summary, final dispatch stage, card, result/newspaper, achievements, patch, and crash state, with spoilers clearly marked.
Create a finale evidence packet
Before leaving the result, capture the final active dispatch, each fired card, impacts, newspaper, medal panel, city achievement, public patch, and a concise earlier-choice summary. Keep the files together and mark them as strong spoilers.
This packet supports three separate questions: did the operation complete, did all mission medals reach gold, and which campaign outcome occurred? If one layer disagrees, investigate it without rewriting the others. For example, a missing Steam notification can be a synchronization issue even when the in-game gold and newspaper are correct. A different city outcome can reflect the route even when Final Harvest itself completed perfectly. Separating the layers prevents destructive replay or save changes based on a platform-only symptom.
For a second ending run, define the one campaign choice sequence being changed before starting and keep ordinary firing competence stable. Record unexpected deviations, because a different miss, requisition, or protected-target event can contaminate the comparison. Two complete evidence packets can establish that routes differ; additional runs are needed to prove which individual action is necessary. Publish that distinction beside any spoiler route.