PUBG mortar targeting: estimate, observe, and adjust

Turn an uncertain mortar attempt into a repeatable estimation and review process.

Start with a current-build verification gate

Prevent an estimation workflow from depending on unsupported or outdated mechanics.

• Check the current game interface and captured official guidance before using any exact control, range, or map-scale value.
• Separate confirmed information from remembered values and community suggestions.
• Pause the attempt when its required mechanic cannot be verified.

Define the target and record the starting estimate

Create a baseline that the squad can review after the first attempt.

• Mark the firing position and intended target clearly.
• Record where the distance estimate came from and how uncertain it is.
• Preserve the initial direction and distance inputs before making a correction.

Handle diagonal positioning without inventing a grid scale

Explain the geometry decision while keeping game-specific dimensions conditional.

• Consider both horizontal and vertical separation when the positions are diagonal.
• Apply diagonal geometry only when the current map scale has been verified.
• Use a rough label rather than presenting an unsupported estimate as exact.

Use the first observable result as calibration

Turn the initial attempt into evidence for one bounded correction.

• Arrange observation before committing to the attempt.
• Classify the result as short, long, off-line, or uncertain only when the landing information is visible enough to support that label.
• Change one relevant input while holding the others constant.

Review the correction loop

Help players distinguish a useful adjustment from an unrepeatable guess.

• Compare the new result with the recorded baseline.
• Reverse the change when the evidence becomes less clear.
• Stop when observation, target information, or current-build verification is insufficient.

Recheck after PUBG updates

Keep the page useful without asserting that a listed update changed mortar behavior.

• Review authoritative patch information before retaining precise mortar notes.
• Retest only the assumptions affected by documented changes.
• Keep the estimation framework while removing values that can no longer be verified.

Decision checklist

• Verify current-build controls and any displayed range information.
• Mark the firing position and intended target.
• Record the source and uncertainty of the distance estimate.
• Account for both axes when using a verified map scale for a diagonal estimate.
• Save the initial direction and distance inputs.
• Change only one input after an observable result.

Worked example

A squad marks a target that is separated from the firing position along both map axes. Because the closed evidence supplies no verified grid dimension or mortar range, the squad does not insert a copied conversion. It first checks whether the current build provides a usable scale, then includes both axes in a diagonal estimate and records that estimate as the baseline. One teammate watches the result. If the result is clearly short while its direction remains suitable, the next attempt changes only the distance input. If the result cannot be observed, the squad makes no numerical correction from that attempt.

Common mistakes

• Copying a precise grid conversion without current verification.
• Treating one axis as the complete distance to a diagonal target.
• Changing direction and distance in the same correction.
• Using an unobserved result as evidence for an adjustment.
• Turning one successful attempt into a universal recommendation.

Related guides