Framework

How do you generate useful RPG rumours?

Generate useful RPG rumours as a six-entry table: four are essentially true, one exaggerates a real situation, and one is a dangerous misconception. Give every entry a named source, a specific site, NPC, faction, or item to pursue, and a consequence if the party follows, repeats, or ignores it. Keep each rumour lighter than a quest hook so players choose what matters.

Game master preparing a six-entry rumour table beside a candlelit tavern map

Make rumours invitations to investigate

A useful rumour gives the players a decision, not a sentence of atmosphere. 'People disappear on the north road' asks them to invent the next question. 'Mara Venn at the tollhouse has been buying every iron bell in town before sunset' gives them a person, a place, an object, and a reason to ask what changed.

Start with something already happening in the campaign: a faction changing tactics, a settlement running short of food, a shrine closing, a stranger asking questions, or a useful item moving through the market. Then decide who noticed part of it and why that person is telling anyone else. The rumour becomes the public edge of a situation the party can approach from several directions.

Use a fixed six-rumour mix

The distribution gives uncertainty a shape. The party can trust that the table contains useful information without knowing which line is safe to believe.

Four essentially true rumours The central claim is reliable, though the source may lack a detail or misunderstand the motive. These entries reward players who follow a lead without making verification pointless.
One exaggerated rumour The source has a real fact, but fear, pride, distance, or deliberate spin has distorted it. Investigating should reveal an unexpected complication rather than a complete dead end.
One dangerous misconception The claim sounds plausible and is materially wrong. Acting on it at face value should create a social, tactical, or political cost, while careful questions expose a safer route.
Six actionable leads Every entry names a person, site, faction, or item the party can visit, question, inspect, follow, steal, protect, or avoid. No entry should depend on a vague 'dark force' with no location or witness.

Anchor every line to the living campaign

Write these four notes beside each rumour before you put it in front of the players:

Source Name the speaker or place where the party hears it. A frightened ferryman, a rival merchant, a shrine attendant, and a bored guard will phrase the same event differently.
Claim Write the line the players actually hear. Keep it short enough to repeat and concrete enough to test. Include a name, landmark, object, time, or public event.
Truth note Record what is true, what has been distorted, and what the source has omitted. Keep this in GM notes rather than revealing it in the spoken version.
Pressure Decide what changes when the party follows, spreads, challenges, or ignores the rumour. Connect that change to a character, settlement, faction, or clock already in play.

Example

Worked example: Six words from Lowmere

Lowmere's ferry has started arriving after midnight with its lanterns covered. The following table gives the party six different ways into that local problem without turning any one rumour into an instruction to accept a quest.

1. The covered lanterns: The ferryman's daughter says the boats hide their lights so the marsh wardens cannot see who crosses. Lead: ferry-master Odo Pell and the west landing. Source: a child who helps coil the ropes. This is essentially true; Odo is avoiding a corrupt patrol that charges illegal night tolls.
2. The drowned bell: A shrine keeper claims a bell rings beneath the reed beds whenever a traveller is about to die. Lead: the half-sunken bell tower at Saint Orra's cut. Source: a priest who heard one note during a storm. This is essentially true; a submerged warning bell is being pulled by the current, and someone is using its sound to cover movements on the bank.
3. The empty barge: Market fishers say the black barge at Moorlock Quay carries bodies under its tarpaulin. Lead: the barge and its owner, Sella Voss. Source: two fishers who saw no crew aboard. This is the exaggeration; the barge carries sealed medicine, but Sella is hiding one living stowaway from the magistrate.
4. The missing ferryman: A guard insists that Odo Pell drowned last winter and that the person running his ferry is a marsh ghost. Lead: Odo's house beside the rope store. Source: a gate guard who has never crossed the river. This is a dangerous misconception; Odo is alive, and confronting him as an undead threat turns a frightened witness into an enemy.
5. The reed-cutters' mark: A travelling knife-grinder says every third reed bundle bears a red thread for the Lantern League. Lead: the reed market behind the old granary. Source: a trader who wants buyers to use his private landing. This is essentially true; the mark identifies safe paths through a faction's controlled marsh.
6. The sealed chest: A dockworker says Sella Voss keeps a silver chest that hums when the moon is low. Lead: the locked cabin on the black barge. Source: a deckhand paid to unload it. This is essentially true; the chest contains the magistrate's stolen evidence, and opening it changes who controls the investigation.
Why it works: All six entries name a lead and a source, but they do different jobs. Four reveal real parts of Lowmere, one adds a complication to a true core, and one warns the GM that a confident player response could make the situation worse. The table creates choices around the ferry, shrine, faction, and magistrate rather than six disconnected quest notices.

Keep the rumour lighter than a quest hook

A rumour is something people are saying. A quest hook is a situation the party can be asked to resolve, usually with a clearer objective, reward, or deadline. If each rumour already contains an objective, opposition, reward, and encounter sequence, the table becomes six quests and loses the freedom that made overhearing it interesting.

Use rumours to connect the setting's parts. A character can repeat a faction's version of a dispute, a settlement can become the place where that dispute is visible, and an item can carry evidence from one location to another. The party decides which thread deserves more preparation. When a rumour survives a session, update its source and consequence instead of leaving it as a frozen entry on a table.

See the complete table in context

A finished output makes the distinction easier to judge: player-facing gossip stays brief, GM truth stays separate, and every line still points into a connected situation.

Read the Lowmere rumour table

RPG rumour prep checklist

Run these checks before you read a rumour aloud or add it to a campaign note:

Do four of the six entries contain a reliable core, with one exaggeration and one dangerous misconception marked in GM notes?
Does every rumour name a specific person, site, faction, or item the party can pursue?
Can the source explain why they believe the claim or benefit from repeating it?
What changes if the party follows the lead, repeats the story, challenges the source, or does nothing?
Is the entry still a rumour rather than a complete quest with an assigned objective and reward?
Which character, settlement, faction, or item will this line connect to the rest of the campaign?

Keep generated rumours connected to the campaign

The Rumour Generator produces six local leads with the four true, one exaggerated, and one dangerous model, then keeps the truth notes separate from the player-facing lines. Add the table as one lightweight note and connect its named people, settlements, factions, and items in the graph when a lead becomes part of play. There is no need to invent a separate religion generator for faith-related rumours; the existing faction, pantheon, and secret-society workflows cover the parts that need their own records.

Try the Rumour Generator

Tools

Guides

Codex Cryptica for sandbox campaigns Keep open leads, settlements, factions, and consequences connected between sessions.