Sunday, November 15, 2026

From Thief to Rogue - Class Identity

What is a rogue and how does it fit into the setting?


Meaning of Rogue
Classic D&D had three classes. The thief class was the first DLC. Over time, the thief class was renamed to rogue, and it probably had something to do with TSR trying to soften D&D's image in response to the satanic panic. There's a difference between thief and rogue.
  • Thief = Someone who definitely steals
  • Rogue = Someone who lives a life that ordinary folk disapprove of

What I like about the word rogue is, like fighter and magic-user, it's vague. A fighter can be a samurai, a legionnaire, a knight, a barbarian, or anything that resembles a warrior. A magic-user can be a witch, a wizard, an enchanter, a mage, etc., etc.  The vagueness of the word gives the player more room to flavor their character. A rogue could be a thief, or they could be a swashbuckler, a bandit, a gangster, a pirate, a ninja, or an assassin.

Vague words for class names means for room for GM and player creativity, but it also means the class becomes more ambiguous.

To reiterate my first question: What is a rogue and how does it fit into the setting?

Rogue Origins: The Thief
When the rogue was added to the class roster, you had four classes that described four distinct playstyles:
  • Fighter = Martial
  • Magic-User = Magic
  • Thief = Skill / Utility
  • Cleric = Combination

The rules of the game also describe the setting. Therefore, the classes implicitly describe the world and how your character fits in there.
  • Fighter = Military Class
  • Magic-User = Scholar Class
  • Thief = Criminal Class
  • Cleric = Clergy
This interpretation neatly explains why the thief fits in with these three classes.

The Fighter trained and likely fought on behalf of some lord. The Magic-User studied and earned money by contributing to a scholarly collection or providing a magic service. The Cleric lived a life of discipline and earned money through collections and tithes. All three of these characters earned their place in the world through their various specialties. They had a place in society and they contributed.

The Thief rejected conventional work and existed outside of traditional institutions. The thief was the odd class because the thief is an opportunist who circumvents the rat-race with high-risk, high-reward crime. Sometimes they belong to gangs, but not necessarily. Their concept of work is quick and easy scores.

The thief lives their life their way. That is really why the new class name of rogue suits them.


Paradigm Shift: From Intelligence to Dexterity
Since World of Warcraft and D&D 4e, the rogue has become known as the DPS or damage per second. The DPS playstyle emphasizes prioritizing high damage output over defense or other strategies.

That's weird. Why would a thief be better at doing damage than a warrior?

The soldier is expected to be strong. High strength adds to damage. The rogue? Not so much. The rogue has to get in, hit, and get out quick. Ah, I know! Let's give the rogue really high Dexterity!

Prior to the DPS concept, your rogue benefitted from having high Dexterity, but no more than anyone else. The thief was the character who had skills. In fact, originally, they were the only class with skills. In classic D&D, level determined how high the thief's' skills were. Ability modifiers weren't as important to thief skills prior to third edition.

Then, when D&D 3e came around, Intelligence was actually a distinctly important statistic for the thief because of the way skill points worked in D&D 3e.

See, in 3e, you earned skill points which you would spend to raise your skills. Each class got a base amount of skill points. The formula was base class value + Intelligence modifier per level. Fighters, Clerics, and Wizards earned 2 + Int modifier, but Rogues earned 8 + Int modifier.

You can see how skills are in the DNA of the Thief / Rogue and how it would be viable to create a high-intelligence thief in D&D 3e.

The smarter a rogue was, the better they were at being a rogue.

This makes sense to me because being cunning, clever, and witty is how you do your rogue thing and stay safe. You avoided trouble with your mind first and if you failed, you fell back on dexterity for running and hiding. Avoiding harm is an expectation of the rogue. Their signature feature is cunning action after all.

By the way, did you know finesse weapons didn't exist in 3e the way they exist in 5e? Weapon Finesse was a feat. You couldn't add Dex to modify melee weapon damage from the start.

Modern fantasy rogues are perceived as agile combatants who sneak attack and maneuver. Classic D&D instead presented them as people who were not martially competent but made up for it with unconventional skills.


