Skip to content

FOB placement

Contributed by Lewis Cawte, Viron, LickMyPikachu, Ren, omgacat and exhausted_ghost

Detail level

This page is Squad leading (SA-200) content.It covers leading a squad. Switch the detail level to read it.
1Exclusive
FOBs have an exclusion radius, so for any contested area of the map you can usually place one FOB at most. It has to be in the best spot possible.
2Expensive
A radio costs 20 tickets if the enemy destroys it, as much as an MSV. On a layer with 250 starting tickets that’s 8 %. It needs active protection and a defendable spot.
3Obvious
A radio can be heard up to about 80 m away, and players spawning at it run in a straight line to the objective. An experienced player can read the map and find it in under a minute.

Stealth FOBs don’t work, and spamming radios is how you lose games. Every radio you place gives the enemy a chance to take 20 tickets from you.

  • Good teams send a small flank squad of 4–5 players to probe your backline, hunting for radios and trying to pull a bigger response out of your frontline.
  • Experienced players also check your second and third objectives for radios left behind.
  • If a radio has no well-defined purpose, dig it down, or better, don’t place it. “Back-up FOB” is not a purpose. Most of the time you don’t need more than two radios on the map.

Picture an MBT parked near the middle of the map with nobody in it. It can’t move or shoot, it’s your team’s spawn, an engineer can take it out with a shovel, and it costs more tickets than the MBT. You wouldn’t leave it alone. That’s your radio.

A familiar story: an SL builds an attack FOB, everyone spawns on the HAB and runs 400 m to the objective, and an engineer drives up and puts the radio on bleed. You lose 20 tickets, half the team runs back out of position, and the enemy gets free tempo. One or two players near the radio would have seen the engineer’s vehicle, called it, and shot him before the C4 went on.

75 s
From the radio starting to bleed until it is destroyed. Collapse on it, kill the raiders, dig it back up.

A radio placement has two jobs:

Objective 1

Easy to retake

Objective 2

Safe from mortars, artillery and direct IFV/MBT fire

On the objective, or the closest building to it

Section titled “On the objective, or the closest building to it”

Generally, put the FOB on the objective you’re defending. The same players then protect both the point and the FOB. Only about 30–40 of your 50 players are infantry; the team that gets more of them to the places that matter wins, so let every player do two jobs at once.

  • Exception: open objectives. If the point is a big open area, such as Trenches on Manicouagan, a nearby building that’s easier to hold is better (there, the shack to the north-west).
  • If the FOB isn’t on the objective, make sure players can reach the objective safely, without crossing big fields or wide open roads.
  • In Territory Control, the FOB should be the rearmost spawn for each major lane. Some layers want two, such as Sumari Bala TC; most want one.

Put the radio and HAB inside a building whenever you can. Outside, they’re open to mortars, vehicles, grenade launchers, airstrikes and artillery, and easy to see from helicopters and UAVs. A radio in the open can simply be mortared to death, and there’s nothing your team can do about it.

The exceptions are maps without mortars (Sumari Bala) and maps with no usable building near the middle objective at the start (Mestia). Even partial cover, like the net at Matrerino Hills on Gorodok, helps against mortars.

Sooner or later an enemy will sneak onto your radio. Worst case it’s an engineer and your first warning is C4 going off. A radio raid is rarely more than 3–4 players, so you’ll nearly always outnumber them on the retake: being easy to retake matters more than being hard to reach.

  • Upstairs radios favour raiders. One staircase funnels defenders into a chokepoint: easy to throw grenades down, hard to throw them up, and easy for an engineer to camp.
  • Barricading it with HESCO or wire only slows you down. The engineer digs the wall down, rebuilds it, and shoots your players while they try to dig through your own wall to save the bleeding radio.
✓Always
  • Put the radio on the ground floor
  • Keep it covered and out of sight, near an edge of a building or compound
  • Make sure it’s easy to get back to if a raider gets on it
