Showing posts with label analysis. Show all posts
Showing posts with label analysis. Show all posts

Sunday, November 8, 2026

10 Simple Reasons to Play a Game Other Than D&D 5e

I often say that I vehemently dislike D&D 5e, but that's not entirely true. Mostly I've moved on. There are specific design choices in 5e that conflict with the kind of TTRPG experience that I seek and enjoy. This post attempts to explain those differences.


1. Advantage / Disadvantage
Advantage and Disadvantage is unintuitive. A normal d20 produces a flat distribution where every +/- 1 is worth a +/- 5%. Disadvantage produces a curve distribution where success changes in a non-linear way. The result is that dis/advantage does not have a consistent numerical value. Sometimes feels like a +/-4, sometimes like a +/-5.

Here's where the mechanic really loses me. Rolling a natural 20 with disadvantage becomes a 0.25% or 1 in 400 chance. Meanwhile, rolling a natural 1 with disadvantage becomes a 9.75% or a 39 in 400 chance. I think this spoils the excitement of d20 system where you always have a 5% chance to roll a nat 20 and succeed.

If your design goal is simplicity while preserving the spirit of the d20 system, a straightforward change to the DC or a flat modifier like in Index Card RPG (ICRPG) is easy to understand without spoiling natural 1s and natural 20s. This is why I prefer fixed modifiers rather than advantage and disadvantage.


2. The Catalog
D&D 5e is the culmination of 40 years of D&D. They came up with a lot of bloat in those 40 years, and a lot of it made it into D&D 5e as standard content. I call this the catalog, and it means the list of fantasy races and sub-races, character classes and sub-classes, backgrounds, feats, and spells. There is a lot of stuff for players to choose. All of these player options are expected to be available whenever they receive an invite to join your game. Taking any of these player options away for any reason, such as making a more coherent or cohesive game, presenting a different genre or subgenre, pursing a different setting, etc., is perceived as nerfing or restricting players. They tend to dislike it.

The catalog is a kitchen-sink. It is all the toys in the toy-box. You don't have to play with all the toys, but existence of options creates expectations of availability. Restricting some of the toys can allow you to curate the kind of game you want to play. You can play a slightly different game or a very different game. If you just want to play with just the army men, there are 5e players who want to add power rangers and sailor moon. They will never be content to just play with the army men. You are stuck playing the kitchen-sink version of the game.

I wrote more about restrictions here: 5e House Rules - High Immersion, High Discipline, GM Curated Style of 5e. I also wrote about why human-centric settings better preserve the tone of your game here: Human‑Centric Fantasy Settings: Why Monster PCs Break Tone. I also wrote about how class designs in D&D 5e are a mess here: How to Fix Modern Class Design. 


3. Alignments
I'm not sure alignments ever made sense, and I don't think E. Gary Gygax ever really did a good job explaining it. By the time we get to D&D 5e, most players view Alignment as a personality type. It's not, but that's not what I don't like about alignment in D&D 5e. There are no built-in restrictions on player character alignment, so inevitably you have one player who chooses one of the butt hole alignments. This leads to a group of players that are less cohesive, less cooperative, and maybe even a little adversarial. I've never liked player vs player conflict, and I never found it fun. Any rule that passively encourages or permits it needs to go.

I wrote about what alignments are very simply here: D&D Alignments - How to Use Them! Read this and tell me I'm wrong about what alignments are. 


4. Player Skill vs. Character Skill
I don't like rolling for everything. It's not fun to roll dice and fail. I want the things I say or do in-character to have their own merit and be worthy of success or failure by the logic of the fiction or setting. I can show you where in the 5e DMG (2014 version) that it says the DM can decide to not use the dice except for in combat. It's page 236 of the DMG, under the section The Role of the Dice.

Quote: "One approach is to use the dice as rarely as possible. Some DMs use them only during combat and determine success or failure as they like in other situations."

That's rules as written, and that line says that the literal written word of the rules is not Rules As Intended (RAI). 

In 5e, everyone seems to think you have to resolve everything with dice. I've played with multiple GMs. They want you rolling for everything. It's ridiculous, it discourages players putting in any kind of effort, and it slows the game down. What I'm subtly referring to is a concept called player-skill-forward which I wrote about here: Player Skill vs Character Skill - Managing Expectations. I also wrote a Primer for No Speech Mechanics in TTRPGs and How to do Speech in TTRPGs (without dice!) which requires a player-skill-forward playstyle.


5. Hard to DM
I would argue that this game is harder to DM than other games. When running Index Card RPG (ICRPG), I could easily keep all my notes to one or two pages and comfortably improv. Prep was a breeze for ICRPG too, and it didn't take a lot of my time.



6. Hit Points in 5e Suck
In GURPS, the rules of the game are intended to model real world physics. There are pros and cons to this, but in attempting to model real world physics, the game is intending to describe objective reality. A GURPS human has 10 HP by default, and there is an upward limit on how much HP a GURPS human can have. 18 is a lot of HP for a GURPS character. This makes damage proportional, objective, concrete, and intuitive. You know if you do 6 points of damage that you've done a lot of damage no matter what scope or scale you're playing.

There are also rules for recovering lost HP that are intended to model real healing and recovery. It makes the in-game world easy to understand. Anything that makes the game easier to understand makes playing the game faster, even if you need to handwave five or ten in-game days to recover after a fight.

Meanwhile, in D&D 5e, everything is a damage sponge, and so combats go on and on and on. Within the narrative, you can stab someone with a spear, and then they can nap it off, which is absurd and immersion-breaking. Tension is difficult to have in a game like 5e, and combat is a slog. It's suits a cinematic style action game but with cartoonish rules.



7. Combat Is Boring
Combat is boring and I'm tired or politely accepting it; But if it's not boring, it's because the GM went and threw some bonkers-high CR monsters at us. Part of the reason why D&D combat is boring is because of HP which I just commented on. The other reason why D&D 5e combat is boring is because it's just too slow.

I would first suggest simplifying turns. Every player gets only one thing they can do on their turn, and they can move up to their normal movement as part of their action. Say what you do, say how, roll your dice.

I wrote a few blog posts about why the game is slow and how to speed it up:


8. Fantasy Ruined Monsters
There are two kinds of monsters: horror monsters, and monsters as exotic people. I think all monsters work best as horror monsters and were probably intended to be horror monsters until twentieth century children's books softened them. Somehow, modern fantasy has inherited the softer version of monsters, and you won't often find the horror monsters in D&D 5e. They're just exotic kinds of people now. I don't like it.

