Writing Combined Arms in BattleTech Fiction

Most BattleTech fiction defaults to ‘Mech-on-‘Mech combat. Two BattleMechs close range, exchange fire, and one goes down. That works, and it will always be the backbone of the franchise. But the universe has tanks, hovertanks, battle armor, conventional infantry, aerospace fighters, artillery, and DropShips, and writing combined arms convincingly gives a fiction writer access to scale, pacing variety, and character perspectives that pure ‘Mech duels cannot provide.

I have written combined arms engagements across more than twenty BattleTech novels and dozens of short stories for Catalyst Game Labs. The craft challenge is real: you have to manage scale differences between unit types, maintain pacing across POV characters who experience combat at fundamentally different speeds, and give non-‘Mech forces genuine agency without undermining the BattleMech’s place at the center of the franchise. Get it right, and the battlefield feels like a living system. Get it wrong, and the tanks and infantry feel like set dressing while the ‘Mechs do the real work. This article is part of a complete guide to writing BattleTech fiction.

Why Combined Arms Matters for Fiction

A ‘Mech-only battle has one register. Two machines close, weapons fire, someone wins. Combined arms gives the writer three or four registers running simultaneously, each with its own pacing, its own sensory palette, and its own stakes.

A hovertank crew experiences combat as vibration, speed, and the narrow view through a gunnery screen. An Elemental in a battlesuit experiences it as claustrophobic physical exertion, jump jet burns, and the terrifying scale of ‘Mechs looming overhead. Each unit type sees the same battlefield terrain differently, and those different relationships to the ground create distinct narrative registers. A MechWarrior in the same engagement sees the tanks as fast-moving annoyances and the battle armor as insects until one of those insects puts an inferno SRM into a heat-stressed torso. Each perspective tells the reader something different about the same fight, and shifting between them creates a layered, three-dimensional battlefield that a single-POV ‘Mech duel cannot match.

Combined arms also creates natural stakes gradients. A BattleMech pilot inside seventy tons of armor has a fundamentally different risk profile from a tanker in a fifty-ton hovertank with a fraction of that protection, who in turn has a different risk profile from an Elemental in a one-ton battlesuit standing in the shadow of a machine that could crush them without noticing. Those differences in vulnerability are story tension waiting to be used.

POV Selection: Who Sees the Battle?

The single most important decision in a combined arms scene is whose eyes the reader looks through. Each unit type offers a different experience, and the POV you choose shapes everything about how the scene reads.

The MechWarrior’s perspective is the default, and it has real advantages. The pilot sits at the top of the scale hierarchy. They see the whole battlefield from a high vantage point. Their sensor suite reads everything: IR signatures, radar contacts, IFF tags. From the cockpit, tanks are fast blips on a screen and infantry are nearly invisible. That godlike perspective is useful for establishing the tactical picture, but it can also flatten the other forces into abstraction.

In Redemption Rites, I wrote a combined arms engagement from three perspectives: the MechWarrior commander, the hovertank gunner, and the opposing MechWarrior who had to deal with both. The hovertank gunner’s POV was built entirely around physical sensation. Writing from non-pilot perspectives requires a complete sensory reset: the hovertank has no neurohelmet, no cooling suit, and a fundamentally different relationship to the battlefield:

Sergeant Cat Emmons was careful to ensure her teeth weren’t clenched when the counter on her gunnery screen reached zero. The fans that lifted the fifty tons of her Zibler hovertank on its cushion of air made every surface of the tank vibrate, and if the fans weren’t precisely sequenced, competing frequencies of vibrations fought their way through the hull. It was enough that if she clenched her jaw, she’d be able to feel her teeth vibrate together. Even the thought of it was enough to make her shiver in disgust.

That is a different sensory world from the cockpit of a BattleMech. There is no neurohelmet, no cooling suit, no myomer feedback. The tanker’s experience is vibration, noise, and speed. The gunnery screen is her window. The seat cushion is thin enough she can feel the boltheads underneath. Everything about that POV tells the reader this is not a ‘Mech, and the person inside it is not protected the way a MechWarrior is.

The infantry perspective sits at the other end of the scale. An Elemental in powered battle armor is lethal against soft targets and dangerous to vehicles, but against a BattleMech, they are operating on a completely different plane. A ‘Mech’s foot is bigger than their entire suit. The ground shakes when one walks past. Writing from the infantry perspective forces the reader to look up, and that shift in physical orientation changes how every ‘Mech in the scene feels.

