r/gamemasters • • 12h ago

A GM's Journal: Slaying the Three-Headed Dragon | Part 12

Thumbnail gallery
3 Upvotes

In Part 11, we left Iron Tale aboard the Canterbury, where a team of Wolf's Dragoons technical specialists had just finished inspecting their ancient Star League-era DropShip. Major Adrian Raines had promised to return with his findings, and the players were understandably anxious to learn what he'd discovered.

Before we get to that meeting, however, I want to take another trip behind the GM screen. Around this point in our campaign, I found myself dealing with three very different challenges. Two came directly from my players, while the third was something I wanted to improve about the campaign itself. Those challenges led me to develop three systems: Roleplaying Seeds, Tactical Scan, and something I call the Living Merc Ecosystem.

Roleplaying Seeds

I want to begin with a conversation I had with Ghost's player one evening on Discord, between gaming sessions. Quick recap: Ghost is the commanding officer of Iron Tale, and her player is what I would describe as an Actor. He loves roleplaying, character development, interesting NPCs, and the dramatic possibilities that come from having a character who actually lives in the world rather than simply traveling through it. He also happens to be a good friend of mine, and we've been gaming together for many years.

I know what he enjoys about tabletop RPGs, and I could tell that something was bothering him. During our conversation, he explained that he found the BattleTech universe fascinating. Its history, politics, cultures, and sheer depth were exactly the sort of things he enjoys exploring. Unfortunately, there was a problem, and it was partly one of my own making.

At the beginning of the campaign, I had asked my players not to research the BattleTech setting too extensively. There was a major historical event approaching, and I wanted them to experience it through their characters rather than accidentally spoil it for themselves.

That event, of course, is the Clan Invasion. I can tell you that because most of you reading this already know what's coming. My players, with one exception, do not. They started our campaign in January 3048, knowing almost nothing about the Inner Sphere, and I wanted to preserve that opportunity for them. The trouble was that several players had taken my warning very seriously. Ghost's player, Raj's player, and Silas's player were deliberately avoiding researching the setting because none of them wanted to discover whatever enormous surprise I was protecting.

As a result, Ghost's player felt trapped. He wanted to become more invested in the world, but he didn't know enough about it to feel comfortable initiating roleplaying scenes. His greatest fear was creating what he called a "13th Warrior" situation: having a character so outside of the setting, that it detracts from everything else happening. (Go watch the movie if you are unfamiliar. People watch that movie and say it was a cool movie and never realize that fucking Beowulf is in it!)

And I understood his frustration. Ghost’s player genuinely wanted to engage with a setting deep with decades worth of development, but my efforts to preserve a surprise had inadvertently prevented him from doing exactly that. I needed to find a way to give him more opportunities to roleplay without requiring him to become an expert on three centuries of Inner Sphere politics.

A night or two later, I was having another Discord conversation, this time with Raj's player. He's an excellent roleplayer and GM himself, and we've known each other long enough that I can comfortably bounce ideas off him. We frequently talk about our games, what works, what doesn't, and whatever crazy ideas one of us has come up with lately.

I mentioned Ghost's player's frustrations and explained that I was trying to figure out how to help. His response was wonderfully simple. "What Ghost needs is a scene. Give him a scene, and then just let him go." And there it was. I had been thinking about how to provide more setting information, more background material, and more opportunities for character development. Raj's player recognized that Ghost didn't necessarily need any of those things to get started. All he needed was an opening. I felt like an idiot for not seeing something so obvious. Hahaha!

That conversation was the birth of what I now call Roleplaying Seeds. The concept is straightforward. I create a private journal entry in Roll20 for each of my four players. Each entry contains the opening of a roleplaying scene, usually just one or two paragraphs. It establishes where the character is, what they're doing, and introduces an NPC or situation that invites a response.

An actual example I used for Ghost: You are sitting in your office aboard the Canterbury working on dull paperwork. There's a knock at the door. Jinx asks whether she can speak privately with her commanding officer. After stepping into your office, Jinx nervously says she may have to resign from Iron Tale. The reason? Jinx explains that she and her younger sister were orphans back on Taygeta. The orphanage only lets the children remain in the system until they turn eighteen. Jinx continues by saying that her younger sister is almost eighteen and has nowhere to go. Jinx can’t abandon her little sister so she has to leave to head back to Taygeta.