Personality - What Kind of Person Becomes a Rogue?
What kind of personality do you have to have to become a rogue? One would assume you have to have a disposition for it. Maybe people expect you to be shifty, bold, daring, and cunning. Maybe you have to be someone who craves freedom and dislikes the demands of society? Maybe they're merry mischief makers, scam artists, rebels, or ne'er-do-wells?

I always thought that the rogue was the adventuring class option for ordinary people who were forced to become adventurers by circumstance. This is the entry point for normal people without combat training, magic, or miraculous powers.

Like Bilbo Baggins. He never burgled a day in his life but was recruited for it.

I rather think that the thief or rogue class is the every-man class that includes the occasional scoundrelly figure. It's the gateway into adventuring for the untrained but clever and resourceful. You're not the powerhouse, the tank, or crowd control. You're the regular guy who's finding his mettle while on a quest for something greater than you.

At least, that's one interpretation and it's one I'm really attached to. And here's what else it does, it loops back into my question, how does your rogue fit into the setting? This starter-adventurer rogue is not a gangster, cutpurse or con-artist. The word rogue becomes a misnomer. Society regards adventurers poorly because adventurers are dangerous and crazy people who defy conventional wisdom and risk certain doom for fortune or glory. The rogue is the plain, ordinary person who dared to cut themselves from normalcy, and they've in a sense gone rogue.

The reluctant adventurer everyman rogue. The story arc is how someone without any powers can earn a place next to great warriors and wizards. That's the kind of rogue I want to play. Maybe it started because you were the survivor of disaster, or maybe you simple don't fit in at home, and one day you left it behind.


Identity: Ingenuity
First there were three adventuring classes: Fighting-Man, Cleric, and Magic-User. No one believed there was a place for an ordinary man. Then came the thief. Can't fight as well as a fighting-man. Can't wear armor. Can't use shields. Can't use magic. Can't turn the undead with faith. What do you do?

The thief: "I make it up as I go."

Friday, November 13, 2026

Wizard Class - Class Identity of the Magic-User

What is a wizard? You're probably thinking about this right now. When you overthink things like I do, meanings of concepts get overworked until they're not recognizable.

Nomenclature
In English (the official language of space and time according to Doctor Who), the "-ard" suffix is attached to the end of a word to denote when someone is of a condition. Example: dullard, drunkard, and wizard. If dullard comes from dull, and drunkard comes from drunk, where does wizard come from? Wiz?

Wise.

Literally, wizard means someone who is wise. A class of the wise. That's a heck of a label for a class. Is this the intelligentsia class?

Wizard as a word originally described a learned person. The association with magic or the occult came later, but that's outside my area of expertise.


Original D&D Classes - Origins of the Modern Wizard?
The original D&D game had only three classes: Fighting-Man which later became the fighter, Cleric, and Magic-User which has since become the wizard.

Classes in Advanced D&D 1e had level titles, which, at least aesthetically, resembled ranks. The titles got more prestigious as you leveled up. Fighter earned titles like soldier, knight, then lord (or lady). Clerics earned titles like acolyte, village priest, bishop, and patriarch. A magic-user enjoyed various titles that don't immediately denote more prestige, and they weren't called a wizard until level 11.

If the rules of the game describe the setting, and by some interpretations they do, classes might describe social classes within the setting rather than just character classifications within the rules. This is actually a very good way to ground the mechanics of your game within the world. Fighter resembles the military class. Clerics resemble the clergy class. Magic-Users resemble the, what, class of scholars? Arcane? Mystics? Sure.

In classic D&D, there was an assumption that when you reached your level cap, the game changed from adventuring to domain play. I have no idea how it worked, but each class secures land, builds its own stronghold, and earns its own followers.

Here's the caveat, there appears to be differences in roles for domain play depending on your class.

While fighters were the sort of military commander, the wizard was more of an advisor or strategist. The sounds like a mentor archetype in fiction. The mentor character is typically a supporting character in fiction; not the main character. Oof. Ouch, Gary.


What is a Wizard, Really?
See, here's the thing. There's no real-world equivalent for a magic-user or fantasy wizard. It's made up. That makes it an abstract concept. Even if we all think we understand what a wizard is, someone else can come along and redefine what a wizard is for their game or fiction, completely turning the concept on its head and subverting all conventions, and they're technically not wrong to do it. You would simply say their version of a wizard is different.