Almost everything gets humanized except maybe zombies and aberrations.

I wrote a few things on this: Monsters in Fiction, Modernity Ruined Monsters, and 


9. Setting
The setting by default makes room for everything in the catalog I addressed above in item 2. This necessarily means the setting must include things that don't feel like they belong. That means the setting lacks cohesion and a feeling like it makes sense. 

Fantasy doesn't mean anything goes; I don't need a realistic setting, but I do need a setting that feels like it makes sense. The default assumptions about a game influence its tone.

I wrote a few things how elements of the setting conflict with each other here: Human‑Centric Fantasy Settings: Why Monster PCs Break Tone and 


10. Tone
I have been hinting at it, but I haven't said so explicitly. The tone of 5e games is cartoonish. It's hard to take seriously. When normal people watch you play your modern 5e game, you all look goofy. You're playing a game where paladins, a class described as a "devout warrior" and "standing against forces of evil", can use a divine smite on a bugbear, where a divine smite is literally named divine and is described as dealing radiant damage, meanwhile a bugbear is described as a goblinoid which is described as mischievous. It sounds like a misuse of divinity and I think by the giggles and cackles from the other players, they agree.

Tone means the mood or atmosphere, or, how the audience / participants should feel. How are we supposed to feel?
  • You get stabbed. You take a nap and you're all better.
  • Characters can take a lot of damage and keep going, and they seem to do so without regard for their safety.
  • Monsters aren't monsters, they're just misunderstood people.
  • Elves are just humans with pointy ears. Fish people, mushroom people, and fire people can just live in the same village.
At the end of the day, D&D 5e feels silly.


Conclusion
Every gamer wants to play D&D 5e and are reluctant to find another game. Therefore, if you want to play any other TTRPG, you'll have no one to play it with. This frustrates me because I don't want to play D&D 5e. There's a lot of games out there and I want to encourage everyone to find one other game they like. Just one! Here's a short list of free alternative games and games like D&D: How to Play D&D for Free.

Also reference this blog post from 2024: 5 Things I don't like about D&D 5e

If you're looking for a suggestion to get your players to try another game, read this: How to Convert 5e Players: The World Within a World Strategy.

Friday, November 6, 2026

Your Fantasy Names are Bad - Grounded Worlds Need Grounded Names

When I need a name, I pull one from the Bible. I do this whether I'm writing fiction, GMing, or creating a player character. Here's why.

Bible names are ancient. These are 2,000+ year old names. I know Christians don't like it when you call their religion a mythology, but let's agree to disagree. If you're of the belief that the Bible is describing myth, then these names are actual Earth mythology. This is the deep Earth lore. How cool is that? These names evoke myth without spectacle.

They're grounded. They are real names, not fake names. Grounded worlds should have grounded names. You might call them plain Jane, boring, or vanilla. You might have some other derogatory way to describe them. I rather approach these names like the Doctor from Doctor Who. He meets someone with a really plain or old-fashioned sounding name, and it makes him smile real wide, then he compliments it three times. 

They're recognizable. Bible names are universal. If your culture doesn't have any Bible names, you might have variants or you might have names that are inspired by or derived from Bible names; or vice versa. Maybe the Bible names are inspired by or derived from the names in your culture. For example, here's a table of 5 common bible names in 10 different languages.

English Spanish Portuguese French German Italian Russian Arabic Hebrew Greek
Mary María Maria Marie Maria Maria Мария (Mariya) مريم (Maryam) מרים (Miryam) Μαρία (Maria)
Joseph José José Joseph Josef Giuseppe Иосиф (Iosif) يوسف (Yusuf) יוסף (Yosef) Ιωσήφ (Iosíf)
David David David David David Davide Давид (David) داود (Dāwūd) דוד (David) Δαβίδ (Davíd)
Sarah Sara Sara Sarah Sarah Sara Сара (Sara) سارة (Sārah) שרה (Sarah) Σάρα (Sára)
John Juan João Jean Johann / Johannes Giovanni Иоанн (Ioann) يوحنا (Yūḥannā) יוחנן (Yochanan) Ιωάννης (Ioánnis)

They're cultural touchstones. This means a widely recognized symbol or reference point within a culture that carries or evokes shared meaning, value, or stories. Bible names have sacred meanings to a lot of people. People who have these names are named after characters from stories that inspired friends and family, or because the character embody values or virtues that the parent believes are important. When you name your kid a Biblical name, you're not just saying "I think this is a pretty name", you're saying, "I want my kid to have / spread this meaning / value / virtue".

They carry emotional weight. Cultural touchstones aside, sometimes you name your kids after Uncle John or Aunt Ruth because they were a beloved member of your family. Most people with Bible names actually have two names; a first name and a middle name. This tradition comes from people being torn between naming their children after a Bible character or naming their children after family or important friends. Having a first name and a middle name solves the problem. If you meet someone who has a Bible name and some other name, ask them about that other name. It might be interesting.

They feel low fantasy and human scale. They feel like real people, not fantasy caricatures. Bible names aren't just names, they're part of the world's tone. Maximus Decimus Meridius is a cool name, and to some people so is Goku, Vegeta, Vash, Monkey D. Luffy, Ichigo, and Naruto; but those names don't suit low fantasy and human scale. These names describe characters who shoot lasers out of their hands and can crush planets while they shape nations or decide the fate of a planet. Meanwhile, David is a guy you might meet at a hardware store.

They're Good for World Cohesion. When you create a period setting, you should use names the sound like they go together and sound like they describe a place in time, a culture, a language, or a myth. It's about choosing a naming convention that reinforces the world’s emotional logic. It’s the same instinct behind:
  • Tolkien using Anglo‑Saxon and Norse names
  • Earthsea using simple, elemental names
  • The Witcher using Slavic names
  • Dark Souls using medieval European names
Modern and Sci-Fi settings can get away with breaking these rules to an extent. I mean, Luke Skywalker anyone? Luke!


Don't-Do's of Names
At the very least, here's a simple list of rules for what not to do with names:
  1. Avoid names that are hard to spell and hard to pronounce. These make names that are hard to remember and they slow down play.
  2. Don't pick names that lack cohesion with the setting (or joke names) because they make world feel fake. You might think Rex is a cool name, but who named you that in a low-fantasy period setting?
  3. Don't pick names that carry no emotional weight. Bob can be a strong name if there's a strong reason behind it. People think Atticus is a strong male name because of the character Atticus Finch. You need a cool namesake to make your name cool.

