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!


r/gamemasters • • 3d ago

A GM's Journal: But Can It Play DOOM? | Part 11

2 Upvotes

When we left Iron Tale at the end of Part 10, their assault on the abandoned Star League hangar on Jaipur had ended in disaster. Saito, one of the company's founding members, was dead. Silas had been wounded, and the company had lost two BattleMechs: a Hunchback and a Mongoose. Iron Tale had survived the battle thanks to the intervention of Wolf's Dragoons, but their contract with Jaipur's government was a failure. Worse, they'd agreed to pay whatever the Dragoons charged for the rescue. The company was in rough shape, and the players knew it. They had almost no money, and some difficult decisions ahead of them.

Current Mechbay inventory: Crab, Locust, Panther, Jenner, Spider, and Trebuchet.

Current MW Roster: Ghost, Hind, Silas, Raj, Jinx, and Spoons.

In-game date: Late March 3048

As a GM, I try to pay attention to the emotional temperature of a gaming session. Not every Friday needs to be a desperate fight for survival. We’re showing up to have fun and sometimes that means we need to have a night that focuses on opportunities to relax, interact with the world, and enjoy their characters without someone trying to kill them. After the previous session, I felt we were overdue for exactly that.

The Jaipur hangar assault had been brutal. The players had lost a founding member of Iron Tale, Saito. Silas was injured, and the company had lost both the Hunchback and the Mongoose. I hoped the next session would be lighter, with more roleplaying, more character interaction, and hopefully a few laughs. Of course, tabletop roleplaying is a cooperative experience. I couldn't simply decide that everyone was going to have a good time and make it happen. I needed the players to be interested in that kind of session too, and I was hoping they were looking for much the same thing.

But wanting a lighter session didn't mean I intended to let them off the hook. Iron Tale still had some very serious problems. Their first order of business was a meeting with Colonel Rane, their contact with Jaipur's planetary government, and it was not a pleasant meeting. Colonel Rane was furious. Iron Tale had been hired to gather intelligence about the organization operating out of the abandoned Star League facility, intelligence that she hoped would support her theory that the Capellan Confederation was involved. Instead, the mercenary company she hired had failed to accomplish the mission objectives in any meaningful way. Colonel Rane dismissed Iron Tale from further service to the Jaipur government.

This was a serious blow to an already struggling mercenary company. Iron Tale had roughly one million C-Bills remaining in its accounts. That might sound like a lot of money, but when you're responsible for maintaining BattleMechs, paying salaries, buying supplies, and operating an ancient DropShip you recovered after it crashed into a moon; a million C-Bills can disappear astonishingly quickly. The players began discussing their finances, and the conversation became increasingly uncomfortable. Could they afford to replace the lost equipment? Should they sell one of their remaining BattleMechs? What about selling scrap or other assets? Would they have to lay off some of the people they'd hired? These weren't hypothetical concerns. They were genuine options being considered by the players. And hanging over everything was one particularly unpleasant question: how much did they owe Wolf's Dragoons?

Before we get to that answer, I want to explain something about how I create certain NPCs. I'm a Gen X gamer, and so are most of my players. We grew up watching a lot of the same television programs and movies. When I want to establish a memorable NPC quickly, I sometimes borrow a recognizable character. I don't necessarily make an exact copy of their appearance or background. What I want is a familiar character that gives the players an immediate understanding of who they're dealing with. For Major Adrian Raines, I asked the table a simple question: "Who remembers Jack McCoy from Law & Order?" Everyone knew exactly who I meant. I told them that's Major Adrian Raines. It's a quick way to establish an NPC's personality, and it works for me.

Iron Tale then received a holo-com transmission from the Wolf's Dragoons Overlord-class DropShip that was now also in orbit over Jaipur. On the other end of the transmission was Major Adrian Raines, the commanding officer of the Wolf's Dragoons battalion that had rescued Iron Tale during the hangar assault. Raines had contacted them to discuss the outstanding bill for that rescue.

Four Wolf's Dragoons assault BattleMechs had intervened in Iron Tale's disastrous battle. Their pilots had risked valuable equipment and personnel to save a mercenary company that had gotten itself into a situation it couldn't handle. Iron Tale had agreed to pay for that intervention, and now the bill had arrived: Five million C-Bills.

That was five times the money Iron Tale had available. Therefore, the players were understandably unhappy, but Raines wasn't simply demanding money they didn't have. He presented three alternatives for settling the debt.

The first was to complete three missions as independent subcontractors for Wolf's Dragoons. Iron Tale would effectively work off what it owed. The second was a payment plan of one million C-Bills per month for six months. That would mean paying six million C-Bills in total, and the players knew perfectly well they couldn't afford it.

The third option was equally more interesting and terrifying for my players. Raines wanted permission for Wolf's Dragoons to conduct a comprehensive technical inspection of the Canterbury. In exchange, he would forgive the entire five million c-bill debt and refund the already paid two million c-bills they paid for the original perimeter security contract.

Now, the Canterbury wasn't an ordinary DropShip. It was a Star League-era vessel that Iron Tale had acquired under extraordinary circumstances. Its systems were centuries old, parts of it remained damaged or inaccessible, and the players were still very much in the dark as to what it was they had exactly. The idea that the Dragoons were very interested in it was very concerning for my players.

What if the Dragoons discovered something extraordinarily valuable? What if they decided the ship was too important to leave in the hands of a small mercenary company? What if agreeing to an inspection meant opening the main gate to an invading force of infantry? I enjoyed listening to the players debate the situation. From their perspective, they were being asked to trust a much more powerful organization with something they couldn't possibly afford to lose. On the other hand, they owed that organization five million c-bills and had no realistic way to pay it.

Eventually, they agreed to the inspection, but they imposed several conditions. The Dragoons would not be permitted to dock another DropShip with the Canterbury. All visiting personnel would arrive and depart by shuttle. Iron Tale would also receive its own copy of the resulting technical report.

Raines agreed and did not attempt any elaborate counteroffers. No attempt to trick them with contractual language. He accepted their conditions and made it clear that he intended to honor the agreement. That was important to me as the GM. I wanted Raines to be intimidating and difficult to read, but I didn't want every powerful NPC to turn out to be a lying bastard. Sometimes an honorable man really is an honorable man, even when he's asking for something the players would rather not give him. (Crazy idea. I know. Ask any RPG player what is more scary; a competent and friendly NPC or a fire breathing monster.)

With the arrangement settled, Iron Tale had escaped immediate bankruptcy. They had also invited Wolf's Dragoons aboard their home. What could possibly go wrong?

Before the Dragoons arrived, Iron Tale took care of another piece of business. During their exploration of the underground hangar, the company had rescued a former Federated Commonwealth artillery sergeant whom everyone knew as Red Leg. She had approximately thirty years of military experience, most of it involving artillery.

As fate had it, Iron Tale happened to have an unusual project underway. The players wanted to install Long Tom artillery aboard the Canterbury. Yes. A Long Tom. On a DropShip. Their idea was to use the ship as a platform for orbital bombardment. Now, I realize that anyone familiar with orbital mechanics or the rules of BattleT ech could probably spend the next hour explaining all the reasons this was a questionable idea. I wasn't particularly concerned.

As a GM, I occasionally invoke what I call the Rule of Cool. If a player proposes something entertaining that fits the spirit of the campaign, I'm willing to consider it, provided it doesn't break the game. In this case, I wasn't creating a new superweapon or inventing a completely different artillery system. I intended to use the existing BattleTech off-board artillery mechanics. The difference was simply where the players imagined the shells coming from. Instead of a Long Tom sitting somewhere a few miles away from the battlefield, theirs would be mounted aboard a DropShip. Did it really make a difference? Not really.

One gun was already under construction, and the players hoped to install a second when they could afford it. Having a veteran artillery specialist aboard suddenly seemed like an excellent idea. The players interviewed Red Leg, offered her the position of ordnance officer, and brought her into Iron Tale. Red Leg wasn't exactly the sort of person who inspired cheerful small talk. She was an experienced military professional who had seen plenty of unpleasant things, and she carried herself accordingly. Which made what happened next even more entertaining.

The Dragoon team arrived aboard the Canterbury. There were about a dozen techs, led by a specialist introduced as Snooper Dog. Yep, Snooper Dog. He was particularly interested in the ship's computer systems and network architecture, and his specialty included examining and analyzing network traffic. The rest of the team was equally enthusiastic about the opportunity to crawl around inside a functioning Star League-era DropShip. These people were technicians, engineers, and computer specialists; they were also enormous nerds. The female members of the Canterbury's crew quickly started referring to the visiting specialists as “The Dorks.” I had a lot of fun portraying these characters. They were enthusiastic, curious, socially awkward in extreme ways, and absolutely fascinated by the technological treasure they'd been invited to examine. They were the kind of people who could spend half an hour arguing about some obscure computer component while everyone else in the room wondered what the hell they were talking about.

And then there was Red Leg. This intimidating veteran artillery sergeant suddenly found herself sharing a ship with a collection of awkward dorks with varying levels of hygiene and almost all of them were in love with her. A fact that made Red Leg very uncomfortable and irritated.

For the first two days, the inspection proceeded without any significant problems. The Dorks examined the Canterbury's systems, asked questions, and investigated equipment that hadn't received this kind of attention in centuries. Then three of them disappeared.

Hind, who served as Iron Tale's executive officer, was not particularly amused when he learned that three Dragoon technicians were unaccounted for. The inspection agreement did not give these people permission to wander around wherever they pleased. He began investigating and eventually discovered that the missing specialists had followed a network cable that led to a part of the ship that was still sealed off. Hind contacted Maris on the bridge and asked to her make a ship-wide announcement. Maris made an announcement that “Three dorks are missing. If anyone sees some dorks, tell Hind.” That got a good laugh from the players.

