IRON NEST GUIDE UNOFFICIAL FIELD INTELLIGENCE

UNOFFICIAL · CURRENT BUILD · SINGLE-PLAYER · LAST VERIFIED 2026-08-17

BY MIA HE · PUBLISHED 2026-08-11 · UPDATED 2026-08-17 · EVIDENCE METHOD

MULTIPLAYER STATUS · UNOFFICIAL

Is Iron Nest Multiplayer? Official Co-op Plans and Mod

Four different things get called “Iron Nest multiplayer”. This page separates what ships today, what the developers have confirmed, what is a separate product, and what modders provide right now — each with its own evidence and last-checked date.

MULTIPLAYER STATUS AT A GLANCE

OFFICIAL AND COMMUNITY TRACKS
MP-01 OFFICIAL PRODUCT

Heavy Turret Simulator — current official build

SINGLE-PLAYER

AVAILABILITY
Available now as a single-player game; native Multiplayer is not in the current official build.
SCOPE
The released Heavy Turret Simulator build is single-player.
ASSESSMENT
The shipped product state does not cancel the separately confirmed future Multiplayer plan.
TIMING
AVAILABLE NOW
MP-02 OFFICIAL PRODUCT

Heavy Turret Simulator — future Multiplayer

CONFIRMED · DATE TBA

AVAILABILITY
Confirmed, but not available in the current official build.
SCOPE
Each player controls their own IRON NEST on the same map in co-op missions or competitive modes. In competitive play, other players become targets.
ASSESSMENT
Base-game Multiplayer support will be free. Player count, detailed rules, and a test plan remain unannounced.
TIMING
DATE TBA
MP-03 OFFICIAL PRODUCT

Standalone Co-op game

PLANNED · LATE 2027 / EARLY 2028

AVAILABILITY
Planned as a separate future product; it is not available now.
SCOPE
Multiple players share one platform.
ASSESSMENT
This is a separate future Co-op product. Its formal title, target platforms, price, and exact date have not been announced. The window applies only to this product, not to base-game Multiplayer.
TIMING
LATE 2027 / EARLY 2028 · ROUGH WINDOW
MP-04 COMMUNITY PROJECT

Community co-op Mods (2 listed)

AVAILABLE · UNOFFICIAL

AVAILABILITY
Author-provided project pages and files were available when checked; current game-build compatibility is not guaranteed.
SCOPE
2 unofficial co-op projects state support for the current full release. Player counts, connection methods, and sync limits differ per project and are listed separately on each card.
ASSESSMENT
These community projects are not official Multiplayer builds, are version-sensitive, and have not been independently tested by this site.
TIMING
VERSION-SENSITIVE · CHECK CURRENT SOURCES

CURRENT OFFICIAL BUILD

STATUS SNAPSHOT

SHIPPED PRODUCT · OFFICIAL

Heavy Turret Simulator — current official build

SINGLE-PLAYER

The released Heavy Turret Simulator build is single-player. The shipped product state does not cancel the separately confirmed future Multiplayer plan.

LAST CHECKED 2026-08-17 devFaq steamStore launchAnnouncement

OFFICIAL MULTIPLAYER PLANS

PLAN COMPARISON

The official roadmap describes two separate products: future Multiplayer support for Heavy Turret Simulator, and a standalone Co-op game built around several players sharing one platform. Their scope, cost boundaries, and timing are not interchangeable.

OFFICIAL PLAN A OFFICIAL

Heavy Turret Simulator — future Multiplayer

CONFIRMED · DATE TBA

Product
Future support for Heavy Turret Simulator
Current availability
Not available in the current official build
Status
CONFIRMED
Player arrangement
Each player controls their own IRON NEST
Modes / scope
Co-op missions and competitive modes on the same map
Cost boundary
Officially described as free base-game Multiplayer support
Timing
DATE TBA
Not announced
Release date, player count, detailed rules, and test plan
OFFICIAL PLAN B OFFICIAL

Standalone Co-op game

PLANNED · LATE 2027 / EARLY 2028

Product
A separate Co-op product
Current availability
Not available
Status
PLANNED
Player arrangement
Multiple players share one platform
Modes / scope
Shared-platform Co-op; further details have not been announced
Cost boundary
The base-game support commitment does not cover it
Timing
ROUGH WINDOW · LATE 2027 / EARLY 2028
Not announced
Formal title, target platforms, price, and exact date