Sunday, November 1, 2026

Game Mechanics Are About Feel, Not Function

I think what makes a game mechanic work is not that it's functional or logical, rather, it's how it feels to the participants when playing with it. Let's look at HP for example. What is HP but your margin of error? More HP, more margin of error. Less HP... You get it. 

Once you have the realization that HP is your margin of error, you might ask yourself how much HP is too little, too much, or just right? One odd question you might ask yourself is what else can be treated as a margin of error? This is where game mechanics get creative. A game called Crown and Skull doesn't have HP. Instead, your skills temporarily go down from hits. This represents how your characters wounds and injuries affect them. When players take a hit, players get to decide which skill gets diminished, and so players have some say in the narrative, and the game doesn't have to burden the GM with everything.

So, for instance, let's say sword is a skill and your sword skill is 5. You get hit, you lower it to 4. When all your skills are 0, this represents an accumulation of wounds that finally end you. When you get an opportunity to improve a skill, you're also improving your toughness in a manner like HP. Sounds logical, right?

With game mechanics and systems, what I'm concerned with is not how they work, but how they feel. Does the game feel fun, does the game feels tense, or does it feel like too much bookkeeping. Does the mechanic make me overthink the concept to the extent that its distracting?

Importantly, would I rather be using another or a simpler mechanic?

So, let's say I had a game where gold replaces HP. The first thing I ask is what sense does that make? What if characters had magic hour glasses. The hour glasses turn gold and golden treasure into gold dust. The gold dust drains away at a rate of one gold piece per day. If you run out of gold dust, you die. The magic of the hourglass makes you indestructible, but in exchange it takes gold away when you should be hurt. In effect, your life is dependent on gold. The scarcity of gold is what makes the game tense. Too much gold, no tension. No tension means you have a boring game. Too little gold, players become too risk averse, and the game is too stressful.

From the GM side, the tracking and allocating of gold becomes a major function. It sounds like finding the goldilocks zone is really, really challenging and once players discover the formula, does that spoil the illusion of the game? How do you feel like you improve? By being able to carry more gold than before?

I think the reason why HP or health is so ubiquitous is it’s ease of use which comes from its intuitiveness, in spite of its other problems like being an over-abstraction of damage and healing. And also, taking a hit and subtracting HP feels better than taking a hit and subtracting skills or items or money or armor. Even though gold as HP basically eliminates the need to spend gold on healing items and other supplies, and skills as HP eliminates a need for a wounds and injuries system, at the end of the day, HP feels better than other mechanics, probably because it's familiar, simple, and easy to visualize.

There are different ways to do HP. In D&D for instance, HP models luck, skill, and fatigue as a buffer until 0 HP which implies a single, serious wound has KO'ed you and threatens your life. You can sleep off a major fall or massive beating. Because it's an easily relishable resource, it has less value. Because you can have 10 HP at level 1 and 100 HP at level 10, it doesn't objectively describe or model actual harm in the world. D&D 5e makes HP feel like a cartoon character or cinematic action hero getting beat up. It makes combat feel like a sport or a game to live out a power fantasy. It's intended to be fun. The opposite is GURPS which explicitly describes HP as a measure of your body's capacity for injury. There is a low HP cap. If you take a massive hit, you roll for shock and knock down. If your HP drops to 0, you roll against incapacitation and death. GURPS makes HP loss feel like sustaining actual harm, and it makes combat feel deadly and frightening, and consequences can last.

GURPS HP inspired Bright-Dark 3d6 HP, not D&D HP. Bright-Dark 3d6 uses low HP to keep tension high and consequences meaningful.

If you're going to create or critique a game, I want you to think in terms of what do the mechanics model, how do game mechanics feel, and how do all the mechanics feel when used together. That's important because the way a game feels is ultimately why people play it. If it feels good, they play it and they enjoy playing it. If it feels bad and they're still playing it, are they enjoying it? What do they enjoy about it? How much enjoyment are they getting, and is it worth the parts they don't enjoy? The way a game feels is part of the value of the game to the participants.

But also remember that everyone has their own kind of fun; see also: Types of Fun (MDA Framework)


Saturday, October 31, 2026

D&D 5e Runs on DM Judgment: A Guide to Adjudication

First, what is adjudication? To adjudicate means to judge or to make a decision about a situation. You take contextual information from the situation, you apply rules and subject knowledge, and you make a ruling. You decide what happens and how it happens. This is one of the roles of the game master (GM) or dungeon master (DM) that is misunderstood by new people (and sometimes not so new people). Today, I'm going to teach you to adjudicate your pretend games.

I'm going to assume everyone is playing D&D 5e and I'm going to be referencing the 2014 version a lot, but this advice should apply to all TTRPGs. Before we get into adjudication, first let's discuss two different ways to interpret the rules. One is called Rules as Written (RAW) and the other is called Rules as Intended (RAI). Discussing and understand these two interpretations is valuable because it means we'll all be on the same page.


Rules as Written (RAW)
Rules as written (RAW) is an interpretation of the rules as literal.

In the PHB, the section for Ability Checks reads "the DM calls for an ability check when a character...attempts an action that has a chance of failure." This is a description of a rule.

Some DMs extrapolate rules as written to mean that this is how the game is played; that any time there is a chance of failure, an ability check is required. Note that rules in the Player's Handbook (PHB) are often written to be referential not instructional, meaning a rule describes how it works, not how the game is played. How a rule works and how the game is played mean two different things.

We know that the DM has to make a decision about whether or not a roll is needed. Instructions for that are not provided in the PHB, they're in the Dungeon Master's Guide (DMG) instead. I hope to show you that the DMG teaches judgment, not procedure.


Rules as Intended (RAI)
Rules as intended means the game's author has an intent other than a straight reading and literal interpretation of a rule. In other words, the author intends that DMs understand how the rule works and decide when and how to use them, or not to use them.

Class, please open your D&D 5e 2014 Dungeon Master's Guides to page 236 and read the section The Role of the Dice.

  • Quote: "Dice are neutral arbiters...The extent to which you use them is entirely up to you."

This is the game's official instruction to DMs on when and how to use dice. Keep this quote in mind for a few more paragraphs.

This section of the DMG has three subsections: Rolling With It, Ignoring The Dice, and The Middle Path. They describe three different styles for running D&D where you roll for everything, roll for almost nothing, or roll somewhere in the middle. All styles are permitted by the official core rule book.