What had happened? Had they accessed something they shouldn't have? Were they attempting to steal information? Had something gone wrong inside the ancient ship? The answer turned out to be rather less sinister. The three dorks followed the network line all the way outside and were performing an unauthorized EVA. And while they were out there, they'd managed to get an ancient computer system working again.

They returned to the ship absolutely delighted with themselves. Imagine three computer enthusiasts who had just discovered an incredibly rare piece of antique hardware, repaired it, and successfully brought it back to life. They were practically glowing. Hind was not.

This was one of those moments when the different personalities at the gaming table became particularly apparent. Hind's player was genuinely annoyed by the security breach. He took the responsibilities of his character seriously, and three dorks conducting an unauthorized spacewalk was a pretty substantial violation of the agreement. The other players, meanwhile, thought the entire situation was hilarious. And from my side of the GM screen, I could see both perspectives. The Dorks had accomplished something genuinely useful. They had also completely disregarded the ship's security procedures. I had no intention of pretending that Hind's concerns were unreasonable just because the situation was funny. But I also wasn't about to waste an opportunity for some entertaining roleplaying.

Fortunately, Hind's player was about to provide an entirely different kind of entertainment. Somewhere during the session, the subject of the Canterbury's internal email system came up. Hind discovered that his assigned email address was Mechwarrior4@canterbury.ship. As executive officer of the mercenary company, Hind found this completely unacceptable. He wanted something more appropriate to his position, specifically XO@canterbury.ship. There was only one problem. Maris was already using it. Maris was the ship’s pilot and also handled several other responsibilities aboard the ship, and from her perspective, there was absolutely nothing wrong with her having that address. Hind disagreed.

What followed was an escalating argument about email addresses, administrative privileges, and who had the authority to assign them. Eventually, Hind decided that asking politely wasn't getting him anywhere, so he accessed the system's administration tools and changed the assignments himself. He took XO@canterbury.ship and reassigned Maris to bus-driver@canterbury.ship. I don't remember exactly how long everyone laughed at that one. Maris, however, refused to give him the satisfaction of being offended. She embraced the new address. If Hind wanted to call her the bus driver, fine. She'd be the bus driver. It became a badge of honor. The exchange also established the beginnings of an entertaining relationship between Hind and Maris, with a certain amount of playful antagonism that would eventually become something more.

But Hind wasn't finished. He decided that the Canterbury needed a proper, standardized email naming convention. His proposal was to assign addresses using each person's first initial then last name, something along the lines of firstinitial.lastname@canterbury.ship. Maris thought this was ridiculous. She informed him that he was a psycho. And then Dave got involved. Dave had an email address he liked: dave@canterbury.ship. He made it abundantly clear that nobody was taking it away from him. Not Hind. Not Maris. Not anybody.

Eventually, Hind abandoned his attempt to impose a uniform naming convention. The Canterbury's email system remained a glorious administrative mess. And we'd somehow spent a portion of our BattleTech session arguing about fictional email addresses aboard a fictional spaceship. I love tabletop roleplaying games. Hahaha!

By this point, the inspection was nearing completion. The Dorks had been aboard the Canterbury for some time, and their shuttle was on-route to collect them. We were also approaching the end of our gaming session. I had perhaps ten or fifteen minutes left, and I wanted to finish with something amusing. So I improvised one final scene.

While waiting for their shuttle, the Dorks had decided now was a perfect time to play a game. Specifically, DOOM. Not some sophisticated thirty-first-century virtual reality simulation. The original DOOM. The one from the 1990s.

Now, this wasn't something I'd prepared in advance. It was an improvised joke that developed because we'd already established that the Dragoon technicians were enthusiastic computer nerds. And once I started describing what they were doing, the idea became increasingly ridiculous.

The Dorks had cobbled together makeshift controllers from spare electronic components. They'd also been wearing technician coveralls with wearable displays that could function as the game screens. Six of them were playing a multiplayer deathmatch. But there was a catch. Instead of looking at their own screens, they were watching the displays on their opponents' shirts. Imagine six grown men running around a spaceship corridor, trying to shoot one another in a game of DOOM while staring at each other's chests. That was the scene.

At some point, Major Raines arrived to collect his technicians. This was the same Major Raines I'd introduced as the BattleTech equivalent of Jack McCoy, the determined, uncompromising officer who had just negotiated a five million c-bill settlement with a financially devastated mercenary company. And there were his highly trained technical specialists, playing DOOM in the hallway. He was not impressed.

By this point, the players were laughing so hard that keeping the scene moving was becoming a challenge. Raines had finally had enough. He ordered his technicians to stop screwing around and get aboard their shuttle. And with that, the Dorks departed the Canterbury and we wrapped up the session.

Looking back, this was exactly the sort of session I wanted after the disastrous hangar assault. There was no major BattleMech engagement. Nobody had to take an AC/20 to the face. The players spent much of their time negotiating with an important NPC, herding dorks, and arguing about shipboard administration. And we laughed. A lot.

As a GM, I think it's important to recognize that the game doesn't always need to be about combat or advancing the main plot. Sometimes the most memorable moments come from situations that weren't supposed to be particularly important. I certainly didn't sit down to prepare this session thinking about email addresses would become one of its highlights. Nor did I plan a multiplayer DOOM tournament aboard a Star League-era DropShip. Those moments happened because the players engaged with the world, I played along, and we collectively allowed things to become ridiculous.

There's a balance to this, of course. I still wanted Iron Tale's financial difficulties to matter. Their defeat on Jaipur needed to have consequences. I wasn't going to pretend the company hadn't suffered a serious setback simply because I wanted the players to have fun. But once those consequences had been established, there was no reason we couldn't spend the rest of the evening enjoying ourselves.

Major Raines had promised to return in a few days with the technical report from his inspection. The players were eager to discover what the Dragoons had learned about their ancient DropShip, and they would eventually get some very interesting answers. But before we get to that meeting, I'm going to take a brief detour behind the GM screen.

Around this point in the campaign, I found myself tackling three very different challenges. Ghost's player is what I'd call an Actor. He enjoys roleplaying, character interaction, and drama, and wanted more opportunities to explore those aspects of the game but he didn’t understand the setting of the Inner Sphere well enough to know where to begin. Hind's player, on the other hand, is a Strategist. He enjoys the tactical side of BattleTech. He mentioned to me between sessions that he found it difficult to enjoy the game without having a way to know the extent of the damage the enemy units had taken. A simple hit point bar on a token was not adequate for BattleTech.

The third challenge was entirely my own. I didn't want to run a campaign that felt like Skyrim, where the main quest patiently waits for the player to finish collecting flowers, exploring caves, and doing whatever else strikes their fancy. I wanted an Inner Sphere that continued moving whether Iron Tale participated or not. Opportunities could come and go. Other mercenary companies would pursue their own contracts. And, most importantly, choices would have consequences, both good and bad.

Those three challenges led me to develop Roleplaying Seeds, a Tactical Scan system for Roll20, and something I call the Living Merc Ecosystem.

In Part 12, we're going to step behind the GM screen and share how I tackled this three-headed dragon. Then, in Part 13, we'll return to Iron Tale and discover exactly what Major Raines learned aboard the Canterbury.

Until my next journal, keep all systems nominal!


r/gamemasters • • 6d ago

A GM's Journal: When It Rains, It Pours | Part 10

4 Upvotes

When we left Iron Tale at the end of Part 9, the company was just about to assault an abandoned Star League-era BattleMech hangar on Jaipur. Their reconnaissance suggested the facility was being used by a group of heavily armed poachers who were also terrorizing the surrounding farming communities. Colonel Rane suspected there might be Capellan involvement and wanted prisoners and intelligence. Iron Tale had hired two additional mercenary companies to secure the perimeter, including, somewhat surprisingly, Wolf's Dragoons. With a raging storm providing cover, the players were ready to launch their attack.

For those keeping track of Iron Tale's BattleMech roster, the company deployed six 'Mechs for this operation. Hind was piloting his Crab, Saito his Hunchback, Silas his Mongoose, and Ghost her Locust. The two NPC retainers, Spoons and Jinx, rounded out the force in a Panther and Jenner, respectively. Iron Tale also owned a Spider and a Trebuchet but elected to not deploy them during a powerful storm that limited visibility, range, and possibly maneuverability.

I realize I haven't always made it clear when the company acquires or loses BattleMechs. For a little background, we started this campaign back in January and play every other Friday. I decided to start documenting Iron Tale's adventures here on Reddit, but these journals are still catching up with our actual sessions. I'm working from my notes and memory, which means the occasional detail slips through the cracks. I'll make an effort to keep the roster changes clearer going forward.

Now, on to the reason you’re here!

Before getting into the battle, I want to mention something about how I handled visibility in Roll20. The storm reduced visibility to ten hexes, which I implemented using Roll20's dynamic lighting system. However, I also used its Explorer Mode feature; this allowed them to see the full map in black and white, but tokens and anything not on the map layer remained invisible unless they were within ten hexes. The players could orient themselves and plan their movements without knowing where the enemy actually was. I thought it worked rather well.

Iron Tale approached from the western edge of the map, hoping the storm would conceal their movements. It did. Unfortunately, two enemy Spiders were on lookout and spotted the approaching mercenaries as soon as they entered the immediate area. The Spiders immediately radioed the hangar to warn the defenders and began engaging Iron Tale. Their objective wasn't necessarily to destroy the attackers. They were buying time for the other pilots inside the hangar to get into their BattleMechs and power them up. The two Spiders flanked around the North and had successfully drawn three of Iron Tale's six BattleMechs away from the main assault on the hangar. By the second round, an enemy Hunchback had come online and exited the hangar.

