PUBG squad fights, trades and safe revives

1. Fight from connected cover

Choose positions from which teammates can respond to the same opponent without sharing every incoming angle. A player far ahead can be knocked before the squad can help. Use terrain to approach together and limit the enemy’s lines of fire.

2. Confirm pressure before pushing

A knock does not reveal every surviving opponent. Identify who can cover the approach and which position remains dangerous. Pushing immediately through open ground can surrender the advantage you just created if an unseen player has a clean defensive angle.

3. Plan smoke and revive coverage

A revive needs protection and a route afterward. Smoke can obscure vision but does not create solid cover or prove safety. Consider hostile angles and the shrinking area before committing several teammates to the same vulnerable revive location.

4. Review the squad’s loss of spacing

Find the first moment where one teammate could no longer be traded or protected. Record the route and what the others were doing. A mechanically missed shot may be secondary to an approach that left each player fighting a separate engagement.

Practice worksheet: turn the lesson into a decision

Use one replay, training situation or recorded match from PUBG: BATTLEGROUNDS. Choose a sequence where the issue in this guide appears. Watch the lead-up once without pausing, then return to the point before the important commitment. The aim is to describe a choice clearly enough that you can recognise a similar situation again.

1. Describe the starting state. Write who can participate, what resources are available and which part of the map or objective matters. Separate directly visible information from assumptions. If a player or resource is not visible, record it as unknown instead of filling the gap with hindsight.
2. Check the first decision. Begin with “Fight from connected cover”. Describe the action that was taken and one realistic alternative. An alternative must respect what the player could know and reach at that moment; it cannot depend on seeing the rest of the replay.
3. Follow the consequence. Look for what the choice changed: access to space, a teammate’s options, a resource, or control of the objective. Record the consequence before scoring the final result. A good decision can still lose an exchange, while a poor one can survive through an opponent’s error.
4. Repeat one correction. Use a consistent practice setup where possible. Keep the same role, controls and starting task while changing one decision. In the next replay, check whether the intended action occurred. This is a self-review exercise; we have not measured a rank, win-rate or latency improvement.

Illustrative situation

Your squad knocks an opponent behind a ridge. Rather than sprint across a road, one player covers likely return fire while the others move between available cover. The team keeps a retreat option if a second squad begins shooting.

Use that example as a question, not a script. What information would justify the action in your own game? What new threat would make you stop? Write a short failure condition beside the plan, so the lesson includes when to change course as well as when to act.

Questions about this lesson

What should I practise first?

Start with “Fight from connected cover”. Choose a situation you can repeat or identify clearly in a replay. Add the next checkpoint only when you can explain why the first action was appropriate. This keeps practice focused on a decision rather than a collection of tips.

What is the most common review trap here?

Assuming smoke removes all risk or a knock guarantees a safe push. Compare the information available before the choice with what the replay reveals afterward. Those are different views of the same situation. The useful correction is a habit you can apply without knowing the future.

Does this replace the current game or event rules?

No. Check the publisher’s current client notes and the organiser’s rulebook for costs, timings, map pools, restrictions and competition format. This lesson explains a decision process and avoids fixed patch-specific values that could become stale.

Can a scoreboard prove this lesson worked?

A scoreboard can show a result, but it does not describe the choices that produced it. Review the relevant sequence and compare similar situations. Avoid attributing a win to one setting or tactic when opponents, teammates and the game state also changed.