What this loadout comparison means
The loadout tool is a source-qualified filter, not a simulation and not a tier list. It reads exact descriptive fields from published ammunition records. A bunker objective matches a shell only when its role explicitly mentions bunker breaching. A withdrawal objective matches only an explicit screening role. A chemical objective matches only a documented chemical effect category. Identification matches visible shell codes.
A returned loadout option means the selected field matches the selected objective. It does not mean the option is available in the current mission, affordable through requisition, safe for friendly forces, or stronger than every alternative. The loadout result prints the exact field so you can see why it appeared.
Why there is no universal best loadout
A universal best loadout would require comparable current data for damage, radius, penetration, availability, cost, reload behavior, mission restrictions, target state, and player intent. The qualified snapshot does not contain that complete matrix. Ranking incomplete fields would turn missing data into an invisible assumption.
The loadout tool therefore makes a smaller claim. It places options with an exact matched field into the result and sorts them deterministically. It does not attach a score, win rate, or best badge. If more than one shell eventually matches, inspect every source and decide with the current mission briefing.
Use the bunker loadout reference
The bunker objective currently points to the documented armor-piercing role. That loadout result is useful when a briefing identifies a bunker and the shell is available. It is not proof of a specific penetration value, number of shots, target health, or firing solution. Those facts remain absent unless a current source qualifies them.
Open the ammunition detail from the loadout result, then check the current shell card inside IRON NEST. Use the firing planner for target geometry. Use the current game calculator for charge and elevation when the public firing table is empty.
Use the withdrawal screen reference
The withdrawal objective matches the documented smoke role that screens friendly withdrawals. The loadout tool repeats that role without expanding it into unsupported radius, duration, wind behavior, or enemy response. A role describes intended use, not a complete tactical rule.
Confirm that the mission actually calls for a withdrawal and that friendly positions are understood. The loadout page cannot observe current battlefield state. It gives you a sourced option to inspect, not authority to ignore the briefing.
Use the chemical effect reference
The chemical objective matches a record whose effect category is chemical gas. The loadout comparison does not infer damage, area, duration, protection, legality, or target susceptibility. Those missing fields are important, so they stay visibly outside the result.
Treat this loadout reference as an identification aid. Read current tooltips and mission constraints before selection. If current text conflicts with the public record, use the source ledger to report the discrepancy rather than trusting a stale loadout assumption.
Use visible shell codes carefully
The identification objective lists records with a visible observed code. A code helps match a screen label to an ammunition record. It does not describe effect or recommend selection. HCHE, HE, STAR, and AP can appear because the public evidence shows those codes, not because the loadout tool considers them equivalent.
Nicknames are also descriptive. Do not use a nickname as a substitute for a current code when entering a firing card. The loadout tool keeps name, matched field, evidence label, date, detail link, and source together to reduce ambiguity.
Punchcards and requisition remain separate
The current qualified punchcard record confirms visible ammunition and powder-charge card types plus a card slot. It does not publish complete unlock costs, drop rates, optimal combinations, or a universal punchcard loadout. This tool does not manufacture those missing comparisons.
Use the punchcard register and requisition register to inspect confirmed scope. Then confirm your current inventory in the game. Player inventory is not stored by this loadout page.
Loadout evidence, privacy, and updates
The loadout comparison runs from data embedded in the static page. Objective selections stay in the browser and are not sent to analytics or Neon. The page stores no loadout state. Reload returns to the first objective. A normalized page view, when approved and enabled, contains only path and title.
Official or current-observed records can publish automatically after source and release gates. Independently corroborated community descriptive fields can publish with a cross-verified label, but ballistic numbers require stricter current evidence. Candidate, single-source, conflicted, and stale fields remain in Radar and never drive this loadout result.