Stop Building Worlds, Start Causing Problems!

How to Avoid Lore Overload and Still Fit Everything In.

By
Robin B Devlin

Every game master worth their dice bag will know this story.

You buy a brand-new notebook, ingest a frankly reckless amount of caffeine, and approach the project of making a new village with the kind of uncontrolled overconfidence of an eight-year-old in a Batman costume.

After all, you’re not merely making a village, damn it; you’re building a world.

You pen hundreds of years of local history and lore, from the first king to the last via the brief but memorable reign of Duke Aleric the Perpetually Baffled. You sketch out a pantheon, work out which aspect of which deity is worshipped in which valley, work out trade routes and noble houses that you definitely did not crib from Game of Thrones, cobble together a coat of arms, devise ancient blood feuds, succession crises, local burial rites, and the migratory habits of the incredibly rare screaming miniature goat.

You know when and why the old bridge was built, and the name of the troll who sleeps under it. You know which stones were taken from which ruined watchtower. You know why certain members of the village wear blue ribbons on their lapels on the first day of spring every year.

You know all of this.

And then the vandals, otherwise known as players, arrive.

They take in the stunning architecture of your lovingly crafted settlement, your exquisite little snow globe of politics, myth, economics, resentment, folklore, agricultural rhythms, and goat logistics.

Then one of them says:

“Is there an inn?”

It’s not because your players are dumb, unappreciative philistines who cannot appreciate a good fictional but completely workable tax code, or the aching beauty of the rolling vistas that you have created.

Well, not only that.

It is because players don’t experience the world the same way GMs do.

A GM sees history, structure, theme, lineage, symbolism, and the interconnected ticking gears of cause and effect.

The players see a whole bunch of doors; people they can talk to, places they can enter, rumours they can chase, monsters they can harass, laws they can flout, problems they can solve or cause, and things they can “accidentally” set on fire while insisting that it’s all part of the plan.

This is the first hard and fast rule of worldbuilding: players don’t interact with the lore; they interact with problems.

None of this means that lore is useless. Quite the opposite. Your lore is the very soil that everything else grows out of. It gives your setting flavour, texture, history, and weight. It’s the reason that this village is more than just a collection of cottages, oddly specific curses, and old men with apocalyptically wild eyebrows.

But lore on its own is not playable. A village does not become interesting because it has a nine-hundred-year history. It becomes interesting once the priest goes missing, the well starts whispering in an unknown language, the mayor starts acting really weird, and the innkeeper is absolutely, one hundred per cent lying through his teeth.

That’s the on-ramp for the game. Not in the history itself, but in the pressure that history creates.

The dead god matters because someone is still receiving prayers. The old war matters because some of the soldiers never stayed dead. The feuding families matter because they both hire the party for conflicting and mutually incompatible jobs.

Lore is what happened.

Problems give your players something they can do something about.

So, for the love of Gygax, build your world, draw your maps, name your rivers, write your myths, and pillage ideas from as many sources as you can.

And then, when your players arrive, give them something they can grab hold of with both hands and give a bloody good yank.

Lore With More Bite

As a worldbuilder myself, I’m not about to advise that you toss your beloved lore bible in the bin. DON’T DO THAT. Maps are freaking awesome, pantheons are fun, and worldbuilding is, in my mind, one of the most fulfilling parts of being a GM.

What I’m trying to say, so there is no misunderstanding, is that you absolutely should put the effort into your worldbuilding, but then, once you’re sat atop a mountain of lore, you need to give your players a doorway in, not hand them a shovel.

Playable lore does a lot of heavy lifting in a TTRPG. It creates tension, danger, obligation, rumours, taboos, grudges, debts, laws, lies, and, our old friend, consequences. The aim is to make lore the reason they are there; the problem is the invitation to play.

An old war is lore.

A bridge that is still being guarded by soldiers who refuse to acknowledge that the war ended a decade ago is a problem.

A dead god is lore.

A secret grove that whispers prayers back in a soft voice that no one recognises is a problem.

A feud between nobles is lore.

Both houses recruiting the party for mutually incompatible jobs is a problem.

An ancient blood curse is lore.

The mayor keeping the latest victim in the cellar is a pretty big problem.

The lore is the explanation. The problem is the thing the players can actually touch.

So, keep that mountain of lore, the maps, the pantheon, and the miniature screaming goat migration. If you like it, keep it. It is your world after all.

But before the players arrive, ask yourself the useful questions: where does this lore put pressure on the present situation? What is broken because of it? Who benefits from it? Who is lying about it? Who is afraid of it? What happens if the party prod it with a big stick?

The Playable Village Test

The best way to take your lovingly detailed notes and make them into something that your players will want to get stuck into? Simple: take your beloved shire and give it a problem.

Not necessarily a “world-ending apocalyptic threat.” I’m not saying you should put a portal to the Abyss guarded by a Tarrasque under the house of the kind little old lady who makes cinnamon rolls, although, that said, you do you, boo. However, sometimes the best problems are small, personal, and even grubby.