My favorite passage comes from Ignoring the Dice.
  • Quote: "Some DM's use them (the dice) only during combat and determine success or failure as they like in other situations."

If you're reading the rules RAW, these two quotes together should recontextualize everything in the core rules for you. In case you missed it, let me explain what the official DM instructions permits in D&D 5e (2014 version). Ahem. The DM decides when checks are needed.

The section of the DMG I have shared with you, The Role of the Dice, reveals the intention of the author:

Your preferred implementation of the rules is permitted.


The DM's Criteria
Now that we're all on the same page about RAW and RAI, we can talk about adjudication. Adjudication is not rules mastery; it's applying common sense to the fiction of the game. By what criteria does a DM use to make rulings? From the section Using Ability Scores on page 237 of DMG:
  • Quote: "Only call for a roll if there are meaningful consequences for failure."

The question then becomes what is a meaningful consequence for failure? The answer is loss of time, resources, opportunity, or immediate harm.

Let me tell you what is not meaningful:
  • Rolling for something free of stress and conflict.
  • If you fail and nothing happens.
  • If you have unlimited chances to re-attempt the action until you succeed.

Therefore, if a player wants to attempt an action, you the DM must determine whether there a consequence of loss or harm. If not, the action succeeds automatically because to call for a roll otherwise trivializes rolling dice and slows down the game. The determination that a player's action is automatically successful is part of your authority as the DM (reference the DMG, page 236-237, subsection The Middle Path.


