Buy 4 albums, get 1 free! Grab the audio you'll use for the next 30 years.
Skip to content

Describing Monsters: Making Every Bear Feel More Alive (Part Two)

A photo of a black bear lying on the ground.
Photo courtesy of Oliver Morgan Media

“The monster moves towards the player character. It tries to bite them, hits, and deals 8 points of damage.” This kind of commentary has all the information a table needs, but it can easily feel uninspiring and dull. Describing monsters needs to set the imagination of the players alight.

However, “the monster slithers, slides, and lunges across the broken flagstones. Rearing back, venom drips from its fangs as it gazes at our hero, Firtes, a hungry look in its eyes. In a flash, it strikes! Sinking those fangs into Firtes’ shoulder, the venom pumps into his veins, feeling like fire” is way, way too long. When descriptions go on and on, it slows down play, players lose concentration, and it saps the fun.

In part one of this mini-series on reskinning monsters, I focused on the theory side of monster design; concepts and names are the starting point for original-feeling monsters, even when they use the same stat block. This article is about making those “bears,” along with any other monster, feel more alive during encounters. The goal is active, vivid descriptions, in as few words as possible.

The Three-Detail Rule for Describing Monsters

Knowing when to shut up is an underappreciated skill for TTRPG gamers, GMs and players alike. GMs in particular need to know when to interject and how long to speak for because they usually talk more. Take too long, and players start feeling they’ve been shanghaied into story-time. Conversely, be too reserved and players struggle with what to focus on or feel the game is unfair.

So, as a loose guideline for describing monsters, I recommend a three-detail rule. There isn’t a universal, one-answer-fits-all answer, so treat this as a rough baseline; mix it up from time to time; it’s not an absolute rule.

The three pieces of information should sound cool or fantastical and give players actionable information. In particular, they should focus on:

1. What makes this monster look and/or sound different to other monsters? Alternatively, what noticeable strengths or weaknesses does it have?
2. How does the monster move or behave?
3. How will it attack?

For instance, the monster in the introduction might get a description like:

The monster slithers on rough scales that shine like diamonds. The thing’s maw gapes wide, venom oozing out from long fangs. What do you do?

The players should realise they are facing a monster on the ground; it’s going to have a bite attack; additionally, its skin could be valuable, but also could provide a high armour or defence rating.

Imminent danger (i.e. how it will attack next) is one of the most important things to telegraph. Just to be clear, do not wait to hint how the monster attacks until the attack itself; this can feel like a ridiculous rug-pull in a bad story. See any M. Night Shyamalan film after The Sixth Sense for reference. Details should come either before initiative, or, at the latest, before anyone has acted. The players should know what’s coming and have time to respond before a hit.

Describing Monsters: Suggestive Approaches

Possible ways to approach the encounter are also good details to include. There’s no expectation the players will act on the information—players will always be players after all; however, at least alternative options have been highlighted. Consider this monster:

The thing jolts and slithers through the air, its body crackling with electricity. Curious, intelligent eyes assess you. Its body pulses blue, the crackling getting louder and louder. What do you do?

This time, the PCs are encountering a flying creature. It might be about to attack using electricity or a lightning-like ability. However, “curious,” “intelligent,” and “assess” suggest the party may have a social way out of the situation if they act fast enough. That’s if, and it’s a big if, they want to avoid a fight.

Here’s another example:

The monster gnashes its glittering teeth and paws the ground with vicious talons. But you also see its ribs plainly visible through slack, purple skin, and hear its ragged breathing. The thing snarls, but never moves away from the nest of speckled eggs behind it. What do you do?

This is another melee monster, this time using both teeth and claws. However, it is likely starving and low on health. The monster is also protecting a nest and unborn young. Again, the PCs could murder-hobo the creature and make a fine omelette; it’s always an option. But staying out of threatening range of the nest is an obvious alternative. Then there’s the question of what happens if they feed the beast and help protect the eggs?

Not every encounter needs to be a moral conundrum; sometimes omelette-making is fun. However, even with minimal description it’s possible to set up potential narrative turns; even “bears” can challenge players with more than just fights.

Stacking Descriptions Round By Round