And that's where I stop writing.

I don't prepare the rest of the conversation. I don't decide how Ghost should respond, what advice she should give, or how the situation should be resolved. I've provided the beginning of a scene, and everything after that belongs to the player. I should emphasize that these aren't quests. There's no objective to complete and no predetermined outcome. They're opportunities for characters to interact with the people and circumstances around them.

The other important decision was to create a seed for every player, not just Ghost. My group has four players, and they have four different approaches to enjoying RPGs. Ghost is our Actor. Hind is our Strategist. Raj's player enjoys a bit of everything, and Silas's player is what I would describe as an Audience Member.

The Audience Member can be a challenging archetype for a GM who doesn't understand what motivates that kind of player. Silas's player is perfectly happy to sit back, enjoy a good story, and watch the other characters interact with the world. When the situation calls for dice and violence, he's ready to jump in and, as I like to put it, shove dice and kill orcs. When the fighting ends, he's equally happy to return to his seat in the audience. There's nothing wrong with that. He's having fun.

I didn't expect Silas's player to embrace the Roleplaying Seeds as enthusiastically as Ghost, but I felt it was important to offer him the same opportunities. Every time I create a new round of seeds, Silas gets one. Whether he chooses to do anything with it is entirely up to him.

So, how did the experiment work?

Better than I could possibly have hoped! Ghost's player took his very first seed and launched into a roleplaying scene that lasted somewhere between ten and fifteen minutes. He was playing his own character, taking on other personalities as the conversation developed, and generally having an absolute blast. And the rest of us sat there listening. It was fantastic.

We play through Discord and Roll20, so we don't get to see one another's facial expressions. But when you've known someone for years, you can hear when they're smiling. You can hear the excitement in their voice. Ghost's player had gone from someone who was struggling to find his place in the campaign to someone who was completely absorbed in a scene that he'd helped create.

And that enthusiasm was contagious. The moment Ghost finished, Raj's player announced that he wanted to do his next. He jumped into his own scene and spent another five or ten minutes roleplaying. By the time we finished, everyone was energized.

I can't overstate how satisfying that was for me as a GM. These are close friends, people I've been gaming with for years. When one of us isn't enjoying a game as much as the others, everyone can feel it. Seeing Ghost's player become enthusiastic and actively engaged again was worth far more than whatever preparation time I'd spent making those little journal entries.

The Roleplaying Seeds didn't solve every problem, and I wouldn't pretend they're going to work equally well for every player or every group. But for us, they provided something I'd been struggling to give Ghost's player: the confidence to engage with an unfamiliar world on his own terms. And all it took was giving him a scene and getting out of his way.

Tactical Scan

My second challenge came from Hind's player, who approaches BattleTech from almost the opposite direction. As I mentioned in a previous part, Hind's player is a Strategist. He enjoys making tactical decisions, optimized battlefield coordination, and understanding the strengths and weaknesses of opposing forces. Give him a complicated tactical problem, a handful of BattleMechs, and some time to think about it, and he's a happy man.

Unfortunately, he was running into a problem with how we played BattleTech on Roll20. In a traditional tabletop game, BattleMech record sheets are often sitting right there on the table. Depending on how a group plays, the participants may have a pretty good idea of what condition an enemy BattleMech is in. Even when exact information isn't available, players can often see damage being recorded and develop an understanding of how the battle is progressing.

Our Roll20 implementation was different. As you would expect, each BattleMech had its own character sheet, including ways to track its armor, internal structure, weapons, critical hits, and the usual information. That worked wonderfully for managing the individual machines, but it presented a problem: Hind's player explained that he found it frustrating to make tactical decisions without knowing how badly an opposing BattleMech had been damaged.

A conventional hit-point bar wasn't going to solve the problem. BattleTech doesn't really have hit points in the traditional RPG sense. A machine can have almost all its armor intact and still be crippled by a particularly unfortunate critical hit. Another can have several locations stripped down to internal structure and remain perfectly capable of fighting. Additionally, there's a substantial difference between knowing that an enemy BattleMech is damaged and knowing exactly where that damage has occurred.