Example - Lock Picking
Take lock picking for example. To pick a lock in 5e, the books explain that the character makes an ability check and applies their proficiency bonus from the tool (thieves' tools in this case). I call this a tool check for simplicity.

If the player is in a safe, comfortable place and they are attempting to pick a lock (let's say a wooden strong box they found on their last adventure), and they have all the time in the world, they successfully pick it. They just do. No rolling. Why? Because they will eventually get it open.

What if the player is trying to open that same locked strong box in a dungeon with dangerous random encounters? Then every attempt costs time. Lost time in a dungeon means torches burn away, light spells expire (not that this matters in 5e in particular), and there are chances of a wandering monster interrupting the distracted character. The DM can call for a roll here. On a failure, time passes, resources dwindle, danger approaches.


Tangent - What do the Rules Forbid and Permit?
What if the character doesn't have proficiency with a tool?

The way 5e is written, 5e very rarely, almost never states what is not permitted. It almost always states what is permitted. I think this is by design. If so, this is good to know about the books because it helps us understand them better.

If you don't have proficiency, RAW, you simple can't apply the proficiency bonus to an ability check. The rules don't state that lacking proficiency forbids characters from attempting actions or using tools.

The only instance I can find in the core books that forbid a player from attempting an action without the right proficiency is DMG, page 102, under Locked Doors, "...doing so requires thieves' tools and proficiency in their use." This appears to be an inconsistency in the game's instruction and possibly due to an oversight.


How Difficult is an Action
D&D 5e gives DMs instruction about choosing a difficulty class (DC) from pages 238 to 239. Let's look at some.
  • Quote: "It's your (the DM's) job to choose a difficulty class for an ability check or saving throw when a rule or adventure doesn't give you one. Sometimes you'll want to change such established DCs."

I read this to mean that the GM may always choose the difficulty class when they believe it's appropriate. If you're running a published adventure or a monster from the monster manual, you may change an established DC.

  • Quote: "Think of how difficult a task is and then pick the associated DC from the Typical DCs table."

This means the DM decides how difficult a task is, and DMs do so using a scale that the game gives:
  • Very Easy (DC 5)
  • Easy (DC 10)
  • Moderate (DC 15)
  • Hard (DC 20)
  • Very Hard (DC 25)
  • Nearly Impossible (DC 30)
The DMG is written like it's advising you to pick a word, not a number. It says "...think of how difficult a task is, and then pick the associated DC from the...table." The number is associated with the word. It tells you your game can be completely functional if you stick with Easy (10), Medium (15), Hard (20).


Objective vs Subjective Difficulty?
Objective difficulty means standardizing DCs for everything with the expectation that the DM is intended to use them. Subjective difficulty means that the difficulty is subjective to an individual's feeling or belief. As previously discussed, the DM chooses DCs when none are provided, and the DM may change a DC established by an adventure or rule.

When you choose a DC when there is none, you are evaluating the action yourself. When you evaluate an established DC, you may change it. The game trusts you and gives you the authority to do this.


Changing Established Game Content
Remember my tangent about how D&D 5e is written to be permissive rather than restrictive?

Page 6 of the Monster Manual has a sidebar that reads "Feel free to tweak an existing creature to make it something more useful to you." Then it refers you to the DMG. Page 273 on the DMG has a Section Creating a Monster and a subsection Modifying a Monster.

You're given guidance here, but no restrictions. The pattern in 5e is that the books repeatedly give guidance, examples, and procedures, but then returns authority to the DM.

This should go without saying, but the author's intent is not anything goes. Remember RAI? The DMG reminds you that changes to statistics change the monster's CR. The game still intends for you to adhere to their Challenge Ratings (CR) system. It gives you tables and explanations to understand the design logic of D&D 5e.


If You Fail, Do You Fail Forever?
Can players repeat failed actions? Short answer: Some but not all.

DMG, page 237, under Ability Checks, ability checks are defined as a test to determine whether a character succeeds at a task. That's it. One task. In fact, this section of the DMG explicitly tells you that players can repeat a task, and to save table time, you can assume that a player who spends ten times as long on the task automatically succeeds.

Note that this portion of the book resolves some situations in your game where players want to repeat checks ad nauseum. This works for things like picking locks or tying knots unless the character is in a rush, under pressure, or in danger.

This section of the DMG also says that no amount of repeated checks can turn an impossible task into a possible task, and, in some cases, failing a check makes it impossible to make the same check to do the same thing. It also says that you can decide if initial failure makes repeated checks more difficult.

How do you know which checks can't be repeated?

Short answer: DM judgment.

How do you judge this? Consider that this is not just a game, it's also a fiction and a setting. Ask yourself what makes sense within the fiction and the setting?

Let's say a player wants to pick a lock in a dungeon. As already discussed, you may call for a roll. If you fail to pick a lock in real life, you simply fail. The lock doesn't break. Neither does the tool. This action can be repeated.

Let's say a player wants to disarm a trap in a dungeon. On a failure, the trap springs. That means the player logically gets one try. The action cannot be repeated unless the trap is reset and needs to disarmed again.

Were you to tell a player no they can't repeat an action, consider your justification. Would you tell them that they can't repeat an action because it's already been done? What changed that prevents them from repeating it? Would you tell them "that's the way the game is played." That justification would be arbitrary and contrived, and the player would justifiably not be satisfied by this ruling.

How about making a knowledge check? Note that the PHB uses the word "recall" rather than "possess" in the descriptions of knowledge skills (arcana, history, nature, religion). Meaning we roll int (knowledge) checks to determine if a character recalls knowledge, not whether a character possesses knowledge. This allows for a possibility that any knowledge can be possessed by any player character, but success of recall varies.

The definition of an ability check (DMG page 237) is for a task, therefore recalling knowledge is a task. I would rule that knowledge is one of those cases where failing a check makes it impossible to make the same check to do the same thing as previously discussed. In other words, failing a knowledge check means you can't recall the knowledge until you try something different or something within the fiction changes. Maybe you hear a new rumor or piece of lore and you can justify "maybe this jogs my memory. I try to recall knowledge." That works for me.

How about for repeated speech checks? Read your DMG pages 244-245.
  • Quote: "Once a charisma check has been made, further attempts might be fruitless or run the risk of upsetting...the subject creature potentially shifting its attitude...Use your best judgement."
I think that portion "Use your best judgement" is the game giving you its trust.


Is the Character Aware That They Failed?
Have you had this experience? "I roll stealth. Uh oh, natural 1. Guess I'm detected!"

First, that is called metagame thinking or metagaming. The player is aware of the concept of an ability check, a die roll, and a natural 1, but the character isn't. Reference DMG page 235 Metagame Thinking. 

Second, when / how does the character become aware that they failed a task? I would also like to point out that page 237 of the DMG defines ability checks as a means to determine success or failure for a task. This definition does not state whether or not the character is aware of success or failure.

So how does a character know if / when they failed (if it's not obvious)? 

We're talking about the moment in the game when the outcome of a task is revealed. 

Option 1. One preferred way to handle this is to hide the rolls from the players; The character finds out when the player finds out. Make a roll when the player declares an action and save that roll for when (or if) it's needed.

Option 2. Consider this: As a DM you don't just decide whether a roll is needed for a task, but also what moment during the game to call for a roll. If a player says "I sneak", you don't have to call for a roll until there's someone or something that can perceive the player character. Then either call for an opposed roll (stealth vs perception), call for a stealth roll vs a DC, or use passive skills, or whatever.

When the failed roll becomes relevant within the game, then you reveal consequences. That's how the character finds out (if the result is not obvious).


Deciding Consequences
The game does not prescribe consequences (outcomes) for success or failure of every action. Sometimes failure means failure, but what happens on a failure is based on the context of that moment in your game. The consequences ought to be what would logically happen on a success for failure within the context of the fiction or setting.

Avoid punitive consequences or gotcha's.

Page 174 of the PHB, the last sentence under Ability Checks reads "...failure, which means the character...makes no progress towards the objective or makes progress combined with a setback determined by the GM."

Did you miss it? RAW, failing an ability check doesn't automatically mean nothing happens or that no progress is made.

Page 242 of the DMG, under Resolution and Consequences, it reads "You (the DM) determine the consequences of attack rolls, ability checks, and saving throws. In most cases, doing so is straightforward...As a DM, you have a variety of...approaches...to make things less black and white." It then lists several options:
  • Success at a Cost
  • Degrees of Failure
  • Critical Success or Failure
These is a core rule, not an optional one, not a variant. I've never played with these rules. I've never heard anyone talk about degrees of failure or succeeding at a cost in 5e. It's very oddly overlooked in discussion about D&D 5e.


Trusting the DM - DM Resolutions and Descriptions
The GM is supposed to be fair, neutral, and consistent. You're not going easy on the players or making the game difficult for them. Arbitrary, contrived, inconsistent, or capricious rulings diminish trust in the GM.  

Once you decide how to resolve an action, you describe it. Your DM descriptions are your players feedback about their actions in the world. DM descriptions need to be objective and clear. If success or failure is supposed to be a mystery until the consequences are revealed, that's fine if it's understood; otherwise, the DMs descriptions should not be ambiguous. "The knot is secure" or "The knot is loose", not "The knot looks good to you" or "You think the knot is secure". Ambiguous descriptions lead to players attempting to repeat actions just to make sure they're safe. Ambiguous descriptions lead to players being suspicious of DM descriptions. That's not cooperative or collaborative play.


Conclusion
Many new DMs approach the game as though the books are trying to provide complete procedures for every situation; however, D&D 5e expects DMs to exercise judgment far more often than they may realize. Honestly, I don't think D&D 5e is beginner friendly, but hopefully you now know that the rules and dice do not determine the game, the GM determines the game with the rules and dice as tools. The rules do not replace the DM's judgment, they support it.

I spent about 10 hours on this post. After writing a game of my own (Bright Dark 3d6 Role-Playing Game), I have a new appreciation for the amount of work that goes into writing a rule book, and by writing this post, I have a newfound respect for the 5e designers and the 5e game itself.


Related: If you're interested in reading more rules that might change the way you think about D&D 5e, I wrote The Authority of the GM / DM which lists many rules across the three core rule books with an explanation or interpretation.

Wednesday, October 28, 2026

Deck of Playing Cards - A TTRPG Exploration Mechanic

Honestly, I think the best systems, mechanics and minigames have been invented. If you create new ones, I think they need to mesh with the basic gameplay loop:
  1. GM describes scene
  2. Players choose action(s)
  3. GM determines results
  4. Repeat
I personally need a TTRPG to keep this gameplay loop.

If you want to use a deck of cards for exploration, here's how I would start.
  1. Shuffle deck.
  2. Placed cards face down in grid or another pattern on the table. The layout represents spaces / rooms / areas where they can move.
    • Wilderness or city: plain grid
    • Dungeon: arrange like a weird maze. Each card is a room.
  3. Tell players where they start (usually the middle card). This card is face up by default.
  4. On players turn, they can make one move. To move, they chose one adjacent card and flip it. Based on the card, there is an encounter or event. Suits tell you a category
    1. Club = combat
    2. Diamond = treasure or fortunate discovery
    3. Heart = good NPC encounter
    4. Spade = environmental hazard or trap
    • Lower / higher numbers can refer to an item on a table or a list, or you can interpret the number and improv the results. Example: Low bad, high good.
    • Royal cards can but don't have to matter. My first instinct is that they represent major locations, major characters, major discoveries, etc.
    • Jokers mean something bad.
Scale:
  • Dungeon: 1 move = 10 minutes
  • City: 1 move = 1 hour
  • Wilderness: 1 move = 1 day
I think this could be playable. The grid creates spatial meaning w/o a map. Suits are intuitive so there's less cognitive load. Numbers determine severity so you can interpret the card and improv the fiction from the card. You the GM would say "you're in a wilderness. What do?" Players say "we go northwest." They flip the card. You tell them "you're in forested hills. Here's some features and sensations." Then you read the card and tell them what happens that turn. Done and done.

Players make choices. Consequences happen.
It's tactile and visual.
It's minimalistic and easy.
If players have fun, then you know this works.

Flaws? Maybe you want to balance the game more towards combat, hazards, and treasure, and less on encountering good NPCs? OK, take out some or all of the hearts, or change what the hearts mean for this location.

Friday, October 23, 2026

Player Skill vs Character Skill - Managing Expectations

There is a discussion in the TTRPG hobby called Player Skill versus Character Skill.

Player Skill describes a playstyle where players solve problems in the game using their own creativity and problem-solving skills. Examples:
  • 1. Players using their own persuasiveness to convince NPCs to help them. The player makes an argument in character, and the GM evaluates it in character, then responds.
  • 2. A player describes how they interact with a feature of a room or scene. If their description would reasonably allow them to find something hidden, then they just find it. For example, if they describe pouring water onto the floor and the game master describes that it drains through a crack of a pressure plate in the floor. They player has revealed a trap automatically!
  • 3. If a player wants to sneak, they describe how they use their environment effectively to avoid line of sight, how they minimize sounds like taking off their noisy armor or jangling weapons, etc.

Character Skill describes a playstyle where players solve problems in the game primarily using powers and abilities on their character sheet.
  • 1. A player declares an intent to persuade an NPC, then rolls some dice and invokes a game mechanic, such as a speech skill.
  • 2. The player declares an intent to search the floor for traps, invokes a search or perception mechanic, and rolls a die.
  • 3. A player declares an intent to be sneaky and invokes a game mechanic by rolling a die.

Player Skill and Character Skill describe two completely different kinds of games. They feel different.

The feel of games with player skill
  • 1. Gives more value to game master descriptions of the room or scene.
  • 2. Incentivizes good player narration, creativity and improv in the moment.
  • 3. Rolling dice is a fail-state for poor creativity, planning, or decision making!
  • 4. Deemphasizes the need for rules knowledge and systems mastery.
  • 5. Solve problems with your wits and know that the dice won't arbitrarily spoil a perfectly good idea!
  • 6. More freeform, rules-lite game.
  • 7. The game becomes simpler and more intuitive. You don't need to know the rules; instead, just understand that anything that can reasonably happen in real life is allowed in the game.
The feel of games with character skill:
  • 1. Players make decisions based on knowledge of game mechanics rather than imagining and describing clear actions.
  • 2. Players are incentivized to master the rules and systems of the game, and even exploit weaknesses in the game design.
  • 3. A greater emphasis is placed on rolling dice, and the game master's interpretations of the dice can feel arbitrary or contrived. Actions that have no business succeeding can succeed, and actions that have no business failing can fail. This can cause ludo narrative dissonance and loss of suspension of disbelief.
  • 4. Creative actions and good planning can grant bonuses, but some players are most creative outside the game when creating their character.
  • 5. Players refer to or rely on their character sheet for answers to problems.
  • 6. Character options get classified as either optimal or sub-optimal, and all decisions eventually become a matter of doing the optimal thing over and over ad nauseum.
  • 7. Good ideas get questioned because there isn't a clear rule for it, and we look for the rulebook to tell us if it's allowed or if it will be helpful, even if it reasonably would or be.

So, if we're playing a game that emphasizes player skill, why do we have game mechanics? Mechanics are not for solving problems, and they're not for resolving uncertainty. They give structure to the game, and they're for simulating actions that need to be simulated. If you want to strike a stationary object, you can just do it because there's no chance of failure. If you want to strike an opponent who's actively fighting back, then we use the mechanics and dice to simulate the outcome. We need to simulate combat because we can't hit each other with swords at the game table, but we don't need to simulate lying and haggling because we can actually do that!

Further, you don't need a mechanic for everything. Mechanics are only needed for things that absolutely need simulation, nothing more. Everything that can reasonably be solved through the logic of the world or narrative should be. This is what the game master (aka the referee) is for! If your opponent is no longer able to defend themself, you don't need to roll a die to hit them! You don't need a rule to tell you that if you take off your heavy metal armor and heavy backpack full of treasure, you can sneak, climb, swim, run and jump better.

What Does My Character Know?
Sometimes, players ask the GM something like "would my character know anything about X?" Either the player is knowledgeable about the game and the setting and wants to confirm what of their player knowledge they may use, or the player has no knowledge about the game and setting, and they want the GM to tell them what their character would reasonably know.

The Character Skill approach to the game is to allow the player to roll an Intellect or Knowledge check or test, or to invoke some feature of their character that lets them automatically possess and recall that knowledge.

The Player Skill approach to the game is to instead tell the player "why don't you explore the world and find someone who does know?"

Consider that this situation is a regular part of that game and liken it to a puzzle. It's a puzzle that can be solved in different ways. With the Character Skill approach, the player merely has to think to use a game mechanic. The solution is then either presented to them or it isn't. If it's presented, the players can then move onto the next challenge. The pacing of the game or major points in the narrative is fast.

With the Player Skill approach, the player has to rely on their own creativity and work out their own solution within the setting and narrative to solve the problem. They can think to research at a library, gather rumors and news from a tavern, or to search for an NPC expert within the setting and ask for knowledge. Access to that expert may have some prerequisites, like gold or a positive reputation. The player may first have to learn about the expert by asking around town. This is a type of discovery and is fun and rewarding to some players. Earning access to an expert NPC can also feel rewarding to some players. It gives more value to the setting by placing more need on the players to learn and understand the setting and the people in it.

The differences between the two styles also means that the player characters are either self-sufficient with non-material resources, or they are a group who occasionally have to make time to gather non-material resources.

Which approach to play is preferrable? Depends on you! How do you have fun? Do you want to solve the puzzles by flexing your own mental muscles, or do you want to solve puzzles by rolling dice? I'm sure there's pros and cons, and there might even be times when one approach is preferrable, and times when the other approach is preferrable.

Mapping
While exploring, either a wilderness or dungeon, how do your characters know when they're lost?

A Character Skill approach would say that players can use a game mechanic and know that they're lost, and then potentially use the game mechanics to figure out where they are. The players may also have access to a map or other visual aid to show the world and their process in it.

The Player Skill approach might say that your characters will know when they're lost in-game the same way that you would know you're lost in real life. You walk or drive around for long enough asking "how far is it? How long have we been traveling? Are you sure we're going the right way? Did we pass it? Does anyone recognize where we're at?" In my experience, recognizing that I'm lost in real life is a process rather than a eureka moment.

Getting lost in the wilderness or dungeon can be dangerous. You can run out of resources, get sick, die to exposure, or be attacked by some dangerous wild animal, monster, or human. Being lost is the obstacle and a source of tension. Being able to find your own way out of it is the solution, and to improve at navigation to avoid getting lost in the future is another solution.

Imagine the roleplay prompt: "you're lost in the dangerous wilderness with limited supplies and a deadline to save the victim of the monster. What do you do?" Some people want to work this out scene by scene, and they want to un-stuck themselves using their player skills. There's potential for team building and learning skills. One solution is to find higher ground, like climbing a hill or a tall tree, then you can see further. The game master will describe what you can see, and then you can work out landmarks and navigate your way back. The adventure was unexpected. There's also a chance to discover something you weren't looking for while you're lost.

Player Skill Over Character Stats
Your player skill is your character's luck, wisdom, intelligence, and charisma. Think. Be careful. If you the player get a funny feeling that something is not right, it's OK to use that feeling in play to keep your character safe. Don't hold back just because your character has low stats!

Game Balance
Do not assume the obstacles and challenges are balanced to match your character's abilities. Rely on your own creativity and ingenuity. There is no right way to overcome a challenge. Not all obstacles need to be overcome; some can be circumvented. Fleeing is always valid. Make sure you always have a way out.

Conclusion
At the end of the day, Player Skill vs Character Skill isn’t just a mechanical distinction, it’s a question of what kind of game you actually want to play. Some tables thrive on dice-driven certainty and character sheets full of buttons to press; others want a grounded, intuitive world where clever ideas matter more than modifiers. Neither approach is universally better, but they create completely different experiences, and mismatched expectations will ruin a game faster than any bad die roll. So decide what kind of play you enjoy, communicate it clearly, and build a table that buys into the same style. When everyone understands the expectations, the game becomes smoother, more immersive, and a lot more fun.

Related: Game Design Sins - Character-Skill over Player-Skill is a post about D&D 4e skill challenges and why they stink.

Sunday, October 18, 2026

One-Page Campaign Form - Managing Expectations

Today, I want to show you some GM aids that reveal two completely different philosophies about running TTRPGs. We're going to talk about them, then we're going to talk about why using a GM aid like this important. First thing to note is that both of these documents are created by the GM / DM and are made available to the players.

Below is a link to a one-page Campaign Planning Form that is standard in GURPS. Open it up and read. Then come back.

What did you notice? What does it emphasize?

Below is a link to a one-page My Campaign form by Matthew Coleville (of MCDM). Read it and come back.
https://drive.google.com/file/d/1ZK5E4Qg3AnfZLj68v6_3sioGrPmrw4Be/view

What did you notice? What does it emphasize?

Comparison: Contract vs Syllabus
Let's compare and contrast these campaign forms as they are both the same tool, but they show different approaches to TTRPGs.

The GURPS campaign form is about defining the limitations of the game and the setting. It starts broadly with genre, realism vs cinematic, and theme. It defines the level of technologic development (stone/bronze/iron age, medieval, steam, modern, futuristic, etc.) and tells you what kind of political powers are in charge and how much control they use. Then it tells you what is allowed at character creation and what isn't, and what the setting thinks about some characters. Finally, it tells you which supplemental books are permitted because GURPS has a lot of them.

Meanwhile, the MCDM campaign form tells players what's in the setting. It's more of a checklist of cool and useful stuff. I'm not sure if its author intended it to be a GM only document, but it can definitely be a player aid. It helps you structure your setting by establishing the pieces of it so that players can do cool stuff and have fun adventures.

The GURPS form is a contract. The MCDM form is a syllabus.

Analysis
The GURPS form defines the scope of the game. It is the GM telling the players "here's the kind of game I'm running, and you need to create a character who fits." It's a constraint document that intentionally narrows the scope of the game. It prevents mismatched expectations. If you join the campaign, you agree to these terms.

The MCDM form, if used as a player aid, orients the players. It gives context. It assumes (high) fantasy genre already and it does only a little to modify the genre or tone. It tells you about one small location, it hints at the greater political system and cosmology, shows a few geographical features, and a few small enemy factions responsible for conflict. Here's what you know, here's who you talk to if you want to learn more. The "Here's what locals think about dwarves, hobbits, elves" section softly tells the players how these fantasy races are in this setting, framed as how they are perceived.

Both forms are useful. Both are smart. But one campaign form solves more problems than the other.

The GURPS form is better suited for managing expectations than the MCDM form. The MCDM form, while it has a space for you to detail how different fantasy races are like in his world, it does not restrict their use by players. The from does not detail what is allowed or disallowed: classes, races, backgrounds, race-class-background combinations, languages, feats, multi-classing, equipment, magic. It doesn't explicitly state what kind of style or tone to expect. It is still a kitchen-sink. Meanwhile, the GURPS form can directly, explicitly say it's a fantasy-sci-fi genre, elves and magic are not in this game, and here's what happens in this setting if you use Psi abilities.

Use the GURPS form if you want to tell your players what nonsense isn’t allowed. Use the MCDM form if you’re fine with whatever nonsense is allowed.

One of the problems with a social contract is that it's unspoken. This sort of campaign document is a snapshot of your specific game, and it should be standard in TTRPGs. Seriously. It's not just "oh, we're playing an Eberron campaign, and the big bad is a tarrasque". This also lets players know all the little particularities of your presentation of the Eberron setting. Your particularities are the highlight of the form because you're the GM and you need to let the players know what kind of game you can handle running, and what kind of game you can't. This should be completed and available when you pitch your game to prospective players.

My Form
After reading these two forms, I decided I wanted one that suited my game, Bright-Dark 3d6 Role-Playing Game. Below, I have provided a link to a one-page campaign document with the items that I think are valuable right now. Your needs / tastes may vary.

Leave a comment on this post. I would appreciate come feedback on this concept and on my form.

Optional / Add-Ons:
What else could be added that's valuable?
  • Related Media: What books, movies, etc. that are similar to your game. This helps orient players fast. If you list Nausicaä of the Valley of the Wind or Firefly, that might stop them from thinking about making a character who would suit The Fifth Element or Breaking Bad.
  • Recommended Reading: Supplemental RPG books, documents, etc. Maybe you wrote a short story about characters in your world, or maybe you have a detailed setting document.
  • Homebrew: Are you big on homebrew? What's your homebrew stuff, or what play-brew stuff is allowed?
  • House Rules / Optional Rules: Every table has this. Make yours clear.
  • All that Lovely, Lovely Session Zero stuff: You know, violence, gore, and whatever other weird no-go zone types of stuff. Player vs Player? Play-styles focus / emphasis, heavy roleplay or heavy bookkeeping, PC death, game balance, game fouls, etc., etc.
  • Miscellaneous. More things in life need a misc. section than you think. 
Related
Hyper-Gratuitousness in Fiction and TTRPGs is an excellent post that you might find valuable for your TTRPGs if you want to include darker subject matter with care.

Sunday, October 11, 2026

Worldbuidling: Geopolitical Hotspots = Human-Scale Conflict

When I see worldbuilding content on the internet, people don't start with the geopolitical hotspots, and that's a problem.

What is a geopolitical hotspot? It's a place where two or more cultures come into military, political, or economic tension. Often due to disputes or competition over territory and resources.

Geopolitical hotspots = conflict

Starting with the geopolitical hotspots is the shortcut you need to make your world map interesting. In fact, throw out the concept of the world map for a second and just focus on a regional map. Your campaign isn't global scale (yet). You only need one region where multiple cultures are fighting over the good stuff. That's what makes a good fantasy map.

What people tend to do is they get lost in the weeds of realistic world map or they want a map that's visually pretty or exciting. They ask, "do the mountains belong there?" and they get stuck. I'm not telling you that it's wrong to ask if the mountains would logically form there like that; That actually can serve to make your map more believable. What I'm advising is to make concessions on realism for the sake of forcing, even contriving a geopolitical hotspot into your world.

Serious man, just put it in!

Sample Region Map - The Calean
Here’s a simple example to show how a geopolitical hotspot turns a plain map into a story engine. Below is a region called The Calean. It's named after the central feature, the Calea Sea. It's a very simple map I cooked up in I don't know, half an hour?

Full disclosure: I traced it from another map found in this video by the YouTuber likealightart9414. I hope he doesn't mind. Then I named everything. In his video, likealightart9414 said he didn't like this map. *Scoffs* excuse me?


For this map, realism, scale, aesthetics, or ready-to-play-ness are not the intent or goal. It's here to teach. 

Cultures
Distinct cultures turn geography into a story. I want you to identify the four major kingdoms / nations: Adamia, Bethland, Erlina, and Gregoria. I know there's other stuff on this map, but these four areas are the main points. Arbitrarily, we're going to ascribe to them distinct cultural identities.
  • Adamia: Militaristic, imperial. Value law and order. Lots of noble houses and bloodlines.
  • Bethland: Famous for art and science. Value luxury. Perceived as soft. Meritocracy with a raising merchant class.
  • Gregoria: Very religious, courageous, humanitarian. An unmatched naval power. A budding republic with a powerful symbolic monarch.
  • Erlina: Stubbornly proud, tough, and wealthy. Famously use mercenaries and foreign armies to fight for them. They have resources and you can't take them away.
What's important (to me) is that the cultures are distinct. You can immediately evaluate the aspects of the culture like the colors and mascot of a team in a competition and pick the one you like.

Boundaries
Next, let's look at how geography shapes their relationships. Creating a few boundaries means you have an area where kingdoms may blend without losing their distinction, and where the contrast is most immediate. These are places where political, economic, or military tension is most apparent.  

River Nina separates Adamia and Bethland, and it also coincidentally marks a climate boundary. Which climates specifically? Well, scientifically speaking, Adamia is kind of cold, Bethland is kind of warm. There you go. These are now two distinct areas, and it adds variety to the cultures and political powers.

Gregoria is connected to Adamia by an impassible isthmus where The Stellas mountains are. The logistics of marching an army across are mindboggling, so there are no land invasions. 

Reina Mountains separate Bethland from Erlina. You could say there are a few mountain passes, but it's easier to travel by sea.

The Calea Sea has not one but two choke points: The Delilian Straight controlled by Gregoria and the Felixan Straight controlled by Erlina. If you want to get in and out of the Calea Sea, you have to be on good terms with at least one of these cultures. Naturally, Erlinda and Gregoria compete over Isle Levi which creates both straights.

The fact the Erlinda and Gregoria have a competition going, there isn't one single power who monopolizes passage in and out of the Calea Sea. This competition is important because it makes being on good terms with one nation or the other important.  

Calea Sea
This sea is the main artery connecting everything. That's what's the point of the sea, but why is there conflict here? Resources? Trade? Colonialism? War? Religious conflict? Bad blood? That's up to you, but it is important to define why these powers are in conflict. Try and come up with a few conflicts. Here's an example:

  • Adamia and Bethland compete over control of the River Nina. It's an nutrient-rich, important waterway that can take you inland. Adamia claims that their snowcapped Adamant Mountains (just off the map) feed the Nina. 
  • Erlina competes with Gregoria over control of the Isle Levi and both straights.
  • Adamia competes with Gregoria over silver mines in The Stellas. Both nations are also competing for control of that northern coast.
  • Erlinda and Bethland have territorial disputes and the various passages of the Reina Mountains as boundary is unclear. There are smaller cultures here too: Mountain people who make iron goods and practice war, and valley folk who farm goods for them.
  • There are also small islands. The inlanders consider themselves part of the kingdom that controls them, but because they are isolated, they also consider themselves distinct from their continental peers and resent the continental conflicts.

Finale
Geopolitical hotspots matter because they give your setting human-scale, actionable content to engage in. It's not "We must take the ring to Mordor" content, it's "The British are Coming!" content. It's "Then the Fire Nation attacked" content.

Checklist
  • Major powers with distinct cultures
  • Vulnerable minor cultures in between
  • Valuable resources
  • Natural boundaries
  • Choke points
  • Territorial disputes
  • Competing interests
  • Climates, history, terrain, myth as flavor at the end
Use this checklist to turn any blank region into a living engine of story, politics, and adventure.

Related: How to Create a Fantasy Setting (Loria) shows you what to do from here.