Current build
Start with the task, not the weapon
A 50v50 match creates more information than one player can process. The squad needs a short task that can be repeated: hold a sector, attack an edge, observe a route, supply a position, recover a casualty or open a crossing. The role choice follows from that task. Squad Leader and Commander keep the plan visible; Recon observes; Infantry occupies; Armour creates pressure; Mortar Squad supports a location; Helicopter roles connect US air support; engineers and field roles make the route usable.
This is why the role roster is organized by unit and purpose. A new player does not need a universal tier list. They need to see that Machine Gunner supplies sustained fire, Medic handles casualty recovery, Spotter handles reconnaissance and observation, and Pilot handles helicopter operation. Pick the missing function, then ask which map surface lets it act. That choice keeps the squad’s first order tied to a visible need.
Field note
Read air, earth and water
Before movement, name the surface. Air support can change the timing above a runway, bridge or dock. Tunnels can change the support line below a cave, village or jungle edge. Patrol boats can change the route along a river. Swimming, climbing and fast crawling can change the individual approach, while dragging an injured player changes the recovery decision. The map record gives the nouns; the system record gives the verbs.
A good call joins both: helicopter support for the runway edge, tunnel fallback at the cave, boat at the river crossing, climb to the bank, drag casualty to cover. That grammar is simple enough for a busy voice channel and precise enough for Recon, Armour and Infantry to act on different parts of the same plan. It also gives a late-joining player a location and an action immediately, even when the original order was missed or the sector has already shifted.
Field note
The six-step squad sequence
First, confirm the current sector or objective. Second, name the visible terrain and the route it permits. Third, ask which role or support function is missing. Fourth, state the action and its destination. Fifth, move through the opening while reporting the new surface. Sixth, name a fallback before the first route fails. Repeat the sequence when contact changes the map. The steps are short enough to become a habit and broad enough to work in Warfare or Offensive.
The sequence also protects against common errors. A player who chooses a role before hearing the task may duplicate the line. A squad that attacks a map name without a terrain callout may cross the wrong surface. A support request without a destination may arrive too late to matter. A plan without a fallback may turn one casualty into a stalled push. The doctrine is a guardrail for attention, not a rigid script.
Field note
Adapt the sequence to the faction
US Forces add helicopter fire support and supply drops to the task-to-route sequence. State what the air action should change, then move through the ground opening or use the attention it creates to reposition. The Logistics Officer and Pilot records explain why the support has dedicated roles, but the Commander and Squad Leader still connect those roles to the sector task.
The NVA adds buildable tunnel networks. State the surface the network supports, then explain whether it is a fallback, flank, reinforcement line or pressure point. The visible route still matters, but the team can organize below it. Both factions therefore use the same doctrine with different support verbs. The player’s job is to keep the task and terrain language stable while the system changes the route. A clear purpose prevents the support point from becoming an isolated destination and helps the squad recognize when it should move on before the support becomes a liability.
Field note
Measure the plan by information
A failed push can still produce a useful result if the squad learns which surface changed the timing. Record the route, the contact point and the fallback that remained. If a boat blocked a crossing, that is a vehicle and riverine note. If a runway exposed the push, that is a map and reconnaissance note. If a tunnel changed the flank, that is a faction and systems note. After-action language keeps a new match from repeating an old surprise.
Use the dossier’s page structure to follow the question. Roles answers who can act. Battlefields answers where. Systems answers what changes the action. Vehicles answers which moving surface is involved. Modes answers why the sector matters. The sequence becomes more useful as each page supplies one concrete piece of the next plan. A short trace is enough to make that connection visible after the match, and it gives a returning player a faster briefing for the next deployment.
Field note
Leave a trace for the next squad
The best after-action note is small enough to repeat and specific enough to change the next decision. Record the objective, the surface, the role that acted and the fallback that remained. A note such as ‘the runway was visible before the crossing and Recon called the lane too late’ can lead to a different briefing. A note such as ‘the attack failed’ cannot. The point is not to assign blame; it is to preserve the information that the next Squad Leader can use before contact.
This habit also connects the pages without turning them into a checklist of unrelated facts. The map record gives the setting, the system record describes the change, the vehicle record identifies a moving pressure surface and the role record explains who can answer it. Warfare and Offensive give the immediate objective. Once the player can move through that chain, doctrine becomes a practical language for a live 50v50 match rather than a fixed recipe that breaks when the terrain changes.