✕Never
  • Use constructables to block the radio
  • Put it deep inside a building
  • Put it upstairs
  • Two exits, ideally. A building with one way in and out is easy to camp with a vehicle or with constant mortar fire. Sometimes there’s no choice, such as Akim Central on Gorodok.
  • Out of a vehicle’s line of fire. Even under a full roof, check whether a vehicle can shoot in from outside: on the south edge of Akim Central, an IFV on the southern highway can fire straight into the HAB.
Public games: keep them close
RADIOHABSpawners are always near the radio,so raiders are spotted early

In public games, put the HAB next to the radio. Players spawning in are close to the radio when the enemy shows up. Dropping the radio and running to the edge of the build radius to place the HAB is called stretching the HAB: it buys almost no stealth against experienced players, and while your players run from the HAB to the radio, the engineer has time to set up an ambush.

Competitive · SA-300
Competitive: split them
RADIOHABRaiders must chooseradio OR HAB

In competitive games, split them. Raid squads are small; if two players have to proxy the HAB, few are left to attack a radio defended by one or two. Good teams don’t mind a proxied HAB, because they spawn on their rallies.

Backup spawn and ammo
The HAB gives you a steady spawn and resupply. Your rally should still be your main spawn: it’s more flexible, and it’s how you take map control and attack enemy spawns. Spawn on the HAB when the rally burns or you need ammo; spawn on the rally to retake a proxied HAB.
Mortars
Very powerful in good hands, especially on maps like Kokan and Chora.
Repair station
Keeps your vehicles in the fight, wins duels with enemy armour that comes to you, and saves them a long, predictable drive back to main past the enemy HAT. Essential on armour-heavy layers.

The ideal FOB does all three, which is another reason fewer FOBs is better.

Should I place a FOB?
  1. Does your team have a FOB?
    No→Place a FOB on your defence objectiveAny spawn in play beats sitting at main.
    Yes ↓
  2. Is that FOB on, or right next to, the objective you’re defending now?
    No→Place a FOB on your defence objectiveYour FOB is out of position, for example because the objectives have moved on. A FOB on your defence point protects the point and itself with the same players.
    Yes ↓
  3. Does it make sense for your team to attack?
    No→Use a rally
    Yes ↓
  4. Can your team reasonably attack with rallies?
    Yes→Use a rally
    No ↓
  5. Is there a decent spot for an attack FOB?
    No→Use a rallyAn indoor radio, a reasonable distance from the objective. Not a field or a forest where mortars and vehicles can kill the radio.
    Yes ↓
  6. Will your defence abandon the defence point at the first convenient spawn?
    Yes→Use a rally
    No ↓
  7. Place an attack FOBIt works, but you're probably over-committing to the attack. You have about 15 minutes before your defence point folds, so capture fast.

After omgacat’s flowchart (Tactical Trigonometry).

  • Defence FOB: almost always. You defend the point and the FOB at the same time, and it’s a safe place for mortars and a repair station.
  • Attack FOB: it depends. Players mass-spawn and run straight at the objective, so the FOB is easy to find: on experienced servers, expect the enemy to hit it within 5–15 minutes. Be ready to defend it, and to take it down yourself if the attack fails.
  • Ask who will actually spawn there. If it’s only your squad and a few others, you needed a rally, not a FOB.
  • Team wiped? A bad FOB beats none. Eating a possible 20-ticket loss is worth it if it stops you losing the game. Put it close to an objective, though: too far away and the whole team resets out of position.

Shovel numbers every builder, and every raider, should know:

2×
An engineer’s shovel builds and digs about twice as fast as a normal one
3×
Digging something down takes three times longer than building it up
10×
Barbed wire is ten times cheaper than a HESCO wall: 15 construction vs 150
  • It isn’t tied to the swings. Building and digging is a constant change in the object’s health that starts as soon as you hold the mouse button. The engineer’s swing animation is only about a third quicker, but the actual build speed is about double: one engineer is worth two normal shovels.
  • Wire beats HESCO for the cost. Making wire passable takes half the shovel hits of digging a HESCO wall down one level (18 vs 36), but it costs a tenth as much. So for the same construction, wire is five times harder to get through.
  • Put the wire close together. Overlapping objects have to be dug down one at a time before you can start on the next, which can make it up to ten times harder to get through.