Why shots miss

Freeze the shot state first

When a shot misses, do not immediately move the controls. Record the exact shell, charge, bearing, elevation, target label, and plotted range that produced the shot. Then record the reconnaissance result in neutral terms: shot short, shot long, shot left, shot right, shot centered with wrong effect, or shot not observed. Preserving the shot state prevents a correction from erasing the evidence needed to diagnose the original miss.

A missed shot can originate at several layers: source report, coordinate transcription, map convention, target projection, Nest vector, game calculator entry, shell selection, firing card transfer, turret control, or result interpretation. The fastest diagnosis follows that chain from earliest to latest. Randomly adjusting elevation after every missed shot may hide a bearing mistake or wrong origin. A shot ladder makes the failure small enough to inspect and ensures each correction has a stated reason.

1. Check the shot source report

Return to the report that defined the target. Was the coordinate copied with the correct sign and decimal position? Did the bearing come from the Nest or from a spotter? Did the distance describe spotter-to-target or Nest-to-target? Was the target label associated with the right mission objective? One wrong source field can place a shot far away while every later calculation remains internally consistent.

Read the report fresh instead of comparing it only with your note. If a spotter is involved, keep spotter position, spotter bearing, and spotter distance in their own row. Project the target from that origin. Only then compute the shot bearing and range from the Nest. A large directional miss or an impact on the opposite side of the map strongly justifies this source audit before any small control correction.

1. Compare every copied value with the current report.
2. Label the origin for every bearing and distance.
3. Confirm the target belongs to the active objective.
4. Rebuild the shot plot if any source field changes.

2. Check the shot plot and conventions

Inspect north, X direction, Y direction, angle origin, and rotation direction. This site uses bearing clockwise from north. A mathematical angle measured counterclockwise from east will produce a different target even when the number is identical. Check cardinal directions: a shot bearing near ninety should point east, and a shot bearing near two hundred seventy should point west. If the plot violates that simple check, fix the convention before firing again.

Confirm the current Nest position rather than assuming the center of a grid. A community guide warns that the Nest position may require calibration, so the current session map is the working authority for a private shot. Inspect swapped X and Y values and transposed digits. Then draw or view the Nest, spotter, and target together. A shot plot should explain where each vector begins and ends. If it cannot, it is not ready for a firing card.

3. Check the shot calculator pass

Verify that the range entered into the game calculator is the range from the Nest to the target, not a spotter distance or a previous target range. Confirm that shell and charge belong to the same calculation and that elevation was copied from the resulting current interface. Public manual formulas conflict, so this release does not use a community formula to override the game calculator. A plausible number is not proof that the correct shot inputs were used.

Repeat the calculator pass from the preserved target range and shell selection. Write the new charge and elevation on a new shot row. If the values match the original, keep investigating. If they differ, identify which input differed instead of merely replacing the result. A diagnostic shot should teach you why the first shot missed. The developer evidence in the current ledger states that wind is not part of the discussed firing problem, so do not add wind as an unsupported hidden variable.

4. Check shot transfer at the turret

Compare the preserved firing card with the control displays. Confirm shell label, charge, bearing, and elevation one by one. Look for a previous shot value that remained on a control, a digit entered in the wrong place, a bearing rounded too early, or a charge changed after elevation was calculated. When the interface allows it, read each displayed value back before the next shot. Transfer errors are ordinary and should be diagnosed without inventing a deeper ballistic explanation.

If an interruption occurred during transfer, rebuild the entire shot state from the card. Do not continue from memory. If the next shot uses corrected controls, keep target geometry and shell stable unless evidence also requires those changes. One changed category makes the result interpretable. If several controls are changed together, a successful shot does not reveal which correction mattered and a missed shot does not reveal which change failed.

• Displayed shell matches the written shot shell.
• Displayed charge matches the calculator row.
• Displayed bearing is the Nest bearing.
• Displayed elevation matches the same shell and charge pass.

5. Classify the shot pattern

A huge miss suggests a source, origin, convention, coordinate, or gross transfer error. A consistent left or right miss suggests a directional issue after the major checks pass. A consistent short or long miss suggests range, charge, elevation, or their transfer. A centered impact with no required effect suggests shell role. An unobserved shot does not support a correction until mission state, target selection, reconnaissance timing, and visibility are checked.

Use pattern language carefully. One shot is one observation. Two comparable shots may show direction, but only if their target geometry, shell, charge, and transfer are documented. Do not fire a sequence of undocumented corrections and then infer a rule from the final hit. Preserve each shot row and state the single reason for the next change. The correction should move the impact in a predicted direction. If it does not, step back up the ladder.

6. Apply the smallest shot correction

For a directional shot error, first verify source and convention, then inspect target bearing and turret bearing. For a range shot error, first verify coordinates and Nest range, then inspect calculator inputs, charge, and elevation. For an effect error, verify impact location before changing shell. For an unknown result, do not change a numeric value without new evidence. This decision order limits the number of possible causes at each step.

Write the correction before touching controls: 'Change bearing from A to B because the observed shot was right and the source plot is verified.' After transfer, compare the displayed state with the new row and fire once. Record the result. If the shot moves as predicted but remains off, a second measured correction may be justified. If the shot moves unexpectedly, return to the earliest layer that was assumed rather than verified.

Separate a shot error from a software issue

Patch 1.0 build 1558 fixed several turret-related and other issues, which shows that software behavior can affect an operator session. If controls do not respond as expected, state resets, or behavior contradicts a reproducible procedure, check the current patch notes and restart only according to safe game practice. Keep a software symptom separate from a normal missed shot. Record build, mission, action sequence, expected behavior, and observed behavior before seeking support.

Do not label an unexplained shot as a bug simply because the calculation looked correct. First complete the source, plot, calculator, and transfer checks. If the same verified shot state produces inconsistent behavior under repeatable conditions, collect evidence and consult official channels. The sources page links the current official store, news feed, and developer discussion used by this release. Community reports can identify demand, but they do not prove the cause of your individual shot.