Writing a roleplaying game

As you might have noticed, I’ve been busy in my free time with my completely self-written new roleplaying game „Raiders of Arismyth“.

Unlike „Mail Order Apocalypse“, which was me applying a wild hair setting idea to an existing ruleset, this project has a different background: I wanted to play in a particular style, and was lacking a game system for that. Not to say that there aren’t systems that could work for this, but there would be compromises and homebrew rules and so on, so I might as well start from scratch!

It is now a bit over a year later, and I’m nearing the finish line. A good moment to take a look back: What design goals did I have in mind, what kind of fun did I want to capture, and do I think I succeeded?

The main drive was that I had accumulated a lot of painted and unpainted fantasy miniatures over the past 30-odd years I’m playing this sort of games. And most of the time, they have been sitting in display shelves or boxes, not being used at all. And I really wanted to use them!

So, I wanted a regular game where I could bring them to the table. And there is a fun in moving them around, counting squares and looking at possible tactics. The game I wanted should support this.

Wanting to have miniatures on the table also sort-of dictates what kind of scenarios and adventures you play: There is little sense of setting up miniatures for a court intrigue, or a detective adventure where the majority of the session involves talking to a bunch of people.

So, combat scenarios it is, and most often, this means dungeon crawling.

And that brought up the next requirement for my prospective new game: I didn’t just collected miniatures over those 30-odd years. Of course I also have a library of adventures and scenarios. It’s a hodge-podge of systems and settings, ranging from one page scenarios to sprawling megadungeons. I should be able to use those in the new game!

Let’s make this a list:

  • I want to use miniatures
  • I want a dungeon/combat focused game
  • I want to be able to easily drop in lots of different scenarios and adventures

Some other things are also important to me, regardless of the game system or setting I play: I like to play fast and player-centric. While I do enjoy the storytelling parts of being the dungeon master, I don’t want to monologue. Instead, the players should be the ones who talk most and who drive the action as much as possible.

I’m most content if I can lean back and react to the players, instead of dragging or pushing them towards a goal of my own.

That also means that I don’t want to be bogged down by too many complicated rules. Every time I have to stop the action and look something up, things get delayed too much in my opinion. So the rules should be very clear and concise, and allow me to come up with rulings on the fly that don’t feel out of place.

So, let’s add two more requirements:

  • Have simple and consistent rules
  • allow for as much player-empowerment and player-centric game as possible

That said, I wanted the game to be accessible to new players, but also provide mechanics and crunch for them to sink their teeth into. Videogames have these skill trees, where one can plan and map out a progression, looking forward to that juicy power at the far end of the tree.

That makes another two requirements:

  • easy enough to start playing within 15–30 minutes of introduction
  • deep enough so that experienced players can plan ahead and spend time „tinkering“.

And then I added one last requirement simply for personal taste:

  • Certain tropes and „problematic“ content should be left out. I always for example hated the pseudo-dilemma of „orc babies“.

Let’s have a look at the individual requirements and how I tried to meet them in terms of game design:

I want to use miniatures

Just put them on the table.“ might be the most straightforward answer, but I also wanted the to be useful for the game. So squares-based floorplans, movement rules and other mechanics that are derived from miniatures were added. I didn’t want to overcomplicate things, so I left out things like which way a miniature is facing and the like.

As a corollary to the use of miniatures, I wanted to make combat a very dynamic thing. Combatants should be moving around a lot, instead of just standing there and bashing at each other. I tried to help this by adding skills and rules that promote lots of movement, and penalized standing still.

I want a dungeon/combat focused game

This didn’t need a lot of conscious effort to make it happen, but having it listed as a requirement did inform me a lot on what I could leave out of the game. There are no rules for social conflict, diplomacy, ruling fiefdoms or similar things. I left out rules for overland travel, or rules to keep track of consumables.

I want to be able to easily drop in lots of different scenarios and adventures

This led me to two things:

  1. I needed to make the game world open and vague enough so that I can drop in a broad variety of other content into it with minimal fuss
  2. Have some sort of idea of how to easily convert monster and NPC statistics into my own ruleset.

To be honest, I haven’t really tackled the second part yet. Mostly because I didn’t need to so far, but I think it won’t need a lot of work. My monster stat blocks are usually short enough anyway, so adapting others should be easy.