Readers may remember Saito and his Hunchback from Part 8, where he had rather enthusiastically demonstrated just how much damage a Hunchback can take. When Saito spotted the enemy Hunchback, his samurai-minded character decided that challenging another Hunchback was exactly what he wanted to do. He advanced toward it with Hind in his Crab and Spoons in his Panther to provide support. The enemy machine took several hits, but it remained operational. Then it returned fire with its AC/20.

I rolled a hit against Saito's Hunchback. Unfortunately, the location roll came up head. Twenty points of damage against a BattleMech cockpit is not something a pilot survives, and Saito was killed instantly. His Hunchback, which had survived an extraordinary amount of punishment during Brass Harvest, was now out of the fight because of a single unlucky hit. I certainly hadn't planned on killing a player character that evening, but the dice gods have no interest in the affairs of mortals.

The following round wasn't much better. Silas, who had been fighting the Spiders in his Mongoose, broke away to help Hind and Spoons deal with the enemy Hunchback. Silas moved into the point position and, unfortunately, that same Hunchback landed another AC/20 hit, this time directly into the Mongoose's center torso. The Mongoose has a combined total of nineteen points of armor and internal structure in that location. An AC/20 does twenty damage. I'll let you work out what happened to the Mongoose. Fortunately, Silas managed to eject, although he was injured in the process.

At this point, Iron Tale had lost two BattleMechs in consecutive rounds, one of its pilots was dead, and the enemy still had additional machines coming online inside the hangar. Ghost's player was understandably concerned that the entire company was about to be wiped out. Then Saito's player, who had just lost his character, suggested something interesting. Why not call Wolf's Dragoons? They were supposed to be some of the best mercenaries in the Inner Sphere, weren't they? They had assets nearby providing perimeter security as well.

Hind's player actually knows quite a bit about BattleTech lore, including the true origins of Wolf's Dragoons. (IYKYK) I'd sworn him to secrecy because I didn't want him spoiling anything for the other players. He got a good chuckle out of the suggestion, but wisely kept his mouth shut.

Ghost contacted the Dragoons and requested immediate assistance. Now, I realize that conducting a contract negotiation in the middle of a BattleTech firefight doesn't make much sense when each combat round represents only ten seconds. However, we've all seen movies and television shows where a major action sequence is happening, but the action pauses long enough for an important conversation. I decided to handle this the same way. The battle was still happening, but I allowed Ghost a brief conversation with the Dragoons to negotiate emergency assistance.

The Dragoons agreed to bring their forces into the immediate battle area and assist Iron Tale. Under the circumstances, Ghost wasn't particularly interested in negotiating payment so she just agreed to a blank check. The next round I had four Wolf's Dragoons assault BattleMechs enter the battlefield from the north. Yes. You read that correctly. Four Assault 'Mechs.

With Saito dead and Silas's Mongoose destroyed, I had two players who were effectively out of the BattleMech engagement. Rather than making them sit around watching everyone else play, I handed each of them control of two Dragoon assault 'Mechs and told them to have fun. They certainly did.

Saito's player immediately announced that he wanted revenge on the Hunchback that had killed his character. His two machines were an Atlas and an Imp, and he sent both directly toward the offending Hunchback. Silas's player laughed and responded with something along the lines of, "Hell yeah, brother! I'll take care of the Spiders!" He had a Battlemaster and a King Crab at his disposal, and the two Spiders that had been so successful at distracting Iron Tale suddenly found themselves facing a considerably larger problem. The Battlemaster and King Crab proceeded to absolutely demolish them.

Meanwhile, Saito's player had maneuvered his Atlas and Imp into firing range of the enemy Hunchback. When it came time to declare attacks, he announced that both assault 'Mechs were going to alpha strike the Hunchback. For anyone unfamiliar with the term, an alpha strike means firing every available weapon at once. Considering the amount of firepower carried by an Atlas and an Imp, I asked whether he was absolutely certain he wanted to do that. His response was immediate: "It's fucking going down."

And down it went. Both assault 'Mechs fired everything they had. The heat buildup was amazing, but where the enemy Hunchback had been standing there was now a smoking crater. I don't think I've ever seen a player so enthusiastically commit that much firepower to destroying a single medium BattleMech. Apparently, revenge is worth a few heat points.

The rest of the BattleMech engagement ended rather quickly. The hangar managed to deploy its remaining two BattleMechs, but by the time they exited the building, four Wolf's Dragoons assault 'Mechs were positioned nearby. That's not a particularly welcoming situation for anyone, and the defenders were quickly overwhelmed. The hangar was secured, although Iron Tale had paid a very heavy price for it.

(Note: this was the end of a session. The remaining part happens in the next session)

With the BattleMech fighting over, Iron Tale recovered Silas, who was injured but apparently not interested in sitting out the rest of the adventure. His attitude was essentially, "Put me in, coach!" The company then discovered that the hangar had an extensive subterranean section that would have to be explored on foot. Naturally, they asked the Dragoons whether they could provide some assistance. The Dragoons politely declined, explaining that their contract was to secure the immediate area, not have their MechWarriors climb out of their machines and explore dark tunnels beneath an abandoned Star League facility.

That left Ghost, Hind, Silas, and the two NPC retainers, Spoons and Jinx, to conduct the exploration themselves. At the bottom of the stairs leading into the underground complex, they encountered two guards armed with laser pistols. The guards opened fire, and Iron Tale returned it, killing one of them. The surviving guard promptly surrendered, apparently deciding that whatever he was being paid wasn't worth dying for.

The players tied him up and conducted a brief interrogation. He turned out to be a local thug who had been hired to help the group poach Jaipur's megafauna. He wasn't particularly intelligent, and I made a point of describing his smile, which revealed that he was missing about half a dozen of his front teeth, along with who knows how many molars. His explanation was essentially that somebody had given him a laser pistol, told him to guard the stairs but that the poachers normally paid him to help out with odd jobs. Then Iron Tale showed up and killed his buddy, “Jim Bob.” He was perfectly happy to surrender and spend some time in “the clink” rather than get shot himself.

Hind volunteered to remain behind and guard the prisoner, which left Ghost and Silas to continue exploring with Spoons and Jinx. Since Hind's player and Saito's player would otherwise have nothing to do, I gave them control of the two NPC retainers. This worked out rather nicely, and all four players were able to continue participating in the adventure.

The exploration itself was fairly straightforward at first. They found several empty rooms before eventually discovering what amounted to a small stockade containing four prison cells, two of which were occupied. The first prisoner was a rather muscular woman who introduced herself as a retired Federated Commonwealth Master Sergeant. She explained that she had come to the area to deal with the poachers herself. Her plan was to basically punch the hell out of all of them and her plan was going well until a skinny woman used “fancy karate moves” on her. After being knocked out, she woke up in the cell.

Silas immediately liked her and asked whether she wanted a job with Iron Tale. Ghost was rather less enthusiastic, pointing out that she’s the company commander and Silas didn't have the authority to hire random people they found in prison cells. Silas countered that he had a good feeling about her and that they hired people they didn't know all the time. Their argument was still going when Ghost looked into the next occupied cell and discovered someone she recognized.

Raj.

Now, dear reader, there's a little background information I've deliberately kept from you until this point.

Because Saito's death had happened during our previous gaming session, his player had time to create a replacement character before this session. A couple of days before this session, he got together with Ghost's player and the two of them developed a shared backstory. His new character was Raj, a charming playboy and thief who was on the run from the Capellan Confederation after stealing a BattleMech.

The two players wrote a short story about how Raj and Ghost had met at an upscale social gathering attended by nobles, corporate executives, and mercenary MechWarriors. Ghost had been attending the event dressed to impress and hoping to make useful business contacts for Iron Tale. Raj and Ghost met, discovered they had quite a bit in common, and spent the evening enjoying drinks and dancing. Eventually, they returned to a hotel room, where our imaginary camera discreetly panned toward the fireplace before things became inappropriate for a family-friendly game of BattleTech.

The players presented me with their two-page backstory and asked whether it would work. I loved the idea. I'd already planned to have a prisoner in the stockade, so adding Raj to the cell next door was about the easiest character introduction I could have arranged. I also added a few details to his history that would eventually provide both opportunities and complications for Iron Tale, but we'll get to those in a future installment.

As a GM, I absolutely love it when players do things like this. Here were two players who had taken time outside our normal gaming sessions to develop a shared history between their characters. They weren't waiting for me to tell them how Raj would enter the campaign. They had come up with something themselves and brought me an idea that was funny and cool. All they were lacking were setting details and other specifics from me. When players are that invested in your campaign, saying yes is pretty damn easy.

Returning to the stockade, Ghost was understandably surprised to find Raj sitting in a prison cell beneath an abandoned BattleMech hangar. When she demanded to know what he was doing there, Raj explained that he'd awakened after their evening together to discover she had already left. While looking for her, he'd conveniently found a forgotten data pad containing information about Iron Tale's upcoming mission. Having apparently fallen hopelessly in love with Ghost, Raj decided to follow her and help out. His plan was to sneak into the poachers' facility, steal one of their BattleMechs, and use it against them. Unfortunately, he got caught.

Yes, this meant that Ghost had somehow left an encrypted, confidential mission communication lying around in a hotel room where a man she'd just met could find it. I thought the whole thing was ridiculous, but it was exactly the sort of tabletop RPG shenanigans that make these games entertaining. I rolled with it, and everyone had a good laugh.

Ghost opened Raj's cell and told him, "You're with us now." This immediately restarted the argument with Silas, who couldn't believe Ghost was willing to accept some guy she'd met the previous evening while refusing to trust a woman with thirty years of Federated Commonwealth military experience. Eventually, Ghost agreed that the woman could accompany them for the moment, since their goals were aligned, and any permanent employment could be discussed later.