In fiction, wizards are typically the mentor, advisor, scholar, or villain rather than hero.

Who are the famous wizard-mentors of fantasy? Merlin. Gandalf. Dumbledore. Obi-Wan Kenobi. Yes, Obi-Wan counts! Watch Episode IV, A New Hope! He totally counts!

Also, Dumbledore is in there now. Good on you, JK Rowling. You know you are successful as a writer when one of your characters can be counted among classical archetypes. Respect.

What happens when the full-fledged wizard becomes the protagonist?


Doctor Who?
The Doctor is a fully-fledged wizard-protagonist. He's a scholar, a traveler, a keeper of obscure knowledge, someone who understands things ordinary people do not, he solves problems through knowledge rather than force, he mentors younger companions, and he seems mysterious and supernatural from the perspective of ordinary people.

Just replace his sonic screwdriver with a magic wand. Replace the TARDIS with a wizard's tower. He doesn't perform spells, but he has the wisdom to perform scientific feats that are like magic to others because no one else can replicate them.

D&D says wizards are magic artillery. Literature says wizards are wise.

The Doctor is often the most powerful person in the room because he understands the situation better than anyone else. That is a wizard according to the classical definition.

Magic isn't what makes a wizard. Wisdom is. It's in the name!


What Kind of Magic-User Are You?
Circling back to classic D&D, the old name for the wizard class was Magic-User and wizard was a high-level class title. They chose magic-user as a class name because they weren't concerned with what kind of magic-user you were, like illusionist, necromancer, wizard, warlock, or sorcerer. They were only concerned that you were a magic-user.

In this line of reasoning, what kind of wisdom does your wizard possess? What kind of wizard are you, and how does your wisdom fit into the setting? Are you an occult scholar? A sage? A scientist? A strategist? A seer? A teacher? A healer? Yes, I'm counting healers!


D&D 5e Wizards Are Still Wizards (Kind of)
Modern D&D distinguishes wizards from other spellcasting classes by the source of their magic. Wizards learn spells through study, practice, and mastery. They can research spells and add them to their spellbooks. They're categorized into arcane traditions which focus on specific schools of magic (abjuration, conjuration, divination, enchantment, evocation, illusion, necromancy, and transmutation).

The D&D 5e wizard is relatively in line with the concept of a wiz-ard. I would tweak it by giving them more utility spells and less damaging spells.


Conclusion
The identity of the wizard is wise one rather than powerful one. You're more than your spells. When you play a wizard, figure out how you fit into the setting. You start out as an apprentice wizard at low levels. Your experience makes you wiser. Your growing power is an expression of that wizening. By higher levels, get an NPC apprentice. Pass it down. Your wisdom is who you are. It's your legacy. And put a little bit of the Doctor in your character!

Wednesday, November 11, 2026

Fighters are Universal - Class Identity

Having played enough D&D 5e and having lurked in enough internet spaces where people discuss the game, I can tell you that human fighters are statistically the most commonly occurring characters in D&D 5e (according to some old, published data from D&D Beyond here and here), but also the most criticized as being really basic, simple, or vanilla.

I take issue with this criticism. The fighter is not basic. It's a blank slate.


The Classic D&D Fighter
Classes in classic D&D determined your playstyle and your role in the party. Classic D&D did not balance the classes so that everyone was equally valuable in every situation. If you wanted to excel in combat, you picked fighter. No one else had as much HP, could hit as well, could get their AC as high, or use magic swords.

Fighters were the all-star in combat. Everyone else was back-up. Modern D&D powered everyone else up. The fighter doesn't stand out anymore. They lost their niche a hardest to hurt and hardest hitting to the Barbarian.


Every Culture has its own Fighter 
The word fighter means one who fights. That's it. It's intentionally vague. It doesn't prescribe what kind of fighter you are; it just describes you as a fighter. It's up to you how you want to flavor your fighter within the setting. Are you an Amazon warrior, a Roman Legionnaire, a Samurai, a Knight?

What is a kung fu practitioner or a shaolin monk, what D&D effectively calls a Monk, but the fighter of its own culture? What is a Barbarian but a fighter from a technologically underdeveloped culture? What is a Paladin but a religious fighter? What is a Ranger but a fighter who traded heavy armor for outdoor survival skills?

