WARDOGS L81 mortar workflow

Confirm current controls and Season 02 supply rebalancing

The linked community guide describes Beta-era operation. Official Season 02 notes change construction speed, build costs and ammunition resupply; these are separate costs, and not every structure became more expensive to build. Recheck the active build, input prompts and supply requirements before spending FOB supplies.

Set up a ranging shot

Reported workflow: hover a spotted map target for distance, mark it, align the mortar with that direction, match the displayed range and fire one round. Have an observer confirm the impact before continuing. Season 02 rain affects spotting range, so rely on what the observer can actually confirm.

Before the test round, agree on one observer and a clear target marker. Example call: “One ranging round; report short or long, then left or right.” The observer should describe the impact relative to that marker rather than an unmarked moving enemy.

Correct range and bearing separately

Example call: “short, but aligned.” Change range first, then observe again. “Left, correct distance” calls for a bearing correction. These are communication examples, not a measured aiming formula. Stop when the target moves or observation is lost.

Worked communication example: the observer reports “short, aligned.” Keep the bearing, adjust the displayed range, and fire one more observed round. If the next report is “range correct, left,” retain the range and correct bearing. No fixed elevation or distance increment is implied by this example.

Check a no-ammo prompt

Read the exact message. Community reports associate the L81 with Ammo Supplies in its FOB, and Season 02 changed mortar resupply demands. Inspect the relevant inventory and ask logistics to verify the stock. Distinguish a restock requirement from an assumed per-shot cost.

If supplies appear present but the prompt remains, record the exact warning, mortar location, relevant FOB inventory and current build. Avoid guessing a per-shot cost from an old guide; the source evidence does not establish one for the active build.

Keep a useful test record

Record your client build, input device, map, marked distance, chosen range, first impact and supply state. If an old guide disagrees with the current prompt, retain that evidence and use the active client instructions.