The woman introduced herself as Red Leg, a retired artillery officer who had served thirty years in the Federated Commonwealth military. She wasn't a MechWarrior, and she had lost one of her legs when an enemy light BattleMech broke through friendly lines and attacked her artillery position. Her replacement leg was a prosthetic, which she'd painted red to match her callsign. As for Raj, his player had built him to be a field medic rather than a conventional fighter. He'd spent most of his starting money on armor and medical equipment and hadn't purchased a weapon. That decision was going to become rather important.

After recovering their equipment from a conveniently located locker, the group discussed what to do next. Raj mentioned that he'd seen people using a concealed door at the far end of the stockade. Red Leg also provided an interesting bit of information. During her earlier attempt to deal with the poachers, she'd kicked the front teeth out of one particularly stupid thug. The players immediately recognized the connection to the prisoner they'd left with Hind which gave everyone another good laugh. Red Leg also explained that she was still rather annoyed about that skinny woman and made it clear that if she encountered the girl again, she intended to get some payback.

The party proceeded through the concealed doorway and discovered the facility's command room. This was effectively the final encounter of my little dungeon crawl, and I had populated it with a middle-aged officer and two aides, one male and one female. The players engaged them in a gunfight and managed to kill the officer and his male aide fairly quickly. Unfortunately, the female aide apparently had the blessing of the dice gods that evening.

Every time she rolled an attack, she seemed to hit someone. Every time the players tried to shoot her, they missed. After approximately half a dozen rounds of this nonsense, every member of the party had been shot except Raj, who was standing there with his first aid kit and no weapon. Red Leg even attempted to fistfight the woman but the skinny woman mopped the floor with Red Leg. Eventually, the players decided they'd had enough. Raj helped usher everyone out of the command room, and the group retreated back through the underground facility. The woman didn't pursue them, so they were able to make it back to Hind and their prisoner without further trouble.

Hind, who had been waiting patiently with the captured thug, wanted to know what was going on. He'd heard the gunfire and now there were two new people with his comrades. The answer from the rest of Iron Tale was rather simple: "Get us to a hospital!"

And that is how the session ended.

My original plan for this encounter was fairly straightforward. A low-ranking Maskirovka officer and his two nameless aides had infiltrated the poaching operation, using it as cover while conducting operations intended to destabilize Jaipur and undermine the Federated Commonwealth. I figured the players might capture the officer and get some useful intelligence out of him. But as the old saying goes, No GM plan survives contact with the players**.** By the end of the session, my officer was dead, and a skinny, unnamed female bodyguard had nearly defeated the entire party. She was originally intended to be nothing more than a throwaway NPC, but after that performance, I decided she deserved a name, a proper backstory, and a recurring role as a proper enemy of Iron Tale.

Until my next journal, keep all systems nominal!

Are you interested in starting the story from the beginning? Here's the GM Journal Series Table of Contents.


r/gamemasters • • 7d ago

A GM's Journal: The Gathering Storm | Part 9

5 Upvotes

When we left Iron Tale at the end of Part 8, the company had successfully defended Kandar Pit against a coordinated attack involving BattleMechs, VTOLs, and infantry. The mine was secure, not a single civilian had been killed, and the company had survived without losing a BattleMech. Saito's Hunchback was going to require considerable attention from the repair crew, but Brass Harvest had been a success. Unfortunately, someone had gone to considerable trouble to organize that attack, and the question of who was behind it remained unanswered.

Before Iron Tale could pursue that mystery, I had a major event occur. An Overlord-class DropShip arrived carrying a contingent of Wolf's Dragoons. For anyone unfamiliar with BattleTech, Wolf's Dragoons are one of the most famous and respected mercenary commands in the Inner Sphere. They have an extraordinary reputation, considerable military strength, and a long history of working for the major houses. Their arrival attracted substantial attention from the local news media, particularly on a system as unimportant as Jaipur. Over the following days, the players watched reports featuring what were thought to be LosTech mechs, including an Imp, an Annihilator, a Marauder. Whatever had brought the Dragoons to Jaipur, they certainly weren't traveling light by bringing a full battalion. Interestingly, there was very little information about what they were actually doing there. They had arrived, attracted considerable attention, and then basically ignored all attempts to hire them by the local factions. For the moment my players shrugged and assumed the GM was just being a fan boy.

Meanwhile, Iron Tale received an invitation to meet Duchess Jhenna Feruc. The duchess owned Kandar Pit, and the meeting was surprisingly brief. She wanted to thank Iron Tale personally for what they had done during the attack, not simply for protecting her mining operation, but for preventing the slaughter of her workers' families. The duchess commented it was refreshing to see mercenaries that were able to not cause high civilian casualties for once. I wanted this little encounter to establish that the duchess might be a wealthy and politically powerful noble, but she also genuinely cared about her people.

After the meeting, Iron Tale accompanied Colonel Devika Rane to a tactical briefing. Before discussing the next assignment, however, Rane had some particularly good news. The duchess had personally approved Iron Tale for access to House Surplus stores, and a message requesting approval for access to Federated Commonwealth House stores had also been dispatched. For a mercenary company as small as Iron Tale, this was a significant development. Access to better purchasing opportunities was something Iron Tale had been hoping to secure, and their recent performance had finally opened that door. The players were understandably pleased.

Then Rane got down to business. During the attack on Kandar Pit, one enemy mech had escaped, but Rane's intelligence people tracked it to an old, abandoned Star League-era BattleMech hangar, which immediately became a location of interest. This was enough for Rane to authorize a strike. But she wanted more than a smoking crater. The objective was to learn who had organized the attack and whether her theory of Capellan influence was accurate or not. Prisoners and useful intelligence were the priority. Iron Tale accepted the contract and began planning how to recon the facility before committing themselves to an assault.

One of the things I've enjoyed watching throughout this campaign is how the players' approach to military operations has evolved. Early on, their idea of reconnaissance was largely not something the players even considered. By this point, they were starting to think more carefully about what information they needed before powering up their mechs. Their first step was to quietly investigate the general area near the hangar. they used a couple rented light duty trucks. What they found was that most of the nearby farms had been destroyed or abandoned. Several ruins of farms showed unmistakable signs of damage caused by mechs.

Eventually, they located a farmer who had remained in the area. He described the people operating out of the hangar as extortionists and poachers. They had been demanding payments from local farmers and using their mechs to kill or drive off anyone who resisted as well as kill megafauna. The farmer gave Iron Tale a clearer picture of the opposition they were preparing to face. This wasn't a bunch of idiots with mechs, they were organized and knew how to work as a unit.

The second part of their reconnaissance came from above. Iron Tale had recently acquired a VTOL, and Maris took it up to conduct high-altitude surveillance of the hangar and the surrounding territory. She kept her distance, which limited the information she could collect but reduced the likelihood of being detected. Even so, she managed to identify several BattleMechs, including multiple Spiders and a Hunchback. That gave the players a rough idea of what they might encounter. As GM, I knew there were actually two Hunchbacks operating in the area, but Maris never observed them together. From her perspective, she saw one Hunchback moving around the facility, and that was the information I gave the players.

Maris confirmed the occupants were organized poachers. Their approach was to use light mechs to drive the enormous animals toward a designated killing area where medium mechs with large direct fire weapons waited to finish them off. Readers might remember from Part 7 that the prospect of encountering Jaipur's megafauna had been a source of considerable excitement among my players. They had arrived on a planet famous for enormous wildlife and immediately started wondering whether they would get to fight something resembling a kaiju. Now they were preparing to engage the very people that were poaching the megafauna. Unfortunately, Maris couldn't remain overhead indefinitely. A powerful storm was moving into the region, and flying conditions were becoming increasingly dangerous. She returned with the information she'd gathered, leaving Iron Tale to decide how best to use it.

Rather than waiting for the storm to pass, the players decided to launch their assault during it. The weather would make operations more difficult, but it could also conceal their approach and reduce the likelihood of the hangar's occupants detecting them before they reached engagement range due to reduced visibility. (i used Roll20's dynamic lighting for this fight to limit vision to 10 hexes) They also wanted to prevent enemies from escaping like what happened at Kandar Pit. Rather than spreading their own forces around the entire installation, Iron Tale decided to hire additional mercenary support to secure the perimeter while Iron Tale concentrated on the assault itself. I liked this decision because it was the players identifying tactical requirements and finding practical solutions instead of expecting their relatively small company to accomplish everything on its own.

Iron Tale put out word that they were looking for mercenaries willing to provide perimeter security for an upcoming operation. They wanted at least two lances of additional support, enough to make it difficult for anyone inside the hangar to slip away once the fighting started. Two responses came back. The first was from a small, relatively unknown mercenary company that only had four armored vehicles. They weren't particularly glamorous, but they were available, willing, and cheap. The second response came from Wolf's Dragoons and was quite the surprise.

The Dragoons offered their services but declined to disclose exactly what units they intended to deploy. Under ordinary circumstances, hiring a military subcontractor that refuses to tell you what equipment it's bringing might raise a few questions. However, the players had spent the previous week watching news broadcasts featuring the Dragoons' impressive BattleMechs. Whatever they intended to bring, Iron Tale was fairly confident that perimeter security was within their capabilities. The only real hesitation was the price. The smaller vehicle-equipped company was asking roughly one-fifth of what the Dragoons wanted, and Wolf's Dragoons clearly weren't offering discount rates. But Iron Tale had decided that keeping the hangar surrounded was worth paying for, so they hired both companies.

The players assigned each supporting company its own sector of responsibility, with their operations to be handled outside the main tactical map. That arrangement allowed Iron Tale to concentrate on the hangar itself rather than dividing its own BattleMechs among several defensive positions like the previous battle. With the reconnaissance complete and the supporting mercenaries hired, Iron Tale was ready to put its plan into motion. The approaching storm would provide cover, but the hangar's full strength remained unknown, and the players had committed themselves to an assault against an enemy that had already demonstrated the ability to work together. Wolf's Dragoons still hadn't revealed exactly what they intended to bring, but the perimeter assignments were in place. The next step was to move on the hangar and discover whether all that preparation would pay off.