If you're not sold, Barbarian, Paladin, and Ranger began conceptually as sub-classes of fighter. Barbarian appeared in issue 63 (1982) of Dragon magazine published by TSR. The Paladin first appeared in Supplement I: Greyhawk (1975). The ranger first appeared in a newsletter called Strategic Review (1975), published by TSR. All specifically as fighter sub-classes.

Fighter means fighter. Whatever your cultures' concept of a fighter is, that's what your variety of fighter is. You are your culture's warrior class. That's all. Sub-classes rather than separate, distinct classes, are a great way to capture that flavor and mechanical variety.


Military or Warrior Class
If you're a fighter, how do you fit into the setting? The easiest way to insert you into the world as a fighter in a way that makes sense is to decide that you are somehow a part of your culture's military or warrior class. This is easily done as many cultures have required men of fighting age to be able to fight. Where you a militiaman? Were you a soldier? Where you a conscript? Where you a knight? Did you become a mercenary when your service was done?

Lots of men went into military service, either as a rite of passage, societal duty, or by force.

Very rarely did some farm boy pick up a sword for the first time and go slay some monsters as some fiction will depict (Lunar the Silver Star anyone?).


The Fighter's Place in Society
Defending the homeland has always a need of civilization regardless of the size or scale of the home. This was the job of the soldier or warrior. Chances are that veterans are seen as protectors, valiant, strong, tough, and tested. They put themselves in danger for everyone else. They are typically worthy of some amount of respect, and they probably had a few inspiring stories to tell that each matched a mark on their body.

Fighters are the heroes of society whose deeds are rarely witnessed by the people they love, and some of those deeds come with aches and pains and nightmares that never go away. This is why they are respected.


When a Fighter Turns Rebellious
Deserters and traitors are what first come to mind when you think of a rebellious fighter. Deserters are the ones who ran. Traitors are the ones who sold out their homeland or their fellows for some reward, or to avoid pain. These are bad, but what happens when fighters turn their sword arms on the people in their own homeland?

A brigand is a soldier who came home, found it unrecognizable, banded with others like him, and they turned their violence onto the innocent. A dark knight is a knight lost his lord and so he painted his armor black and began to work for himself. The same goes for a ronin. These men are dangerous because they don't have the mentality to stop themselves, and their skill with arms and experience means they can't be put down except by seasoned soldiers.

Invaders are most likely to be fighters.

In fiction, we also like to romanticize a fighter who turns evil and comes back to punish society for stealing his life and deciding his fate. Maybe this is an evil paladin or a Sith warlord, or an ordinary man who became extraordinary through his trials and sheer willpower.

These are all fighters.


The Difference Between Fighters and Normal Men
Fighters are all men who have been initiated into a new world of violence. The reasons might not always be the same but are always justified to someone. Maybe you needed to eat. Maybe you needed to serve society whether you wanted to or not. Maybe you're rather join Gangis Khan's army than be slaughtered. Any reason is justifiable to someone who wants to be able to sleep at night. Even the ones with the most justifiable reasons may still struggle to get a wink.

Fighters are the ones who carry the mental and physical wounds of society for the greater good of society. Whether it catches up with all of them or not is uncertain. What makes the wounds worth enduring? Is does the individual glory? Is it the salvation, fortune, security, or prosperity you earn for yourself or others?

Some fighters fight for duty, some don't. Either way, I think what defines the fighter is resilience. Every soldier I've ever met has this one quality. They've gone through the initiation, and they've come out tougher. They know that what doesn't kill you makes you stronger. They've taken wounds and they recovered. They've lost brothers and they've mourned. They've taken life and reconciled it.

The fighter isn't defined by weapon mastery or their cool armor. They're defined by this intangible thing: resilience. You are the one who gets back up.

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.

Wednesday, November 4, 2026

Bright‑Dark 3d6 - Session 0 Checklist

Bright-Dark 3d6 Role-Playing Game doesn’t need a sprawling D&D-style Session 0 because the game already solves the ambiguity problem. The tone, genre, danger level, and realism are baked into the system. So instead of 30 questions, Bright‑Dark needs about 6-9 all laser-focused on the emotional, thematic, and narrative cohesion that makes Bright‑Dark work.

