Hidden-condition research is most trustworthy when it preserves failed experiments. IRON NEST has official city-outcome achievements, mission-specific gold awards, many in-game medals, unusual ammunition, and environmental interactions, but player curiosity is not evidence that every object hides a reward.
2950790, Windows/Steam public 1.0, checked 2026-08-09. This guide teaches verification and names official award anchors; it does not fabricate secret coordinates or triggers.Start with confirmed unknowns
Use the official 33-achievement list as a boundary: fourteen mission completion awards, fifteen gold awards, and four city outcomes. White Shells appears through Pride of Castile without a paired public completion award. That asymmetry is a documented clue, not proof of a hidden thirty-fourth achievement.
Read the live in-game medal panel for additional criteria. Mark text that is hidden, ambiguous, or only appears after completion. Do not conflate a Steam-global percentage with an internal secret.
Separate observation from theory
An observation is “the newspaper changed after this full sequence.” A theory is “firing this shell at this target caused the ending.” Record both in different fields. Include every unusual requisition, shot, friendly/protected target decision, optional interaction, and mission restart.
Community discussions about hospitals, side switching, cats, environmental objects, or unaided fire are leads. They become guide facts only after controlled reproduction or strong complete-run evidence.
Test without damaging a campaign
Complete the ordinary route first. Use supported new-campaign or replay behavior and allow Steam Cloud to synchronize normally. Do not delete or hex-edit an unknown save to manufacture a branch.
Change one candidate condition per run where feasible. When a whole-campaign outcome makes that expensive, coordinate independent players using the same patch and compare detailed logs. Negative evidence narrows the search.
Handle ammunition-based hypotheses
IRON NEST includes leaflet, smoke, illumination, chemical, fragmentation, and armor-piercing examples. A special shell can plausibly affect mission logic, but its narrative role must come from dispatch/results. Do not fire at protected or friendly areas solely because an unverified comment promises an achievement.
Record target, shell, charges, impact, operation response, medal panel, and newspaper. The Target Matching guide helps separate correct effect from speculative collateral behavior.
Treat environmental discoveries carefully
PATCH 1.0 (1558) includes fixes involving the cat and other Nest presentation states. An unusual visual or carry state on an older build may be a fixed bug rather than an intentional secret. Check current announcements before building a puzzle theory.
For any interaction, record location, mission state, prompt, result, and whether it persists after a clean restart. Avoid promising rewards from a decorative control until the game confirms one.
Spoiler-safe publication format
Lead with a non-spoiler description of what category is investigated. Hide or clearly label exact choices and final outcomes. State confidence: official, reproduced, single-run observation, or unresolved lead.
For a confirmed route, publish the minimum known sufficient sequence and note which steps have not been proven necessary. Link the official achievement anchor and a current full-run source when available.
Bug, coincidence, or secret?
Repeat from a known state. A result that survives restart and reoccurs with the same inputs may be intended. A state that appears only after a crash, fails to save, or disappears after PATCH 1.0 (1558) belongs in Support, not a secrets list.
Report reproducible anomalies through the official Community hub with spoilers marked. Never ask other players to download an executable or provide credentials to validate a theory.
Retire a disproved lead
When controlled current-build attempts contradict a rumor, keep a short dated note explaining the tested conditions rather than deleting all trace. This prevents repeated wasted campaigns. Reopen the lead only when a patch, official hint, or materially different run supplies new evidence. A secrets index is most useful when it narrows uncertainty instead of collecting every speculation indefinitely.
If a lead affects an ending, place the complete route behind the same strong-spoiler boundary used by the endings guide and identify the tested save state.