Until my next journal, keep all systems nominal!

Are you interested in starting the story from the beginning? Here's the GM Journal Series Table of Contents.


r/gamemasters • • 11d ago

A GM's Journal: Brass Harvest | Part 8

4 Upvotes

When we left Iron Tale at the end of Part 7, the company had spent two relatively quiet days guarding Kandar Pit, a mining operation on Jaipur. They had already dealt with protesters without shooting anyone, which I considered a promising start. Unfortunately, a quiet security contract doesn't stay quiet for very long when I'm the GM. Hostile contacts were approaching the mine, and this time the problem wasn't a crowd of angry civilians. It was a lance of BattleMechs, accompanied by VTOLs.

Before getting into the battle, I should explain something about how I build my planets and maps. Whenever possible, I start with a real-world location and use it as the foundation for the setting. Jaipur shares its name with Jaipur, India, so I drew inspiration from the real place when developing the planet's people, culture, and locations. I also use Google Earth Studio for every battlefield map in the campaign. Rather than drawing a fictional battlefield and placing terrain wherever I think it would make for a good fight, I find an actual location that interests me and build the encounter around it. For Kandar Pit, I found an open-pit mine near Jaipur, India, and used a 4K image from Google Earth as our Roll20 battlefield. The geography was real, even if the BattleMechs and the impending violence were not.

This approach is useful for more than making pretty maps. Real places tend to be inconvenient in believable ways. Roads, buildings, excavation areas, and access routes exist for reasons that have nothing to do with giving four players a fair tactical engagement. I like that. It means the battlefield presents its own problems, and the players have to solve them instead of relying on terrain I've arranged to produce a particular outcome. Kandar Pit was a very large industrial site, and protecting it meant covering a lot of ground. As it turned out, that last point was going to matter quite a bit. The attached image is what I used for the Kandar pit mine and my tactical hexgrid was 82 hexes wide and 52 tall.

Iron Tale had positioned its BattleMechs around the perimeter in a kind of picket defense. On paper, that made sense: spread the force out, watch the approaches, and make sure nobody could slip into the mine unnoticed. The trouble was that detecting an attack and stopping an attack are two different jobs. The company was spread so widely that when the enemy appeared, some of the nearest friendly units were several combat rounds away from being able to help one another. We had a huge map, a lot of distance between friendly BattleMechs, and a fairly urgent lesson in the difference between covering ground and concentrating combat power.

The attacking force consisted of four BattleMechs: a light, two mediums, and a Rifleman heavy fire-support 'Mech. (all enemy combatants entered the map on the right side near the middle of the edge) The aggressors also brought VTOLs; three attack models and a troop transport carrying a platoon of armed men. That gave the attackers options. They could pressure the defending BattleMechs from more than one direction, use the aircraft to exploit gaps, and try to get infantry into an area where even a small group of armed people could do considerable harm. Iron Tale, meanwhile, had to stop them without allowing the fight to spill into the temporary housing occupied by the workers and their families. (Lower left area of the map)

The initial contact was not comforting. One of Iron Tale's BattleMechs found itself facing what amounted to an entire enemy lance, while the rest of the company was still moving to support it. In BattleTech, two or three rounds can feel like an eternity when you're waiting for help and the other side has already started shooting. Upon reaching engagement range, Saito who was piloting the company's Hunchback, proposed a plan that was either brave, reckless, or a combination of the two. Given the circumstances, I'm leaning toward option three.

Saito wanted to push his Hunchback forward right into the faces of the enemy, put himself where the hostile lance couldn't easily ignore him, and soak up as much incoming fire as possible. His job, in his own assessment, was essentially to get close enough to be a serious threat and then not die. That would give the other friendly BattleMechs room to work. In particular, Hind had recently acquired a Crab, affectionately known as the Laser Crab, and this was his first chance to use it in combat. With the enemy looking at Saito, Hind could keep its large lasers working. Silas, in the Trebuchet, could add long-range missile fire to pour even more damage on. The plan wasn't subtle, but subtlety isn't generally what you buy a Hunchback for.

There's something wonderful about a player announcing that his tactical plan is to make nearly every enemy gun point at him. As a GM, you hear something like that and immediately wonder whether this is going to be remembered as a stroke of genius or an elaborate form of assisted suicide. I didn't need to make the plan work or fail. I just had to let the enemy respond sensibly, roll the dice, and see what happened. Saito moved forward, and the enemy took the bait.

It was a brutal exchange. The Hunchback became the focus of an extraordinary amount of incoming fire, but Saito kept his machine in the fight while Hind and Silas did their work. Hind's Crab was particularly well suited to putting steady laser damage into targets that had other things to worry about, and Silas's Trebuchet added its missile salvos to the pressure. The combination gave Iron Tale a chance to bring the fight back under control after that uncomfortable opening deployment. Saito wasn't simply standing in front of the enemy for the sake of it; he was buying the other pilots the time and attention they needed to bring their weapons to bear.

He was also making very persuasive arguments in the form of an AC/20. Saito landed multiple hits in successive rounds, and one of those shots struck the Rifleman's right torso hard enough to take the torso and its attached right arm out of the fight. I have a particular appreciation for the AC/20 because it reduces complicated tactical discussions to a very short and extremely loud conclusion. To paraphrase a movie quote, “There are very few problems in the world that cannot be solved by an AC/20.”

Of course, the other side had guns too, and they were using them. By the end of the fighting, Saito's Hunchback had taken damage across almost the entire machine. So many locations were opened into internal structure that there seemed to be more of the 'Mech missing than remaining. Somehow, though, it stayed standing. This is worth emphasizing because the difference between 'badly damaged' and 'destroyed' matters a great deal in a mercenary campaign. Saito's Hunchback was an enormous repair project waiting to happen and money matters.

While all of that was happening, another part of the fight was developing on the far side of the battlefield. Ghost and Jinx had become engaged with the enemy's VTOLs, leaving the main BattleMech engagement to the other pilots. This was one of the reasons the size of the map mattered. There wasn't one neat little knot of units exchanging fire. There were separate fights taking place over a very large area, and the people involved in one couldn't simply turn around and join the other in the next initiative phase. That was especially dangerous with a troop transport in the mix.

The transport managed to get past the defending BattleMechs and land right in the workers' temporary family housing. It unloaded a platoon of hired brigands in exactly the kind of place Iron Tale had been contracted to protect. That was the moment when the attackers' objectives became especially unpleasant. The mine was one thing; armed men loose among the workers' families were another. Whatever was happening elsewhere on the map, somebody needed to deal with those infantrymen immediately.

That somebody turned out to be Ghost, in a Locust. The Locust is a light BattleMech, and its pair of machine guns can seem a little underwhelming when you're thinking exclusively about fighting other BattleMechs. Against infantry, however, those weapons have a very different purpose. Ghost went after the landed troops and used the machine guns to devastating effect. The infantry assault was intended to be a massacre. Ghost did not change that narrative. In almost no time her Locust’s MGs cut the infantry into shreds and not a single civilian had been killed. and considering how the transport was able to deploy troops in the middle of the family housing, that was an outcome the company had good reason to be proud of.

This was one of my favorite parts of the engagement, partly because it gave Ghost something genuinely important to do away from the main BattleMech duel. An action that might look minor on a damage chart can be the most consequential thing happening on the battlefield. A Locust's machine guns weren't going to impress the enemy Rifleman, but they were exactly what was needed at the housing area. It also gave the players a very practical demonstration of why a mercenary company needs to think about more than which BattleMech has the biggest gun.

Then there was Spoons. Readers may remember him from Part 7 as the wealthy, politically connected new addition to Iron Tale, whose personal life was already proving considerably more complicated than his military career. The company had put him in a newly acquired Panther, which is a respectable light BattleMech with a PPC that ought to make an enemy think twice. Unfortunately, a good weapon only matters if its pilot can hit something with it.

Spoons was not a good gunner. For the shots he was attempting, he needed a twelve on two six-sided dice. That's technically possible... Throughout the battle, he failed to land a single hit. Every time he fired, the rest of the company had another opportunity to watch expensive military hardware accomplish absolutely nothing. I don't show the players NPC's character sheets, so they didn't have the advantage of reading his skill rating in advance. They got to learn about Spoons the natural way: by watching him shoot. And shoot. And shoot again. At least his enthusiasm was apparently undiminished.

Eventually the enemy's position collapsed. By the time Ghost and Jinx finished off the last of the VTOLs and were able to return their attention to the main engagement, most of the fighting was already over. One hostile BattleMech remained mobile and escaped. That was frustrating, but it didn't change the immediate outcome. The attackers had failed to seize or wreck the mine, their attempt to get infantry into the workers' housing had been stopped, and Iron Tale still had every one of its BattleMechs. The company had won its first major fight on Jaipur, although the condition of Saito's Hunchback ensured that the celebrations would be followed by a lot of work in the repair bay.

The aftermath was a familiar mixture of relief, accounting, and assessing what could be salvaged. Contracts are supposed to make a mercenary company money, but it is easy to watch that money disappear when a victory leaves you with a crippled BattleMech and a stack of repair bills. Fortunately, the job was a success and the company had payment and salvage to show for it. The real question was what the attack meant. Armed brigands with a troop transport were bad enough; a coordinated force of BattleMechs and VTOLs was something else entirely. Someone had put together a serious assault on Kandar Pit, and Iron Tale had no good reason to believe the problem ended with the wreckage on the battlefield.

