How player-built vehicle combat works

The short version. You assemble a vehicle from separate parts, each of which occupies space, adds weight and can be destroyed individually. Matches are won by the machine that keeps working longest, not by the one with the largest number on a bar. The building is where the skill mostly lives.

Somebody coming to this genre from a shooter or a racing game has to unlearn one habit first: the vehicle is not a thing you choose, it is a thing you make. There is no roster to scroll through. There is a box of parts, a grid to attach them to, and whatever you can justify carrying.

The anatomy of a build

Almost every game in this category organises parts into the same handful of roles. The names differ between titles; the roles do not.

The cabin: The heart of the machine and the part everything else bolts onto. It sets the baseline for how much weight the vehicle can carry, how much energy is available to power weapons, and often a bonus of some kind. Destroy an opponent's cabin and the vehicle is finished regardless of what is still attached to it.
Movement parts: Wheels, tracks, hovers or legs. They carry the weight, determine how the vehicle turns, and are usually the most exposed pieces on the machine. Carrying more of them raises the weight you can support but adds surface for an opponent to shoot at.
Structural parts: Frames, bumpers, plates and armour pieces. They hold the shape together, take hits that would otherwise land on something important, and add mass. A build is mostly structure by piece count.
Weapons: Machine guns, cannons, autocannons, launchers, melee attachments and so on. Each draws from the power budget, needs a line of fire, and needs somewhere to sit that is not immediately shot off.
Modules: Support equipment: generators that supply energy, radiators that manage heat, ammunition packs, boosters, cloaking devices, repair kits. Modules are the parts that make a design coherent rather than a pile of guns.

The interaction between those five categories is the whole game. A weapon you cannot power is dead weight. Armour you cannot move is a stationary target. Movement parts you cannot protect are the first thing an opponent takes off you.

A schematic build. Each box is a separate part with its own mass, its own durability and its own chance of being the piece that gets shot off.

Why damage behaves differently

In a conventional action game, a vehicle has a quantity of health. Hits subtract from it. At zero, the vehicle is destroyed, and until that moment it drives and shoots exactly as well as it did when the match started.

Games in this category discard that model. Each part has its own durability, and a hit damages the specific part it strikes. The practical results follow directly:

A vehicle degrades gradually and asymmetrically. Losing the wheels on one side leaves you turning in circles.
Where you are hit matters more than how often. A hit that removes a weapon is worth more to your opponent than three that scuff an armour plate.
Armour becomes geometry rather than a statistic. Pieces are positioned to be hit first, or angled so that shots glance across them, or arranged to leave nothing valuable exposed from the front.
A match can be lost while the vehicle is still driving. If both weapons are gone, you are a spectator with a steering wheel.

This is also why builds in the genre look strange. A design that appears lopsided or ugly often reflects a deliberate decision about which face of the machine an opponent will see first.

Mass, power and the two budgets

Two limits sit behind every build decision, and beginners usually discover the second one the hard way.

The first is mass. Every part weighs something, movement parts support a limited amount of weight, and exceeding that limit leaves the machine slow enough to be useless. A heavily armoured build that arrives at the contested ground after the fight has been decided has contributed nothing.

The second is energy. The cabin supplies a fixed amount, generators add more, and each weapon and powered module consumes some. You cannot simply attach every gun you own. The decision is nearly always between a small number of powerful weapons and a larger number of weaker ones, and that decision then dictates the armour, because more guns need more places to mount them.

The trade-off worth internalising

Armour, speed and firepower pull against one another through the same two budgets. There is no configuration that is strong in all three, and that is the design intent rather than a balance problem. A build is an argument about which of the three you are prepared to lose.

Assembling a first vehicle

The sequence below works in most games of this type and keeps the number of things that can go wrong small.

Start from the cabin, not the weapon. Pick a cabin, note the mass it can support and the energy it supplies, and treat both as the budget for everything that follows.
Attach movement parts next. Four is a sensible default. Confirm that their combined carrying capacity comfortably exceeds the weight you expect to reach, because the rest of the build only adds weight from here.
Mount the weapons before the armour. Place them where they have a clear line of fire and where your own structure will not block them. Check the energy remaining after each one.
Add the modules the weapons need. A generator if you are short of energy, a radiator if the weapons overheat, an ammunition pack if they run dry. These are not optional extras; they are what make the weapons work as intended.
Build the armour last, from the front backwards. Put structure between the likely direction of incoming fire and the cabin, weapons and modules, in that order of priority.
Drive it before you commit to it. Most games provide a test area. Confirm it turns, stops, and can actually point its weapons at something before a match does it for you.

What a match feels like

Matches are typically short, team-based and objective-driven: capture a point, escort something, or eliminate the other side. The rhythm is unusual because of how damage works. The opening is cautious, because the first vehicle to lose its weapons stops mattering. The middle is a sequence of exchanges in which both sides lose parts. The end is often decided by whichever half-destroyed machine can still shoot.

Two habits pay off immediately. The first is to keep your weapons pointed at the enemy and your least valuable structure between you and them, which in practice means approaching at an angle rather than head-on. The second is to treat every exchange as a trade: you are not trying to survive intact, you are trying to lose less than the other vehicle does.

Habits worth avoiding early

Bolting on every part you own. The temptation is to use the new weapon without removing anything. The mass budget punishes this immediately.
Treating armour as a layer of paint. A single sheet of plating across the front adds weight and stops very little. Depth in front of the cabin does more than coverage everywhere.
Ignoring the module slots. Players who skip generators and radiators spend matches wondering why their weapons stop working halfway through a fight.
Rebuilding after every loss. Give a design several matches before deciding it failed. Losing to a better-positioned opponent is not evidence that the build is wrong.
Buying parts to solve a design problem. Almost every early problem is a placement problem. Step 2 deals with spending, and the short version is to wait.

Where this goes next

You now have the vocabulary the rest of this path uses: cabin, movement parts, structure, weapons, modules, and the two budgets that constrain them. The next question is a commercial one rather than a mechanical one, because nearly every game in this category is distributed without a purchase price and earns its revenue elsewhere.

Step 2: what free to play actually costs looks at where the money enters, what to read before you start, and what the Australian Consumer Law says about digital purchases that do not work as described.