Writing Dialogue Under Fire in BattleTech Fiction

Radio communication in ‘Mech combat serves triple duty. It delivers tactical information the reader needs to follow the fight. It reveals character under stress. And it controls pacing, creating beats of human connection between bursts of mechanical violence. A well-placed line of comm traffic does more work than a paragraph of internal monologue, and a badly placed one can shatter the tension of an otherwise effective combat scene.

I have written comm traffic across more than twenty BattleTech novels and dozens of short stories for Catalyst Game Labs. The craft challenge is specific to this franchise: BattleTech characters communicate through sealed helmets, across encrypted frequencies, while their machines are shaking, their cockpits are overheating, and their attention is split between the conversation and the person trying to kill them. That constraint shapes every line of dialogue in a combat scene. The principles of writing ‘Mech combat that respects the rules extend to comms: the way characters talk during a fight should reflect the same physical and tactical realities as the way they shoot. This article is part of a complete guide to writing BattleTech fiction.

Comms Traffic as Tactical Information

The most basic function of combat dialogue is delivering information the reader needs. Unit positions, target assignments, threat warnings, status reports. This is the scaffolding of a battle scene, and it has to be efficient. A pilot in the middle of a firefight does not deliver paragraphs. They deliver fragments.

In Redemption Rites, the Rodemal engagement opened with terse positional exchanges:

“Just like the major predicted,” Lieutenant Greaves said. His Mad Cat III stood at the head of his Star, but when Haya looked at his ‘Mech in her HUD, the protective covers over his big box long-range missile launchers slid open, revealing the double-score warheads nestled there, ready for flight.

That line does two things at once. Greaves confirms the tactical situation (the enemy is moving as predicted), and the visual detail of his missile covers opening tells the reader he is preparing to fire. The dialogue is the information. The narration is the action. They work in parallel, not in sequence.

Compare that to Judah’s command dialogue on the Clan side of the same fight:

“Candra,” he said, “watch your advance. Do not get caught in a pincer.”

Short, direct, professional. Judah does not explain why a pincer is dangerous. He trusts his subordinate to understand the implication. That trust is itself a character detail: Judah is a trainer who has drilled these cadets, and he speaks to them as warriors, not students, even in the moment when their inexperience is about to cost them.

The practical rule for tactical comms: keep them short, keep them specific, and let them carry character. "Press them!" tells the reader what Haya wants, how she gives orders (short, imperative), and that the moment calls for aggression. Three syllables. Three layers of information.

Comms as Character Under Stress

The way a character speaks under fire reveals who they are more efficiently than any amount of peacetime dialogue. Vocabulary contracts. Formality drops or, in Clan characters, intensifies. The gap between what a character says and what they feel widens, and that gap is where the reader finds the character.

In Redemption Rites, Vordel’s laconic humor during urban combat is a character signature:

“Here, little doggy,” Vordel muttered. He stepped around the corner.

Vordel is about to engage a concealed ‘Mech at point-blank range. His dialogue is a joke. That deadpan tells the reader Vordel has done this before, that he processes danger through humor, and that he is confident enough to talk to a 75-ton war machine like a lost pet. After the kill:

His Hellstar, radiating heat even its multitudinous heat sinks couldn’t quite keep under control, stepped back around the corner. “It will come out no more.”

Seven words. The entire fight summarized in a flat declaration. Vordel does not celebrate. He does not describe what happened. He reports the result and moves on. That compression is his character: professional, understated, lethal.

Contrast Vordel with Judah’s mounting frustration on the Clan side:

“Follow your orders, damn you!” he shouted.

Judah is losing control. His cadets are walking into a trap, his subordinate is asking questions instead of obeying, and his professionalism is cracking under the pressure. The profanity ("damn you") is the character tell. A Clan warrior in control of the situation would never curse at a subordinate. Judah’s language has broken down because the situation has broken down, and the reader can hear it.

The craft lesson: combat dialogue should sound different for each character, and the stress of combat should warp each character’s baseline differently. The calm character gets calmer. The aggressive character gets shorter. The anxious character repeats themselves. The professional character’s language becomes more formal as a coping mechanism. The character who is losing control lets their vocabulary slip.

Pacing With Dialogue: The Beat Between Explosions

Comm traffic is one of the most effective pacing tools in combat fiction because it creates human-scale beats inside machine-scale action. A line of dialogue between two weapons exchanges gives the reader a moment to breathe, process what just happened, and prepare for what comes next. Without those beats, combat becomes an undifferentiated stream of action.

In Redemption Rites, the exchange between Haya and Vordel after his fall and recovery is a pacing beat disguised as a status check:

“Aksel?” Haya said. Her cockpit heat was stifling, but she ignored it. Her cooling suit would protect her. “You okay?”

“Fine, Major,” Vordel said. He got the Hellstar back to its feet. “Be right back.”

Four lines. The reader gets a moment of human concern (Haya checking on her subordinate), a status update (Vordel is fine), and a promise of action ("Be right back"). The pacing of the battle pauses for exactly long enough to remind the reader that these are people inside these machines, then resumes. That pause is what makes the subsequent corner fight land harder: the reader cares about Vordel because Haya cares about Vordel.

Clan comm traffic creates different pacing beats. The formal acknowledgment ("Aff, Star Captain") is a ritualized pause. The challenge issued over open comms is a declaration that slows the scene for a moment of cultural weight. In the Rodemal engagement:

“The surats refuse our challenges, Star Captain,” the cadet commander reported. “It will be a melee.”

That report is a pacing beat that carries disappointment, confusion, and the first crack in the cadets’ worldview. The Dragoons were supposed to accept the challenges. They did not. The cadet has to process that violation and adjust, and the reader processes it with them. The beat is brief, but it changes the emotional texture of the scene.