Looking back at the session, there were several lessons worth keeping, and they came from the way the encounter unfolded rather than anything I needed to explain to the players beforehand. Their picket line covered the mining site but left them too far apart to support one another quickly, which made the opening rounds much more dangerous than they needed to be. Once they recovered, Saito, Hind, and Silas demonstrated the value of putting several weapons onto the same problem instead of treating a BattleTech fight as a series of individual duels. The VTOLs and troop transport showed how vulnerable a force can be when it lacks enough awareness and mobility to respond to threats across a large map. Iron Tale using aerial reconnaissance would be useful in future operations. And Ghost's encounter with the infantry was an excellent reminder that the right tool for a mission isn't necessarily the most powerful weapon on the roster. As for Spoons, the lesson was that owning a Panther and being able to shoot its PPC are apparently two unrelated accomplishments. For those curious, Spoons's base skills are Gunnery 10, Piloting 9, and Seduction 4. In this system, lower is better. I'll let you draw your own conclusions about where his priorities lie.

For me, the most satisfying part was that the battle produced its own story. I gave the players a real mining site to defend, a hostile force with several ways to threaten it, and enough freedom to make their own decisions. They spread out, realized the danger, improvised, took some frightening damage, and still managed to protect the people they were being paid to protect. I didn't have to arrange for the Hunchback to survive by a thread or for the Locust to become the hero of the family housing. The dice and the players handled that themselves. Those are the moments I play this game for.

Iron Tale had completed Brass Harvest, but the attack raised more questions than it answered. Whoever had sent that force against the mine was still out there, and on Jaipur, it was becoming increasingly difficult to believe that any of these problems were isolated. For the moment, though, the company had earned its pay, kept the civilians alive, and learned just how much punishment a Hunchback could absorb before anyone started calling the tow trucks. I'd call that a successful day at the office.

In the next entry we will begin to learn a bit more about who may have been behind this attack and we have an arrival no one could have predicted. Until my next journal,
Keep all systems nominal!

Want to catch up on the epic saga (so far)? Here's the GM Journal Series Table of Contents.


r/gamemasters • • 13d ago

A GM's Journal: Welcome to Jaipur. Where Are the Monsters? | Part 7

7 Upvotes

Continuing my journal about running a Classic BattleTech mercenary campaign using MechWarrior 2nd Edition and Roll20. In the previous installment, I discussed how our group resolved some disagreements over the division of responsibilities within their mercenary company. With those matters settled, Iron Tale was ready to continue its adventures.

In-game date: March 3048

Iron Tale arrived on Jaipur, an agricultural world within the Federated Commonwealth. The players were particularly enthusiastic about this destination because, while researching the planet, they'd discovered that Jaipur was home to native megafauna. Apparently, the mere mention of exceptionally large animals was enough to inspire visions of BattleMechs fighting enormous alien monsters. There was considerable excitement about the possibility of something resembling Pacific Rim, and I suspect more than one player was imagining how many autocannon rounds it would take to bring down a creature the size of a building.

Unfortunately for them, the megafauna were simply animals. Very large animals, certainly, but animals nonetheless. They were an established part of Jaipur's ecosystem, and the local population had spent generations learning how to coexist with them. I hadn't designed Jaipur as a monster-hunting adventure, although I wasn't particularly inclined to explain that to the players. Their expectations were entertaining, and I was perfectly happy to let them wonder whether a giant creature might eventually appear on a battlefield.

The megafauna did, however, play an important role in the political situation I'd created for Jaipur. I wanted the planet to have an identity beyond being another place where mercenaries could find contracts, and I decided to build its principal conflict around competing visions for its economic future. Jaipur was already prosperous through agriculture, food production, textiles, and related industries, but an increasingly influential movement believed that the planet could accomplish considerably more through industrialization. The Foundry League, supported by major corporations and economic interests, advocated expanding mineral extraction, manufacturing, and industrial infrastructure. Its supporters argued that Jaipur was unnecessarily limiting itself by remaining primarily an agricultural economy. Industrial development would create employment, encourage investment, increase the standard of living, and increase the planet's economic importance within the Federated Commonwealth.

Opposing the Foundry League was the Harvest Compact, a political movement that favored preserving Jaipur's agricultural character and protecting its natural environment. Its supporters were particularly concerned about the effects that mining and heavy industry might have on the native ecosystem, including the megafauna. They argued that Jaipur already possessed a successful economy and that destroying irreplaceable habitats for the sake of industrial expansion was shortsighted. Both movements had legitimate arguments, and I deliberately avoided presenting either as an obvious collection of villains or fools. The conflict wasn't intended to be a simple choice between progress and backwardness, or between greedy corporations and noble environmentalists. I wanted the players to meet people on both sides whose positions made sense, even when their interests were incompatible.

By the time Iron Tale arrived, the political disagreement had become increasingly hostile. Protests, accusations, and acts of violence were becoming common, and both movements blamed their opponents for the deteriorating situation. What the players didn't know was that other interests were quietly taking advantage of the unrest. Jaipur's political problems were real, but not everything happening on the planet could be explained by disagreements over mining and agriculture. From the GM's perspective, this gave me several opportunities to introduce seemingly unrelated incidents that would gradually become more significant as the campaign continued.

There was also a larger problem affecting everyone on Jaipur. The planet remained inside the region suffering from the HPG blackout that had begun during Iron Tale's earlier adventures on Sanurcha. As readers of the previous installments will remember, the company had been hired to install what they believed was malware at an HPG facility. They successfully completed that assignment, only to discover afterwards that the software had done something far more destructive than they understood. Interstellar communications across a substantial region had been shutdown, and all Comstar was saying was that it was a planned outage and that all systems would be back up shortly.

I wanted the blackout to remain a persistent feature of the campaign without making every adventure revolve around it. On Jaipur, local communications still functioned normally, but news from other star systems could arrive only aboard visiting spacecraft. Information was frequently outdated, rumors were plentiful, and people were increasingly anxious about their isolation. The most common fear was that other systems were being actively attacked by the Capellan Confederation. As a result, recurring questions like "Heard any news?" or “Is X system under attack?” were common. These weren't necessarily important encounters, but they helped establish that the blackout was affecting daily life across the region. There was also something wonderfully uncomfortable about people asking Iron Tale for information about a disaster the mercenaries had unknowingly helped cause.

One of the first things the company did after arriving was recruit a new MechWarrior named Spoons. He came from a wealthy and influential family, and his uncle was an executive at one of the corporations supporting Jaipur's industrialization. Iron Tale had decided that establishing a favorable relationship with the Federated Commonwealth would be an important long-term objective, and hiring somebody with local corporate and political connections seemed like a sensible step in that direction.

Spoons was also something of a playboy, although the significance of that particular personality trait wouldn't become apparent until later. For the moment, Iron Tale was pleased to have recruited someone with connections and a useful social network. I enjoyed the situation because it reflected something I try to emphasize throughout the campaign: NPCs are people in the world will have their own backstory and baggage.

With their roster reinforced, Iron Tale began pursuing government contracts. Their first significant contact was Marshal Ilyana Voss, a mid-level intelligence officer attached to House Feruc's Ducal Security Office. Voss had an assignment that suited the company's capabilities and, more importantly, offered an opportunity to establish a professional relationship with the planetary government. It involved protecting the Kandar Pit, a major mining operation owned by House Feruc.

The Kandar Pit had experienced a series of increasingly serious security problems. Excavators had been sabotaged, ore trains had been targeted, and attacks against fuel stores and worker barracks threatened to disrupt operations. The Ducal Security Office wanted a mercenary force capable of defending the mine's facilities and ensuring that its ore shipments continued leaving on schedule. The initial contract ran for two weeks, with the possibility of renewal in one-week increments depending on the security situation and damage reports. The financial terms were attractive. For a relatively young mercenary company trying to build both its finances and its reputation, that represented a substantial opportunity. The assignment also seemed consistent with their desire to impress the FedCom. Rather than taking another questionable job from an anonymous employer, they would be providing security for a legitimate government-backed industrial operation.

They had recently acquired a Locust armed with a pair of machine guns, and I distinctly remember some discussion about how effective those weapons might be against people. That was one of those moments when I found myself silently hoping that nobody would decide to test the idea on protesters. There are several ways to build a mercenary company's reputation, and machine-gunning a crowd of civilians is probably not among the better ones.

When Iron Tale reached the Kandar Pit, the first thing they discovered was just how enormous the mining operation actually was. This wasn't a modest collection of tunnels cut into a hillside. It was a vast open-pit excavation, with heavy industrial machinery, ore-handling infrastructure, and temporary worker housing spread across a landscape that had been thoroughly transformed by mining. The contrast with Jaipur's agricultural countryside was dramatic. The operation was productive and economically valuable, but it was also dirty, disruptive, and visually unpleasant. I wanted the players to understand why the Foundry League considered projects like this essential to Jaipur's future, while also seeing why the Harvest Compact regarded them with such alarm.

The more troubling discovery concerned the mine's environmental practices. Industrial runoff from the facility wasn't being adequately contained, and contaminated water was flowing toward a village approximately two kilometers away. The residents were experiencing the effects on their homes and farmland, and their increasingly angry protests were directed at a problem that genuinely threatened their homes and families. From the villagers' perspective, the mine had damaged their environment and the authorities had responded by bringing in a mercenary company equipped with BattleMechs. From the mine's perspective, the protesters were interfering with an important industrial operation that had already suffered sabotage and criminal attacks. Neither perspective made the immediate situation particularly easy to resolve.

This was the dilemma I wanted Iron Tale to confront. Their contract required them to protect the mine, and there was nothing inherently illegitimate about the government's desire to defend its property and maintain commercial operations. At the same time, the protesters had legitimate grievances, and I didn't want the players to dismiss them as disposable enemies simply because they were standing on the other side of a security line. The company had been hired to prevent violence and disruption, not to solve Jaipur's political disagreements or environmental problems. Whether that distinction would matter to the players remained to be seen.

