IRON NEST Arsenal Database

This IRON NEST: Heavy Turret Simulator Arsenal Database is a fast decision index, not an invented stats wiki. It lists public names and roles that can be supported now, links each family to the detailed canonical guide, and marks changing fields such as requisition cost, unlock, radius, duration, and mission availability as check in game.

Shell and effect index

“Experimental shells” appear in official promotional language as a broad possibility, but an unnamed teaser is not an entity record. Add a new row only when the current public game or developer source supplies an exact name.

Recon and movement ability index

Choose by the required effect

Start with the verb in the dispatch. “Destroy” points toward a destructive match, “penetrate” toward protection/armor logic, “illuminate” toward star ammunition, “screen” toward smoke, and an information problem toward recon. Chemical or leaflet names do not mean “more powerful”; they answer different objectives.

Then check target, friendly positions, available stock, cost, and the operation’s current stage. A correct shell at the wrong target or wrong time is still a failed solution. Use Target Matching for the decision process and Requisition for resource planning.

Loading and unload status

Before committing a shell, verify the barrel, exact label, powder count, and firing card. Current community discussion indicates that players need an unload solution, but public evidence does not support one universal safe unload sequence for every mechanical state. If a wrong shell is already committed, stop adding powder, read current prompts, and decide between recalculating for the actual load and a supported restart.

The database therefore does not include a fictional “unloadable: yes” field. The canonical Loading guide owns wrong-load prevention and recovery. Exact reversible states still require hands-on testing in the latest build.

What “check in game” means

A current inventory observation should record exact label, category, displayed description, locked/available state, requisition cost, mode, mission, objective stage, patch, activation or loading steps, and visible result. Record a separate row when one of those context fields changes.

Do not fill gaps with zero, “common,” an old Demo value, or a third-party calculator assumption. The Demo is AppID 4300500 and the Playtest/Beta is 4300490; neither silently updates the base-game database.

Database status and next measurements

The entity names above are useful for lookup, but the following fields remain test-required: AP versus APHE/HCHE exact current naming; shell radii and durations; flight behavior per shell; requisition prices; unlock source; mode and mission restrictions; ability coverage and cooldown; whether movement clears enemy tracking; and exact wrong-load recovery states.

When enough repeated samples exist, add versioned detail rows rather than overwriting history. Every numerical record should contain AppID, official patch title, mode, mission, item, sample count, and source screenshot or video.

Sources

• Developer FAQ
• Official Steam Store page
• Official Steam announcements
• Current Steam Community guides