WARDOGS Vehicles & Combined Arms

WARDOGS describes a battlefield where transport and combined arms can change how a squad reaches the Control Zone. That makes vehicle selection a route question. Before buying or taking a vehicle, state what the squad cannot currently do: cross an exposed approach, recover a downed teammate, regroup after a rotation, or keep enough presence at the zone edge.

Then define the handoff. One player owns the movement, one knows the destination, and everyone knows where the squad will dismount and how it will return. This short call keeps the vehicle connected to the objective. Without it, a vehicle can create the illusion of progress while the team arrives outside the scoring pressure.

The first test should be short. A small transport to a visible landmark teaches more than a long rotation whose failure could be route, timing, enemy pressure, or communication. If the handoff works, expand the route one variable at a time.

• WhyName the access or regroup blocker before selecting a vehicle.
• WhoAssign pilot, passengers, destination, dismount, and fallback.
• How farTest the shortest route that can affect the zone.

Pick the dismount point from the current zone and battlefield, not from a remembered route. A cover landmark, a safe edge, and a way back give passengers a next action the moment they leave the vehicle. If the route ends in an exposed dead end, the vehicle solved travel but not survival or presence.

Keep the pilot and passengers aligned on the return plan. If one player stays with the vehicle while others enter the zone, that ownership is a deliberate choice; if everyone leaves, the loss of transport should be acceptable. The exact seat and repair rules require the live client, so the page focuses on the decision relationship rather than invented specifications.

A good log contains the vehicle role, route length, dismount landmark, zone state, and first result. That record can later become a real vehicle database if the client exposes stable identifiers and fields.

• LandmarkUse a visible point to anchor the dismount and return.
• OwnershipDecide who pilots, who rides, and who owns the zone after arrival.
• EvidenceRecord the handoff before judging vehicle strength.

An armored scene can show that pressure and protection are part of the game’s fantasy; it cannot establish armor points, damage reduction, weapon penetration, speed, cost, seat count, repair time, or spawn rules. Keep those values as current-client checks until a repeated record exists.

This boundary still leaves a useful player answer. When the approach is exposed, test whether the vehicle changes access or team survival while keeping the zone visible. When the squad is already close, a vehicle may add noise or remove a fallback. The correct choice is conditional on the problem in front of the team.

When Early Access provides stable vehicle fields, expand this module with a bounded reference or comparison tool. Until then, a route and handoff guide is faster and more honest than a list of unverified tanks.

• ConfirmedTransport, combined arms, and battlefield pressure are real design signals.
• UnknownRoster, costs, seats, durability, and damage need the current client.
• NextCapture stable fields before adding a database.