Writing BattleTech fiction that earns the name requires a specific set of craft skills that generic science fiction writing advice does not cover. The game gives you the numbers: tonnage, weapon ranges, heat curves, hit locations. The fiction has to supply the body, the culture, the physical reality of a human being sealed inside a seventy-five-ton war machine. That translation from game mechanic to narrative experience is what separates BattleTech fiction from mech fiction with the serial numbers filed off.

I am Jason Schmetzer. I have written more than twenty BattleTech novels and dozens of short stories for Catalyst Game Labs across a career spanning over two decades. I edit Shrapnel magazine. The lessons on this page and in the linked articles come from that work, not from theory. Every technique is illustrated with passages from my published manuscripts, primarily Redemption Rites, and every principle has been tested across hundreds of thousands of words of published BattleTech prose.

What Makes BattleTech Fiction Different from Other Mech Fiction

BattleTech is built on a tabletop game with specific, published rules for how machines move, shoot, take damage, and overheat. That game layer is what makes the fiction feel different from Gundam, MechWarrior (the video game version), or any other mech property. When a PPC hits armor in a *BattleTech* novel, the reader should feel that the weapon has a specific range, a specific heat cost, and a specific damage output. When a ‘Mech overheats, the reader should understand that the pilot chose to fire one more weapon than the cooling system could handle, and that the choice has physical consequences.

The fiction does not cite numbers. It translates them. A PPC does not do “10 points of damage.” It punches through armor plating, scatters molten composite across the torso, and leaves a wound that changes what the target can do for the rest of the fight. That translation is the foundational skill. If you get it right, readers who play the game will recognize the logic, and readers who do not play will still feel the weight and consequence of every shot. Writing ‘Mech combat that respects the rules is where that translation starts.

The practical test: can a reader who knows the game identify which weapon just fired based on your prose alone, without you naming it? If you write a weapon that fires a beam of coherent light that leaves a glowing scar across armor, the reader knows it is a laser. If you write a weapon that fires a bolt of lightning that makes the targeting computer flicker, the reader knows it is a PPC. If you write a weapon that sends a stream of depleted-uranium slugs hammering into the torso, the reader knows it is an autocannon. Each weapon has a prose personality, and matching that personality to the game is step one.

The Cockpit Rule: Every Combat Scene Has a Body in It

The single most common failure mode in amateur BattleTech combat fiction is writing the machines without writing the people inside them. Two BattleMechs exchanging fire is not a story. Two pilots, sealed inside cockpits that are slowly cooking them, making decisions about when to shoot and when to hold fire while their neurohelmets feed them false vertigo and their cooling suits struggle to keep their core temperature below the point where their hands start shaking: that is a story.

The pilot inside the machine is the most important character in every combat scene. The neurohelmet translates the ‘Mech’s balance into the pilot’s inner ear. The cooling suit pumps chilled fluid against the pilot’s skin while the cockpit temperature climbs. The command couch vibrates with every step. The air tastes of recycled sweat and ozone. These sensory details are not decoration. They are the mechanism by which the reader inhabits the fight instead of watching it from outside.

The physicality of ‘Mech combat extends beyond the cockpit. A BattleMech has mass, and that mass determines how it moves, how it stops, how it falls, and how the ground reacts when it lands. Verb selection carries the weight: a ‘Mech does not “walk.” It strides, stalks, lurches, or staggers, depending on its damage state and the terrain under its feet. A Locust sprints. An Atlas grinds forward. The verbs are different because the machines are different, and the reader feels that difference in the rhythm of the prose.

The cockpit rule applies to every perspective on the battlefield. Non-pilot POVs have their own physical reality: the hovertank gunner feels vibration, not neurohelmet feedback. The Elemental in a battlesuit feels weight and exertion. The observer at a holotank feels stillness and abstract geometry. Each body in the scene experiences the fight differently, and the reader should feel the shift when the perspective changes.

Heat, Damage, and the Decision Engine

Three game mechanics form the core of the BattleTech combat engine, and all three are available as narrative tools in fiction. Learning to use them is what separates competent BattleTech combat from the kind that reads like any other mech property with different proper nouns.

Heat is the franchise’s signature mechanic. Every weapon generates heat. The ‘Mech’s heat sinks dissipate it. When generation exceeds dissipation, the cockpit gets hotter, the controls get sluggish, and the pilot starts to cook. The pilot can fire everything and risk a shutdown, or hold fire and stay cool but let the enemy close. That decision, fire or hold, is available in every combat scene, and it is one of the most efficient character-revealing mechanisms in the franchise. The aggressive pilot runs hot. The cautious one manages heat carefully. The desperate one fires everything and accepts the consequences. Heat as a narrative weapon covers this mechanic in full.

Damage in BattleTech is graduated, not binary. A ‘Mech can lose an arm and keep fighting. It can lose a leg and fall but remain dangerous. It can take internal hits that destroy weapons, pierce the engine shielding, or detonate its ammunition magazine. That spectrum of outcomes is a pacing tool: a scratch hit early in the fight tells the reader the engagement has started. A critical hit to the gyro in the middle changes the tactical equation. An ammunition explosion at the climax ends the fight in a fireball. Each damage level serves a different narrative function, and choosing the right one for the right moment is the core of writing damage and consequences.

