WARDOGS Team Roles & Squad Composition

Official WARDOGS material names Infantry, Medics, Pilots, Builders, and Engineers. These examples give a new squad a vocabulary, but they do not establish a final class roster, locked ability set, cost, cooldown, or tier list. Start with the job the squad cannot currently do and use the live role screen to verify how the label is implemented.

If the squad is absent from the zone, assign presence. If a route keeps losing players, assign support or revive. If the team cannot cross an approach, assign transport, piloting, building, or engineering. A role becomes useful when its first action can be seen in the objective state.

Hold the assignment through one comparable handoff. Swapping the whole composition after a single loss erases the information the match produced.

• VocabularyUse the five named examples to start a job conversation.
• GapChoose the lane the current squad lacks.
• VerifyUse the current client for exact kit details.

Assign who watches the zone, who opens the approach, who protects a revive, who owns transport, and who changes cover or access. The same player can own more than one lane, but the call should be explicit enough that the squad knows what will happen next and who can replace it if the life changes.

This ownership model also protects the economy. A vehicle or weapon purchase should serve a named job; an objective cash action should have a player who knows the route and fallback. The resulting record is about a handoff, not a claim that one role is universally strong.

When the zone moves or the team loses a life, ask which owner is now missing. Reassignment is a normal part of a randomized objective game, not proof that the original role failed.

• OwnerName the player responsible for the next action.
• HandoffState destination, support, and fallback.
• ReplaceReassign the missing lane after the state changes.

Write the role lane, zone state, purchase, first action, visible result, and next test. This lets the squad compare a revive route with a transport route or a zone hold with a push without pretending the two situations are identical. It also provides a clean input for future database work if stable role fields emerge.

Avoid a tier list built from one match, one streamer clip, or one successful vehicle move. The point race, zone, destruction, and communication all shape the result. A role that looks weak in a lost flank may be exactly what the next squad lacks when the objective is unattended.

A complete role and squad product can be added when the client exposes stable role IDs, loadout relationships, and repeated outcomes. Until then, the job-based route is the most reliable decision layer.

• RecordRole lane, zone, purchase, action, result, next test.
• AvoidOne-match universal tier claims.
• ExpandAdd stable role relationships when the client supports them.