Consider Romeo and Juliet. It is essentially the story of two entitled brats who want to get it on despite the fact that their families hate each other intensely. The result of this three-day relationship? Six deaths, and a love story we still talk about more than 430 years after its first performance.

Make your hook into the adventure something small, unobtrusive, and innocuous: a missing priest, a poisoned well, a stolen relic, or a field that, despite the best efforts of the town’s finest horticultural minds, grows nothing except black flowers.

The trick is to know when to stop asking, “So, what’s this place’s history?” and when to start asking, “And how does that make a problem now?”

That is the playable village test. You don’t need to answer all of these questions with a perfectly formatted dissertation with the citations all worked out in advance. You just need enough pressure for your players to notice, prod at, break, fix, misunderstand, or accidentally make worse.

In particular, I find these six questions to be useful.

What is wrong here?

Straight to the point: this is the hook.

Something should be off-kilter about the village. The well has started to whisper the deep personal secrets of all those who drink from it. The priest has gone missing. The mayor is acting strangely. The old watchtower has a light in it after years of being abandoned.

Or maybe the local children have invented a song that references the party individually before they even arrive.

Whatever it is, it should be something that upsets the natural order of things, or at least the version of that order the villagers like to pretend exists. The calm surface cracks. The mud bubbles. The chickens stop laying. The old men stop arguing about turnips long enough to look worried.

Something wicked this way has come.

This does not mean for one moment that everyone knows what the problem actually is. In fact, it is usually more fun if they categorically do not, or, better yet, have conflicting ideas about the source of the problem.

The villagers might have rumours, theories, bad explanations, convenient lies, old superstitions, and one old woman who is completely right, but has unfortunately chosen to explain the whole thing through aggressive goat metaphors.

Who Benefits from It Staying Wrong?

This is where the problem sharpens its teeth.

If the well is cursed, then who is making money from selling clean, non-cursed water? If the priest has vanished, who has stepped in to minister to the village and collect donations? If the bridge is still being guarded long after the war officially ended, who is collecting the tolls? Or, if you want to be a little cliché, who controls the trolls? If the village is terrified of the woods, who has been using that fear to keep people away from whatever is hidden there?

Problems become more interesting when someone benefits from them. I call this The Scooby-Doo Coefficient.

This person doesn’t have to be evil. They might be scared, desperate, compromised, blackmailed, greedy, proud, or just heavily invested in nobody finding out about the body under the floorboards.

Now your party aren’t simply solving a puzzle; they are interfering with somebody’s well-laid plans.

Who Is Suffering?

This is where you keep the problem grounded. It’s easy to write a wonderfully eldritch mystery and put it in a richly detailed setting, but a mystery in isolation blows away like fog over a cursed duck pond.

Players need to see not only what the problem is, but also what it’s doing to people. After all, if the sleeping curse just gives everybody a solid eight hours a night, there’s not really much of a sense of injustice there.

So, ask yourself as you set up your fiendishly devious problem for your unfortunate village: who can’t sleep because of the thing in the well? Who lost their child to the woods? Who is paying twice for grain because the bridge tolls have become extortionate? Who is being blamed for something they didn’t do? Who is one more bad night away from picking up a pitchfork and taking matters into their own hands? Who is afraid to speak?

Someone suffering gives the problem a living face. It also gives the party a reason to care beyond “the GM has clearly put content here.”

Who Is Lying?

When someone is suffering, something is wrong. When someone profits from it staying wrong, someone is probably lying, hiding something, or at the very least standing suspiciously close to the truth while refusing to make eye contact.

Not always maliciously. Lies come in many flavours: shame, fear, guilt, loyalty, love, greed, politics, panic, self-preservation, and the time-honoured village mass hobby of “we all agreed not to mention what happened at the old mill.”

When you know who is lying and why, you need to figure out what they are lying about.

The mayor says the beloved local priest is on a pilgrimage, but his room and its contents tell a different story.

The shopkeeper claims to know nothing about the missing person, but the pendant in his till drawer suggests otherwise.

The blacksmith says nobody uses the old road anymore, but his boots are covered in red clay mud found only there.

A lie gives your players a starting point, something to test. It gives them contradictions, clues, pressure points, and that priceless little table moment where someone says, “Hang on…”

What Happens if the Players Do Nothing?

This is where you introduce a ticking clock.

Something should always be happening in the background. If nothing happens unless the players act, the world can feel less like a living place and more like it is waiting politely in a corridor. Problems should always be on the move.

The well gets louder. The missing priest returns wrong in some subtle, indefinable way. The secret the mayor has been keeping gets someone killed. The feud turns bloody. The old war reignites over some stupid bridge. The festival the villagers have all been so tight-lipped about starts at dawn, whether the party is ready or not.

You don’t need a complex timeline. Something as simple as a six-segment clock will do: a circle divided into six parts, with each segment representing an event of increasing consequence.