Weapon choice connects the pilot to their machine. A MechWarrior who loads PPCs and large lasers is accepting high heat for high damage at range. A MechWarrior who loads autocannons and SRMs is planning to brawl. A MechWarrior who carries an LRM-20 and stays at maximum range is telling the reader they prefer to fight at arm’s length. Weapon choice as character work is one of the quietest and most effective characterization tools the franchise offers, and the OmniMech reconfiguration scene is where that choice becomes an explicit decision moment in the narrative.

Combat Pacing and the Three-Phase Structure

A BattleTech combat scene has a natural three-phase rhythm: approach, commitment, and resolution. The approach phase is long-range fire, deliberate movement, and the pilot assessing the tactical situation. The prose is measured. Sentences are longer. The reader has time to orient. The commitment phase begins when the range closes and the pilot is locked into the fight. The prose compresses. Sentences shorten. Weapon exchanges come faster. The resolution phase is the decisive moment: the kill shot, the critical hit, the ejection, the retreat. It should be fast and proportional to the fight that preceded it.

Weapon type controls tempo within each phase. Autocannons are staccato: short, sharp, percussive. PPCs are single, heavy beats with silence between them while the capacitor recharges. Lasers sustain. LRMs cascade. The sonic and kinetic personality of each weapon shapes the rhythm of the prose around it. A fight between two autocannon-heavy ‘Mechs reads differently from a fight between a PPC sniper and an SRM brawler, and that difference should be audible in the prose. Pacing a ‘Mech battle covers the three-phase structure in detail.

The spaces between shots are where character lives. A pilot who pauses before firing is making a decision. A pilot who fires immediately is acting on instinct or desperation. The moment between “target acquired” and “trigger pulled” is the narrative equivalent of the game’s firing phase, and it is the most valuable real estate in a combat scene. Physical attacks (kicks, punches, and death-from-above) create their own pacing disruption: they are close-range, high-risk, and they force the prose into a different register than weapons fire.

Culture on the Battlefield

BattleTech combat is cultural. A Clan warrior fights differently from an Inner Sphere soldier, not just in doctrine but in the language they use, the internal monologue they maintain, and the way they process victory and defeat. The Clan vs. Inner Sphere collision is one of the richest sources of conflict in the franchise, and it is most visible in the small details: the formal Clan challenge met with Inner Sphere silence, the Trueborn warrior who will not use contractions even under fire, the mercenary who calls a 75-ton war machine “little doggy” before walking around a corner to kill it.

Dialogue under fire serves triple duty in combat scenes: it delivers tactical information, reveals character under stress, and controls pacing. Comm traffic is the human voice inside the mechanical violence. Without it, the fight becomes an undifferentiated stream of machine action. With it, the reader hears the pilot’s fear, confidence, humor, or desperation layered under the weapons fire.

The battlefield itself is a participant in every engagement. Terrain and environment shape tactics, limit options, and change the feel of the fight. A forest engagement reads differently from an urban one. A desert with no cover reads differently from a city where every building is a potential sensor barrier. The terrain should change during the fight: trees knocked down, buildings collapsed, craters opened by missed shots. The battlefield at the end of the engagement should never look like the battlefield at the start. Combined arms complicate the terrain further, because a hovertank, an Elemental, and a BattleMech all relate to the same piece of ground in fundamentally different ways.

And the fight does not end when the shooting stops. The aftermath is where consequences become real: the damage assessment, the field repair, the wounded pilot, the empty cockpit where someone used to sit. The aftermath scene is where the next story arc begins, and rushing through it is one of the most common mistakes writers make.

The Complete Craft Series

Each article below is a deep dive into a specific aspect of BattleTech combat fiction, with manuscript examples from Redemption Rites and analysis drawn from two decades of professional writing in the franchise.

Foundation: Writing ‘Mech Combat That Mimics the Rules | The Physicality of ‘Mech Combat | The Pilot Inside the Machine

Combat Mechanics: Heat as a Narrative Weapon | Damage and Consequences | Weapon Choice as Character Work | Pacing a ‘Mech Battle | Physical Attacks

Battlefield: Terrain and Environment | Combined Arms | Non-Pilot POVs

Culture and Structure: Clan vs. Inner Sphere Styles | Dialogue Under Fire | The Aftermath | OmniMech Reconfiguration

Where to Study Published Examples

The BattleTech novel catalog is the classroom. The Gray Death Legion trilogy by William H. Keith, Jr. set the standard for physical, grounded mech combat. The Blood of Kerensky trilogy by Michael A. Stackpole brought intensity and scale to Clan Invasion warfare. My own Redemption Rites demonstrates both Clan and Inner Sphere perspectives with combined-arms engagements, and is the primary source text for this guide series.

The reading order guide will help you find the right entry point. The best BattleTech novels page identifies the titles that set the standard for combat writing. And if you are interested in writing for Shrapnel or submitting to Catalyst Game Labs, my advice for aspiring Shrapnel contributors covers the submission process and what the editors look for.