Pacing Across Unit Types

Different unit types fight at different tempos, and your prose needs to reflect that difference. A hovertank skimming at 130 kph experiences combat as a blur of speed and brief firing windows. A BattleMech striding at 60 kph experiences it as a deliberate exchange of fire across closing ranges. Battle armor on foot experiences it as a sprint from cover to cover, punctuated by jump jet hops and the concussive hammering of weapons fire that seems to come from every direction.

The practical craft solution is to match your sentence rhythm to the unit. Hovertank prose should be fast, compressed, full of motion. In Redemption Rites, the Zibler crews experienced the engagement as a high-speed slash through the enemy formation:

The Zibler was skimming at near its maximum speed, a smidge under 130 kph. The gunnery controls vibrated beneath Cat Emmons’ gloved hands, and she felt the boltheads beneath the seat’s slim cushion pressing against her legs.

Short sentences. Physical details. Speed as a constant presence. The reader feels the velocity and the vibration without being told "the tank was going fast."

When the POV shifts to the MechWarrior commander watching the same engagement, the tempo changes:

Haya almost didn’t believe it. She’d never, in her entire career, seen so many ‘Mechs taken down so quickly. Thirty hovertanks, all of them armed with plasma cannons, had screamed out of concealment. All three companies’ worth. And in the first clash, nine of the Wolf ‘Mechs went down, most to ammunition explosions.

Not quite a third of the cadets.

In less than ten seconds.

That is the same battle from the command perspective: slower, reflective, assessing the damage. Haya has time to count and calculate because she is in a BattleMech, not in a hovertank doing 130 kph through a firefight. The pacing shift between these two POVs tells the reader that the battle is happening at two speeds simultaneously.

Battle armor prose should be the tightest of all. Infantry operates at human scale, and the sentences should reflect that: short, physical, close to the ground. When battle armor deploys from a hovertank, the transition is abrupt:

One of her cavalry Ziblers scuttled past, slowing just long enough to dump a Point of five Dragoon Elementals out its rear. All five came to their feet, jumped once, and dumped inferno-tipped short-range missiles into the Anvil.

In a moment it was awash in jellied flame.

Five sentences. Deploy, stand, jump, fire, result. That compression is the infantry tempo in prose: everything happens at close range, fast, with no room for reflection.

Making Non-‘Mech Forces Dangerous

The hardest craft problem in combined arms fiction is giving tanks, battle armor, and conventional infantry genuine agency without making BattleMechs feel weak. BattleTech is a BattleMech franchise. The ‘Mech has to remain the dominant unit on the battlefield. But if the other forces are just targets, the scene has no tension.

The solution is specificity. Non-‘Mech forces are dangerous in specific, limited ways, and your prose should make those limitations clear while still letting them matter.

Hovertanks are dangerous because they are fast, hard to hit, and can carry weapons that exploit specific vulnerabilities. In Redemption Rites, the Zibler hovertanks carried plasma cannons, weapons that injected enormous heat into their targets. Against ‘Mechs that were already running hot from combat, that heat injection triggered ammunition explosions. The tanks did not outfight the ‘Mechs in a straight exchange. They exploited a vulnerability that the ‘Mechs’ own weapons created. The plan was specific:

Major Gamble’s plan had been simple: draw the cadets into a skirmish, get them to work their heat up and focus on the Tarantula BattleMechs, and then hit them with the hovertanks specially modified to bring them down without killing the MechWarriors.

That specificity is what makes the tactic believable. The hovertanks did not charge the ‘Mechs head-on. They were part of a combined arms plan where ‘Mechs created the conditions and tanks exploited them. Each arm of the force had a role that the others could not fill.

Battle armor is dangerous because it operates at a scale ‘Mechs cannot effectively engage. A BattleMech can step on an Elemental, but it cannot chase one through a building or stop five of them from climbing its legs. Physical attacks between ‘Mechs carry dramatic weight because both machines are roughly matched; when a ‘Mech kicks a tank or steps on battle armor, the scale mismatch is the point. In Redemption Rites, Elementals served as the final stage of the combined arms sequence: after the hovertanks knocked ‘Mechs down with heat-injection weapons, the Elementals moved in to secure the downed pilots. That role, capture and control at close range, is something only infantry can do.