The practical technique: place one line of dialogue every three to five paragraphs of combat action. That ratio keeps the human voice present without slowing the fight. If a scene goes more than a page without dialogue, the reader loses connection to the characters. If every other paragraph is dialogue, the combat starts to feel like a conversation with occasional explosions.

Clan Dialogue vs. Inner Sphere Dialogue in Combat

Clan and Inner Sphere combat styles differ in doctrine and cultural values, and that difference extends to how characters communicate under fire.

Clan combat comms are formal, even under stress. Contractions are rare for Trueborn warriors. Affirmatives and negatives use the Clan forms (aff, neg). Challenges are issued in full, even when the enemy is closing. The formality is not affectation. It is discipline expressed through language. A Clan warrior who maintains formal speech under fire is demonstrating control.

Inner Sphere combat comms are clipped, informal, and team-oriented. Callsigns, shorthand, slang. The Dragoons in Redemption Rites used unit nicknames ("Ticks" for Elementals, "Marys" for Mariks), abbreviated confirmations ("Roger"), and the kind of gallows humor that professional soldiers use to manage fear. The informality is not sloppiness. It is efficiency expressed through familiarity.

The contrast is visible when both sides appear in the same scene. The cadets’ challenges over open comms, formal and earnest, are met with silence from the Dragoon frequency. That silence is the Inner Sphere response to the Clan protocol: we heard you, we do not care, and we are not going to play your game.

When you write mixed Clan-and-Inner-Sphere scenes, let the dialogue styles clash. A Clan warrior who barks "Neg!" in response to a subordinate’s suggestion is communicating differently from an Inner Sphere officer who says "Negative, hold position." Both mean the same thing tactically. Culturally, they are different languages.

Writing Channel Switches and Frequency Management

A detail that separates professional military fiction from amateur combat writing is frequency management. Characters do not all talk on the same channel. A company commander speaks on the command net. A lance leader speaks on the lance frequency. An individual pilot might switch to a private channel for a personal exchange. Each switch is a story decision about who hears what.

In Redemption Rites, Emmons switched channels within a single engagement:

“Caxton,” she said, after switching her intercom to the gunner’s channel, “you ready?” … “Roger,” she replied, and flicked back to the regular intercom channel. “Guns up, sir,” she reported.

Two channel switches in a few sentences. The first is private (gunner to assistant gunner, confirming readiness). The second is professional (gunner to vehicle commander, reporting status). Each switch tells the reader about the communication hierarchy inside the tank and about Emmons’ role in it. She talks to Caxton as a colleague and to Reyes as a subordinate.

Channel management also creates dramatic opportunities. A character who forgets to switch channels and broadcasts a private comment on the command net. A commander who deliberately broadcasts on an open frequency so the enemy can hear. A pilot who switches to a private channel to say something they cannot say in front of the unit. Each of these is a story moment built from the simple mechanics of military radio.

The pilot inside the cockpit hears comms through the neurohelmet’s speakers, filtered and compressed. The sound quality itself is a detail: clear on a close-range channel, crackling on a long-range one, distorted by jamming or damage. These audio textures layer under the dialogue the same way heat and terrain layer under the combat action.

What Not to Say: The Power of Comm Silence

The most powerful dialogue tool in combat fiction is the line that is not spoken. A character who stops responding. A frequency that goes dead. A pilot whose last transmission cuts off mid-sentence. These silences carry more weight than any line of dialogue, because the reader fills them with their own dread.

In Redemption Rites, the most devastating comms moment was not a line of dialogue but a visual:

A Gauss round turned Dillon’s cockpit into a smear across the Lupus‘ upper torso.

There is no final transmission. No dying words. No dramatic sign-off. Dillon’s frequency just goes silent, and the reader understands what happened because the narration shows it. The silence on the comm channel is the death notice. Damage and consequences apply to communications as much as they apply to machines: when the cockpit is destroyed, the voice disappears.

Partial transmissions are equally powerful. A pilot whose sentence is interrupted by a hit. A commander whose order is cut off by static. A report that starts with a callsign and ends with silence. Each of these tells the reader something happened without describing it, and that restraint is often more effective than showing the event.

Write the silence. When a character dies, let their frequency go quiet. When damage takes out the comms array, let the pilot fight in isolation, unable to hear orders or report status. When the battle is over and the survivors check in, let the missing voices speak louder than the present ones.

How Do You Write Dialogue Under Fire in BattleTech Fiction?

Keep tactical comms short. One sentence, sometimes a fragment. The pilot’s attention is split between talking and fighting. Their dialogue should reflect that division.

Let each character’s voice change under stress. The calm pilot gets calmer. The aggressive one gets shorter. The frightened one speaks faster. The professional’s language tightens into clipped, formal precision. The character losing control lets their vocabulary break down.

Use dialogue as pacing. One line every three to five paragraphs of combat action keeps the human voice present without slowing the fight. Place dialogue beats at natural pauses: between weapon recharges, during movement phases, at the moment a tactical situation changes.

Differentiate Clan and Inner Sphere speech patterns. Clan comms are formal and ritualized. Inner Sphere comms are clipped and team-oriented. Let the styles clash when both sides appear in the same scene. Weapon choice reveals character through action; dialogue reveals it through voice.

Manage frequencies. Characters talk on different channels for different purposes. Switches between channels are story decisions. Private channels create intimacy. Command nets create authority. Open frequencies create risk.

And write the silence. A dead channel is the most powerful dialogue beat in combat fiction. Let the missing voices carry the weight of what happened.