Challenge Missions are IRON NEST’s repeatable layer. The developer FAQ describes varied, procedurally generated situations, ammunition and ability unlocks, and Steam leaderboard competition. Campaign teaches authored operations; Challenge tests whether the operator can rebuild the firing chain under changing evidence.
2950790, Windows public 1.0, checked 2026-08-09. Exact scoring weights, unlock thresholds, and generation pools must come from the current mode display and repeatable runs.Enter with a reusable workflow
Use the same disciplined chain every run: dispatch, evidence plot, target position, Nest-to-target measurement, calculator, requisition, loading, bearing/elevation, arming, firing, impact review, newspaper. Variation changes inputs, not the need to verify them.
Prepare a compact card template before starting. Record run seed or visible identifier if the game supplies one, Challenge type, target, resources, abilities, shots, result, score, and public patch.
Adapt to generated evidence
Do not memorize Campaign coordinates. Plot the observers and references actually supplied. Generated conditions can make a familiar target type appear in different geometry or resource state.
Resolve uncertainty before loading. A fast wrong shot can cost more score and time than a deliberate triangulation. If the target moves or an ability repositions the Nest, discard the old range and bearing.
Learn unlocks from confirmed completion
The official materials say Challenge play unlocks ammunition and abilities, but do not publish a complete static progression table. After each correct run, capture the result and any new item exactly as displayed. Record mode variant and score so later observations can identify the true trigger.
Do not claim an unlock merely because it appeared in the console after several sessions. A separate Campaign completion or prior Challenge may have caused it.
Preserve a valid score
The FAQ says the highest single-run score is saved after the mission is correctly completed and the newspaper is dismissed. Finish every required objective and proceed through the newspaper. Quitting after the shot or force-closing during transition can leave the result unsaved.
A beautiful impact is not a score until the operation recognizes completion. If the leaderboard does not update, first confirm the local result, Steam connection, account-link state, and normal end sequence.
Improve one scoring variable
Build a clean baseline, then test accuracy, speed, expenditure, assistance, or another displayed factor one at a time. Exact scoring formulas should be reported from controlled comparisons, not inferred from rank alone.
When two runs have different generated conditions, raw scores may not isolate operator performance. Keep the challenge type and visible scenario data beside the score.
Use the two challenge styles correctly
Official Store wording refers to two Challenge Modes, while the FAQ discusses Challenge Missions broadly and a Chill cumulative-kill leaderboard. Use the live menu names. The Uncontested guide explains the lower-pressure/cumulative context without assuming it is a sandbox with unlimited resources.
Do not turn community shorthand into a third official core mode. Campaign and Challenge are the two core categories stated in the FAQ.
Recover from a missing result
Confirm the newspaper was dismissed, Steam was online, and the run completed correctly. PATCH 1.0 (1558) improved Discord account-linking code generation/issues; that code is service integration, not a redemption reward.
Preserve screenshots of local score, time, account-link state, and leaderboard. Restart Steam/game normally and verify files before altering any save. Report a reproducible mismatch with the exact public patch.
Compare generated runs fairly
Record every visible scenario modifier and starting resource. If two runs differ, use them to study workflow, not to claim an exact score delta from one operator choice. A scoring test is strongest when the same Challenge conditions recur or the game exposes a stable comparison. Keep leaderboard rank separate because other players can change it between observations.
When an identical scenario cannot be reproduced, compare process measures instead of claiming a scoring formula: verified cards, corrections, wrong effects, and completed transitions. These reveal operator improvement without pretending two generated battlefields are numerically equivalent.