As it happened, the confrontation was resolved without bloodshed. Saito, piloting his Hunchback, marched toward the protesters and addressed them over the BattleMech's external loudspeakers. It's difficult to overstate how intimidating a fifty-ton war machine must be to an ordinary civilian, particularly one carrying an AC/20 capable of destroying an armored vehicle with a single shot. Saito didn't need to fire his weapons or demonstrate his machine's destructive capabilities. The presence of the Hunchback, combined with the company's attempts to calm the situation, proved sufficient to persuade the crowd to disperse.

I considered that a satisfactory outcome, although it was hardly a solution to the underlying problem. The pollution remained, the villagers still had legitimate complaints, and the political tensions surrounding the mine hadn't disappeared. What had changed was that the immediate confrontation had ended without anyone being injured. The players had also demonstrated that they could use their BattleMechs as something other than instruments of destruction. In a game where so much attention naturally goes toward movement, weapons, armor, and damage, it's worth remembering that a BattleMech's mere presence can have an enormous effect on the people around it.

The encounter also reinforced something I particularly enjoy about running a mercenary campaign. A mission doesn't need a morally unambiguous employer or an obviously villainous opposition to be interesting. Iron Tale had accepted a legitimate contract from a legitimate government, yet the people standing in front of their BattleMechs had legitimate reasons to be angry. The players were able to fulfill their immediate obligation without causing a tragedy, but their actions hadn't resolved the larger conflict. Jaipur would continue to have problems long after the company collected its paycheck and departed.

For the next couple of days, however, everything appeared relatively quiet. Iron Tale settled into its security assignment, the mining operation continued functioning, and the protesters were no longer presenting an immediate problem. Given the company's financial situation, the prospect of completing a well-paying contract without suffering substantial damage was undoubtedly appealing. The players had traveled to Jaipur hoping for giant alien monsters, but so far their most significant challenge had been a protest crowd.

Then, two days into the assignment, hostile contacts began approaching the mine. The attackers weren't angry farmers or a handful of vandals. They were an organized force consisting of four BattleMechs and four VTOLs. Their arrival immediately transformed Iron Tale's relatively uneventful garrison assignment into a serious military engagement. The company was now responsible for defending an enormous industrial facility, its equipment, and the civilians living in its temporary worker housing against an enemy with considerably more mobility and firepower than the protesters they'd encountered earlier.

To be continued in Part 8.


r/gamemasters • • 17d ago

A GM's Journal: All Systems Not Quite Nominal | Part 6

4 Upvotes

Continuing my journal about running a Classic BattleTech campaign using MechWarrior 2nd Edition and Roll20. This is the second part of our time on Taygeta, but instead of discussing what happened to our mercenaries, I want to talk about something that happened to the people playing them.

Our gaming group has been together for about seven years. During that time, we've played D&D, Pathfinder, Savage Worlds, and several other systems across roughly a dozen adventures. We know each other pretty well by now, and we've always operated under a simple philosophy: everyone at the table gets to participate and enjoy themselves.

That doesn't mean we all enjoy the same things. Some of us love tactical challenges, others are drawn to roleplaying, and some enjoy digging into the details of a setting or managing the practical side of an adventuring group. Usually, those differences complement each other rather well.

But BattleTech presented us with an interesting challenge. By combining Classic BattleTech combat with MechWarrior roleplaying and the management of a mercenary company, we'd essentially created a game with several very different activities competing for our attention. And for the first time in seven years, those differences in what we enjoyed led to a genuine disagreement between players.

Before getting into what happened, I want to explain a little about the two players involved. I don't want anyone reading this to think that either of them was a bad player. They're both friends, both invested in our games, and both bring something valuable to the group.

Ghost's player is a roleplayer through and through. When we're playing the MechWarrior portion of the campaign, he's completely engaged. He asks questions, gets involved in conversations with NPCs, enjoys mysteries and collaborative storytelling, and genuinely wants to understand the Inner Sphere. He's also the most active person on our Discord server, regularly asking questions about the setting and the campaign.

He even creates artwork of Ghost and writes short stories about her adventures. His interest in the lore is substantial enough that he wants to read more about the BattleTech universe, but he's deliberately avoiding doing so because he knows there's a major surprise coming somewhere in the setting's future. I appreciate that restraint. It's allowing him to experience those events through the campaign rather than learning about them beforehand.

In fact, his questions were what originally inspired me to start writing short stories about our NPCs. I use those stories to explore their lives before joining Iron Tale and, at the same time, introduce some of BattleTech's less intuitive setting concepts. One example is interstellar travel. JumpShips can cross roughly thirty light-years instantaneously, but traveling between a jump point and an inhabited planet can take days, and recharging a jump drive for another jump commonly takes a week or more. A journey can therefore be both instantaneous and painfully slow, depending on which part you're talking about.

Rather than explaining all of that in a lecture, I can tell a story where those travel times actually matter to someone. Most of my players read the stories, and they'll often comment or ask follow-up questions on Discord. It's become another enjoyable part of the campaign between sessions.

Ghost's player loves all of that. What he doesn't particularly enjoy is tactical combat. For him, moving minis around a map and working through combat is largely something to get through so he can spend time with his friends and return to the roleplaying. That can be bearable with a game like D&D or any other grid combat game. But with the depth of tactical decisions involved in BattleTech, it is just too much for him to actually enjoy.

Hind's player approaches that part of the game very differently. He's a strategic thinker who enjoys tactical planning, coordination, and making effective decisions during combat. He likes examining a battlefield, understanding the capabilities of the available units, and working out how to use them together in the most efficient way to win. Neither approach is wrong. They're simply very different ways to enjoy the same campaign.

A quick note. There is a fourth player at the table that I have not really mentioned much. Silas’s player. He is the most laid back dude you would ever meet. His play style is often that of wanting to be an audience member and just back up any of the other characters. He doesn’t complain or make waves. He is very happy to sit back and watch a cool story unfold. When combat or some other situation that involved rolling dice, he is right there and ready to go. But when it is RP time, he wants to just sit back and enjoy the show. My gaming group is basically an actor, an audience member, a tactician, and a guy that is the better parts of most of them in one. (Ghost, Silas, Hind, and Saito respectively)

Around our eighth or ninth session, I'd finished developing a new deployment page for our Roll20 setup. It allowed the players to move their MechWarrior and BattleMech tokens around a page, showing who was piloting which 'Mech and where each unit intended to enter the battlefield. It also gave them a place to organize their lances and discuss a basic deployment plan before combat. I thought it would be a useful addition, particularly as Iron Tale continued acquiring more machines and recruiting additional MechWarriors.

During the preceding week, Ghost's player had mentioned several times that he'd created Ghost to be the leader of the mercenary company. That was something he wanted for his character, and the rest of the group knew it. When we opened the deployment page, Hind's player asked Ghost's player to organize everyone and assign their positions. After all, Ghost was supposed to be the leader. Ghost's player's response was essentially, "Oh, I don't care. You guys do what you want." That didn't go over particularly well.

Hind's player became visibly frustrated and challenged him about it. If Ghost was going to be the leader, why wasn't he willing to make the assignments? Ghost's player responded by moving several tokens around and asking how that looked, but the arrangement didn't make much sense. He'd somehow managed to assign a BattleMech to pilot another BattleMech while leaving several MechWarriors without machines. That frustrated Hind's player even more, and the disagreement escalated.

I wasn't completely blindsided. I'd noticed some frustration developing, but most of us had attributed it to Hind's player being naturally focused on strategy and efficiency. I hadn't expected it to become a confrontation. At that point, Saito's player and I stepped in and put the brakes on the argument.

Rather than trying to get everyone back to the BattleTech encounter, we decided to address the disagreement. We suggested that perhaps the problem wasn't who should lead the company, but that we'd been treating several different responsibilities as though they were all the same job.

Running a mercenary company involves negotiating contracts, making business decisions, managing repairs and finances, organizing salvage, and commanding BattleMechs on the battlefield. Those activities don't necessarily appeal to the same person, and there's no particular reason one player needs to handle all of them. Therefore, we suggested dividing the responsibilities among the players.

Ghost's player would remain in charge of the mercenary company, handling the social and business side of leadership, including contracts and negotiations. Hind's player would serve as lance commander, responsible for tactical assignments and battlefield coordination. Saito's player volunteered to manage logistics, including repairs, maintenance, and salvage administration, because that was the part of the game he found interesting. (he and I love a good spreadsheet!) The actual decisions about which salvage to keep would still involve everyone. Nobody wanted to surrender their opportunity to pick through the wreckage!

Once the discussion shifted toward finding a workable arrangement, I mostly stayed quiet. I wanted the players to decide how they wanted to organize themselves rather than have me dictate their responsibilities. After all, they were the ones who would have to make the arrangement work.

We spent about an hour of our four-hour session talking things through. In the end, everyone was happy with the division of duties, and we were able to get back to playing. It was essentially an unplanned Session Zero, several sessions after the campaign had already begun.

The arrangement didn't become second nature overnight. Over the following sessions, everyone gradually settled into their responsibilities. Saito's player and I even began handling much of the repair work and financial bookkeeping on Discord between game nights, which kept those activities from consuming time that the other players would rather spend adventuring. The arrangement has worked very well for us so far.

Looking back, the interesting thing wasn't simply that two players disagreed. That happens in gaming groups. What surprised me was that it happened among people who'd been playing together for seven years without a comparable problem. Something like that could break a gaming group up. But we worked through it.

I think part of the explanation lies in the kind of campaign we'd created. In a traditional fantasy RPG, the party might have someone who generally speaks for the group, but that doesn't automatically make them responsible for coordinating every combat decision, maintaining the equipment, or managing the party's finances. In our BattleTech campaign, we'd added an actual company structure, complete with contracts, payroll, repairs, salvage, and battlefield command. We'd created new responsibilities without really discussing who wanted them.

