NPC Tips Hints for when you're stuck

IRON NEST sources and versions

This page lists the sources behind the IRON NEST guides and data pages on NPC Tips and the game versions they describe. Each of those pages links to its own section below.

Versions and patches

Official IRON NEST patches since the 1.0 release. Guides name the build they describe in the line under their title; this list explains each build number.

  1. Patch #1 · Version 1.0 (1547) · · Patch notes

  2. Patch #2 · Version 1.0 (1558) · · Patch notes

  3. Patch #3 · Version 1.0 (1577) · · Patch notes

  4. Patch #4 · Version 1.0 (1618) · · Steam announcements

  5. Patch #5 · Version 1.0 (1622) · Steam build 24750322 · · Steam announcements

    Current baseline. Game-data statements on this site were read from this build, extracted August 17, 2026.

  6. Patch #6 · Version 1.0 (1663) · · Patch notes

    Released after the baseline. A guide has been checked against it only where the guide says so.

  7. Patch #7 · Version 1.0 (1683) · · Patch notes

    Released after the baseline. A guide has been checked against it only where the guide says so.

Official sources

The developer's own channels. Guides also cite the official IRON NEST Discord; Discord messages are named by channel and date and are not linked, because they can only be read after joining the server.

How we read the game files

Values read from the game files come from Steam build 24750322 (Version 1.0 (1622), Patch #5), extracted on August 17, 2026 from a local installation. They describe that build only, and no author gameplay testing is claimed unless a guide says so.

How each evidence label is used, how conflicting sources are handled and how to report a mistake are explained in the Editorial Policy.

Sources by page

Each page below lists every source it cites, what that source supports on the page, and its limits. A few third-party guide sites are described rather than named and are not linked.

Pages not listed here list their sources on the page itself.

Achievements

  • IRON NEST global achievements on Steam · Checked

    Supports: The full public list of achievements: the count, names, descriptions and the changing global percentages.

    Limits: Shows no stable per-achievement hidden flag, and the global percentages change over time.

  • Patch #6 announcement on the IRON NEST Steam Community hub · Published · Checked

    Supports: The official record that Steam gold-medal achievements not unlocking was fixed.

    Limits: Does not say whether every older account is backfilled automatically.

  • Steam store data for IRON NEST (appdetails) · Checked

    Supports: A second official count of 33 achievements.

    Limits: Highlights only 10 achievements and gives no complete list or stable hidden flag.

  • NPC Tips: IRON NEST medals reference (game files, build 24750322) · Checked

    Supports: The Campaign and medal structure used to send each achievement to the guide that owns it.

    Limits: Game files identify missions and medals, not Steam achievement details.

  • NPC Tips: IRON NEST endings guide · Checked

    Supports: The guide that owns the four ending routes.

    Limits: Used to hand off the ending achievements; the Steam list remains the source for achievement names and descriptions.

  • Official IRON NEST Discord · #bug-reports thread · Posted · Checked

    Supports: A developer's explanation of how gold medals were meant to add up across runs, with dated replay troubleshooting.

    Limits: The current fix status comes from Patch #6; replaying is not a permanent or guaranteed fix.

Bearing from Spotter

  • IRON NEST game files, Steam build 24750322 · Checked

    Supports: Requisition card definitions, English text, the Spotter wording in missions, direct graph references and random report branches.

    Limits: Describes build 24750322 only; it does not give random odds, Forward Observer error functions, full target selection or how the Scout Plane looks and works on screen.

  • Developer reply on the Steam Community forum: Counter-Battery discussion · Published · Checked

    Supports: Historical context on the Scout Plane, Star Shells and Counter-Battery.

    Limits: Describes an earlier design stage, not a current-build rule.

  • Official IRON NEST Discord · #ironnest-gameplay (developer) · Posted · Checked

    Supports: A developer's check of the reference point in one player's Forward Observer case.

    Limits: One player case; it does not establish odds or a general diagnosis.

  • Official IRON NEST Discord · #ironnest-gameplay · Checked

    Supports: Typical player questions about report origins, accuracy, Scout Plane variants and Forward Observer behaviour.

    Limits: Questions show what confuses players, not the answers or the mechanics.

  • Third-party guide: how to triangulate · Published · Checked

    Supports: The report-origin and bearing-and-distance workflow, used as a research lead.

    Limits: Third-party guide with examples from one run; build facts come from the game files.

  • Pro Game Guides: Complete IRON NEST beginner's guide · Published · Checked

    Supports: An independent workflow for map lines, intersections and handing the firing line to the gun.

    Limits: Published before Version 1.0; it cannot establish current-build mechanics.

  • Diegplaysgames on YouTube: Fire on Call run · Uploaded · Checked

    Supports: A timestamped run showing the report-to-map-to-turret workflow.

    Limits: Reviewed from an automatic transcript of one run; it does not establish universal mechanics or reusable values.

Blind Fire

  • IRON NEST game files, Steam build 24750322 · Checked

    Supports: Campaign order, English mission text, the mission flow, enemy entities, shell definitions and which medals belong to the mission.

    Limits: Describes build 24750322 only; values and partly decoded event conditions do not give a reusable firing solution, the friendly-fire trigger, a fixed time limit or the mission's medals.

  • Third-party walkthrough: Blind Fire · Published · Checked

    Supports: Reported Alpha, Bravo and AA workflow, and how to manage the map board.

    Limits: Third-party guide; its tactics and values do not prove current mechanics on their own.

  • Third-party mission database: Blind Fire · Checked

    Supports: Reported walkthrough and which medals belong to the mission.

    Limits: Third-party database with no publication date shown; its parameters and medal assignments are not treated as current facts.

  • Treble110 on YouTube: Blind Fire · Uploaded · Checked

    Supports: One player's workflow for the mission and troubleshooting context.

    Limits: Reviewed from an automatic transcript, not a controlled or frame-by-frame review.

  • TEC on YouTube: mixed-mission run · Uploaded · Checked

    Supports: Reviewed and set aside: the transcript mixes other missions.

    Limits: Supplies no Blind Fire mechanic.

  • Official IRON NEST Discord · archived player questions · Checked

    Supports: Player questions about AA locations, the friendly-fire message, requisition, missing imagery and timing.

    Limits: Shows only that a player asked or reported something, not the underlying mechanic.

Calculate Elevation

  • IRON NEST game files, Steam build 24750322 · Checked

    Supports: Charge tables for 21 shells and the six maximum-distance endpoints in the current build.

    Limits: The fields alone do not prove the calculator's full method, its rounding, low-angle behaviour on screen, or which charge is best.

  • IRON NEST game files, Steam build 24750322: calculator error links, display and printer fields · Checked

    Supports: The artillery computer's endpoints, the error connection, display and printer fields, and The Gorge broken-computer graph.

    Limits: The decoded configuration does not replace checking in play and does not show the full method or midpoint rounding.

  • Official IRON NEST Discord · #faq · Posted · Checked

    Supports: The official workflow: tactical map, ballistic computer, gun elevation and matching charges.

    Limits: Does not publish the calculator formula, its rounding or every error condition.

  • Official IRON NEST Discord · #faq · Posted · Checked

    Supports: The historical official direction for the 60-degree elevation ceiling.

    Limits: A dated statement, not a full description of the current calculator method.

  • Luna Tycho on YouTube · Uploaded · Checked

    Supports: A timestamped run showing a calculation without the computer and manual firing.

    Limits: Reviewed from an automatic transcript of one run; it cannot establish universal behaviour or fixed shot values.

  • Destructoid: How to shoot without the elevation calculating computer (Arka Sarkar) · Published · Checked

    Supports: A cross-check of the community formula, its units and the workflow without the computer.

    Limits: Third-party article; it does not make the interpolation an official formula or prove the fields are independent.

Calculator

  • IRON NEST game files, Steam build 24750322 · Checked

    Supports: Calculator labels, the six powder-charge range bands, shell definitions and The Gorge mission event.

    Limits: The files do not show the calculator's full method, how its fields depend on each other, its rounding, or every error message.

  • IRON NEST game files, Steam build 24750322: artillery computer component · Checked

    Supports: The artillery computer's endpoint settings, range tolerance, minimum range and links to shell data.

    Limits: The settings can be reproduced; the interpolation, rounding, full method and every error branch were not fully reconstructed.

  • IRON NEST game files, Steam build 24750322: shell flight-time fields · Checked

    Supports: Shell base speed, the speed curve by charge, the stopwatch fallback of range divided by speed, and the in-flight countdown fields.

    Limits: Predicts time in the air for this build only; it does not prove real-world ballistics, trigger delay or exact impact time.

  • Official IRON NEST Discord · #ironnest-gameplay · Posted · Checked

    Supports: A player's pocket-watch timings for charges 1 to 6 at 60 degrees, with a fitted curve.

    Limits: Player timing, not an official specification; it does not measure preparation or trigger delay.

  • r/IronNest on Reddit: “Tips for newbies” · Checked

    Supports: A player explanation that flight time scales with range, with timing checks per charge.

    Limits: Approximate player observations; they do not establish exact impact timing.

  • Official IRON NEST Discord · #faq · Posted · Checked

    Supports: The official measure, calculate, load and fire workflow: tactical-map measurement, the calculator, matching powder charges and turret setup.

    Limits: Does not publish the formula, rounding or what each calculator field means.

  • Official IRON NEST Discord · #faq · Posted · Checked

    Supports: The developer's reason for keeping the 60° maximum-range direction.

    Limits: A pre-1.0 statement; it does not publish the formula and does not on its own describe the current build.

  • Third-party IRON NEST guide · Published · Checked

    Supports: The general map-to-calculator-to-loading workflow and worked examples.

    Limits: Third-party guide; not a calculator specification and not proof of current-build behaviour.

  • Destructoid: How to shoot without the elevation calculating computer (Arka Sarkar) · Published · Checked

    Supports: A manual distance-in-metres formula and a workflow without the calculator.

    Limits: Third-party article; it does not establish that the calculator's fields are independent or how it behaves in play.

  • Game Launch Central on YouTube · Uploaded · Checked

    Supports: One run showing a firing solution, matching elevation and charges, and loading checks.

    Limits: Reviewed from an automatic transcript; one run does not prove the formula or a failure rule.

  • Luna Tycho on YouTube · Uploaded · Checked

    Supports: A manual solution without the calculator, using distance, maximum distance and the 60° endpoint.

    Limits: Reviewed from an automatic transcript of one run; it does not establish the current formula or how to recover a mission.

  • Diegplaysgames on YouTube: calculator explanation · Uploaded · Checked

    Supports: The distance × 12 ÷ charges explanation, plus flight-time and dual-barrel observations.

    Limits: Reviewed from an automatic transcript; its fixed values are one-run examples.

  • Official IRON NEST Discord · #ironnest-gameplay · Checked

    Supports: Player questions and reports about the manual formula, repairs, how the fields depend on each other, and the Not Enough Charges message.

    Limits: Player statements, not official confirmation; some questions have no reliable answer.

  • r/IronNest on Reddit: “A firing table for Iron Nest” (AnCE_o7) · Checked

    Supports: Players using translated firing tables and spreadsheets instead of the calculator.

    Limits: The table image was not transcribed cell by cell and is not an official formula or table.

  • r/IronNest on Reddit: “Ranging chart” (sofar55) · Checked

    Supports: A player ranging chart and the equivalent formula Angle = Range × (12 ÷ Bags).

    Limits: The chart image was not transcribed; its lower cutoff is player-made, not an official minimum or rounding rule.

  • byrod/iron-nest-calculator on GitHub · Published · Checked

    Supports: A fan calculator's linear interpolation and input model, at a fixed commit.

    Limits: Shows only that implementation; its lower limit, two-decimal display and interface are not official specifications.

Calibration Fire

  • IRON NEST game files, Steam build 24750322 · Checked

    Supports: Campaign order, the mission graph and flow, entity roles, event filters, shell grants and English mission text.

    Limits: Describes build 24750322 only; it does not give a universal firing solution, the full interface, a fixed order of miss messages, the Hospital outcome, or which medals belong to the mission.

  • IRON NEST global achievements on Steam · Checked

    Supports: The public name of the Calibration Fire task and which achievements exist.

    Limits: Does not show Campaign numbering, the task flow or which in-game medals belong to the mission.

  • Developer FAQ on the Steam Community forum · Published · Checked

    Supports: The shared measure, calculate and fire workflow used from mission to mission.

    Limits: Does not describe Calibration Fire's own steps or completion check.

  • CallMeLou on YouTube: full game, no commentary · Uploaded · Checked

    Supports: One continuous run of the Calibration Fire task and its transition to the next mission.

    Limits: One recording does not confirm the current build, a standard duration, fixed coordinates or firing values, the starting inventory, or a single route.

  • Official IRON NEST Discord · archived player questions · Checked

    Supports: How players describe shots that fly the opposite way, leave the map or land short, and questions about the Hospital, the target and shell names.

    Limits: Questions show what players ran into, not the correct answer, current mechanics, confirmed bugs or how often it happens.

  • Third-party IRON NEST guide · Published · Checked

    Supports: Campaign coverage and the shared firing loop, used to check where this guide stops and other guides begin.

    Limits: Third-party guide; it cannot establish task-specific mechanics or reusable firing values on its own.

  • Third-party mission database: Calibration Fire · Published · Checked

    Supports: Reported task, inventory, reward, medal, briefing and message details, checked for conflicts.

    Limits: Third-party database; its resource, inventory, medal, subtitle and story details are not used without stronger evidence.

Community Resources

  • Google search results for IRON NEST community destinations (US, English) · Checked

    Supports: Search results used to find community destinations, overlaps and same-name conflicts, including the check for a standalone soundtrack release.

    Limits: Search results do not establish who controls a destination, authorisation, live community state or game facts.

  • IRON NEST game files, Steam build 24750322 · Checked

    Supports: The game identity, and a check for any authoritative external-community fields in the files.

    Limits: The game files do not name current Discord, Patreon, Reddit or soundtrack destinations.

  • Official IRON NEST Discord invite link · Checked

    Supports: The direct invite link, checked on the review date.

    Limits: The link alone does not prove developer control, that it stays valid, or current membership, channels, moderation or response times.

  • Developer post on the Steam Community forum: official Discord server · Published · Checked

    Supports: The developer's confirmation that the Discord is the official community server.

    Limits: The post does not guarantee an invite stays valid or describe the live server.

  • IRON NEST on Linktree · Checked

    Supports: A cross-check of the Discord, Patreon, Steam and other developer-controlled destinations.

    Limits: Some labels can go stale; being listed does not make every destination developer-owned.

  • IRONNESTgame on Patreon · Checked

    Supports: The creator-controlled Patreon page and its optional support entrance.

    Limits: Tiers, prices, benefits, member counts and terms change and are not recorded by this guide.

  • Official IRON NEST Discord · #faq · Posted · Checked

    Supports: The dated line between symbolic support, playtest access and development information.

    Limits: A historical policy; it does not guarantee later campaign terms, rewards or benefits.

  • r/IronNest on Reddit · Checked

    Supports: That the subreddit exists, where community discussion happens, and its moderation context.

    Limits: Does not by itself prove developer ownership, official moderation, activity or gameplay facts.

  • Official IRON NEST Discord · #dev-chat (developers) · Posted · Checked

    Supports: The developers acknowledging r/IronNest and working with its creator.

    Limits: Acknowledgement and collaboration do not prove the developers own or moderate it.

  • Developer reply on the Steam Community forum: music · Published · Checked

    Supports: Who worked on the music together, and the soundtrack's status.

    Limits: The reply does not name a standalone release, a full track list, a licence, a purchase option or a single composer.

  • Simon Blüthner on itch.io: Iron Nest OST (a different game) · Checked

    Supports: Shows that a prominent same-name soundtrack page belongs to a different game.

    Limits: Not a destination for this game, an authorisation source or a complete soundtrack.

Dead Reckoning

  • Third-party walkthrough: Dead Reckoning · Published · Checked

    Supports: Walkthrough and troubleshooting context.

    Limits: Third-party guide; it does not prove current mechanics on its own.

  • Third-party mission database: Dead Reckoning · Checked

    Supports: Mission text and number examples.

    Limits: Third-party database; its number examples are used only within what the page states.

  • DieselDesigns Gaming on YouTube: Dead Reckoning · Uploaded · Checked

    Supports: One player's run of the mission.

    Limits: Reviewed from automatic captions; it needs cross-checking.

  • Treble110 on YouTube: Dead Reckoning · Uploaded · Checked

    Supports: Another player's run of Dead Reckoning.

    Limits: Reviewed from automatic captions; it needs cross-checking.

  • Official IRON NEST Discord · archived player questions · Checked

    Supports: Troubleshooting questions from players.

    Limits: Shows what players reported; it does not prove mechanics.

  • Official IRON NEST Discord · #bug-reports · Posted · Checked

    Supports: A player report used for No Quarter troubleshooting.

    Limits: Player report; the mission's No Quarter threshold is still unresolved.

Download

  • IRON NEST: Heavy Turret Simulator on Steam · Published · Checked

    Supports: The full game's product identity, Steam App ID, release date, purchase page, and where to find price and requirements.

    Limits: A changing store page; regional prices, discounts and configuration need a dated check.

  • Steam store data for IRON NEST (appdetails, US English) · Checked

    Supports: Paid status, Windows support, the release date, a dated US price and the full game's requirements.

    Limits: One US response on one date; it does not guarantee later or worldwide values.

  • IRON NEST: Heavy Turret Simulator on GOG · Published · Checked

    Supports: The dated GOG product page for the full game.

    Limits: Does not establish the current price, configuration, DRM details or whether patches arrive at the same time.

  • IRON NEST: Heavy Turret Simulator on the Epic Games Store · Published · Checked

    Supports: The dated Epic Games Store product page for the full game.

    Limits: Does not establish the current price, configuration, features or whether patches arrive at the same time.

  • SteamDB: IRON NEST (App 2950790) · Checked

    Supports: App, depot, branch, build ID, update-time and price-history metadata.

    Limits: Not a Valve or developer source, a purchase page, an authorisation record or a source for current prices or cross-store parity.

  • Official IRON NEST Discord · #faq · Posted · Checked

    Supports: The release date, launch stores, historical US launch pricing and minimum requirements.

    Limits: A pre-release FAQ; its launch discount is historical and current store details need a dated check.

  • NPC Tips: IRON NEST roadmap · Checked

    Supports: Where the completed release status ends and future platform plans begin.

    Limits: This site's own page; it does not add claims to this guide.

  • NPC Tips: IRON NEST Demo guide · Checked

    Supports: The Demo App identity and the source chain for how the Demo differs.

    Limits: This site's own page; the Demo guide owns the details.

  • IRON NEST game files, Steam build 24750322 · Checked

    Supports: The product fingerprints of the full game (App 2950790, build 24750322) and the Demo (App 4300500, build 23991575).

    Limits: Does not prove store authorisation, price, playtest status, cross-store parity or gameplay differences.

  • Official IRON NEST Discord · server-wide search · Checked

    Supports: Historical context on playtest keys from the NEST FEST playtest (February 23 to March 2, 2026).

    Limits: Does not establish current key availability, current playtest status or reseller authorisation.

  • Google search results for “iron nest official access” (US, English) · Published · Checked

    Supports: How search results mix official stores, the Demo, the playtest and third-party download listings.

    Limits: Shows search intent only; results do not prove authorisation, file safety or game facts.

Endings

  • IRON NEST global achievements on Steam · Checked

    Supports: The four named city-outcome achievements, their official names, and the Pride of Castile achievement.

    Limits: Names only: the page does not say what triggers each outcome, gives no Ending 1–4 order, and shows no build.

  • Official IRON NEST announcements on Steam · Checked

    Supports: The official patch baseline at research: Version 1.0 (1618), Patch #4.

    Limits: Reviewed through Patch #4; no patch note confirmed the Pride of Castile unlock reports.

  • Official IRON NEST Discord · #faq · Checked

    Supports: That Chill mode is a separate mode, not part of the Campaign endings.

    Limits: Does not show the current Chill exit, newspaper or settlement flow.

  • Official IRON NEST Discord · #ironnest-gameplay (developer) · Checked

    Supports: A developer message that Chill mode has no ending.

    Limits: Posted during the pre-release playtest and Demo period; not a Version 1.0 procedure.

  • Third-party endings guide: White Shells · Published · Checked

    Supports: Restarting the finale for another outcome, the betrayal route through High Command and the retaliating artillery, and preparing resources before betrayal.

    Limits: Third-party guide; the build is not stated, and some Celebration, Subdued and betrayal details conflict with other sources.

  • Third-party guide: all four endings · Checked

    Supports: Restarting the finale for another outcome, and the betrayal route through High Command and the retaliating artillery.

    Limits: Third-party guide; the build is not stated.

  • Levas on YouTube: White Shells ending · Uploaded · Checked

    Supports: PRPG leading to A City in Celebration, CYAN to A City Subdued, ATMC to A City Silent, and the TRAITOR state to The Road Not Taken; eight of the nine screenshots on this guide.

    Limits: Release-version footage with no build shown; these routes were not reproduced on Patch #4 by this site.

  • TimHawk on YouTube: White Shells ending · Checked

    Supports: WP leading to A City Subdued, ATMC to A City Silent, the Celebration result and the TRAITOR outcome; one screenshot on this guide. Its Ending 2 and Ending 3 numbering is the conflict this guide explains.

    Limits: Release-version footage with no build shown; the Celebration run does not show a readable PRPG load.

  • Official IRON NEST Discord · #ironnest-gameplay · Checked

    Supports: Player reports that scout planes missed three or four guns after betrayal and Star Shells revealed them (August 13, 2026), and that Pride of Castile did not unlock after all four outcomes (August 9–13, 2026).

    Limits: Player reports with no build shown; they do not establish a fixed target count or a confirmed bug.

  • CallMeLou on YouTube: full game, no commentary · Uploaded · Checked

    Supports: White Shells as the final named operation of the Campaign.

    Limits: One observed run, not a developer-published mission number; no build shown.

Field Data

  • IRON NEST game files, Steam build 24750322 · Checked

    Supports: Every value in the three reference tables, and the repeated identifiers and outdated internal names this page warns about.

    Limits: Describes build 24750322 only. What a field's unit means and how a value behaves during play are not established.

  • IRON NEST Demo game files, build 23991575 · Checked

    Supports: The demo's data, kept separate from the 1.0 tables.

    Limits: Describes demo build 23991575 only.

Final Harvest

  • IRON NEST game files, Steam build 24750322 · Checked

    Supports: Campaign order, the mission graph, English mission text, enemy entities, counter-battery fire, the fire-direction centres, the train, support calls and completion conditions.

    Limits: Describes build 24750322 only; it does not make firing inputs reusable or settle resource, medal or unlock values.

  • Third-party walkthrough: Final Harvest · Published · Checked

    Supports: Reported train, counter-battery and support workflow.

    Limits: Third-party guide; one route and its values do not prove a universal solution.

  • Third-party mission database: Final Harvest · Published · Checked

    Supports: Reported mission, resource, ammunition, medal and unlock details.

    Limits: Third-party guide; its resource, medal, unlock and best-shell claims are not used without corroboration.

  • Treble110 on YouTube: Final Harvest · Uploaded · Checked

    Supports: One player's route and timing.

    Limits: Reviewed from an automatic transcript, not frame by frame; one run does not establish current mechanics or a universal route.

  • Official IRON NEST Discord · archived player questions · Checked

    Supports: Player questions about counter-battery fire, the fire-direction centres, AA, completion, HCHE, field reports and being detected.

    Limits: Shows what players asked or reported, not current mechanics, confirmed bugs or a community consensus.

Fire and Light

  • IRON NEST global achievements on Steam · Checked

    Supports: The mission name and its achievements.

    Limits: Lists achievements by unlock rate, not mission number, and does not publish gold thresholds.

  • Developer FAQ on the Steam Community forum · Published · Checked

    Supports: Background on the loop from one mission to the next.

    Limits: Has no Fire and Light-specific steps.

  • Official IRON NEST announcements on Steam · Checked

    Supports: Patch history from Version 1.0 (1558) to (1622).

    Limits: No patch entry mentions Fire and Light.

  • IRON NEST game files, Steam build 24750322 · Checked

    Supports: Mission title, messages, flow, entities, shells, medals and requisition prices, from build 24750322 and the demo build (23991575).

    Limits: Describes those builds only; the unit of the impact radius is not confirmed.

  • CallMeLou on YouTube: full game, no commentary · Uploaded · Checked

    Supports: A release-era full run; the Fire and Light chapter runs from 7:02 to 27:26.

    Limits: Recorded before Patch #4; no build number is shown.

  • Many A True Nerd on YouTube: demo playthrough · Checked

    Supports: A narrated demo-era playthrough of Fire and Light.

    Limits: Demo build; no build number is shown.

  • hello Tomi on YouTube: demo full guide · Uploaded · Checked

    Supports: A full demo guide to Fire and Light: the two-phase structure and values from one run.

    Limits: Launch-period demo; its coordinates are examples from one run.

  • hello Tomi on YouTube: short demo playthrough · Uploaded · Checked

    Supports: A short demo run covering spotter bearings and the first firing solution.

    Limits: Demo build; reviewed from the transcript only.

  • TheTank1988 on YouTube: demo Missions 1–2, no commentary · Uploaded · Checked

    Supports: A no-commentary demo run of Missions 1 and 2.

    Limits: Demo build; reviewed from the transcript only.

  • Ivan Ironfist Ch. on YouTube: Star Shell correction · Uploaded · Checked

    Supports: A release-era walkthrough of Star Shell correction.

    Limits: Recorded before Patch #4; its values are examples from one run.

  • Official IRON NEST Discord · server-wide search · Checked

    Supports: Where players get stuck, and developer statements about how Star Shells work.

    Limits: Checked in an archive of the server that ends in late August 2026.

  • Third-party walkthrough: Fire and Light · Checked

    Supports: A two-phase walkthrough with worked examples.

    Limits: Third-party guide; its values are examples only.

  • Third-party mission database: Fire and Light · Checked

    Supports: Transcribed in-mission messages and mission parameters.

    Limits: Third-party transcription; the build is not stated.

Fire Correction

  • IRON NEST game files, Steam build 24750322 · Checked

    Supports: Fire and Light's correction wording, shared shell records, task records and build details.

    Limits: Establishes the explicit correction wording; class names and missing fields do not reveal the full correction logic.

  • NPC Tips: IRON NEST calculator · Checked

    Supports: This site's reviewed flight-time model, its watch and bridge limits, and what timing it leaves out.

    Limits: Supports the hand-off to the calculator; the calculator guide, not this page, owns the timing formula.

  • NPC Tips: Fire and Light guide · Checked

    Supports: This site's review of where Fire and Light's Star Shell correction starts, which way it points and how it feeds the firing solution.

    Limits: That mission flow must not be applied to missions that do not show the explicit correction.

  • NPC Tips: The Gorge guide · Checked

    Supports: This site's review of single-shot observation and the one-control-at-a-time crater method.

    Limits: The method depends on the mission and situation and does not give a universal correction value.

  • Third-party IRON NEST guide · Published · Checked

    Supports: A research lead on correction loops, stale firing cards and report origins.

    Limits: Third-party guide; it does not establish current-build mechanics on its own.

  • Apollo Trail: How to calculate firing solutions in IRON NEST · Published · Checked

    Supports: Conflicting claims about correction loops and manual calculation, checked against stronger evidence.

    Limits: Its fixed thresholds, controls and medal advice lack official or observed support and are not published.

  • Diegplaysgames on YouTube: Fire on Call run · Uploaded · Checked

    Supports: Timestamped report-origin, map-to-gun and follow-up-shot workflow.

    Limits: Reviewed from an automatic transcript of one run; it does not establish universal values or the full current interface.

  • Zach Hazard on YouTube: How to operate the IRON NEST · Uploaded · Checked

    Supports: A lead on the map, calculator, rotation, elevation and firing-station workflow.

    Limits: Recorded before the Version 1.0 baseline; it cannot override current-build text.

  • Savage Vegeta on YouTube: IRON NEST complete beginner's guide · Uploaded · Checked

    Supports: An early map, calculator and firing-sequence workflow.

    Limits: Demo footage; it shows how players operate, not Version 1.0 rules.

  • Official IRON NEST Discord · server-wide search · Checked

    Supports: Typical questions about correction arrows, rebuilding shot cards, timing and rotation.

    Limits: Questions show recurring uncertainty, not the answers; the archive ends in late August 2026.

Fire on Call

  • IRON NEST game files, Steam build 24750322 · Checked

    Supports: Mission graph and flow, English mission text, Campaign order, shell identifiers, enemy entities and which medals belong to the mission.

    Limits: Describes build 24750322 only; configuration counts do not guarantee the same positions, groupings or route in every run.

  • Official IRON NEST announcements on Steam · Checked

    Supports: The Patch #4 fix for Fire on Call being interrupted after targets were cleared early.

    Limits: Does not say whether later reports about stand-down, sleep or field reports are resolved.

  • Third-party walkthrough: Fire on Call · Published · Checked

    Supports: Walkthrough and shell-order context.

    Limits: Third-party guide; single instructions do not prove current mechanics on their own.

  • Iron Nest Wiki (Fandom): Fire on Call · Checked

    Supports: Mission-guide context.

    Limits: Third-party wiki page with no publication date shown.

  • Diegplaysgames on YouTube: Fire on Call run · Uploaded · Checked

    Supports: One player's run of the mission.

    Limits: Reviewed from an automatic transcript; one run is not a general solution.

  • Official IRON NEST Discord · #ironnest-gameplay · Checked

    Supports: Player reports about stand-down, sleeping, TEAR and HE order, and field reports stopping.

    Limits: Shows what players reported; does not establish current behaviour or a confirmed fix.

  • Official IRON NEST Discord · #bug-reports · Posted · Checked

    Supports: Reported mission-logic and newspaper errors.

    Limits: Player bug report; not reproduced on the current build and no fix confirmed.

Guides

  • IRON NEST game files, Steam build 24750322 · Checked

    Supports: Campaign order, public mission titles, and Calibration Fire's objective and completion text.

    Limits: Supports recorded text and structure, not every interaction or player workflow.

  • Official IRON NEST Discord · #faq · Posted · Checked

    Supports: The high-level mission workflow from orders through the map, calculator, gun setup, firing and stand-down.

    Limits: Not a full list of stations, a fixed six-step procedure or a universal troubleshooting guide.

  • IRON NEST: Heavy Turret Simulator on Steam · Published · Checked

    Supports: The official description of a single-player heavy-turret simulator and its Campaign.

    Limits: Store copy does not establish detailed mechanics or station procedures.

  • PaintUFast on YouTube: beginner run · Uploaded · Checked

    Supports: One recorded beginner's run, used to find interaction questions and evidence gaps.

    Limits: One player's route with run-specific values and advice; it cannot establish universal controls or correction rules.

  • Official IRON NEST Discord · #game-suggestions · Posted · Checked

    Supports: Typical onboarding questions about map tools, triangulation and where to find the next answer.

    Limits: Questions show what players need, not whether a mechanic or fix is correct.

High Tide

  • IRON NEST game files, Steam build 24750322 · Checked

    Supports: Campaign order, English mission text, timer relationships, graph branches, enemy entities and which medals belong to the mission.

    Limits: Describes build 24750322 only; the configuration does not fix enemy totals, wave counts or a firing solution for any run.

  • Third-party walkthrough: High Tide · Published · Checked

    Supports: Reported moving-target workflow and how to manage the queue of targets.

    Limits: Third-party guide; its values and tactics do not prove current mechanics on their own.

  • Third-party mission database: High Tide · Checked

    Supports: Reported mission, ammunition, resource and medal details.

    Limits: Third-party database with no publication date shown; its resource and medal values are not treated as current facts.

  • Diegplaysgames on YouTube: calculator explanation · Uploaded · Checked

    Supports: Reported ammunition choice, timing and how to manage the pressure.

    Limits: Reviewed from an automatic transcript, not frame by frame; one run is not a general solution.

  • Random video dump on YouTube: High Tide strategy · Uploaded · Checked

    Supports: Selected for this guide, but no usable transcript could be collected.

    Limits: Supports no gameplay statement on this page.

  • Official IRON NEST Discord · archived player questions · Checked

    Supports: Player questions about landing-craft timing, ammunition and difficulty.

    Limits: Shows what players asked or reported, not current mechanics or a community consensus.

Iron Road

  • IRON NEST game files, Steam build 24750322 · Checked

    Supports: Mission title and order, briefing text, the mission flow graph, enemy entities, shells and medal definitions.

    Limits: Describes build 24750322 only; shell unlocks for the mission are not decoded.

  • IRON NEST game files, Steam build 25182032 · Checked

    Supports: The build 25182032 mission entity table: 27 hostile spawns, and the six infantry and two mechanized units added since build 24750322.

    Limits: A structural count; it does not show which kills count toward a medal or which medal variant the mission awards.

  • Official IRON NEST Discord · #dev-works-in-progress · Posted · Checked

    Supports: The developer's work-in-progress list for the patch after 1.0 (1622): the softlock, the kill-streak medal, the Steam gold achievement and save-and-continue.

    Limits: A developer message in a work-in-progress channel; which patch shipped these fixes comes from the official Patch #6 notes.

  • Patch #6 announcement on the IRON NEST Steam Community hub · Published · Checked

    Supports: The official Patch #6 notes, Version 1.0 (1663): the softlock and consecutive-kills medal fixes on Iron Road, the Steam gold achievement fix and saving on mission exit.

    Limits: Does not say how the consecutive-kills medal was fixed.

  • Patch #7 announcement on the IRON NEST Steam Community hub · Published · Checked

    Supports: The official Patch #7 notes, Version 1.0 (1683): the fix for loading from a save preventing the player from going to sleep.

    Limits: The fix is game-wide and does not name Iron Road.

  • Official IRON NEST Discord · #bug-reports · Posted · Checked

    Supports: Community reports of 19 hostile targets, the gold medal problem, a test-branch observation of added enemies, a test-branch report that the mission would not end after a save and reload, and a later explanation that the kill streak counts shots that each kill a target.

    Limits: Community reports from an incomplete archive; the number of added enemies in the test-branch observation differs from the game files.

  • Official IRON NEST Discord · #ironnest-gameplay · Posted · Checked

    Supports: A playtest notice that Unrelenting Volley needed 20 kills while only 19 targets were found, and a later player note that gold needs 20 killing shots in a row.

    Limits: Observed before the fix.

  • Third-party walkthrough: Iron Road · Published · Checked

    Supports: Waypoint timing, AP emplacements, War Horn timing and optional targets.

    Limits: Third-party guide; its values are examples from one run.

  • Third-party mission database: Iron Road · Checked

    Supports: Transcribed in-mission messages and mission parameters.

    Limits: Third-party transcription; the build is not stated and its parameters are not used as rules.

  • MeegHub on YouTube: Iron Road · Uploaded · Checked

    Supports: A release-era run, used to cross-check HCHE use and the schedule.

    Limits: Reviewed from automatic captions only; no build number is shown.

  • KillrobPlays on YouTube: Iron Road · Uploaded · Checked

    Supports: A release-era run, used to cross-check the train hit, the emplacements and the War Horn.

    Limits: Reviewed from automatic captions only; no build number is shown.

  • QuadThumb Gaming on YouTube: Iron Road · Uploaded · Checked

    Supports: A release-era run, used to cross-check HCHE use, waypoint timing and missed shots.

    Limits: Reviewed from automatic captions only; no build number is shown.

Liberation

  • IRON NEST game files, Steam build 24750322 · Checked

    Supports: Liberation's minimum requisition and powder charges, and its four medals.

    Limits: Structural values from build 24750322 (unchanged in 25182032); not verified in play.

  • Official IRON NEST Discord · #ironnest-gameplay (developer reply) · Posted · Checked

    Supports: The developer's answer that requisition credits carry over between missions, with a minimum given at the start of each mission.

    Limits: Does not give the minimum for each mission.

  • Third-party mission database · Checked

    Supports: Mission parameters, the High Command briefing, the target list and medal criteria, as transcribed.

    Limits: Third-party database without a stated build; its rules are cross-checked against footage and community reports before use.

  • Third-party walkthrough: Liberation · Published · Checked

    Supports: The three-stage structure, the free recon card, why AP suits danger-close targets, moving Iron Nest, the completion condition and the hospital icon.

    Limits: Third-party walkthrough updated before Patch #4, not a statement of the rules.

  • Many A True Nerd on YouTube: demo playthrough · Checked

    Supports: A demo-era run of the full mission: P4 recon, destroying the AP cache, the medical-centre marker and aiming to avoid civilians.

    Limits: Pre-release demo footage; details and balance may differ in the full release, and no build number is shown.

  • CallMeLou on YouTube: full game, no commentary · Uploaded · Checked

    Supports: The mission flow: moving Iron Nest, spotter triangulation, P4 recon, destroying the AP cache and the Campaign map. All screenshots on this page are frames from this video.

    Limits: One run recorded before Patch #4; each screenshot supports only what is visible in that frame, and no build number is shown.

  • GamerCA on YouTube: Liberation gameplay · Uploaded · Checked

    Supports: Cross-checks the 300 requisition start, the P4 recon order, the +75 RP cache reward, HE having no effect on the cache, spotter accuracy and the requisition console items.

    Limits: Automatic captions contain transcription errors; one run recorded before Patch #4.

  • hello Tomi on YouTube: demo full guide · Uploaded · Checked

    Supports: Shows that the Liberation card at the end of the demo is a mission-select screen, not the end of the demo.

    Limits: Does not show Liberation gameplay itself.

  • Official IRON NEST Discord · #dev-works-in-progress · Posted · Checked

    Supports: Known medal-system issues and the planned fixes, including the Iron Road kill-streak fix that was in testing.

    Limits: Describes work in testing, not a shipped change; the Iron Road entry is not a Liberation fix.

  • Official IRON NEST announcements on Steam · Checked

    Supports: The version baseline, and that the Patch #4 and Patch #5 notes have no Liberation entry.

    Limits: A missing entry does not prove nothing changed.

  • IRON NEST global achievements on Steam · Checked

    Supports: The official mission name, Liberation, and which achievement names exist.

    Limits: Does not describe mission mechanics; which achievements belong to the mission comes from third-party guides.

  • Official IRON NEST Discord · server-wide search · Checked

    Supports: Community reports on whether the P4 cache moves, kill-streak rules, the Austere 30 RP limit, when DRIL unlocks and the hospital map icons.

    Limits: Community reports without links to single messages; community roles such as [IRON] or Tester are not developer confirmation.

Lore

  • IRON NEST game files, Steam build 24750322 · Checked

    Supports: English text, mission wording, dated setting details, mission graphs and the 205-record newspaper index of truncated summaries.

    Limits: The files hold no publishable full newspaper text, full world timeline, Operator biography or reliable mission-to-newspaper link.

  • IRON NEST: Heavy Turret Simulator on Steam · Published · Checked

    Supports: The official dieselpunk heavy-artillery, single-player description of the game.

    Limits: Store copy does not establish world history, faction beliefs or how newspapers work.

  • IRON NEST: Heavy Turret Simulator official YouTube channel · Uploaded · Checked

    Supports: The Operator's role in turning incomplete information into a usable picture of the battlefield.

    Limits: Supports that narrow role, not a biography or every current control and story detail.

  • Official IRON NEST Discord · #faq · Posted · Checked

    Supports: The Operator's task loop and the newspaper that summarises each operation and world events.

    Limits: Does not link each newspaper to a mission or confirm extra reputation or procedural systems.

  • Official IRON NEST Discord · developer replies and community discussion · Checked

    Supports: Developer replies about canon and the rebel coalition, and player questions about morality and the Operator.

    Limits: Only clearly attributed developer messages count as official; other members' readings remain reported.

  • LT Gaming on YouTube: story commentary · Uploaded · Checked

    Supports: One player's reading that links the newspapers, propaganda and distrust of High Command.

    Limits: One commentary shows a possible reading, not current canon or a universal moral conclusion.

  • Iron Nest Wiki (Fandom): Lore · Checked

    Supports: A sample of claims about alternate history, Castile and national parallels, used to find conflicts.

    Limits: Contributor summary with uncited inference; it cannot establish canon without game text or an official source.

  • iron-nest.wiki: Newspaper consequences · Published · Checked

    Supports: Claims about newspaper consequences, reputation, procedural objectives and ability reactions, checked for conflicts.

    Limits: Those extra mechanics are not supported by the build evidence reviewed for this page.

  • TV Tropes: IRON NEST: Heavy Turret Simulator · Published · Checked

    Supports: Interpretations of Castile, the civil war, propaganda and the moral framing.

    Limits: Mixes observation and inference; it does not establish official political categories or canon.

Map

  • IRON NEST game files, Steam build 24750322: map icons, Symbols Chart and legend · Checked

    Supports: Map icon definitions (71 icon-to-sprite links, 70 visible after excluding Invisible), the Symbols Chart, map instruction textures and the audited legend text.

    Limits: Does not establish fixed grid dimensions or every frame, colour, modifier, reward, spawn or mission rule.

  • Official IRON NEST Discord · #faq · Posted · Checked

    Supports: Where tactical-map measurements fit in the simplest firing loop.

    Limits: Gives no icon list and does not settle every map-tool behaviour.

  • Official IRON NEST Discord · #bug-reports (developer) · Posted · Checked

    Supports: A developer's troubleshooting note that Final Harvest's Ref Alpha and Waypoint A share an icon.

    Limits: One mission on one date; not a complete legend or a permanent rule.

  • Official IRON NEST Discord · #ironnest-gameplay · Posted · Checked

    Supports: Repeated player requests for a complete icon key and help identifying symbols.

    Limits: Questions show demand, not whether an answer or mechanic is correct.

  • Third-party map symbol reference · Published · Checked

    Supports: Community icon coverage and terminology, used as a cross-check.

    Limits: Third-party page; the game files, not this page, decide the published count and names.

  • Pro Game Guides: IRON NEST map and measurements guide · Published · Checked

    Supports: Reported grid dimensions, marker descriptions and plotting workflow.

    Limits: Third-party guide; fixed dimensions and current-build mechanics remain unverified.

  • Atova on YouTube: demo map tools tutorial · Uploaded · Checked

    Supports: Reported map tools, markers, reference points and icon-key workflow.

    Limits: Automatic transcript of a demo-era video; it cannot establish Version 1.0 mechanics.

  • Game Launch Central on YouTube · Uploaded · Checked

    Supports: Reported pencil, marker and triangulation workflow.

    Limits: Reviewed from an automatic transcript, not frame by frame; a player's wording does not establish a current-build rule.

  • Nexus Mods: Tactical Map Tools · Published · Checked

    Supports: Shows that Tactical Map Tools is a separately distributed third-party mod.

    Limits: Only the page's title, address and type are used; the mod's features, compatibility and safety are not endorsed.

Medals

  • IRON NEST game files, Steam build 24750322 · Checked

    Supports: Every medal's metric and its bronze, silver and gold thresholds, the 15 medal names, the game's own English description of each medal, and which medals each mission scores.

    Limits: Describes build 24750322 only. The fields do not say how a condition is timed or counted during play.

  • Official IRON NEST Discord · #announcements · Posted · Checked

    Supports: The Patch #5 announcement that dates Version 1.0 (1622) to August 15, 2026.

    Limits: Does not say whether medal thresholds change between patches.

  • Official IRON NEST Discord · #ironnest-gameplay · Checked

    Supports: Player reports of the medal results screen, of the same medal earned in several missions, and of a run that met the Rapid Engagement Medal numbers without receiving it (August 15–17, 2026).

    Limits: Single-run player reports; no developer reply was found on when the Rapid Engagement timer starts.

  • Third-party database: medals · Checked

    Supports: A third-party threshold list whose values match this page, including the Rapid Engagement Medal.

    Limits: Third-party database with no build, date or method stated.

  • Destructoid: all gold medal requirements in IRON NEST · Published · Checked

    Supports: A third-party list of medal requirements by mission, used for comparisons on this page and for an earlier version of the mission index.

    Limits: Gives no medal names or build and mislabels some rows; the mission index now comes from the game files, which list a different medal for six missions.

  • Third-party guide: medals · Checked

    Supports: That in-game medals and Steam achievements are separate systems, and the “over a hundred” medal count this page explains.

    Limits: Third-party guide; its medal count conflicts with the game files, and it names only two medals.

  • allthings.how: how to get all 33 achievements · Published · Checked

    Supports: The Steam achievement breakdown: 33 achievements, 15 of them for taking every gold medal in a mission.

    Limits: A single third-party source, flagged where this page uses it.

Mods

  • Official IRON NEST Discord · #faq · Posted · Checked

    Supports: That Steam Workshop support is being considered, with tools in slow development and no promise or schedule; there is no official mod channel today.

    Limits: A statement of intent that a later announcement can replace.

  • Official IRON NEST Discord · #faq · Posted · Checked

    Supports: That no native Linux version is planned and the game runs under Proton.

    Limits: A statement as of March 10, 2026.

  • Patch #6 announcement on the IRON NEST Steam Community hub · Published · Checked

    Supports: The current official patch at the September 1, 2026 recheck: Patch #6, Version 1.0 (1663), August 22, 2026.

    Limits: Gives the game's patch only; it says nothing about whether any mod works with it.

  • Official IRON NEST Discord · #general-chat (developer) · Posted · Checked

    Supports: Why the in-game FOV cap is low: the notepad, clock and other controls sit in 3D space and become unreadable at a high FOV.

    Limits: A chat message, not an announcement; later versions may change it.

  • MelonLoader on GitHub: README and releases · Checked

    Supports: How MelonLoader is installed and removed, the folders it creates, and that its latest release is 0.7.3.

    Limits: Loader documentation; it proves nothing about compatibility with IRON NEST.

  • BepInEx documentation: installation · Checked

    Supports: How BepInEx is installed, and that IL2CPP games need the bleeding-edge line.

    Limits: Written for the stable line, which IRON NEST mods do not use, and it has no uninstall section.

  • BepInEx documentation: Proton and Wine · Checked

    Supports: The winhttp override BepInEx needs under Proton and Wine.

    Limits: General documentation, not written for IRON NEST.

  • BepInEx bleeding-edge builds · Checked

    Supports: That BepInEx 6 bleeding-edge build #785 exists and was the latest, matching the build mod authors point to.

    Limits: A download channel; it does not show that a build works with IRON NEST.

  • Nexus Mods: IRON NEST mods · Checked

    Supports: The 25 mods in this page's directory, with their platform pages, update dates and scan labels as of August 15, 2026.

    Limits: The listing changes weekly; only the two co-op entries were rechecked on September 1, 2026.

  • Thunderstore: IRON NEST community · Checked

    Supports: The IRON NEST community on Thunderstore, as a second place mods are hosted.

    Limits: Lists far fewer mods than Nexus Mods.

  • Nexus Mods: Fire Control System · Checked

    Supports: Fire Control System's install step, and its author's warning not to use it on the leaderboard.

    Limits: The author's own statements; its code was not reviewed.

  • Nexus Mods: Synchrony · Checked

    Supports: That Synchrony targets Demo v0.4.0 with MelonLoader 0.7.3.

    Limits: A Demo-era mod that states nothing about the full release.

  • Nexus Mods: Iron Nest co-op · Checked

    Supports: That Iron Nest co-op 2.0.0 and later are for the full release, and the mod's Nexus scan label.

    Limits: Author statements; the page description was one version behind the 2.4.1 release.

  • Iron Nest co-op 2.4.1 release on GitHub · Posted · Checked

    Supports: Iron Nest co-op 2.4.1, released August 30, 2026 and still on BepInEx 6 IL2CPP, and what it added.

    Limits: Author release notes; this site did not install or test the mod.

  • Nexus Mods: BepInEx MelonLoader Loader IL2CPP · Checked

    Supports: That this bridge claims to run MelonLoader mods under BepInEx 6.

    Limits: Not independently verified, and one mod author says their mod does not run under it.

  • Nexus Mods: Open Nest Co-op · Checked

    Supports: That Open Nest Co-op supports both BepInEx 6 and MelonLoader 0.7.3, where its files go, its warning not to install both loaders, and its Nexus scan label.

    Limits: Author statements; a scan label is Nexus's automated result, not a security audit.

  • Open Nest Co-op 0.2.0 release on GitHub · Posted · Checked

    Supports: Open Nest Co-op 0.2.0, released August 25, 2026 and titled for game patch 1.0 (1663).

    Limits: Author release notes; this site did not install or test the mod.

  • Nexus Mods: OpenNestCore · Checked

    Supports: That OpenNestCore is a shared library for both loaders that loads AssetBundles and usually comes bundled with the mods that need it.

    Limits: Its install path conflicts with most other sources.

  • Official IRON NEST Discord · #iron-nest-modding-community · Checked

    Supports: Messages from players, testers and mod authors (June–August 2026): loader packages pulled from Nexus because they were built for the Demo, where MelonLoader and mod files go, BepInEx standalone packages, the BepInEx and MelonLoader conflict and a crash from installing both, rebuilding BepInEx's generated folders, the Proton launch option, and the VR NEST release and early feedback.

    Limits: Community messages, including Tester roles, not official policy; several are second-hand or untested.

  • Official IRON NEST Discord · #game-suggestions · Checked

    Supports: Player requests to raise the FOV cap (June 16, 2026) and to remove or toggle the “press E to interact” prompt (June 28, 2026).

    Limits: Requests only; no developer reply was found.

  • Official IRON NEST Discord · #general-chat · Posted · Checked

    Supports: A release-day question about turning off the interaction prompt, which went unanswered.

    Limits: A single question, not evidence of a setting.

  • Steam Community forum: “Made a basic VR mod” · Posted · Checked

    Supports: A 2024 post describing a basic VR mod that was not released.

    Limits: Historical; it shows nothing about current VR support.

  • Steam Community forum: “Modding question” · Posted · Checked

    Supports: A player question about whether a custom-music mod counts as cheating on the leaderboard, and a reply describing a leaderboard opt-out in the Demo's settings.

    Limits: A single recollection about the Demo; the option was not verified in the full release.

Requisition Console

  • IRON NEST game files, Steam build 24750322 · Checked

    Supports: The 32 purchasable punchcards with their costs and the game's own description of each; the requisition the game's text reports for destroying enemy and friendly targets; the shared record behind the three Forward Observer cards; and each campaign mission's minimum requisition.

    Limits: Describes build 24750322 only. It does not show what unlocks a card or how mission-objective rewards are calculated.

  • IRON NEST game files, Steam build 25182032 · Checked

    Supports: That the mission save added in Patch #6 records requisition points.

    Limits: Shows what the save stores, not whether the points are restored exactly when a saved mission is continued.

  • Official IRON NEST Discord · #faq · Checked

    Supports: That the official FAQ at the 1.0 release says nothing about requisition, punchcards, credits or the console.

    Limits: Shows only that the FAQ is silent; it does not settle whether credits carry over.

  • Official IRON NEST Discord · #ironnest-gameplay (developer reply) · Posted · Checked

    Supports: The developer's answer that requisition credits transfer between missions and can be saved up, with a minimum given at the start of each mission.

    Limits: Does not give the minimum for each mission or say how skirmish and challenge modes are handled.

  • Official IRON NEST Discord · #bug-reports thread · Posted · Checked

    Supports: A tester's report that entering Liberation first after launching the game can reset credits to the mission minimum, with example minimums for two missions.

    Limits: A player report, not a developer statement; the developer's fix is listed for an update that had not been released when this page was checked.

  • Official IRON NEST Discord · #announcements · Posted · Checked

    Supports: The Patch #5 announcement that dates Version 1.0 (1622) to August 15, 2026.

    Limits: Does not list punchcard prices or say whether they change between patches.

  • Patch #6 announcement on the IRON NEST Steam Community hub · Published · Checked

    Supports: That Patch #6 added saving on mission exit and continuing a mission from the save.

    Limits: Does not say which values the save keeps.

  • Official IRON NEST Discord · #ironnest-leaderboard-notifications · Posted · Checked

    Supports: Internal card identifiers printed in the bot's run analysis; all seven match the extracted card data.

    Limits: Shows only the cards used in one run, with no prices; it cannot establish the total number of cards.

  • Official IRON NEST Discord · #ironnest-gameplay · Checked

    Supports: Player and tester reports that requisition carries over between missions with a minimum for each mission, and that skirmish and challenge modes are separate (August 2026), and observations of ammunition costs and card use (August 15–16, 2026).

    Limits: Player reports; the minimums they quote are not confirmed by the game files, a few earlier posts disagree, and prices on this page come from the game files instead.

  • Third-party guide: requisition console · Checked

    Supports: Where the console is and how to order from it, worked from 1.0 gameplay footage.

    Limits: Third-party guide with no build stated; other descriptions place the console elsewhere.

  • Third-party database: punchcards · Checked

    Supports: A third-party card list that matches this page name for name, plus MSTD, which it marks as not normally purchasable.

    Limits: No date, build or method stated.

  • Third-party database: requisition · Checked

    Supports: The “25 per star” credit formula this page explains why it does not use.

    Limits: A single source with no date, build or method, and it cannot produce the rewards seen in play.

  • PaintUFast on YouTube: beginner run · Uploaded · Checked

    Supports: A 1.0 playthrough showing how cards are ordered, a priority-target reward of 75 requisition and a first-mission starting balance of 350.

    Limits: One run; the build is not shown, and the values are observations rather than rates.

Review

  • IRON NEST: Heavy Turret Simulator on Steam · Published · Checked

    Supports: The full game's product identity and official store record.

    Limits: Price, ratings, review totals and store details can change; none is aggregated here.

  • NPC Tips: IRON NEST Demo guide · Checked

    Supports: Demo access, what the Demo includes, evidence for the core loop, and the self-test route.

    Limits: This site's own page; the Demo guide owns the details.

  • NPC Tips: IRON NEST missions list · Checked

    Supports: The Campaign structure, the 15 named story missions and the Challenge Missions boundary.

    Limits: Does not establish play time, difficulty, replay value or whether a reader will enjoy it.

  • NPC Tips: IRON NEST multiplayer guide · Checked

    Supports: The current single-player state and how planned native multiplayer differs from it.

    Limits: Keeps base-game plans, separate co-op products, community mods and other platforms apart.

  • PCGamesN: IRON NEST: Heavy Turret Simulator review · Published · Checked

    Supports: One writer's experience of the procedure, the organisation it demands, the rhythm and later missions.

    Limits: A single scored review; its score is not used or averaged here.

  • PC Gamer: Iron Nest is the best battleship game I've played in years · Published · Checked

    Supports: One writer's experience of the hands-on procedure, the atmosphere and wanting co-op.

    Limits: Not a full feature or current-build review; opinions stay attributed.

  • Cockney Gamer on YouTube: review · Uploaded · Checked

    Supports: A long-form account of the calculation load, the satisfaction and the concerns.

    Limits: Reviewed from an automatic transcript, not frame by frame; no score is used here.

  • LT Gaming on YouTube: story commentary · Uploaded · Checked

    Supports: Experience of the core loop and immersion before release.

    Limits: Cannot establish current stability, final scope or overall quality.

  • Worth A Buy on YouTube: demo impressions · Uploaded · Checked

    Supports: Experience of the mechanical sound, the enclosed view and the manual procedure.

    Limits: Demo era; used only for core-loop self-test signals.

  • Steam Deck HQ: IRON NEST on Steam Deck · Published · Checked

    Supports: A short Steam Deck hands-on with settings context.

    Limits: The writer disclosed limited play; the result cannot be applied to other devices or settings.

  • Steam Community forum: player discussions · Posted · Checked

    Supports: Positive and negative player posts about repetition.

    Limits: Individual posts, partly extracted; they do not show a consensus.

  • r/ShouldIbuythisgame on Reddit: “Should I buy the Iron Nest?” · Posted · Checked

    Supports: Buying questions about repetition, space and the unusual mechanics.

    Limits: The post body could not be read; used only as a sign of what buyers ask.

  • Official IRON NEST Discord · server-wide search · Checked

    Supports: Individual questions and reports about repetition, difficulty, satisfaction, hours, replay and Linux performance.

    Limits: Individual reports are not representative.

  • NPC Tips: Editorial Policy · Checked

    Supports: That this review uses registered facts, attributed experiences and labelled inferences instead of a site playtest or a score.

    Limits: Describes this site's method; it establishes no game fact or third-party experience.

Rock of Gibraltar

  • IRON NEST game files, Steam build 24750322 · Checked

    Supports: Mission title, messages, enemy entities, shells and medal definitions.

    Limits: Describes build 24750322 only; what the timer means and the lead formula are not confirmed by the game.

  • IRON NEST global achievements on Steam · Checked

    Supports: Mission names, checked against this site's mission list.

    Limits: The mission order comes from a continuous full-game run and the build's Campaign order, not from this page.

  • Official IRON NEST announcements on Steam · Checked

    Supports: The Patch #4 fix for the last two Rock of Gibraltar medals.

    Limits: Patch #4 predates the build this guide reads.

  • Third-party walkthrough: Rock of Gibraltar · Checked

    Supports: The reference-chain method, the firing window and how to lead the optional vessel.

    Limits: Third-party guide; its values are examples from one run, and the 11:08 time is one observation.

  • Third-party mission database: Rock of Gibraltar · Checked

    Supports: Transcribed in-mission messages and which medal variant belongs to the mission.

    Limits: Third-party transcription; the build is not stated and its values were not matched field by field.

  • DieselDesigns Gaming on YouTube: Rock of Gibraltar · Uploaded · Checked

    Supports: A run used to cross-check the transcription.

    Limits: Reviewed from the transcript, not frame by frame; no build number is shown.

  • Official IRON NEST Discord · server-wide search · Checked

    Supports: Where players get stuck, medal complaints and reports about moving targets.

    Limits: Checked in an archive of the server that ends in late August 2026.

Shell Types

  • IRON NEST game files, Steam build 24750322 · Checked

    Supports: All 21 shell definitions and their build values, the game's own description of each shell, what each shell load costs, and the target data behind the shell groupings.

    Limits: Describes build 24750322 only. Engine values are printed without real-world units, and the data does not show what unlocks a shell.

  • IRON NEST Demo game files, build 23991575 · Checked

    Supports: The demo's 9 shell types, for the comparison with 1.0.

    Limits: Describes demo build 23991575 only.

  • Official IRON NEST Discord · #faq · Checked

    Supports: The machine's size, about 20 m × 30 m × 50 m including the barrels, and that the official FAQ does not cover shell types, caliber, loading or unloading.

    Limits: Silent on everything else on this page; that silence rules nothing in or out.

  • Official IRON NEST Discord · #announcements · Posted · Checked

    Supports: The Patch #5 announcement that dates Version 1.0 (1622) to August 15, 2026.

    Limits: Does not list shell values or say whether they change between patches.

  • Official IRON NEST Discord · #ironnest-gameplay · Checked

    Supports: A statement on the official community server that the shell type does not change flight time or elevation (August 17, 2026).

    Limits: A remark in a community channel, not official documentation; this page checks it against the shared ballistic values in the game files.

  • Official IRON NEST Discord · #game-suggestions · Checked

    Supports: A player feature request to unload a loaded shell.

    Limits: A request, not a statement of what the game does or will do.

  • Official IRON NEST Discord · #lore-discussion · Checked

    Supports: The 800 mm caliber as the figure players agree on.

    Limits: Player consensus with no source; the caliber is not officially confirmed.

  • TPose Gaming: IRON NEST ammo list · Published · Checked

    Supports: A third-party list of 21 shells with codes, blast radius and costs, marking PYRO, TGAS and PGAS as demo leftovers.

    Limits: No build, method or units stated.

  • Pro Game Guides: every IRON NEST shell type · Published · Checked

    Supports: The 7-shell list this page explains as the demo count.

    Limits: Presents 7 as the complete set; its prices match the demo, not 1.0.

  • PaintUFast on YouTube: beginner run · Uploaded · Checked

    Supports: A 1.0 playthrough showing shells being requisitioned and loaded.

    Limits: One run; the build is not shown.

  • Third-party database: caliber · Checked

    Supports: The 800 mm caliber, a shared charge-to-range table for all shells, and that a loaded shell cannot be unloaded.

    Limits: A single third-party source with no date, build or method.

  • Developer answer on the Steam Community forum: unloading and powder charges · Checked

    Supports: The developer's answer that a loaded gun cannot be unloaded, and the ways to recover: recalculate elevation for the charges actually loaded, use the second gun, change target, or reload after firing.

    Limits: Does not cover loading too few charges; no build is stated.

Siege of Cartagena

  • IRON NEST game files, Steam build 24750322 · Checked

    Supports: Mission title and order, messages, enemy entities, shells, medal definitions and requisition costs.

    Limits: Describes build 24750322 only; how long counter-battery fire lasts and how armour-piercing rounds interact were not decoded.

  • Third-party mission database: Siege of Cartagena · Checked

    Supports: Transcribed in-mission messages, which medal variant belongs to the mission, and counts of each enemy type.

    Limits: Third-party transcription; the build is not stated and its values were not matched field by field.

  • Third-party walkthrough: Siege of Cartagena · Checked

    Supports: Chained measurement, battery search sectors, smoke requests and recovering with Emergency Move.

    Limits: Third-party guide; its values are examples from one run and the recovery method has a single source.

  • Jay Tompkins on YouTube: Siege of Cartagena · Uploaded · Checked

    Supports: A release-era run: the mission flow, AP against the batteries and smoke requests.

    Limits: Reviewed from the transcript, not frame by frame; no build number is shown.

  • DieselDesigns Gaming on YouTube: Siege of Cartagena · Uploaded · Checked

    Supports: A release-era run: the mission flow, AP against the batteries and smoke requests.

    Limits: Reviewed from the transcript, not frame by frame; no build number is shown.

  • Official IRON NEST Discord · #dev-works-in-progress · Posted · Checked

    Supports: A developer statement that mission completion and timing text could be clearer.

    Limits: A pre-release design comment, not a description of how the current build behaves.

  • Official IRON NEST Discord · #bug-reports · Checked

    Supports: Reports of the mission stalling after both coastal batteries were destroyed.

    Limits: Community reports; no fix is confirmed on the current build.

  • Official IRON NEST Discord · #ironnest-gameplay · Checked

    Supports: Player questions about counter-battery pressure, coastal battery ammunition and positions, and the mission not completing.

    Limits: Checked in an archive of the channel that ends in late August 2026.

Supply Cache

  • IRON NEST game files, Steam build 24750322 · Checked

    Supports: Supply Cache labels, underground and AP text, Chill reward wording, Liberation's mission flow, Challenge fire-direction-centre wording and graph limits.

    Limits: Describes build 24750322 only; which object the cache is, reward values, repeat events and how the marker looks remain limited as the page states.

  • Official IRON NEST Discord · #ironnest-gameplay (developer) · Posted · Checked

    Supports: A developer's dated explanation of the underground marker and why AP is needed.

    Limits: The reply gives no build number, and the marker shape was not rechecked in current footage.

  • Official IRON NEST Discord · #ironnest-gameplay · Checked

    Supports: Player reports about HCHE and questions about Chill cache counts and respawns.

    Limits: Tester roles and single runs do not establish a normal ammunition rule, the affected version, a total, a limit or how respawns work.

  • GamerCA on YouTube: Liberation gameplay · Uploaded · Checked

    Supports: Liberation's recon and AP sequence, with historical reward context.

    Limits: One historical run with automatic-transcript limits; it cannot set Patch #5 or cross-mode number rules.

The Gorge

  • IRON NEST game files, Steam build 24750322 · Checked

    Supports: Mission title and order, briefing and mission messages, enemy entities, shell values and medal definitions.

    Limits: Describes build 24750322 only. The elevation formula and how kill streaks are counted were not decoded.

  • Third-party mission database: The Gorge · Checked

    Supports: Transcribed in-mission messages, which medal variant belongs to the mission, and counts of each enemy type.

    Limits: Third-party transcription; the build is not stated and its values were not matched field by field.

  • Third-party walkthrough: The Gorge · Checked

    Supports: Manual engine restart, the observed-fire method, common mistakes and example values from one run.

    Limits: Third-party guide; the build is not stated and per-run values are examples only.

  • DieselDesigns Gaming on YouTube: release-era playthrough · Uploaded · Checked

    Supports: A release-era run showing the engine restart, recon to the east, drill and HCHE rounds, observed fire, the pass clearing and optional rear targets.

    Limits: Reviewed from the transcript, not frame by frame; no build number is shown.

  • Treble110 on YouTube: speedrun · Uploaded · Checked

    Supports: A speedrun clearing the eastern targets and skipping ahead.

    Limits: Reviewed from the transcript; no build number is shown, and speedrun shortcuts are not the mission objective.

  • Official IRON NEST Discord · #ironnest-gameplay · Checked

    Supports: Player questions about the manual-fire formula, the mission not progressing and how medal kill streaks are counted.

    Limits: Player reports, not developer statements; checked in an archive of the channel that ends in late August 2026.

Triangulation

  • IRON NEST game files, Steam build 24750322 · Checked

    Supports: Named-origin inputs, bearing and distance structures, chained points, the accuracy limit, requests for more intelligence, and the Position Report bearing-or-distance link in the mission graph.

    Limits: Proves build text, fields and direct graph links only; it does not give random odds, timing across modes, map gestures or later-patch behaviour.

  • Official IRON NEST Discord · #faq · Posted · Checked

    Supports: The overall teleprinter-to-map-to-calculator-to-fire loop.

    Limits: Gives no triangulation-specific steps or map-tool gestures.

  • Official IRON NEST Discord · #dev-chat (developer) · Posted · Checked

    Supports: Developer teaching examples on shallow angles, rounding error, extra observers and double intersections.

    Limits: A pre-1.0 developer statement, not a description of how the current build behaves.

  • Official IRON NEST Discord · server-wide search · Checked

    Supports: Player questions about origins, double intersections, accuracy margins and the Position Report.

    Limits: Community explanations show what players reported, not the underlying current-build mechanic.

  • Third-party guide: how to triangulate · Published · Checked

    Supports: Two bearings, mixed constraints, the Position Report, chained points and troubleshooting.

    Limits: Third-party guide; its examples from one run are not current-build proof.

  • Tpose Gaming: IRON NEST triangulation · Published · Checked

    Supports: Two bearings, mixed constraints, two distances, chained targets and common errors.

    Limits: Third-party guide; its claims about tool colours and the interface remain unverified.

  • Pro Game Guides: IRON NEST map and measurements guide · Published · Checked

    Supports: Known points, two bearings, two distances, the firing line and an FAQ.

    Limits: Published before Version 1.0; it cannot establish current-build behaviour.

  • Atova on YouTube: demo map tools tutorial · Uploaded · Checked

    Supports: Map tools, mixed constraints, chaining and the firing line, demonstrated.

    Limits: Automatic transcript of demo footage; not used as a current Version 1.0 interface rule.

White Shells

  • IRON NEST game files, Steam build 24750322 · Checked

    Supports: Campaign order, the mission graph and flow, English mission text, node fields, entity roles, spawns, the timer and the completion structure.

    Limits: Describes build 24750322 only; it does not give a universal firing solution, a best route, or unlock values.

  • Official IRON NEST Discord · #ironnest-gameplay (developer reply) · Posted · Checked

    Supports: The developer's answer that requisition credits carry over between missions, with a minimum given at the start of each mission.

    Limits: Does not give the minimum for each mission.

  • IRON NEST game files, Steam build 24750322: White Shells event filters · Checked

    Supports: The destroyed-entity filters and the link between White Shells and the Artillery role that ends the betrayal fight.

    Limits: Describes build 24750322 only; it does not prescribe a shell type, coordinates, target order or a count for other versions.

  • CallMeLou on YouTube: full game, no commentary · Uploaded · Checked

    Supports: The continuous Campaign sequence and one visible White Shells run.

    Limits: One run does not prove a fixed duration, universal coordinates or a single route.

  • Levas on YouTube: White Shells ending · Uploaded · Checked

    Supports: Visible actions and outcomes, used for the hand-off to the Endings guide.

    Limits: Supports only the actions shown, not broad shell-type rules or a mission walkthrough.

  • TimHawk on YouTube: White Shells ending · Checked

    Supports: An independent check of the visible outcome route.

    Limits: Supports only what is on screen; the build, full route conditions and replay behaviour are not established.

  • Third-party mission guide: White Shells · Published · Checked

    Supports: Reported resource, target, route and restart questions, checked for this guide.

    Limits: Third-party claims are not used without stronger evidence; resource and unlock values stay out of the page.

  • Third-party endings guide: White Shells · Published · Checked

    Supports: Ending coverage and the Pride report, for the hand-off to the Endings guide.

    Limits: Third-party guide; it does not cover this mission walkthrough and cannot prove build-specific mechanics.

  • Official IRON NEST Discord · archived player questions · Checked

    Supports: Player questions about mission goals, resources, retaliation, artillery counts, special shells and achievements.

    Limits: Shows what players ran into, not current mechanics, confirmed bugs or a community consensus.