The key is that non-‘Mech forces win through coordination, not through raw power. A single hovertank against a fresh BattleMech is overmatched. Thirty hovertanks against heat-stressed ‘Mechs, timed to strike after the ‘Mechs have been softened up, is devastating. That is the difference between spectacle and tactics, and it is the difference between combined arms that feels earned and combined arms that feels like the writer is cheating.

The MechWarrior’s Blind Spot

One of the most useful combined arms storytelling tools is the MechWarrior’s condescension toward conventional forces. Clan MechWarriors especially tend to dismiss anything that is not a BattleMech, and that arrogance is a character flaw you can exploit.

In Redemption Rites, the Clan cadet commander Judah registered the incoming hovertanks and made an assessment:

Judah didn’t fear the hovertanks. Several kinds of hovertank could hit quite hard, to be sure. Even the largest ‘Mech respected the SM Destroyers, for example. But they lacked the staying power in armor and weaponry of a ‘Mech. He had little doubt that in a standup fight, his cadets could destroy the new hovertanks.

Judah was not wrong in his assessment. In a standup fight, his cadets probably could destroy the hovertanks. But the hovertanks were not fighting a standup fight. They were executing a specific combined arms plan, and Judah’s failure was not tactical incompetence. It was the failure to recognize that his opponent was not playing the same game he was.

That blind spot is available to any MechWarrior character. The pilot who dismisses the infantry screen. The commander who does not account for hovertank flanking speeds. The Clan warrior who expects a Trial of Position-style engagement and gets a combined arms ambush instead. Each of these is a character moment built on the same foundation: the assumption that ‘Mechs are the only thing on the battlefield that matters.

The opposing perspective is equally useful. The tanker or infantryman who knows they are outclassed in raw firepower but has a plan to level the field is a character archetype that only combined arms fiction can produce. Emmons, the Zibler gunner, did not pretend she could slug it out with a BattleMech. She used her speed, her weapon’s specific thermal effect, and her commander’s plan to accomplish something a ‘Mech alone could not.

Structuring a Combined Arms Scene

A combined arms engagement needs structure, because the reader has to track multiple unit types, multiple tempos, and multiple levels of vulnerability simultaneously. The most reliable structure is sequential layering: introduce the forces, establish the plan, execute with POV shifts, and resolve from the command perspective.

Establish the combined arms composition early. In Redemption Rites, the strike force’s organization was laid out before the engagement:

Today, Haya’s Charlie of the Tarantulas was ten ‘Mechs, ten hovertanks, and fifty Elementals.

That single sentence tells the reader what forces are in play. When the hovertanks appear later, the reader is not surprised. When the Elementals deploy from the tanks’ rear pods, it makes sense because the reader already knows they are part of the force.

Execute the engagement with deliberate POV shifts between unit types. The shift from the hovertank gunner’s tight, vibrating cockpit to the MechWarrior commander’s broader tactical view is a pacing tool. The shift from the MechWarrior commander to the opposing MechWarrior who just realized the hovertanks are the real threat is a stakes escalation. Each POV change should do narrative work: reveal new information, raise the tension, or change the reader’s understanding of who is winning. The three-phase pacing structure of a formation-scale ‘Mech battle is where these different unit-type tempos have to hold together.

Resolve from the perspective that has the broadest view. The commander who can assess the outcome, count the losses, and decide what comes next gives the reader the shape of the whole engagement. Haya’s realization that thirty hovertanks had taken down a third of the Wolf ‘Mechs in ten seconds was a resolution beat that only the command perspective could deliver.

Combined Arms as Worldbuilding

The way a faction uses combined arms tells the reader about that faction’s military culture, and that is worldbuilding delivered through action rather than exposition.

Wolf’s Dragoons in Redemption Rites used combined arms as an integrated system: ‘Mechs, hovertanks, and Elementals operating as a single strike force with a coordinated plan. That told the reader the Dragoons were professional, flexible, and experienced enough to make three different unit types work together.

The Clan cadets they faced used ‘Mechs almost exclusively, with their organizational culture treating other unit types as subordinate or irrelevant. When Candra, a cadet Star Commander in a 100-ton Grand Titan, asked Judah whether they should deal with the hovertanks "after the ‘Mechs," that single line of dialogue told the reader everything about Clan combined arms doctrine (or the lack of it) that a paragraph of exposition could not.