This is not about punishing players for failing to guess the “right” answer quickly enough. It is about reminding the table that the problem has momentum.

The clock gives you a sense of direction.

The problem should be going somewhere, quite probably somewhere unpleasant.

What Changes if the Players Interfere?

The point isn’t merely that the players “solve the problem.”

Their actions should change the situation somehow. Unless there is a very good reason for it, such as a bigger payoff later in the campaign, you should never have the outcome of an arc like this preordained.

I have played in games where the GM had clearly made up their mind that no matter what we did, everything would end a certain way. That’s not a game. If your party might as well have stayed in the tavern for all the difference they made to the world, then you’re not really running a game. You are telling your own story while your friends roll dice.

So, your players’ actions should change the situation.

Maybe after they expose the mayor, the village is left without a leader. Maybe they stop the curse, but the proto-god under the hill was protecting the village from something worse. Or maybe they rescue the priest, only to discover he was missing because he chose to be.

Good problems have nice convenient handles, but they also have splinters.

Just because the players should be able to affect the place doesn’t mean it should always be a nice clean break. Their involvement should reveal new pressure, create choices, and make the village feel less like a painted backdrop and more like a place full of people who now have to live with whatever insane thing the players just did to solve the original problem.

The test isn’t “have I written enough lore?” or “have I developed a working agricultural calendar for the screaming miniature goat?”

The real test is “what can the players do here?”

If you give the village problem a beneficiary, a victim, a liar, a clock, and consequences, your village suddenly isn’t simply lore.

It’s playable.

Turn Lore into Pressure

Lore: The local temple once served a now-forgotten river god.

Pressure question: What happens when a god is forgotten but not actually dead?

Problem:  The river has started to flow uphill, and the current priest (of a different god) has vanished.

Or perhaps you want to make things a little more political?

Lore: The mayor’s family has been ruling the village for good or ill for generations.

Pressure question: Who is still owed loyalty, money, blood, or silence because of that family?

Problem: The mayor is terrified of the blacksmith because the blacksmith knows the family’s claim is false, and has proof hidden in the forge… but the blacksmith has gone missing.

Maybe a little eldritch forest fun is more what you’re after?

Lore: The forest is sacred to the old spirits.

Pressure question: What happens when someone violates the old agreement?

Problem: Someone is cutting trees at night, and the stumps bleed. The villagers blame outsiders, but the axe marks are from tools made in the village.

Just as you should not throw your lovingly cultivated lore out of the window, you should also resist the urge to force your game’s history down your players’ throats like some kind of fantasy-based Ludovico Technique.

The players don’t need the whole story right off the bat.

They need to know where the lore, the old story, is pressing against the game, the present story.

Give them the symptom first. Let them find the history once they care.

Let them follow bad theories, chase blind alleys, interrogate the wrong suspicious elderly lady, accuse the innocent blacksmith, annoy the mayor, and slowly piece together what happened through play.

In other words, don’t tell them your lore.

Let them uncover the problem it left behind.

NPCs Should Be Pressure Points

If the lore of your world is like a massive, sprawling, multi-level deathtrap dungeon, then the NPCs you put in your world are like the keys to the back door.

This doesn’t mean that you need to write a full psychological dossier for every shopkeeper, guard, farmer, beggar, rat-catcher, and man standing by the bar looking like they might be important to the narrative. You don’t need to know their opinion on who might win the annual donkey derby at the village fair, especially if it’s six months away, or the name of the schoolmistress who told them they would never amount to anything.

What you do need is to know where they connect to the problem.

Just jotting down: Gavin the shopkeeper, 42, makes and sells rope. This isn’t useless, but it’s a little drab and doesn’t give your players anything to grab onto. For all intents and purposes, Gavin is basically a price list that is part of the scenery.

Instead, write: Gavin the shopkeeper sells rope, overcharges outsiders, and is hiding the priest’s bloodstained robes under the sacks of hemp.

Now Gavin is playable.

Your party can suspect him, question him, threaten him, bribe him, follow him, or accidentally burn down his shop while he is technically helping with the investigation.

Not every NPC needs to be secretly important. Trust me, I have done it, and that way, madness lies. Before you know it, you will have conspiracy corkboards and twitchy players interrogating every fruit and veg seller like they are Tiamat’s personal sommelier.

That said, a useful NPC should have at least one pressure point. They should want something, know something, fear someone, lie about something, benefit from the problem, or be suffering because of it. They might have seen something they do not understand. They might have made a deal they regret. They might be one bad conversation away from doing something stupid.

That is enough.

A village full of names is a database.

A village full of pressure points is a game.

Players can (and will) ignore lore. They can’t ignore motion forever

Final Thought: Build the Handle

Lore is a mechanism that you have spent hours crafting and designing down to the smallest possible detail. Problems are the handle sticking out.

Players need something to grab, pull, question, break, threaten, save, steal, expose or accidentally blow up.

Roll high, or die trying,