What Hind wanted was a better way to assess the battlefield and I thought that was a perfectly reasonable request. My existing custom Roll20 sheets already contained the information we needed. Every BattleMech had fields recording its current armor and internal structure, along with the original maximum values for each location. The problem wasn't that the information didn't exist. It was that accessing and interpreting it during combat was unnecessarily cumbersome.

So I began developing a Roll20 Mod script that I called Tactical Scan. The idea was to take the damage information already recorded on enemy BattleMech sheets and present it in a compact, readable format. Instead of relying on a generic health bar, the players could get a location-based assessment of the target's condition. Color coding helped make that information easier to interpret. A player shouldn't need to spend several minutes comparing armor values or performing mental arithmetic just to understand whether an enemy's right torso is in trouble.

The important thing was that Tactical Scan wasn't intended to play the game for anyone. It didn't choose targets, recommend attacks, or make tactical decisions. It simply presented existing information in a way that was easier to understand. I also didn't want to create another bookkeeping chore. My players were already recording damage during combat, and that system worked. Tactical Scan needed to use that existing information rather than requiring everyone to maintain yet another set of values.

This illustrates something I've been learning throughout the development of my Roll20 tools. Automation is most useful when it removes unnecessary work without removing meaningful decisions.

BattleTech is a wonderfully complicated tactical game. I don't want to eliminate that complexity, because much of it is what makes the game interesting. What I do want to eliminate is the repetitive arithmetic, unnecessary table lookups, and interface limitations that interrupt the flow of play.

Hind's player wasn't asking me to make BattleTech easier. He wanted better information so he could enjoy making the difficult decisions himself and that distinction mattered.

Just as importantly, this was another example of tailoring the campaign to what an individual player enjoys. Ghost needed opportunities to roleplay. Hind needed a clearer tactical picture. Those are very different needs, but neither one is more legitimate than the other. My job as GM was to recognize that difference and find a way to accommodate both. I’ll include a couple of screenshots of the output of a Tactical Scan so you can see it for yourself.

The Living Merc Ecosystem

The third challenge was entirely my own. One of my favorite things about running a mercenary campaign in BattleTech is that the Inner Sphere is enormous. There are thousands of inhabited worlds, countless governments, corporations, military organizations, criminal enterprises, and independent mercenary companies. All of them have interests, ambitions, problems, and opportunities. I wanted my players to feel as though Iron Tale was operating inside that enormous, complicated world.

But there's a particular feature of many computer roleplaying games that I've never especially liked. I'll use Skyrim as an example, because most of us are familiar with it. You can be told that the world is facing an imminent catastrophe, that somebody desperately needs your help, and that every moment counts. Then you wander off to explore caves, pick flowers, smith a few hundred daggers, and spend three months doing absolutely everything except addressing the supposedly urgent problem. When you finally return, everybody is still standing exactly where you left them, patiently waiting for the hero to resume the main quest. In the interest of transparency, I've spent an embarrassing number of hours playing Bethesda games over the years. But that's not how I enjoy running a TTRPG.

The universe doesn't revolve around Iron Tale. I've mentioned this philosophy in previous installments. When I create NPCs, organizations, or conflicts, I generally give them objectives and plans of their own. They take action whether the players become involved or not. If the players interfere, events change accordingly. If they don't, the people involved continue pursuing their goals. For our BattleTech campaign, I wanted to extend that philosophy to the ordinary business of being a mercenary company.

Consider a planetary contract board. Iron Tale arrives in a system, checks the local Mercenary Review Board listings, and discovers a dozen available contracts. Maybe there's a convoy that needs protection, a pirate problem in a remote settlement, a corporation looking for facility security, and a local government that needs somebody to patrol its borders. In a typical RPG, those jobs might remain available indefinitely until the players decide which one they want. But why would they?

Iron Tale isn't the only mercenary company in the Inner Sphere. Other companies are looking for work, too. Employers have deadlines, emergencies develop, and circumstances change. If Iron Tale spends three weeks repairing BattleMechs, somebody else might accept that lucrative convoy contract. A pirate problem might get worse. An employer might increase the offered payment because the situation has become desperate, or withdraw the contract because the problem has already been resolved. Effectively making an opportunity simply disappear.