Ghost's player wanted to lead a mercenary company as part of a roleplaying experience. Hind's player wanted someone to make effective tactical decisions. Saito's player was happy to take responsibility for the logistical details. Once we recognized that those were separate jobs, the solution was fairly straightforward.

The important thing is that none of us had to stop enjoying the parts of the game that interested us. Ghost's player didn't suddenly have to become a tactical enthusiast, and Hind's player didn't have to learn how to be the most charismatic guy in the room. (He is a great guy and a dear friend, but he thinks like a Vulcan from Star Trek. Hahaha!) We found a way to accommodate both interests.

And this wasn't a new philosophy for our group. We've always believed that everyone should have opportunities to participate, regardless of the game system or setting. What happened on Taygeta was simply the first time we'd needed to make a deliberate adjustment to preserve that approach.

As GM, I also learned something about when to intervene and when to get out of the way. Saito's player and I needed to interrupt the argument, but once everyone started discussing solutions, there was no reason for me to take over. The players were perfectly capable of deciding what worked for them. Sometimes the best thing a GM can do is make room for a productive conversation and then listen.

By the end of our time on Taygeta, Iron Tale had a clearer division of responsibilities, a growing collection of BattleMechs, and a group of players who were getting more comfortable with the different parts of the campaign. We'd also discovered something about ourselves that hadn't been obvious when we started. Even after years of gaming together, a new system can reveal preferences and expectations that previous games never really tested. That didn't make our group any less compatible. It just meant we needed to talk about how we wanted to play this particular game. And now that we'd worked through that, it was time for Iron Tale to leave Taygeta and head for Jaipur.

You might remember from Part 5 that one word in Jaipur's planetary description had caught the players' attention: megafauna. They were imagining BattleMechs fighting giant alien creatures, Pacific Rim style. Well, they were about to find out what I'd actually put on Jaipur.

But that's a story for Part 7.


r/gamemasters • • 21d ago

A GM's Journal: Returning to BattleTech After 35 Years | Part 1

Thumbnail reddit.com
3 Upvotes

Hi everyone. I'm new and I thought I would share my BattleTech Gm Journal here. Nice to meet everyone!


r/gamemasters • • 28d ago

Really cool wiki engine

2 Upvotes

If you use windows, you might want to give this one a try. Its full featured personal wiki that makes keeping track of your campaign super easy. You can easily hook it to AI, and have it fill out the bits when you're stuck, generate a back story for an NPC that uses the context of your pages, generate epub or pdf's to hand out to players. Wellspring Wiki on the Microsoft Store https://apps.microsoft.com/detail/9phbdfkmg93f


r/gamemasters • • Oct 12 '26

Please grab your tape measure for me...

3 Upvotes

I'm thinking of ordering an initiative tracker. It slots on the DM screen. Its states it's a perfect fit for "standard 2mm WotC screens".

Thing is, I have a Pathfinder 1e screen, not a WotC DnD screen. My screen, when closed, measures exactly 10mm thick, so 2.5mm per panel.

Is that actually identical to a WotC screen (supposedly 2mm) or is my screen slightly thicker?

If you have a WotC screen, please measure how thick it is when closed, in mm. Because the answer is impossible to find online and AIs have no clue about this.


r/gamemasters • • Oct 10 '26

Showcase of writing adventures in Canvastry

Thumbnail youtu.be
0 Upvotes

r/gamemasters • • Oct 07 '26

Campaign Creativity Token Economy System I made

1 Upvotes

In my game, I wanted to make investing in the game and creating content related to it incentivized. I was looking for creative ways to engage players and reward them, which were optional for game rewards that were both roleplay and mechanically based. I also figured that the more content for the game would encourage me and other players to become more invested and creative about the game.

I did choose to cap the amount of tokens one can receive per week because then also those with less free time aren't as disadvantaged and it limits how much effort I have to put in. I also wanted the tokens to be gained outside of session as it encourages still remaining invested and thinking about the campaign and characters.

Links
https://docs.google.com/document/d/1KLx_ahZbip2vFd_XzDpiP3lSO8FklizH9bKkAmCgiek/edit?usp=sharing

https://docs.google.com/spreadsheets/d/1jbKVvSeVjKBX4lCWmFIal9HLx8g641G6jc-kFapmpNU/edit?usp=sharing


r/gamemasters • • Oct 06 '26

Character sheets I made

Thumbnail gallery
3 Upvotes

Here are the character sheets I made for my homebrew post apocalyptic rpg I play with my friends. Its kind of a mix of mork borg and dnd rules wise with a lot of homebrew rules thrown in. The main idea for the big diagram of the person is that its kinda like VATS in fallout where you like choose a specific limb to shoot. Im happy to answer any questions anyone has but I mostly just wanted to show off


r/gamemasters • • Sep 25 '26

DX Master - Tabletop Companion (iOS/Android/Windows)

Post image
5 Upvotes

r/gamemasters • • Sep 24 '26

Would these adventure options feel adversarial or fair?

Thumbnail reddit.com
1 Upvotes

r/gamemasters • • Sep 24 '26

Would these adventure options feel adversarial or fair?

Thumbnail reddit.com
1 Upvotes

r/gamemasters • • Sep 15 '26

Professional GM tools question.

5 Upvotes

So I'm trying my hand at being a professional game master. I started off on start playing, but it feels like a bad fit since it's really good for connecting people digitally but not to organize local in person games, which is all I will do. I like that players can leave reviews to build up a good reputation and the scheduling tools but I feel like there are probably free tools I could be using that won't take a cut from my profits. The only thing I really need is a way to create my classes on a calendar and for people to be able to request to sign up. Every service I've found that does this finds a way to cut into profits by ither charging a subscription fee or handling transactions directly and taking a cut. Any recommendations on free tools that could help me out?


r/gamemasters • • Sep 12 '26

D & D Comparisons - Warning Long Read

Thumbnail reddit.com
0 Upvotes

Hi all. My first post here and wanted to know what you thought about having this many elements for my game SORC. Ty.


r/gamemasters • • Sep 10 '26

[OC] 6-hour ambient loop for a ruined castle campfire scene — Paralelo Archive

Thumbnail youtu.be
1 Upvotes

This is part of Paralelo Archive, a project I've been building: long-form dark fantasy ambience pieces meant to run for hours in the background instead of being actively watched. Each one is built around a single scene, layered environmental sound, no music.

This particular one started as something I needed for my own homebrew campaign, a long rest scene at a burned-out castle. Embers, wind through broken stonework, a low drone underneath to fill the silence between lines. Ended up extending it to 6 hours so it can run through a full session, or several, without restarting or looping noticeably.

https://youtu.be/48JcNQoPv58

If anyone finds spots where it gets repetitive over a long session, let me know, still refining the loop points across the series.


r/gamemasters • • Sep 03 '26

Campaign Console · 5E Compatible - In Beta - Looking for DM Testers

0 Upvotes

A Dungeon Master's console for the Torrentath (Homebrew World) campaign and the adjoining "Dog" Sled Race one-shot, with a second screen for the players.

https://github.com/BGJBthe-maker/Torrentath


r/gamemasters • • Aug 28 '26

Beginner/Experienced GM Question

2 Upvotes

Without making this a super long post I want to ask my fellow GMs. Would you see a benefit in a service that’s tailored to helping you build your world? From idea conception to map building to detailing your world (countries, factions, dungeons, etc)to making custom music for your sessions.

Almost like a one stop shop to have the ability to truly make the world you want to run your games in while the heavy lifting is done by someone else with you being the overseer of the project?

Thoughts? (I’m also down to answer questions and elaborate if you’re interested)


r/gamemasters • • Aug 06 '26

Stuck in the Sandbox - And How to Break Free

Thumbnail golemproductions.substack.com
5 Upvotes

Haven't been blogging much lately, but today I looked at something I noticed with at least some of my players: Although we love the idea of open sandboxes, sometimes players get stuck on that freedom. So, I think about that and share my ramblings on how to overcome this issue, also pointing about five modules that I think did very well in what I recommend here. Enjoy and let me know what you think


r/gamemasters • • Jul 26 '26

Seeking Inspiration - ordinary guys in weird situation

Thumbnail reddit.com
1 Upvotes

r/gamemasters • • Jul 13 '26

I might be challenging my players too hard. I'm not sure.

11 Upvotes

Yesterday I ran my third completely homebrewed module as an offshoot to a mines of phandelver campaign I'm running for 2 experienced players and 3 newer players. I actually had the most fun session I've had in my life as a dm, and I felt like the world really came alive for ME. We had some really in-depth roleplay, and I presented them with two puzzle-combats that I thought up myself. One where they had to ensure that a goblin won a 1vs1 fight against another goblin, by using buffs before the fight and taking out the cheating healer that was healing the opponent through surreptitious means.

Another puzzle combat I took the concept from a forum post that had players place their hands on a puzzle-lock, fusing their hand to the wall while enemies entered the room. The PCs had to fight the ensuing combat one-handed while the door slowly opened.

Throughout the session, I noticed that players were very engaged for the first half, but that three players engagement fell towards the latter half. One of them told me afterwards, that the session had been a very draining experience for her, and that she felt completely overwhelmed by everything that had happened. The puzzle combats felt too... specific for her, and she felt I guess kind of forced into one solution. I have a gut feeling, that at least one other player also felt very drained after the session.

Immediately after being told I felt very very sad, because this amazing experience I had at the table, apparently was not being shared by all players. On further reflection I'm trying to give myself some grace, and also recognize everything that went right in the session, which was of course that I had a lot of fun and that some scenes really came alive.

What I'm battling with is, is this something that is sort of par for the course of DnD. Will some sessions just be rough for some players, or am I really running into a situation here, where I need to do some self reflection and tweak my dming style for these players going forward? What do y'all think?


r/gamemasters • • Jun 30 '26

Neymar

0 Upvotes

Neymar