Qualified ammunition register
Ammunition
Check documented shell codes, visible roles, evidence dates, and current limits before transferring an ammunition choice to a firing card.
Use the ammunition database
This register is generated from the current validated snapshot, not copied from a competitor list. Every ammunition row must point to a current entity version and at least one retained source. Evidence labels describe what the source can support; they are not popularity scores and they do not make an unknown field true.
Open a record to inspect its factual fields, verification date, source locator, patch scope, aliases, and related field files. Missing values remain missing. If a record is single-source, conflicted, or stale, it moves to Community Radar and cannot create an indexable detail page or feed an operational calculator.
Ammunition records publish observed names, codes, and role descriptions that have direct support. Damage, radius, cost, unlock order, angle, charge, and range values remain absent unless a current-build source supports the exact field.
Current snapshot
6 qualified ammunition records
- Armor-piercing roundOfficial Ammunition
The official store describes armor-piercing rounds as the ammunition used to breach bunkers.
Also listed as: AP, AP shell
- Official role
- Bunker breaching
- Observed card code
- AP
- HCHE shellOfficial Ammunition
Official Steam screenshots show an HCHE firing card and a shell marked H.C.-H.E. with the nickname Love Letter.
Also listed as: H.C.-H.E., Love Letter
- Observed code
- HCHE
- Observed nickname
- Love Letter
- HE shellOfficial Ammunition
Official Steam screenshots show HE requisition cards and HE selected at the turret firing controls.
Also listed as: HE
- Observed code
- HE
- Phosgene gas shellOfficial Ammunition
The official store confirms phosgene gas as one of the game's specialized shell effects.
Also listed as: Phosgene gas
- Effect category
- Chemical gas
- Smoke roundOfficial Ammunition
The official store describes smoke ammunition as a way to screen friendly withdrawals.
Also listed as: Smoke, Smoke shell
- Official role
- Screen friendly withdrawals
- STAR shellOfficial Ammunition
An official Steam screenshot shows a requisition card labeled STAR shell.
Also listed as: STAR
- Observed code
- STAR
Operator method
Work with the ammunition register
Start from the objective you are trying to solve, then open the narrowest relevant ammunition record. Read the summary and qualified facts before following an alias, relation, or outside source. Keep the record name, verification date, snapshot checkpoint, and any current-client value on the same note. This makes it possible to tell which part came from the public ammunition database and which part you observed during the present session.
Use related records as a navigation graph, not as permission to invent missing mechanics. A mission can link to an achievement, ammunition can link to a target role, and a card can link to requisition only when the retained relation states that connection. Open both records and compare their individual evidence boundaries. If a required field appears on neither page, check the current client or leave it unknown instead of carrying a number across categories.
After an official patch, review the records touched by changed names, interfaces, rules, or content. Stable descriptive facts may remain useful, but source-scoped values need a fresh check before automation republishes them. If evidence becomes stale or contradictory, the public route must fail closed and the item moves to Radar. That maintenance rule lets this ammunition register grow without requiring manual approval for every unchanged record.
- Open one qualified record and identify the exact supported field.
- Follow explicit relations only when they answer the current task.
- Keep session observations separate from public database facts.
- Recheck build-sensitive values after a patch checkpoint changes.