For the first part, I found inspiration in the world setting of Earthdawn: The world gets rediscovered after the survivors of some cataclysm finally come back to the surface.

My worlds cataclysm was a war between an evil goddess and the rest of the world. In the end, she was defeated, but half of the continent became inaccessible for a thousand years. That made the south both known (from really old maps and books) but also unknown and dangerous (a lot could happen in those 1000 years).

The player characters are those brave adventurers who venture into the south to rediscover the lost parts of the world, and just maybe preventing that evil goddess from rising again.

All this really allows me to drop in nearly anything that is even remotely of the „fantastic“ genre. The world in the south is mostly just the sketch of a map, leaving enough room for nearly anything.

Have simple and consistent rules

When writing „Mail Order Apocalypse“ I really fell in love with the Into the Odd ruleset again. With just three stats and an „everything is a save“ mechanism, one can easily find rulings for every situation.

Except, I don’t really love-love stats. And I especially didn’t want too much randomness for character creation. No randomness at all might even be best, at least for the core character bits.

Instead, I came up with the idea that „everything is a skill“. Those can be purchased with advancement points, and that’s it. And each skill is a competency. You either are competent, or you’re not. No „I’m 64% good at swimming“

Mechanically, I settled on a pool system, where you throw as many dice as you have skills connected to the task at hand, then count the successes — with each single dice having a 50:50 chance to be a success. Figuring out things usually simply involves sorting and counting dice. No complicated addition or subtraction needed.

That base mechanic is used throughout the game and it proved to be working well throughout playtesting. And I could easily adapt things to new situations on the fly: You get extra dice when something helps you, or you loose successes in certain circumstances.

Player-empowerment and player-centric game

This ended up being more a „how to run the game“ philosophy than hard rules. This is not a story centric game where players have rules-encoded ways to create facts like in Fate. Instead, the rules are written in a way that explicitly leaves a lot of decision-making with the players, and only demands dice rolls when things are very unclear, otherwise favouring the „yes, that works“ answer from the referee.

Easy enough to start playing fast

It is really important to me, that people can jump into the game pretty easily, if guided by a referee who knows the rules.

I prepared character sheets that have all the important bits as checkboxes and easy-to-fill forms, as well as a simple random table to populate ones inventory in one go.

All in all, creating a character takes only a few choices: What five advancements to take, how to distribute life points, and what to put into the inventory. Add a name and a quick description and you’re good to go!

There is very little math involved in this, next to no dice rolling, and not too much agonizing over the skill choices: Five advancements is not a lot, and people tend to spend them fast.

Deep enough for experienced players

This is where the skill tree really starts to shine: People can explore and test and think about different combinations of skills and magic. There are a few obvious combinations, but also a lot that are not so obvious.

The skill tree really offers a lot of flexibility but also planning-ahead material.

Avoid „problematic“ content and tropes

The classic thing I wanted to absolutely avoid are things that can be tinged with racism. In-game populations that are evil by birth just rubs me the wrong way, and it creates moral pseudo-dilemma like the „innocent orc baby that will absolutely grow up to be a bloodthirsty monster, so should you kill it right now?“

I scratched the whole notion of lots of different sentient „races“ and instead ruled (inspired by this blogpost by Cavegirl) that there are no other sentient populations or „races“ than humans. Of course, there are monsters that do monstrous things, but there are no civilizations of orcs that are jus there.

(In fact, in my game world, Orcs are human corpses brought back to beastly life by some otherworldly evil entity)

Similarly, there are no elves or dwarfs in the game world (although there are humans that might fit the stereotypes in some way). Getting this right while keeping to some „fantastic“ vibe is still a work in progress, but I’m getting there.

Generally, the world is more and more borrowing from classic „medieval“ tropes and clichés, so my players can expect a lot more monsters from that sort of place.

Conclusion

I think in terms of the rules mechanics, the game is done. Of course, there’s always more spells and skills and abilities I could add, I should probably revise a few of the random tables a bit, write out more examples and have an editor have a go at the rules to make sure they are really as legible as I want them to be.

And then there is the world: It is evocative, but with only very broad strokes, leaving a lot of room for anything I might want to add later.

It very much supports a West Marshes Campaign style of gaming, where groups from a large stable of characters form and disband to explore different places and return home to report. I have managed to set up some sort of overarching thread and threats, but the player characters are still trying to get a grasp of what exactly these are.