The Essential Bright-Dark 3d6 Session‑0 Questions
These aren’t generic TTRPG questions. They’re tailored to the Bright-Dark tone: grounded, melancholy, hopeful, dangerous, human.
  1. What does your character care about deeply enough that the GM can build stakes from it? In other words, what matters to you so deeply that losing it would hurt?
    *This is the most important question to running Bright-Dark!
  2. What kind of Bright-Dark story are we telling?
  3. How grounded and dangerous should the world feel?
  4. What themes do you want your character to explore?
  5. What level of supernatural presence do we want?
  6. How connected are the characters emotionally?
  7. What boundaries or sensitivities should we respect?
  8. How much spotlight do you want?
  9. What is your character’s quiet hope?

1. What does your character care about deeply enough that the GM can build stakes from it?

In Bright-Dark, stakes are personal.
The world may be dangerous, but danger only becomes meaningful when it touches something the characters care about. 
  • Before play begins, each player should tell the GM what matters most to their character: a hope, a fear, a relationship, a promise, or a fragile part of themselves they cannot bear to lose.

This is not backstory for its own sake.
It is the emotional anchor the GM uses to shape conflict, tension, and consequence. Adventures begin with the world’s troubles, but they become Bright-Dark stories only when those troubles threaten the things the characters hold close.

Knowing the Characters to Create Stakes
When the GM knows the characters, the stakes write themselves. When the GM does not, the story has no weight.


2. What kind of Bright-Dark story are we telling?
Bright-Dark is a tone, not a genre, but there are flavors:
  • wandering melancholy adventure
  • intimate character drama
  • quiet survival
  • mythic but grounded fantasy
  • soft supernatural intrusion
  • political or social tension
This question aligns everyone’s expectations for emotional weight and pacing.


3. How grounded is the world’s danger?
Bright-Dark thrives on believable stakes.
  • Are you comfortable with realistic injury?
  • Are you comfortable with characters being afraid, shaken, or vulnerable?
  • Should danger feel constant, occasional, or rare but serious?
This sets the lethality dial without needing D&D’s “gritty realism” debates.


4. What themes do you want your character to explore?
Bright-Dark characters carry wounds and small hopes. Examples:
  • Grief
  • Redemption
  • Trust
  • Found family
  • Quiet courage
  • Moral ambiguity
  • Healing
  • Sacrifice
This question ensures every character has emotional weight that fits the tone.


5. What level of supernatural presence do you want?
Bright-Dark uses magic sparingly and meaningfully. Options:
  • Low magic (rare, subtle, mysterious)
  • Medium magic (present but not flashy)
  • Mythic intrusions (angels, spirits, cosmic forces)
  • No magic (pure grounded drama)
This prevents mismatched expectations like “I want flashy spells” vs “I want realism.”


6. How connected are the characters?
Bright-Dark works best when characters care about each other.
  • Do you already know each other?
  • Do you share a wound?
  • Do you share a hope?
  • What binds you emotionally?
This avoids the “we meet in a tavern” problem entirely.


7. What boundaries or sensitivities should we respect?
Bright-Dark deals with melancholy and vulnerability, so you need clarity on:
  • Violence level
  • Emotional triggers
  • Interpersonal conflict
  • Romance boundaries
  • Moral themes
  • Lines and veils
This keeps the tone safe without breaking immersion.


8. How much spotlight do you want?
Bright-Dark is character‑driven, so ask:
  • Do you want lots of personal scenes?
  • Do you prefer ensemble scenes?
  • Do you want slow‑burn arcs or fast arcs?
This prevents overshadowing or under‑involvement.


9. What is your character’s quiet hope?
This is the most Bright-Dark question of all.
  • What small thing keeps your character going?  
  • What fragile hope do they cling to?  
  • What do they want to protect?  
This gives you emotional anchors for the entire campaign.


Why Bright-Dark Only Needs These 9
Because the system already defines:
  • Tone  
  • Realism  
  • Danger  
  • Genre  
  • Pacing  
  • Supernatural logic  
  • Moral texture  
D&D needs 30 questions because it can be anything. 
Bright-Dark needs 9 because it is something.
  • This game is focused.  
  • The tone is intentional.  
  • The implied world is coherent.  
  • The mechanics reinforce your themes.
  • So, Session 0 is elegant, not bloated.

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.