The three-details guideline has an obvious issue. Although this series is primarily aimed at quickly improvising “bears,” what about more complex monsters? One solution is to stagger the information.

For instance, what about a dragon-like monster? At minimum, it probably has decent Armour Class, intelligence, a breath weapon, bite, claws, tail sweep, and wing attack. In this case, I’d prioritise the most pressing information: its size, defensive stats, movement, and most dangerous attack (the breath weapon); if saving the breath weapon for later, I’d add its next likeliest attack (the tail sweep, for example):

With a beat of mighty wings, this huge monster rises into the air, diamond-hard scales glimmering. A molten shimmer from its mouth betrays a rising fire even as it swishes its powerful, spiked tail. Reptilian eyes, centuries old, give you an arrogant glare. What do you do?

The players are now aware of the movement, defences (both the creature’s armour and intelligence), tail and breath attacks; they might anticipate the wing attack as well, but it’s always better to be sure with open communication; that will come later.

Are there more than three details here? Absolutely, it’s more like a guideline, anyway. However, facing something as complex as this is unusual, so it fits a pattern with occasional—and appreciated—exceptions.

Describing Monsters without Unfair Surprises

Giving both the breath attack and tail sweep clue gives me options. Even if I choose fire breath this round, there’s no surprise when the monster tail sweeps later, and vice versa.

Also, further options are easy to add by giving information when the dragon gets hit, or at the end of the round. For example:

Our hero Firtes stabs up with his spear, powering through the beast’s tough hide making it roar in pain. It looks down at this ant who dares hurt it, flexing its dagger-length claws with murderous intent.

Or similarly, at the end of the round I might announce:

The monster rears back, howling in fury at the arrogance of these would-be assassins. The creature tests its wings with three huge beats as it gets ready to knock down this impudence.

Players have workable knowledge of what’s to come: who is the next likeliest target, and a new attack pattern. Things might change; a PC might taunt the monster to get its attention, or it might fall back on a previously described attack. But there are no nasty gotchas in store.

Even with standard trope enemies, like a gaggle of zombies, it’s good practice to foreshadow their particular attack. What might seem an obvious assumption to the GM isn’t always plain to the players. Don’t leave it to chance; state it outright.

Describing Monsters: High Energy Verbs; Cut Adverbs

It’s common advice given to writers by editors to avoid adverbs. It cuts down the word count and inspires the reader’s imagination much more effectively.

Likewise, this is great advice for GMs and players, too. Consider “the monster moves quickly across the room” versus “the monster lunges across the room.” Similarly, “walks slowly” versus “plods” or “lumbers.” Verbs can pack so much information.

No matter the language, this holds true. The Japanese sentence “化物は部屋の向こうから猛進する” is like “the monster charges across the room.” This has much more energy than a more basic verb like “行く” (“go”).

Usually, the GM sets the tone at the table. If the energy levels are down, often so too is the game. Language is a massive part of this. The most enthusiastic GM in the world isn’t hitting their potential if their language falls flat. Build up that vocabulary by reading more. Unfortunately, there is no quick fix.

Dungeon Universe

To some degree, this idea takes inspiration from the RPG Dungeon World. Replacing Dungeons & Dragons standard terms like “attack” with “hack and slash” and “volley,” it encourages evocative language. However, I’m suggesting doing this for every part of a monster’s vocabulary: its movement, its violence, and its communication.

Monsters shouldn’t move; they should lurch, saunter, stumble, lunge, stalk, or glide.

They shouldn’t attack; they should snap, lash, stab, snatch, crush, or flay.

Monsters shouldn’t simply say things; they should snarl, howl, whisper, snivel, bellow, or mewl.

Of course there will be mind blanks. Sometimes the only words that come to mind will be move, attack, and say. Keep the action moving over floundering for a word that doesn’t come quickly. But whenever possible, flex those language muscles. It’s the fastest way to make one “bear” feel different to another, even with the same stat block in use.

When Describing Monsters, Gaps Are Good To a Point

There are other advantages to minimal descriptions. Leaving gaps gives opportunities for player curiosity and questions. Exhaustive questions not only takes up more time, it signals there’s no room for collaborative storytelling.