I do wonder if I should write the background of these threads and threats into the gamebook, as inspiration for other referees, or if that would ruin the blank canvas and rob others of the chance to build their own world of the Kari. (Kari being the name of the human empire the game world is centered on)

Self Descriptions made Easy

I have a „Manual of Me“ in my professional e‑Mail signature for a while now. That describes when and how to reach me, and how I communicate or set tasks.

What it doesn’t do in depth or any detail is describing what I’m really good at or what I’m bad at.

And that is something that no team should ever ask from its members. Forcing people to write down or reveal what they are good and bad at is… bad. For multiple reasons:

One reason is that a lot of times, people don’t really know what their relevant weaknesses are. Or they don’t like to face them. Or they know them, face them internally, but won’t ever admit to them to their boss or coworkers. Because, let’s face it, there is a real risk that this will be used against them.

In those cases, you’ll end up with weaknesses as „too driven“, „too detail oriented“, „not taking breaks enough“, with the hopes that they’ll look good.

The other thing is that what I might perceive as a big weakness might actually be insignificant in the team dynamic. Who cares if I can’t do math in my head at the speed of thought, I have a calculator app and a spreadsheet available at all times anyway!

So instead, I recommend thinking and talking at length within a team about how one communicates, decides, and documents things. There are lots of differences on how this can happen, especially if you cross cultural borders by having a diverse multinational team. (see https://​erinmeyer​.com/​b​o​o​k​s​/​t​h​e​-​c​u​l​t​u​r​e​-​m​ap/)

Putting those differences and preferences out into the open is really useful.

Things that are good to explain about oneself

Get your folks to explain themselves in these terms:

  • what are their productive/waking hours? Are they night owls, early birds, or something in between?
  • Do they prefer face-to-face, synchronous, asynchronous or just written communication?
  • How do they like to separate documentation and decision-making?
  • What is their instinct when it comes to looking for information? Which systems do they use, who do they ask (if they ask someone at all)?
  • What are their notification etiquette? Are there times where you shouldn’t try to call them, or is that something you don’t need to worry about?
  • How do they want to get tasks assigned and reviewed, how do they do this themselves?
  • What are their preferred ways of addressing them? Honorific, nicknames, full names, pronouns, the works.

A tangent on leadership

I strongly advise that the team lead or most senior person of the group leads by example here. Don’t put the onus on the others to find out what is appropriate to share or tell, don’t let them guess what is necessary information. This is absolutely a managerial responsibility, to set the tone and expectations in a way that doesn’t discourage people, or makes them write in supplicant answers, in the hope to not look bad.

Communication can and should be trained, but it needs to start honest and open. If your team thinks they cannot be that way, you won’t get anywhere with them.

And power imbalances, even if you’re the most approachable manager of all, are still a thing. Subordinates will always have the next firing/hiring/promotion round in the back of their minds. Individual members of your team might thus not only worry about how they are perceived by you, but also by their peers, who could gleefully exploit any (perceived) weaknesses of others in order to get that promotion for themselves, or to prevent being axed when the inevitable downsizing comes.

Back to self descriptions

Self descriptions are useful. They make unspoken assumptions visible and clear, they highlight the differences between individuals in a way that makes them useful instead of a source of conflicts.

And they provide the basis on which to improve communication and collaboration within a group of people.

These self descriptions are not an end to themselves, they are a tool to figure out future collaboration and communication. Ideally, you encourage everyone to revisit their and other people manuals every now and then too.

I have my own Mastodon instance now

One of the cool things of federated social media is that each instance can have their own rules and conventions.

One of the bad things of federated social media is that each instance has their own rules and conventions.

What do I mean? I started out on octodon​.social and felt pretty good there. Then I realized that a lot of people I followed initially went silent. Turns out that they were on infosec​.social, and for $reasons (reasons I understand, but don’t necessarily need to adopt myself) , the admin of octodon​.social blocked that instance. So I eventually and very reluctantly moved to hachyderm​.io. Turns out, the same thing is happening there too, just with different servers.

Fediverse moderation has several levels:

  • end user self-defense: „This person did something bad and I prevent them from interacting with me.“
  • moderating local content on a personal basis: „This person on the same server as me did something bad, so here are the consequences for them“
  • moderating external content on a personal basis: „This person on a different server as me did something bad, so I limit how they can interact with people on my server“
  • moderate external content on an instance basis: „I find this whole other instance suspect, so I limit how everyone on that whole instance can interact with people on my server“

If my personal sensibilities and those of the people who moderate my insteance differ (and they will absolutely differ to some degree!), you will at best just miss out on a bit of content but at worst will suddenly be cut off from people you interacted a lot.

This is compounded by the fact that there is no documented consensus for moderation across instances. (Like darcy​.is would have provided, btw :) ) You won’t know what’ll happen until it actually does.

