Targeting & Artillery

IRON NEST Shell Types: Verified Source Scope

A source-filtered answer on published ammunition totals and the shell names, effects, statistics, and loadouts not confirmed by first-party material.

iron nest shell types has one confirmed high-level answer: the official product page lists 30 ammunition types and 20 abilities. The accepted material does not publish a named shell list, effects, damage, range, statistics, or a recommended loadout. The demo description also refers to 30 unlockable ammunition types and abilities, without supplying a detailed shell catalogue. Every specific shell claim is Pending confirmation.

The direct shell-types answer

The published total confirms that ammunition variety is part of the game's stated scope. It does not identify which ammunition entries are shells, how they are named, or how they behave. A list copied from discussion, footage, or a search result cannot be treated as official documentation without direct support. Names and effects remain Pending confirmation.

What the product page confirms

Official product material lists 30 ammunition types and 20 abilities. This is a useful boundary because it confirms content scale without inviting invented details. It does not provide a table of ammunition properties or say how each type is selected. Any claim about an individual item's value or use is Pending confirmation.

What the demo description adds

The official demo description refers to 30 unlockable ammunition types and abilities. That wording supports public confirmation that unlockable ammunition-and-ability content exists in the demo presentation. It does not provide the names, unlock conditions, item effects, or a split between specific categories. Those details are Pending confirmation.

Manual artillery is separate evidence

Official descriptions also present a heavy-artillery simulation with coordinates, map measurements, large mechanisms, and manual cannon aiming. This confirms the broader setting in which ammunition appears. It does not explain a shell-selection interface or connect a named ammunition type to a target outcome. Loadouts, handling rules, and firing results remain Pending confirmation.

Statistics cannot be reconstructed

No accepted material here supports damage values, range values, trajectory figures, capacity, or comparison charts for shell types. Filling a table with plausible numbers would be fabrication even if it looks useful. The same is true for claims about a best shell, a required shell, or a shell that solves a particular situation. Every numerical or performance statement is Pending confirmation.

Keep names and effects unverified

This page does not assign names to the 30 published ammunition types or infer effects from their total. It also does not convert abilities into shell modifiers or assert how either category unlocks. A player can keep an observation as an observation, but it should not become a source-filtered fact by itself. Direct official material is required before any item-level entry can be added.

How to use this status page

Use the confirmed totals to understand the published scope, then leave individual shell facts blank until a first-party source names them. This keeps a future catalogue easier to verify and prevents a fabricated list from spreading through the site. It also preserves the difference between what the product page says and what a reader expects it to mean. At present, shell names, effects, statistics, and loadouts are Pending confirmation.

Readers can keep a screenshot or personal note as a dated observation while waiting for a direct catalogue. The observation should not be promoted into a named ammunition entry, a numerical value, or a recommendation. Separating those records makes a future official list easier to compare and correct.

Archive notes

Frequently asked questions

How should I use a field guide?
Treat it as a procedure: carry one confirmed value to the next station and mark every assumption.
What should I do when the current interface differs?
Preserve the visible difference, then rebuild the affected part of the solution instead of copying an old setting.
  • Pending confirmation