Official and developer sources
IRON NEST Steam Store
Current product listing, platform categories, purchase terms, developer and publisher names, and the Store's demo entry. Price and labels can change.
Open source
IRON NEST Demo on Steam
Official standalone Demo listing for app 4300500. Use it to open or install the current Steam demo.
Open sourceDeveloper Frequently Asked Questions
Developer-authored and maintained answers about release status, mission modes, scoring, platforms, multiplayer, Workshop consideration, and other plans. Read the update date and original wording.
Open sourceSteam News and Announcements
Dated developer patch notes, launch posts, devlogs, and status announcements. Use a specific post, title, and date when supporting a claim.
Open sourceOfficial IRON NEST Linktree
Developer-operated directory for current Steam, Discord, YouTube, and social destinations. It helps establish destination identity but does not make this Field Manual official.
Open sourceOfficial YouTube channel
Developer video destination identified through the official Linktree. Use video identity and title carefully; do not derive precise controls or mechanics from unreviewed visual frames.
Open sourceA destination can be official while a particular claim still needs a more specific source. The Linktree establishes an identity chain; a dated Steam patch post establishes what that patch listed. Prefer the page closest to the fact being stated.
Community destinations
Reports, Feedback & Localization Hub
Developer-linked Steam hub for reports, feedback, and localization. It is an official reporting destination, but individual user reports are not confirmed causes or fixes.
Open sourceSteam Discussions index
General community conversation, questions, and player reports. Ordinary threads do not support factual claims unless a specific developer-authored or pinned statement supplies the claim.
Open sourceOfficial Discord destination
Community server linked by developer sources for announcements, discussion, localization participation, and described leaderboard commands. Channel structure and invitations can change.
Open sourceThe reporting hub and Discord are useful places to provide context to the developer or talk with other players. They are not automatic evidence that every report is reproducible. Keep “someone reported this” separate from “the developer listed this as fixed.”
How official and community source roles differ
| Destination type | Good use | Not enough for |
|---|---|---|
| Live Steam Store or API | Current listing metadata at a stated check date | Permanent price or an unannounced future feature |
| Developer FAQ | Developer statements and plans with its update date | Claiming every future plan is already available |
| Specific Steam News post | Patch, launch, devlog, or dated platform statement | Guaranteeing that this site reproduced the result |
| Developer report hub | Submitting evidence and finding developer instructions | Treating every community symptom as confirmed |
| General Discussions | Conversation and discovery | Supporting ordinary gameplay facts without a developer-authored source |
The distinction protects both readers and contributors. Community reports can reveal questions worth investigating, while first-party pages establish the bounded public statement.
Identity and date checks
- Start from the Steam Store or official Linktree when identifying a developer-operated destination.
- For a factual claim, open the specific FAQ answer, patch post, announcement, or Store field rather than citing a directory homepage.
- Record the official publication or update date and the date you checked it.
- For volatile data such as price, platform labels, invitations, and forms, recheck the live destination.
- If an ordinary discussion conflicts with a developer post, do not silently promote the discussion to official status.
This directory was checked August 10, 2026. External URLs can move, invitations can expire, and Store metadata can change. The labels explain the reviewed role of each destination; they are not a promise that every external page will remain unchanged.
