Regional Progression and Objectives

IRON NEST’s current official feature list describes a campaign with several layers at once: a handcrafted story, procedurally generated objectives, 15 regions, more than 100 unlockable medals, two challenge modes and leaderboards, plus a combined count of 30 ammunition types and abilities. This is a substantial framework, but it is not a published walkthrough of what unlocks where.

The most accurate way to read these features is as distinct promises that may intersect without being identical. Regions describe campaign breadth. Story describes authored narrative content. Procedural objectives describe repeatable or generated task structure. Medals and ammunition/ability systems describe progression scale. The reviewed sources do not give a table mapping every region to a chapter, objective type, medal, shell, ability, challenge, leaderboard, or unlock condition.

That distinction is the difference between a useful campaign reference and a speculative guide. This page explains what the official wording establishes, what it leaves open, and how players can record discoveries without turning a partial playthrough into a false universal route.

The confirmed pieces of the campaign structure

The phrase 15 regions confirms that the campaign is geographically or operationally broader than one location. It does not supply the names, order or rules of those regions in the public sources reviewed by this project. See 15 regions: official evidence for the evidence boundary.

The phrase handcrafted story confirms authored narrative content. It is reasonable to expect deliberate writing, framing and story beats. It is not evidence that every mission has one fixed outcome, that every location is visited once, or that every story chapter corresponds one-to-one with a region.

The phrase procedurally generated objectives confirms generated objective content. It does not disclose the generator’s pool, constraints, seed behavior, difficulty curve, recurrence rules or relationship to story missions. A procedural objective may share a region with authored material, but the public wording does not state exactly how such sharing works.

The feature list also advertises more than 100 unlockable medals and 30 ammunition types and abilities in combined wording. It does not divide that combined number into separate exact counts, list unlock requirements, or say which items belong to which region. The abilities and progression reference documents this wording and its limits.

Do not turn a campaign scale into a sequence

A frequent guide-writing mistake is to arrange a set of expected areas into an implied route: coastal opening, mountain middle, capital climax, industrial finale, and so on. That is attractive because it gives a campaign a familiar dramatic shape. It is not supported by the 15-region count alone.

An unlock sequence requires direct evidence. Acceptable evidence might be a current build’s region-selection screen, an explicit completed/locked state, a first-party patch note, a mission chain shown in official documentation, or a repeatable observation with clear prerequisites. A single player’s order can be affected by choices, mode, prior completion, profile state, a patch, or simply misread UI.

Until that evidence exists, use neutral language: “the campaign includes 15 regions,” “this mission displayed this name,” or “this objective appeared in this observed context.” Avoid “first,” “later,” “final,” “unlock,” “required,” and “exclusive” unless the source actually demonstrates them.

Story missions and procedural objectives

The official listing deliberately presents handcrafted story and procedural objectives together, so neither should erase the other in a guide. Story content may provide the campaign’s authored stakes and setting; procedural content may supply variation, replayability or ongoing operational tasks. The sources do not set a public boundary that lets this wiki label every individual mission ahead of observation.

When documenting a mission, record its own signals. Does the game label it as story, challenge, objective, operation, task, contract, or something else? Is there a named character, fixed briefing, continuation prompt, repeat option, score, leaderboards, medal notification, or randomized target setup? Record the visible language rather than translating it into a genre assumption.

The pre-release developer Q&A discussed multi-stage mission ideas. That is useful context for the team’s design thinking, but the interview predates launch. It cannot prove the current number of stages, trigger conditions, or finale structure. Current version 1.0 behavior and current official pages take priority.

Progression: record the trigger, not the theory

Medals, ammunition and abilities invite theories about how a player should progress through regions. The released feature list confirms their scale, not their specific gates. A medal icon after a mission might be associated with score, completion, a hidden objective, a story milestone, a mode, or another condition. A newly available card or ability might be tied to a tutorial, mission outcome, profile level, regional transition, or update.

To document a progression event responsibly, capture the before state, the exact activity, objective result, after state, displayed notification, build version, and any explicit condition. Repeat where practical. If the event happens only once in an authored mission, label it as a witnessed story-context event rather than a general unlock formula.

Do not use the combined “30 ammunition types and abilities” figure to claim 30 shell pages or a separate ability total. Do not assign AP, smoke, phosgene, STAR, HCHE or the pre-release card labels to a particular region unless the game itself does so. The ammunition evidence status page explains why visible labels and current product wording support different levels of detail.

A useful campaign journal

Players can build a high-confidence regional journal with a small, repeatable template:

1. Copy the exact displayed region or mission label; do not replace it with a guessed real place.
2. Note build version, save/profile context, date and mode.
3. Mark whether the game itself identifies the content as story, procedural, challenge or another category.
4. Preserve the objective text, teleprinter reports and map state separately.
5. Record outcome, medals, scoring, unlock notice or leaderboard prompt exactly as shown.
6. Distinguish a visible observation from a repeated test and from an interpretation.
7. Link every proposed regional page to its direct source or current-build record.
8. Leave unknown sequence and prerequisite fields blank rather than filling them with a likely route.

This journal benefits ordinary play too. It makes it easier to compare how objectives behave over time, diagnose why a medal did or did not appear, and tell whether a later result reflects a changed region, a changed mission type, or a changed player setup.

How regions can still matter without a published chart

The lack of a public chart does not mean regions are decorative. It means the specific relation needs evidence. A region may supply narrative context, mission framing, visual identity, a map position, an objective pool, an unlock gate, or a combination of these. The official count tells us that campaign geography is part of the game’s intended scope; the map and briefing workflow tell us that local operational context matters.

The proper response is to observe the connection at the point it becomes visible. If an objective menu visibly filters by an exact region, document that filter. If a medal description names a place, cite the text. If an ability is awarded after a named mission, capture both states and do not claim the mission is universally required until repeated or explicitly stated. If a visual terrain context changes no displayed variable, write it as scenery rather than a mechanical modifier.

This restraint keeps future pages easy to update. New evidence can add a precise relation without having to unwind a web of confident but unsupported prerequisites.

The dependable conclusion

IRON NEST officially promises 15 regions, a handcrafted story, procedurally generated objectives, more than 100 medals and a combined 30 ammunition types and abilities. These are complementary campaign-scale facts. They do not form a publicly documented region-by-region unlock chart.

Use exact on-screen labels and before-and-after records to document missions, rewards and progression. Keep current-build evidence ahead of pre-release design discussion, and keep a named region, an objective, a medal and an ability as separate claims until the game or developer explicitly connects them. That approach gives players a campaign guide that grows with verified discoveries instead of outrunning them.