What qualifies for this firing table
A firing table row is operational only when one current ammunition version supplies range, charge, and elevation together. Each firing table value must be numeric, carry an explicit unit, use the ballistic risk class, and be marked tool safe. The entity must be published, active, and backed by official or repeatable current-client evidence. Its build must equal the snapshot build. A supporting source must remain attached to the same version.
The firing table rejects partial evidence. A verified shell name does not qualify its old elevation screenshot. A current range does not qualify a charge copied from another build. Two community reposts do not become independent sources. Engagement does not raise confidence. If one required field fails, the firing table emits no row.
Why an empty firing table is useful
An empty firing table communicates a precise boundary: the site knows documented ammunition names and roles, but it does not have safe current ballistic numbers. That distinction protects a player from transferring a precise-looking value whose unit, range, or build is unknown. The table does not fill gaps with interpolation or a generic projectile formula because IRON NEST can implement its own game model.
The firing table remains functional while empty. It displays the current snapshot, the required fields, the reason for withholding, a link to map geometry, and a print action. When a future source passes the gate, the same firing table template can publish it automatically after tests. No manual page rewrite is needed.
Read every firing table column
The Shell column identifies the qualified ammunition entity and links to its evidence page. Range displays the exact input point and unit. Charge displays the exact position or other named convention from the source. Elevation displays the exact angle and unit. Evidence identifies authority, build, and verification date. Source links to the material used for that row.
Do not detach a number from its row. A firing table value is meaningful only with shell, range, build, and units. If you copy a row to paper, print the whole table or write all fields. Recheck the current game whenever a patch changes aiming, ammunition, interface labels, or progression.
No interpolation between firing table rows
The calculator looks for an exact qualified range. It does not draw a curve between two firing table rows, and it does not extend a row beyond its observed point. Interpolation would be a new ballistic claim, not a neutral formatting choice. That claim needs its own current-client validation and repeatability evidence before the firing table can expose it.
If the requested range has no exact firing table row, use the current game calculator. You may still calculate target geometry and convert the resulting bearing. Keep the game-derived charge and elevation on a private firing card. The absence of a row is not evidence that the shot is impossible; it is evidence that this public table cannot support the value.
Print the firing table safely
The print action opens the browser print dialog. Navigation, long guidance, and decorative controls are removed from the print layout. Qualified rows retain shell, range, charge, elevation, build, date, and source. The site does not create a server-side document and does not upload what you print.
Before relying on a printed firing table later, check its build against the updates ledger. Printed data cannot update itself. Replace the sheet when the current game build changes or when a source is superseded.
How new firing table evidence arrives
The scheduled content workflow checks official patch notes, store material, developer statements, and qualified current-client observations. Candidate values enter the evidence store with source locator, origin, captured time, game build, unit, and conflict state. A field can be published only after the evidence resolver accepts it. Ballistic fields require the strictest class.
The firing table generator reads the validated snapshot, not a competitor page. Competitors can identify a candidate to investigate, but their value does not enter this table. The source ledger remains the audit trail, and prior versions stay in Neon for rollback rather than being silently overwritten.
Use the right neighboring tool
Open the ballistics calculator to calculate map range and bearing, then ask whether an exact firing table row exists. Open the mils converter when a known bearing must move between named conventions. Open the loadout comparison for documented shell roles. None of those tools turns a missing firing row into a guessed one.
For raw entity evidence, use the ammunition register and source ledger. For unresolved claims, use Community Radar. Radar records are excluded from this firing table, from operational results, and from the sitemap.
Run a final transfer check
Before moving any published row into the turret, compare the selected shell name, displayed range, active build, and interface units. Confirm that the target geometry came from the Nest rather than a spotter origin. Read the current mission briefing for restrictions and required effects. If one label differs, stop and use the live game value.
After the shot, preserve the complete firing card and observation. A miss can come from source report, coordinate entry, direction convention, shell choice, game controls, or transfer. Changing one value at a time makes the error traceable. A local observation helps your next shot, but it does not modify public data or bypass the evidence gate.