This past weekend, I had the privilege of speaking on a couple panels at the second annual Fort Collins Comic Con. (Unofficial motto: “We’re bigger than you think!”)
The panels were all about running tabletop roleplaying games. Together with Bill Keyes, Sean Patrick Fannon, and Ross Watson, we answered questions from the surprisingly-large crowd about how to get started as a GM, how to keep your players happy, and how to keep a long-term campaign from catching fire, crashing through a line of school children, and plummeting into a pit of giant snakes far below.
We were thrilled at the number of new Game Masters in attendance. As Sean pointed out, the only way the hobby (and the industry) expands is by more people stepping up to the challenge of running RPGs; we can only have as many gaming groups as we have GMs. While the old guard can keep it going, new blood is what makes it grow.
Especially with the new GMs in mind, I’d like to share three recurring bits of advice from the panels:
- Communication is Key: Talk to your players. You’re all on the same team, working towards the same goals of a good time and a good story. Work with your teammates to determine the direction of the game (“So no more sewer adventures, then? Got it.”) and resolve any problems that come up (“Sorry, dude, but that clown costume has got to go. Yes, the makeup is great, but it’s distracting to the other players, and it’s freaking my cat out.”).
- Match Characters to Campaign: One of the things to talk about with your players is how best to mesh the characters they’re excited to play with the campaign that you’re excited to run. This could start with you (“This campaign takes place on a space pirate ship, so make some space pirates”) or it could start with the players (“We all made space pirates!”), but it should end with everyone playing the role they want in the adventure they want.
- Start Small: Finally, if you’re a new GM, don’t feel obligated to create a world-spanning epic for your first few forays into running the game. Find a pre-written adventure (or campaign, if you’re that committed) that appeals to you, read it over, and run it. Yes, your players may go off-script. And yes, things will happen that aren’t covered in the adventure. That’s okay. It’s just one adventure. And when it’s done, you’ll be that much more prepared to run the next adventure. (For more tips on running your first adventure, I recommend this funny and insightful piece by the Angry DM.)
Thanks to the Fort Collins Comic Con team, and to Bill for inviting me. I had a great time at the con, and hope to do it all again next year!
I picked up the Systems Failure RPG on a whim about ten years ago. Okay, it wasn’t totally a whim. It was in response to the publisher’s public cry for help; they were on the verge of bankruptcy and needed all the sales they could get. I’d been eyeballing a couple of their titles, and used their crisis as an excuse to pick them up. (And yes, the publisher recovered from its slump and is still going strong today. You’re all welcome.)
Fast forward a couple years: I’m moving to Colorado, and deciding which games to bring and which to give away. “I still need to read this one,” I think, and pack Systems Failure into a box labeled “Yet Still More RPG Books.”
Fast forward a couple more years: “I need a book to read on the bus. Oh, right. Systems Failure!”
Fast forward another week: “That looks pretty fun. I won’t be able to get any of my friends to a new system, though. I wonder how hard it would be to convert to Savage Worlds?”
And then… nothing. For six years.
…Until a month ago, when an opportunity arose for me to run a one-shot of anything Savage Worlds. Since the group had already played more than their share of Karthador and Ghost Punchers, I let my gaze drift across my gaming bookshelf until it landed on Systems Failure.
“Yes,” I said to myself, nodding with melodrama. “It’s time.”
In Systems Failure, the players take on the roles of American resistance forces fighting a guerilla war against an occupying force of aliens. The aliens, which feed off (and shoot) energy, are called “bugs” because they look like giant insects. The world is post-apocalyptic, though more Dawn of the Dead than Mad Max (the cities are still prime for looting, if full of bugs). It’s still got nomadic automotive barbarians, of course. Because those guys are cool.
Our crew of survivors set out to trade crops for batteries at the local barter-town, but found the place taken over by an advance force of bugs. Never one to walk away from a fight, they waited until nightfall, scouted around a bit, then commandeered a National Guard tank and charged the bug HQ. Wackiness ensued.
Savage Worlds handled the setting beautifully. The only things I actually converted were the bugs themselves, with which I played fast and loose. They might not have been mechanically identical to their counterparts from the original system, but they were narratively the same: increasingly fast, tough, and able to shoot energy beams from their bodies.
We all had a good time with it.I won’t be surprised if we return to the world of Systems Failure. But if we don’t, that’s fine; I’ve got dozens of other unread, unplayed RPGs still waiting for for their moments in the sun.
I finally fought my way free of the Sarlacc pit long enough to do some playtesting on that Robot Drop game I keep muttering on about. And, as I suspected, the game as written was as dull as a butter knife sealed in rubber and wrapped in bubble wrap.
The biggest problems were these:
- When you can put robots into play anywhere on the board, the “move” action is pretty pointless.
- When you’ve only got one action a turn, it takes forever to make any meaningful changes to the game state.
- It also takes roughly forever to deal 20 damage to an opponent’s Home.
With that in mind, I made a few tweaks to the rules:
- Robots only come into play adjacent (diagonally or orthogonally) to their Homes.
- Players have three actions a turn.
- You only need to inflict 15 damage on a Home in order to win.
(I’m actually a bit unsure on that last one. The first couple playtests suggested 15 is the sweet spot, but the next tests howled that 15 is still too high. I might try 10.)
The second iteration felt more exciting than the first, but it’s still a little slow for my tastes. I’ve got some ideas for the next iteration that should speed things up without sacrificing too much strategy. I’ll keep you posted!
Last week I casually brought up that I was working on a new game, and rambled on like a senile old man about its components. (“Back in my day, we didn’t have numbers on game pieces. We had shapes like triangles and birds’ feet, and you just had to count ’em!”)
Today I’d like to revisit Robot Drop in a little more detail. Specifically, let’s look at the game’s setup and turn sequence.
- The game is played (for now, at least) on a 7 x 7 grid. Each player has a “home” in one space of that grid.
- At the start of the game, each player shuffles his pile of 10 robots and draws three.
- One player is randomly chosen to go first.
The game is played in a series of turns. On your turn, do the following in order:
- Draw a robot.
- Take one action, which may be any of the following:
- Put a robot into play into an empty space on the board.
- Move a robot in a straight line up to two spaces (and yes, you can pass through friendly units).
- Rotate a robot any amount. (Remember: facing matters.)
- Count down all timers in the game. So if you just played a unit with a Timer value of 4, it counts down to 3. Or a robot with a current timer of 2 counts down to 1.
- Attack! All units that have counted down to zero attack simultaneously. When a robot attacks, it deals damage equal to its base Timer value to the first enemy robot in the direction that it’s facing. (Attacks pass through friendly units.) For example, if a robot has a Timer value of 4, it deals 4 damage.
- Reset all robots that have counted down to zero back to their based Timer values.
I’m still messing around with the victory conditions. The simplest and most traditional idea is that you win if you inflict 20 damage on your opponent’s Home. There will probably be some other ways to win too (control the magic Bot Spot? have the most birds’ feet?), but it’s a good place to start.
I’m working on a new game. It’s called “Robot Drop” (for now) and, while you might think it sounds like a typical “dudes fighting on a board” game, it’s actually an exploration of temporal and tactical game play space using… dudes. On a board. Who are… um. Fighting.
Okay, it’s not exactly smashing genre boundaries, but it does have some cool new mechanics that I think are different enough to make it interesting.
Let’s check out one of the playing pieces.
The key element here is the unit’s Timer value. When the unit comes into play, its timer is set to that stat. At the end of each turn, the timer “counts down.” When it hits zero, the unit attacks, dealing damage equal to its Attack value.
What’s not so clever, is that each unit has six numbers on it.
Oh, sure, six numbers is nothing on a chit for a war game like Delta Commandos Squad Forward Assault Leader, but I’m targeting a more general audience; an audience (like myself) that would be a little freaked out by so many numbers on a playing piece.
Clearly, the solution here is to make most of these numbers their default value.
For example, Speed will almost always be 2. Let’s just say “units can move two spaces” in the rules, thus making it the default, and remove the stat from the unit.
Shields? Default to zero. Range? I’m going to get brave and give everything infinite range, since the board really isn’t that big. As for Attack…
It’s no coincidence that Timer and Attack are the same value. If you have to wait five turns for your attack to go off, it should be pretty powerful — and in this game, 5 damage is enough to destroy most units.
So let’s make the Attack value default to being the same value as the Timer.
Let’s see how it looks now:
Ah, that’s much cleaner!
What’s more, you’ll note we now have space for text or icons or whatever on the playing piece. So if we want to deviate from the default (“Shields 3” for example, or “Speed +2”) we can do that where necessary without cluttering up all the other units.
So is the game any good? I’m just printing up a prototype right now, so we’ll find out together in the days to come!
Jaxar the Barbarian, aka “that juice-fueled toddler” loves to go on long walks.
“Outside!” he cries, pulling at my hand. Once on the sidewalk, he leads me down the street, around the corner, up the hill, and through a thousand miles of orc-infested wilderness en route to Mordor. Or maybe a playground. He likes swinging on the swings.
Between moments of active parenting, I use these epics journeys to listen to audio books. Recently, I’ve been listening to a lot of books from Librivox. Librivox, for the uninitiated, is an amazing website that provides free public domain audio books. They’ve got an army of volunteers who read and record the books, then release the recordings themselves to the public domain.
Thanks to these saints of the spoken word, I’m catching up on my John Carter novels. They’re a bit cheesy, and definitely products of their time, but they’re packed with awesome gaming ideas and pure pulpy fun. What’s more, the reader sounds more than a little like Nick Offerman, so it’s easy to imagine Ron Swanson narrating Carter’s Martian adventures, which makes them all that much more entertaining.
Come on, Jaxar! That ring won’t toss itself into Mount Doom!
I found I didn’t miss Episode I at all. And I don’t know if it was the context, or just the fact I hadn’t seen it since it was in theaters, but Episode II wasn’t as bad as I remembered. Oh, it still wasn’t good. It was, in fact, rather stupid, but it was pretty, the action scenes were fun, and it did a good job of setting up Anniken as willing to cross every line in order to save Padme in Episode III.
My daughters enjoyed the movies and didn’t seem to realize or care that the prequels weren’t up to the bar set by the originals. And that’s fine. I restrained myself from pointing out the worst parts of Episodes II and III. Well, mostly. I might have said something about how foolish it was for the Jedi Council to blindly accept a clone army created as part of a secret plot a decade earlier. (“Oh, what a shiny wooden horse! Bring it here. And we don’t even know where it came from — how exciting!”)
Out of curiosity, I asked Thing One if she realized that Senator Palpatine was Darth Sidious. To my surprise, she said no. I’m guessing that’s the case for lots of kids who saw the prequels first, or didn’t make the connection between Sidious and the Emperor. I’ll be curious to see her reaction if she watches the prequels again knowing that the kindly old politician is actually a Sith schemer.
My final surprise was how much my two year-old son got into the movies. Maybe I shouldn’t have been surprised; flashing lasers, explosions, and bright colors are appealing on a primal level. Also, he’s in his “trucks, tractors, and robots” phase, and Star Wars, with its spaceships, vehicles, and droids definitely scratches that itch.
Overall, I’d have to recommend the Machete Order. It was a positive experience that elevated both Episode II and Episode VI, and helped tell a cohesive story.
While those two-legged meatbags scurry across the board trying to gobble up resources like iron, food, and population in order to create and maintain their armies, their eight-legged adversaries are ignoring such logistics and simply conquering the realm. Right?
I’ll be honest. After spending more time than I’d like to admit pondering the spider-side of the game, I’m not entirely satisfied with what I’ve come up with. But it’s better to have something you can test (even if it’s not perfect) than to spend still more time coming up with something you think is perfect (because it’s not).
So ready or not, I’m pulling the trigger on this spider-plan.
While human players draw resource cards for each of their resource spaces, the spider player draws spider cards for each space the spiders occupy. (This encourages you, as the spider player, to spread your units out as much as you can.)
Spider cards have up to three bits of information on them:
- Power Value
- Magic Value
- Spider Type
I’m thinking they always a Power value (probably 1-3), but the others don’t show up on every card.
Like human players, the spider player can spend cards from hand to pay for the actions listed on his or her command sheet. Unlike human players, those actions are more restricted in terms of where they can take place. New recruits, for example, need to enter play where you have a nest, and new nests can only be spawned where you have a minimum of three units.
Here, check it out:
Hmm. Actually… this should work. It’s close enough to the human player experience that it doesn’t seem completely disconnected, but different enough to seem like its own thing. I feel better about it now than I did when I started writing it up.
Not to jinx it, but we might be ready to prototype this game.