How to Explain Setting Lore Through Play When Characters Know More Than New Players
When your characters know the setting better than the people playing them, give players the information their characters would reasonably have at the moment it matters. Then let them use it to make a choice, read a clue, or speak with an NPC. This keeps the scene moving while making the characters’ experience visible. The approach works best when you distinguish useful background knowledge from secrets the players are meant to uncover.
Start with the decision the scene asks players to make
Before preparing lore, write down the scene’s immediate decision: for example, whether the party will trust a guide, enter a district, or approach a guarded monument. Give the players any character-level knowledge needed to understand that choice. If the local custom is to leave weapons at a shrine entrance, say so before the party decides how to enter. You can deliver the fact in a sentence, in a description of other visitors, or through an NPC’s response.
This is a practical application of D&D’s guidance that players need the information required to make choices, within the characters’ knowledge and senses. The same principle is useful in other games, though their rules and conventions may differ. The GM can pace descriptions and reveal further detail as characters investigate. (D&D Beyond Basic Rules: “The Basics”)
Separate background knowledge from discoverable secrets
Sort each piece of lore into three simple groups before the session: common knowledge, character-specific knowledge, and unknown or disputed information. Common knowledge can be stated directly. Character-specific knowledge can be prompted from the player whose character has the relevant background. Unknown information belongs in the investigation, and disputed information should be presented with its source or uncertainty attached.
For instance, most residents may know that the old bridge is closed at night. A character raised nearby might know which caretaker still has a key. Whether the bridge was closed because of a structural failure or a political order could remain an open question. This sorting prevents a useful clue from being withheld as if it were a secret, while preserving genuine discoveries for play.
Prompt the character who would know
When the scene touches someone’s expertise, address the player through their character: “You trained with the city watch. What would you recognize about this checkpoint?” If you already know the answer, supply the useful fact and invite the player to put it into the scene: “You know this badge marks a senior officer. How does your character respond?” The player need not perform a speech or improvise the entire history; a brief reaction is enough.
This gives a new player a clear handle without asking them to memorize the setting guide. If the player is unsure, state the fact plainly and move on. Knowledge prompts should open a choice, not become an unannounced test of whether someone studied the lore outside the game.
Put lore into the scene’s details
Show setting knowledge through things characters can observe: the order of a ceremony, a worn emblem, a title used in conversation, or the way a shopkeeper changes their greeting when a uniform appears. Pair each detail with a short explanation when its meaning affects a decision. A distinctive city description can orient players, but extended background before they have a reason to act can delay the scene. D&D Beyond’s city-campaign advice recommends concise, sensory descriptions that give players a picture of the place without overwhelming them. (D&D Beyond: “How to Run City Campaigns in Dungeons & Dragons”)
A useful pattern is detail, meaning, choice: “The guards wear the blue sash of the river council. Your character knows council officers can inspect cargo without a local magistrate. The merchant looks toward you—what do you do?” The first sentence makes the information visible, the second translates its significance, and the third returns control to the players.
Let knowledge create options, not orders
Character knowledge should help players decide, not tell them which decision is correct. Offer the relevant context and, when useful, name the likely trade-offs: a formal introduction may grant access but attract attention; using a local contact may be faster but create an obligation. Leave the response to the player. Advice from The Alexandrian about sharing rules expertise makes a related point: helping someone choose should not become choosing for them, and offering a few options with their upsides and downsides can preserve their agency. (The Alexandrian: “Player Lore – Sharing Your Mastery”)
For a new player, make the choices legible without prescribing one. You might say, “You know this guild treats public accusations as a formal challenge. You can raise the issue openly, ask for a private meeting, or leave it alone for now.” The options are examples, not an exhaustive menu; the player can propose another approach.
Handle uneven knowledge with short, fair checks
If only one character would know a fact, tell that player what the character recalls, then ask what they share with the group. For information gained while separated, a brief note or a concise return report can work, but avoid making routine communication consume table time. A discussion on RPG Stack Exchange describes several approaches to character knowledge, including giving a player only the details needed to report what their character noticed; treat these as adaptable suggestions rather than universal rules. (RPG Stack Exchange: “How do I let characters share knowledge only they know?”)
Use a roll only when the rules and situation make recall uncertain or consequential. Decide in advance what success reveals and what failure changes. A failed recall roll should not erase ordinary knowledge that the character plainly ought to have; it might instead mean the character remembers a partial account, confuses two similar symbols, or needs to consult someone. Apply the game’s own mechanics, since systems handle expertise and information differently.
Check whether the lore helped the scene
After the scene, ask yourself three practical questions: Did the players understand the choice? Did at least one piece of setting knowledge affect what happened? Did the explanation leave room for players to respond in their own way? If the answer to the first is no, clarify the relevant fact earlier next time. If lore did not change the scene, shorten or relocate it. If players treated a rumor as certain history, make the source and uncertainty clearer.
You do not have to explain every fact a character knows. Give players enough to act as people who belong in the setting, invite them to express what their characters know, and reserve unanswered questions for moments when discovering the answer matters. This turns setting knowledge into usable context at the table: something players can act on, question, or pass along in play.