Inner Sphere militaries, Periphery pirate bands, mercenary companies, and Clan Clusters all approach combined arms differently, and those differences are cultural. A story set during the Succession Wars, when BattleMechs were irreplaceable and every tank was expendable by comparison, has a different combined arms dynamic than a story set during the ilClan era, when OmniVehicles and advanced battle armor have narrowed the gap. The way a pilot’s weapon choice reveals character applies at the unit level too: what a commander chooses to bring into the field, and how they use it, is characterization.

Writing the Moment of Conversion

Every combined arms skeptic in your fiction should have a conversion moment: the point where they realize the conventional forces changed the outcome. That moment is satisfying because the reader has been watching the MechWarrior dismiss the other forces, and now they see the result.

In Redemption Rites, Haya was a MechWarrior who understood combined arms intellectually but still carried a MechWarrior’s instinctive sense of superiority:

Like any MechWarrior, she’d also felt a bit of superiority over conventional troops. It was a natural rivalry, for all it had been a friendly one, in the Dragoons at least, but it was also one that had existed since the earliest ‘Mechs had first stepped on tanks.

At the moment, she was a believer.

That two-sentence beat, the acknowledgment of bias followed by the admission that the bias was wrong, is available in any combined arms scene. It works because it is honest. The MechWarrior is not suddenly pretending they never looked down on the tankers. They are admitting, in the aftermath of watching those tankers demolish a ‘Mech formation in ten seconds, that they were wrong. The conversion is earned because the evidence is on the field.

The physical layer of ‘Mech combat gives BattleMech scenes their sensory weight, but combined arms scenes need equivalent sensory work for every unit type. The hovertank crew feels vibration and speed. The Elemental feels the weight of the suit and the concussion of nearby weapons fire. The MechWarrior sees the tactical picture but misses the ground-level details. Each sensory palette is its own craft challenge, and each one pays off when the reader understands that this battlefield has more than one kind of soldier on it.

The way damage escalates through a battle takes on a different character when the damage comes from multiple unit types. A ‘Mech that is already heat-stressed from energy weapon fire and then takes a plasma cannon hit from a hovertank is in a different kind of trouble than one that simply exchanged fire with another ‘Mech. Combined arms damage is layered, and each layer comes from a different direction, a different range, and a different kind of threat.

If you are building a BattleTech reading list and want to study combined arms in published fiction, look for the scenes where the camera leaves the cockpit. The best combined arms writing in the franchise happens when the tanker, the infantryman, or the aerospace pilot gets to tell their part of the story. That is where the battlefield becomes a world.

Frequently Asked Questions

How do you write combined arms combat in BattleTech fiction?

Write combined arms by giving each unit type its own POV, pacing, and sensory palette. Hovertank crews experience combat as speed and vibration. Battle armor infantry experience it at human scale with BattleMechs looming overhead. MechWarriors see the tactical picture but can miss ground-level details. Shift between perspectives to create a layered, three-dimensional battlefield.

How do you make tanks and infantry feel dangerous in BattleTech fiction without weakening BattleMechs?

Give non-‘Mech forces specific, limited capabilities that exploit vulnerabilities BattleMechs create for themselves. Hovertanks that inject heat into already-overheating targets, battle armor that captures downed pilots, artillery that forces movement into kill zones. Non-‘Mech forces win through coordination and exploitation, not raw power. That keeps the BattleMech dominant while making the combined arms plan feel earned.

What is the best POV for writing a combined arms scene in BattleTech fiction?

Use multiple POVs. The MechWarrior commander gives the tactical overview. The hovertank gunner gives speed and ground-level intensity. The battle armor soldier gives scale and vulnerability. Shifting between perspectives during a single engagement lets the reader experience the same battle from different scales and risk levels.

How does combined arms differ between Clan and Inner Sphere forces in BattleTech fiction?

Clan forces traditionally prioritize BattleMech combat and treat other unit types as subordinate. Inner Sphere and mercenary forces use combined arms as an integrated system where each unit type has a specific role. That doctrinal difference is worldbuilding delivered through action: how a faction fights tells the reader about its military culture.

How do you pace a scene with multiple unit types fighting at different speeds?

Match sentence rhythm to unit type. Hovertank prose should be fast and compressed with short sentences emphasizing speed and vibration. BattleMech prose can breathe with longer sentences and tactical assessment. Battle armor prose should be the tightest, reflecting infantry-scale urgency and close-range action. POV shifts between unit types create natural pacing variation.

Scroll to Top