It’s also a shortcut to evocative storytelling.

In The Metamorphosis, Franz Kafka describes a creature with “numerous legs.” He doesn’t say 10 legs, or 100, or 10,000. In Danse Macabre, Stephen King hits upon the same technique. His point is the moment you define a ten-foot (~3m) long bug, it loses part of its fear factor. King notes that a ten-foot long bug is scary, but fixed numbers enables us to rationalise the previously unknown.

King is talking horror; however, this works the same for any kind of imaginative description. It is particularly useful in a hobby that should feel weird and/or fantastical. So, in all descriptions I would avoid fixed numbers where possible.

It’s Not Always Easy

Miniatures and table-top tokens make this gap for imaginative interpretation harder, and consequently improvising “bears” quickly more awkward. Tokens, either top-down or pog-style showing only part of the monster, reduce the imagination gap, but don’t eliminate it. Full-frontal pogs and detailed miniatures obliterate it completely.

This is simply something groups will have to experiment with to find what they enjoy most. There are some truly gorgeous miniatures and token designs out there. However, I’m not surprised some groups choose low-fi tokens or counters instead; coloured blocks, sweets/candy, and other counters represent creature locations, but make the imagination work harder to visualise a scene.

Lastly, there are some very important exceptions when an imagination gap is not a good move. Anywhere description clashes with mechanics, give way to the mechanics. For instance, how far a creature can move and its attack reach all trigger certain rules in D&D. In these cases, I would never be vague. Cool imagery, no matter how evocative, never takes priority over clarity.

Examples of Describing Monsters

In the first article, I came up with the Weepers: big hunting cats with golden coats that hunt in pairs using the Brown Bear D&D 5.5 stat block; ambush predators, they squirt blood from their eyes to confuse their prey (no mechanical effect on the PCs) before striking.

These cats don’t move: they slink, stalk, pounce, and race (as opposed to “run”). They also don’t attack: they maul, rend, clamp down on, rip, slash, and swipe. Before initiative, I might describe something like:

A silky, golden body slinks its way down the path. Its eyes leaking blood freely, its savage jaws glistening with saliva, and its brutal claws scarring the earth. What do you do?

When the cat takes damage or at the end of the round, I would introduce the second cat. Something like:

the Weeper throws its head back and howls. Another howl answers the call. From behind, a second gold-coated hunter closes the trap.

The second cat acts on the same initiative as the first, no extra rolling necessary. It’s straight into the action.

Let’s make another monster.

Sticking with the Brown Bear stat block, first up is concept. I’m going with a simplified Couatl without wings. Superficially, the Bear’s claw attack becomes a razor-sharp tail attack. So, locals call them Razor Tails and Blade Vipers. It glides, drifts, and darts across ground; it snaps, bites, and pierces with its jaws while stabbing, thrusting, and spearing with its tail.

Before initiative, I could describe:

Smooth, prismatic scales shimmer as the creature glides across the ground. It hisses; a forked-tongue flickers; giant fangs drip saliva onto the ground. A warning crack from its wicked-sharp tail carves through the air. What do you do?

Conclusion

Vivid, concise description can make any stat block come alive at the table. Keep the details focused on what matters most to the players; stagger information as necessary and leave gaps for imaginations to fill in where you can. All of this advice is useful for any creature’s description, but it’s extra important when reusing a “bear” template.

And to sum up the series, here’s a recap on how to reskin a “bear” from start to finish:

1) Choose a stat block. It needs low defences, decent health, and a simple attack that hits hard.
2a) Decide on a concept (combining is easiest), a name or two, a look, and a sound.
2b) If needed, consider making a very short vocabulary list to describe its actions. Thesauruses are wonderful things.
3) Keep descriptions to around three details, prioritising what is most important for the players to know. At the top of the list is the creature’s next likeliest attack.
Leave gaps to leverage imagination; avoid them where it will clash with the mechanics of the game.
If necessary, stagger information across rounds; when the monster gets hit or before the next round starts are prime timing.

I signed off the first article with the obvious Shakespeare quote. This time I leave you with the sage wisdom of Paddington, another UK national treasure. We must always remember, “bears will be bears.”