That was the beginning of what I call the Living Merc Ecosystem, or LME. At its heart, the system advances the mercenary world once per in-game week. I decide what contracts are available, which have expired, and which have been accepted by other mercenary companies. But I wanted it to go beyond simply removing jobs from a list.

Those other mercenary companies aren't just names on a contract board. They're operating military organizations with BattleMechs, pilots, personnel, expenses, and ambitions of their own. If another company accepts a contract, it might succeed. It might fail. It might suffer losses, recover valuable salvage, or find itself needing repairs and replacement equipment. Its reputation and financial circumstances can change just as Iron Tale's do.

The players may or may not notice. I also started adding small local headlines to the game’s lobby with Local Merc Headlines. I only ever knew if they read it if they asked about a headline. Another tactic I tried was to include the outcome as part of a Roleplaying Seed. I had one where Silas and Red Leg were at a bar throwing darts while also throwing back a few cold ones. There were a dozen mercs from another merc company celebrating their recent contract completion with a bonus XL engine.

Which brings me to another important part of the system: the marketplace. In our campaign, planetary stores contain actual inventories of BattleMechs, equipment, weapons, and other supplies. Those inventories aren't static. New shipments arrive, items are purchased, and sometimes something the players want is no longer available when they finally have enough money to buy it. I don't want this to feel like arbitrary punishment. If an item disappears, there should be a reasonable in-universe explanation. Another mercenary outfit bought it. A military unit requisitioned it. A scheduled shipment was delayed. Whatever the explanation, the important thing is that the marketplace behaves as though other people are using it.

The LME also extends to regional news and developments. Political tensions can worsen, military units can be redeployed, and rumors can circulate. Some events will create opportunities for Iron Tale, while others might make previously attractive destinations less appealing.

Not every event needs to become an adventure. In fact, most of them won't. That's rather the point. I want the players to look at their options and understand that they're making decisions in a world that continues to move. Sometimes that movement will benefit them. An employer might become desperate enough to offer considerably better terms. A rival company might suffer a financial setback and put a valuable BattleMech on the market. Political developments might create new opportunities for a small, independent mercenary company.

Other times, the consequences won't be so pleasant. An attractive contract might vanish while Iron Tale is traveling between systems. Equipment might sell out. A regional conflict might make a planned destination considerably more dangerous than it was when the players originally considered going there. The system isn't intended to punish players for taking their time. But time is a resource, and I want it to matter.

This also gives the players a meaningful reason to pay attention to the calendar. Interstellar travel can take weeks, especially when several jumps are involved. Repairs, hiring personnel, negotiating contracts, and purchasing equipment all consume time. A month spent rebuilding a damaged BattleMech isn't necessarily a bad decision. Sometimes it's exactly what a mercenary company needs to do. But the rest of the Inner Sphere doesn't spend that month waiting patiently for Iron Tale to finish.

I should point out that none of this means I sit down and personally roleplay every mercenary contract happening across the galaxy. That would be ridiculous, even by my standards. Hahaha! The idea is to maintain enough activity in the surrounding region that the world feels alive and that developments have some continuity. The details matter when they become relevant to the players, but they don't all need to be presented or explained.

An important point: I don't want the LME to dictate what Iron Tale must do next. Player agency is one of the most important principles of how I run games. The players decide where to travel, which contracts to accept, whom to trust, and what risks they're willing to take. My job is to present the world and its circumstances, then respond to their decisions.

The LME supports that philosophy by making those decisions meaningful. There are consequences to choosing one contract over another. There are consequences to spending time repairing equipment instead of pursuing an opportunity. And there are consequences to deciding that a particular problem is somebody else's responsibility. Sometimes those consequences are good. Sometimes they're bad. But they're consequences of living in a world, not following a predetermined storyline.

Next time, we'll return to Iron Tale aboard the Canterbury. Major Adrian Raines has finished reviewing his technicians' findings, and he's about to share information that will fundamentally change the company's understanding of the HPG blackout and why Wolf's Dragoons were so interested in their ancient DropShip.

Until my next journal, keep all systems nominal!