So, for me, the problem is this:

A venn diagramm with four circles.  Three circles are arranged so they do not overlap and are labeled A, B, C.  The fourth circle is in the middle and overlaps each of the other three a bit and is labeled "me"

Yep, that is me, in the middle of a few non-overlapping communities. (There are also a lot of communities that do overlap, but let’s ignore those for now) So, when I join a server in community A, and A suddenly decides to defederate from C, I lose that chunk of people. When I join B instead, and they already hate A, I lose out a different chunk.

Finding that elusive instance Z that plays nice with everyone else is gonna be… hard.

And now that folks like Meta and others are opening ActivityPub servers lines are drawn in the sand: „If you federate with Meta, I will block that instance!“ Or „if you don’t protect the children, I will protect them from you!“. Or „We’re sex positive, if you block the furries, I’ll defederate from you!“ 

And here am I, just wanting to talk to my friends and see cat pictures. So, I opt out of the drama and have my own single-person instance now: @jollyorc@social.5f9.de No, don’t ask me if you can join it, I don’t want that kind of responsibility. Take 9 Euros per month and go to fedi.monster, they’ll help you out.

Management books you should read, and what to learn from them

I’ve been on a small bender on this, and this is what I learned, in short. Reading my summaries could spare you the time of reading the actual books, but I don’t recommend it — they are chock-full of useful language and terms to describe situations, which will help you apply the lessons better.

The Art of Action: How Leaders Close the Gaps between Plans, Actions and Results

This is the book about how you best communicate goals and plans to a team, so they can start working on them without being micromanaged. The trick: Explain the Why, then When, and the What (problem), not the How nor the What (solution), then have them repeat these things back to you in their own words to check for understanding and completeness (you might have forgotten something).

Getting Naked: A Business Fable About Shedding The Three Fears That Sabotage Client Loyalty

You want your clients trust. In order for that to happen, you need to be honest with them, especially when it comes to your own shortcomings. Let your successful work stand on its own. Don’t grandstand, don’t pretend your better than them, but don’t be shy to be firm on the things you know to be right.

Radical Candour

Feedback is important, especially negative feedback. It needs to be on time, absolutely honest, and to come from a position of kind caring. If you give feedback in order to belittle, demean or because you’re on a power trip, you’re an asshole. But you’re also an asshole if you don’t give any negative feedback when you see flaws, because then no one can get better.

Reinventing Organizations: A Guide to Creating Organizations Inspired by the Next Stage in Human Consciousness

This is a slightly esoteric book. Read on despite the woo, it gets rewarding. Organisations work better when you let them live like an organism, with purpose and innate reactions instead of programmed machine-like behaviors. When you truly empower people to take ownership of their work, they’ll do better. That means everyone basically manages themselves.

Strong Product People: A Complete Guide to Developing Great Product Managers

I don’t agree with a lot of the actual people managing advice. It is well-meaning, but putting it into action would throw diverse people of all kinds under the bus, as a lot of the advice subconsciously encourages group-think and only hiring people that are like everyone else in the team.

But the idea of defining your good, meaning „figure out what a good person for $Position really needs to be able to do“, and then coming up with a metric on how to measure this ominous „good“ is brilliant management advice, as it allows you to give useful and meaningful and above all, actionable feedback.

The Mom Test: How to talk to customers & learn if your business is a good idea when everyone is lying

Don’t ask leading questions. Don’t ask questions where any desire to please you could colour the answer. Ask open questions that give you useful insights regardless of the answer given.

The Lean Startup: How Today’s Entrepreneurs Use Continuous Innovation to Create Radically Successful Businesses

hah, gotcha: I haven’t actually read this yet. Come back later! :)