Counter an armored push without burning the squad budget

Before you start

• A current anti-vehicle option your account can actually equip.
• A squad member who can spot the vehicle and a route that does not abandon the objective.
• A reserve that covers the counter kit without consuming the entire next deployment.

Classify the pressure before buying

A Humvee, logistics truck, tank, artillery vehicle and armed helicopter create different problems. Current Steam comments describe protected Humvee and APC windows, while Reddit discussions disagree about how much small-arms fire, AP ammunition or explosive damage different vehicles need. Treat the vehicle name, variant and position as evidence you must record, not as a shortcut to a fixed damage number.

1. Read the vehicle silhouette and variant before opening the vendor.
2. Ask whether the threat is blocking the objective, the supply route or only a rotation.
3. Mark a fallback position so the counter team is not trapped beside the target.

Choose one layered answer

Community players currently mention MAAWS, RPGs, C4, mines and Stingrays as armor answers. Those are player-tested ideas, not a complete counter table. Pick the option your squad can use now, then add a second layer only when the target or terrain demands it.

1. Choose a direct explosive or launcher option if the target must be stopped immediately.
2. Use mines or a Stingray when the route and setup time make a prepared counter possible.
3. Carry medical or recovery utility so the counter player can stay useful after the first attempt.
4. Keep enough cash for the next life instead of buying every option at once.

Stage a reserve without trusting an old cargo claim

Recent comments describe placing launchers and rockets in vehicle inventory or crates near an FOB, but the replies disagree about what fits and how long items remain available. Inspect the current container and confirm that the receiver can retrieve the exact item before treating a reserve as ready.

1. Name the receiving FOB and the person responsible for the reserve.
2. Deliver one known item first and confirm the visible inventory changed.
3. Record the vehicle, container, launcher and ammunition labels used.
4. Do not publish a slot count from a single comment as a general rule.

Commit from a useful angle

A counter only helps when it creates time for the rest of the squad. Attack from cover, coordinate the shot and keep one player watching the objective or escape route. Current discussions report both one-shot track damage and multi-shot failures, so use the first attempt to gather a result rather than to prove a theory.

1. Spot the vehicle and call its direction, variant and movement.
2. Synchronize the shot or placement with the squad.
3. Record hit location, ammunition, range and whether the vehicle stopped, escaped or was destroyed.
4. Leave if the attempt costs more than the objective is worth.

Turn a match into better evidence

The useful report is a compact test record: current build, vehicle variant, weapon, ammunition, hit location, range, number of attempts and result. Conflicting reports are a reason to collect better observations, not a reason to publish the most confident comment.

1. Save the match time or screenshot if it does not expose private information.
2. Compare only like-for-like tests: same vehicle variant, hit location and ammunition.
3. Update the squad’s next purchase from repeated results, not one dramatic kill.
4. Send unresolved bugs through the official report channel.

Common problems

• One comment saying “one rocket” is not a universal damage rule.
• A Stingray or launcher purchase can be a losing trade if the target is already leaving.
• A stolen vehicle that changes team colors can still have an access bug after locking; Team17 has forwarded that report for investigation.
• Do not copy an unverified cargo capacity or claim an exploit is a strategy.

Keep reading