COMMUNITY CO-OP MODS

AUTHOR-PUBLISHED · UNVERIFIED

Both projects below are listed on the same terms, in no particular order, and this site has tested neither. Their player counts, connection methods, loaders, and sync limits come from different authors and differ from each other, so read each card on its own rather than carrying a detail across.

MP-MOD-01 · UNOFFICIAL COMMUNITY PROJECT

Iron Nest co-op (Updated for Iron Nest release)

Published by Jager2251

Unofficial community mod
Observed version
2.4.1
Game version stated
Version 2.4.0 restored compatibility with game build 1663, according to the author; the current Mod release is 2.4.1
Platform last updated
2026-08-30
Last checked
2026-09-01
Author-claimed players
Up to 5 per lobby, according to the author
Connection
Steam lobby code
Required loader
BepInEx 6 IL2CPP x64 · author-tested build 6.0.0-be.785
Site testing
Not independently tested

PLATFORM SCAN FLAG

Safe to use NexusMods automated scan, as checked 2026-09-01

This is the hosting platform’s own automated result, quoted as it appears there. It is not a finding by this site and not a security audit. We show it for every project on this page so that its presence or absence is never read as a judgement about one of them.

AUTHOR-CLAIMED CAPABILITIES

  • According to the Mod author: shared crew actions for operating the platform.
  • According to the Mod author: shared artillery-computer range, bearing, shell, powder, and target-type inputs, plus generated mission cards.
  • According to the Mod author: an optional host-controlled shared record player; synchronization is off by default and each player keeps a local volume setting.
  • According to the 2.4.1 release notes: synchronized fire-control confirmation switches, gun-arming feedback, and Maptools Iris settings.
  • According to the Mod author: shared ammunition, charges, requisition, purchases, repositioning, reconnaissance resources, and player presence in a Steam lobby for up to five players.

LIMITATIONS TO READ FIRST

  • First-time mid-mission join for a new player is not supported; participants should join before the host starts the mission.
  • Reconnect/resync applies only to participants who were present when the mission started, and it may not completely restore consistent mission state. Version 2.4.1 also states that doors and hatches closed during a disconnect no longer remain open after rejoining.
  • Co-op mission checkpoints cannot be resumed. While the lobby is open, save and checkpoint interaction is disabled, and the mission starts from the beginning.
  • Record-player volume remains local even when the host enables shared playback.
  • High Command and Field Reports text uses the host language.
  • The Mod requires a third-party loader and changes local game files.
  • Compatibility may change after a game, Mod, or loader update.

SOURCE-CODE BOUNDARY

The Mod source code has not been published. GitHub provides documentation, Releases, and Issues; it is not a source-code repository.

KNOWN REPORTS

As checked at 2026-09-02T05:29:17Z, the public Issues tracker listed seven open entries: one item labelled bug (#11), two labelled potentially fixed (#9 and #15), and four feature requests or enhancements (#1, #12, #13, and #14). This time-bound label snapshot is not a quality, stability, or safety score, and report volume is not comparable between projects.

jagerIssues

MP-MOD-02 · UNOFFICIAL COMMUNITY PROJECT

Open Nest Co-op

Published by Tong317

Unofficial community mod
Observed version
0.2.0
Game version stated
GAME PATCH 1.0 (1663), according to the author’s page title
Platform last updated
2026-08-25
Last checked
2026-09-01
Author-claimed players
Not stated by the author
Connection
Steamworks P2P · host creates a room from the in-game Co-op menu, which opens a Steam lobby
Required loader
BepInEx 6 or MelonLoader 0.7.3 · the author states host and client do not need the same loader
Site testing
Not independently tested

PLATFORM SCAN FLAG

Safe to use NexusMods automated scan, as checked 2026-09-01

This is the hosting platform’s own automated result, quoted as it appears there. It is not a finding by this site and not a security audit. We show it for every project on this page so that its presence or absence is never read as a judgement about one of them.

AUTHOR-CLAIMED CAPABILITIES

  • According to the Mod author: shared crew actions across the turret, loading chain, and mechanical interactions.
  • According to the Mod author: a shared fire-control and ballistics workflow, while calculation sheets are deliberately not synchronized.
  • According to the 0.2.0 release notes: host-authoritative Nest position, entity types and positions, control-state fixes, network governance, lag simulation, and frame diagnostics.
  • According to the Mod author: shared tactical map, power and electricity state, ambient presence, lobby, P2P transport, roster, ping, and chat.

LIMITATIONS TO READ FIRST

  • Every player must install the exact same Mod version; according to the author, mismatched versions cause desync or connection failures.
  • The ballistic calculation sheets are not synchronized. The author states this is deliberate so that running the maths stays one crewmate’s job.
  • Compatibility with other Mods is not guaranteed; the author states conflicts may cause crashes, desync, or connection errors.
  • The Mod requires a third-party loader and changes local game files.
  • The game must be launched through Steam with the Steam client running.
  • Compatibility may change after a game, Mod, or loader update.
  • The author warns each installation to pick one loader: “Pick ONE loader — never install BepInEx and MelonLoader at the same time.” This applies to a single machine, not to the host-and-client combination.

SOURCE-CODE BOUNDARY

The author page states the source is published in a GitHub repository under a GNU AGPL v3.0 licence. This site has not compared that repository against the distributed files.

KNOWN REPORTS

As checked on 2026-09-01, the project’s Nexus Bugs section showed zero open reports. Its GitHub Issues tracker separately showed one open request for a LAN version. The two trackers measure different queues, and neither count is a quality, stability, or safety score or a basis for comparing projects.

openNestBugs openNestIssues

One further multiplayer-adjacent project, “VR. Co-op. PvP.”, is listed on the platform, but its page targets the Demo — its install steps tell you to right-click the demo, and it was last updated on 2026-07-01, before the 2026-08-06 full release. It is not covered here and gets no card, because a Demo-era project cannot show current full-release compatibility. See the mods guide co-op, VR and multiplayer section for it.

Loader installation, file locations, uninstall steps, and the full Mod directory stay on the mods guide. This page keeps only the multiplayer-specific decision facts. See the Co-op, VR and multiplayer section of the Iron Nest mods guide.

WHAT IS NOT CONFIRMED

EVIDENCE BOUNDARIES

OFFICIAL NOT ANNOUNCED

  • A release date or release window for base-game Multiplayer.
  • The player count, detailed rules, or test plan for base-game Multiplayer.
  • The standalone Co-op game’s formal title, target platforms, price, or exact date.
  • Whether the standalone Co-op game will be free.
  • Official endorsement or support for any current community Co-op Mod.

devFaq devlog2

COMMUNITY PROJECT NOT VERIFIED

  • Whether downloaded files are safe. A platform scan verdict is the platform’s automated result, not an audit by this site or by the developers.
  • Whether the Mod source code matches the distributed binary, including where an author publishes a repository.
  • Continuing compatibility with current or future game builds.
  • Whether every mission, synchronized feature, and reconnect scenario works as described.
  • Whether the current releases resolve every desynchronization report or synchronize every possible game state.
  • Support for a new player joining a mission for the first time after it has started.
  • Any comparison between the two listed projects. Their claims, limits, and report counts come from different authors and are not measured against each other here.

jagerNexus jagerReleases jagerGithub jagerIssues openNestNexus openNestReleases openNestGithub openNestBugs openNestIssues

“Not confirmed” describes the available evidence. It does not prove that a claim is false.

MULTIPLAYER FAQ

COMMON QUESTIONS

  1. Q01

    Is Iron Nest multiplayer?

    No, not in the current official build. Iron Nest: Heavy Turret Simulator is currently single-player. Future base-game Multiplayer is confirmed, but it is not available yet.

    devFaq steamStore launchAnnouncement

  2. Q02

    Will Iron Nest be multiplayer?

    Yes. The developers have confirmed future base-game Multiplayer with co-op missions and competitive modes, but they have not announced a release date.

    devFaq

  3. Q03

    Does Iron Nest have co-op?

    The current official build does not have native Co-op. Co-op missions are confirmed for future base-game Multiplayer, a separate shared-platform Co-op game is planned, and unofficial community Mods are available now.

    devFaq steamStore launchAnnouncement devlog2 jagerNexus jagerReleases openNestNexus openNestReleases

  4. Q04

    When is official multiplayer coming?

    The base-game Multiplayer date is TBA. The late 2027 / early 2028 rough window belongs only to the separate Co-op game, not to the base-game Multiplayer update.

    devFaq devlog2

  5. Q05

    Is official multiplayer a free update?

    The official commitment covers free base-game Multiplayer support. It does not establish the price of the separate Co-op game or every other future add-on.

    devFaq

  6. Q06

    Is the standalone co-op game the same as base-game multiplayer?

    No. Base-game Multiplayer is future support for Heavy Turret Simulator in which each player controls their own IRON NEST. The standalone Co-op game is a separate product in which multiple players share one platform.

    devFaq devlog2

  7. Q07

    Is the Iron Nest co-op mod official?

    No. Both listed projects are community Mods, not Multiplayer features developed, endorsed, or supported by the IRON NEST developers. This site has not independently tested either of them.

    devFaq steamStore launchAnnouncement jagerNexus jagerReleases openNestNexus openNestReleases

  8. Q08

    How many players does the Jager2251 co-op mod support?

    The Mod author claims support for up to five players per Steam lobby. This site has not independently tested that player count or every synchronized feature.

    jagerNexus

  9. Q09

    Can a new player join the mod in the middle of a mission?

    No, first-time mid-mission joining by a new player is not supported in the Jager2251 project. Version 2.2.0 adds reconnect and resync only for a participant who was present when the mission started, and complete state restoration is not guaranteed. The Tong317 project states different limits, listed on its own card.

    jagerNexus jagerReleases openNestNexus

  10. Q10

    Does Iron Nest have coop?

    Same answer as co-op — the spelling makes no difference. The current official build has no native co-op. Co-op missions are confirmed for future base-game Multiplayer, a separate shared-platform co-op game is planned, and unofficial community Mods are available now.

    devFaq steamStore launchAnnouncement devlog2 jagerNexus jagerReleases openNestNexus openNestReleases

  11. Q11

    How many co-op mods are there for Iron Nest?

    This page covers two unofficial co-op Mods that state support for the current full release: Jager2251’s Iron Nest co-op, and Tong317’s Open Nest Co-op. Their player counts, connection methods, and sync limits differ, so read each card rather than assuming they behave alike. A third multiplayer-adjacent project targets the Demo and is not covered here. For every other kind of Mod, see the mods guide.

    jagerNexus jagerReleases openNestNexus openNestReleases

SOURCES

EVIDENCE LEDGER

Product facts and community-project observations stay in separate ledgers. Local claim links jump here so the source class, access date, and caveat remain visible beside every external citation.

OFFICIAL SOURCES

  1. 01
    LAST ACCESSED
    2026-08-17

    ACCESS NOTEOfficial source identity, label, and URL are shared with the Roadmap evidence registry.

    CAVEATThe developer-maintained FAQ is the decisive source for current official Multiplayer scope and timing.

  2. 02
    LAST ACCESSED
    2026-08-17

    ACCESS NOTEOfficial source identity, label, and URL are shared with the Roadmap evidence registry.

    CAVEATThe official store listing corroborates the current build’s Single-player feature state; it does not define future Multiplayer scope.

  3. 03
    LAST ACCESSED
    2026-08-17

    ACCESS NOTEOfficial source identity, label, and URL are shared with the Roadmap evidence registry.

    CAVEATThe official launch announcement corroborates the released product context; future Multiplayer details come from the developer FAQ.

  4. 04
    LAST ACCESSED
    2026-08-17

    ACCESS NOTEOfficial source identity, label, and URL are shared with the Roadmap evidence registry.

    CAVEATThis official development log corroborates the separate shared-platform Co-op concept; the current developer FAQ controls if details conflict.

COMMUNITY PROJECT SOURCES

  1. 01
    PUBLISHED
    2026-08-03
    LAST ACCESSED
    2026-09-01
    VERSION CONTEXT
    Description observed at 2.4.0; Nexus Files and GitHub latest release both showed 2.4.1

    ACCESS NOTEThe accessible Nexus description was at 2.4.0 while Nexus Files and the author’s GitHub latest release both showed 2.4.1. Current version metadata therefore uses the two newer matching records; capability wording separates the 2.4.0 description from the 2.4.1 release-note additions. Read-only review; no Mod file was downloaded or executed.

    CAVEATThis author page supports attribution of project claims, not developer endorsement, download integrity, stability, or universal compatibility.

  2. 02
    LAST ACCESSED
    2026-09-01
    VERSION CONTEXT
    Repository documentation observed alongside Mod version 2.4.1

    CAVEATThe repository publishes documentation and project tracking, but not the Mod source code or an independent audit of distributed files.

  3. 03
    PUBLISHED
    2026-08-30
    LAST ACCESSED
    2026-09-01
    VERSION CONTEXT
    Latest observed release 2.4.1

    CAVEATRelease notes describe author-intended behavior and fixes; this site has not independently reproduced them or verified full state consistency.

  4. 04
    LAST ACCESSED
    2026-09-01
    VERSION CONTEXT
    Seven open non-PR entries observed at 2026-09-02T05:29:17Z

    ACCESS NOTEThe public tracker changes over time; follow the linked tracker for current status.

    CAVEATIssue reports show that individual reports exist. Their count is not a quality score, is not comparable between projects with different install bases, and does not prove that every user can reproduce them.

  5. 05
    PUBLISHED
    2026-08-11
    LAST ACCESSED
    2026-09-01
    VERSION CONTEXT
    Mod version 0.2.0 observed on 2026-09-01; page last updated 2026-08-25; page title states GAME PATCH 1.0 (1663)

    ACCESS NOTERead-only source review; no Mod file was downloaded or executed.

    CAVEATThis author page supports attribution of project claims, not developer endorsement, download integrity, stability, or universal compatibility.

  6. 06
    LAST ACCESSED
    2026-09-01
    VERSION CONTEXT
    Repository and GNU AGPL v3.0 licence observed alongside release 0.2.0

    ACCESS NOTERead-only repository review. This site has not compared its code against the distributed files.

    CAVEATA published repository shows the author states the source is available. It does not establish that the distributed binary was built from it, and it is not a security audit.

  7. 07
    PUBLISHED
    2026-08-25
    LAST ACCESSED
    2026-09-01
    VERSION CONTEXT
    Latest observed release v0.2.0

    CAVEATRelease notes describe author-intended behavior and changes; this site has not independently reproduced them or verified the distributed files.

  8. 08
    LAST ACCESSED
    2026-09-01
    VERSION CONTEXT
    One open LAN feature request observed at the community ecosystem recheck

    ACCESS NOTEThe public tracker changes over time; follow the linked tracker for current status.

    CAVEATA feature request is not a bug. The count is not a quality score and is not comparable with another project’s tracker.

  9. 09
    LAST ACCESSED
    2026-09-01
    VERSION CONTEXT
    Zero open reports shown on 2026-09-01

    ACCESS NOTEThe public tracker changes over time; follow the linked tracker for current status.

    CAVEATA report count is not a quality score, is not comparable between projects with different install bases, and does not prove that every user can reproduce the report.

CHANGE LOG

VERIFICATION HISTORY

  1. 2026-09-01 · MP-REC-004

    Rechecked both community co-op projects against their current Nexus and GitHub records. Jager2251 is now at 2.4.1 with expanded artillery-computer, record-player, fire-control, and Iris synchronization plus a no-checkpoint-resume boundary. Open Nest Co-op is now at 0.2.0 for game build 1663 with position and network-state changes. Both Nexus scan labels currently read “Safe to use”; those platform labels remain separate from this site’s testing and safety judgment.

    jagerNexus jagerReleases jagerGithub jagerIssues openNestNexus openNestReleases openNestGithub openNestBugs openNestIssues

  2. 2026-08-17 · MP-REC-003

    Rechecked the Jager2251 project. Version 2.2.1 and every author claim were unchanged, but the public Issues tracker moved from four open entries to six: three new bug reports were filed and the custom-music feature request was closed. Recorded the Nexus automated scan verdict for the project for the first time.

    jagerNexus jagerReleases jagerGithub jagerIssues

  3. 2026-08-17 · MP-REC-002

    Added a second community co-op card for Tong317’s Open Nest Co-op after an independent source audit, and began showing each project’s Nexus automated scan verdict beside its own observation date. The author states no player count for this project, so that field records the absence rather than borrowing the other project’s figure.

    openNestNexus openNestReleases openNestGithub openNestBugs openNestIssues

  4. 2026-08-11 · MP-REC-001

    Published the Multiplayer status page with the current official-plan evidence and the same-day Jager2251 version 2.2.1 source baseline.

    devFaq steamStore launchAnnouncement devlog2 jagerNexus jagerReleases jagerGithub jagerIssues openNestNexus openNestReleases openNestGithub openNestBugs openNestIssues