A tavern is where adventures start. This generator produces the kind of overheard gossip a party hears the moment they sit down — half-truths, warnings, and whispers that each hint at a thread worth pulling. Every rumor is built to imply a plot hook, so you can scatter a handful around a town and let your players decide which leads are worth chasing.
How it works
Each rumor is assembled from three independent tables. A source clause sets who
is talking and how — the hooded traveller mutters that or two farmhands argue over whether. A subject names the focus of the gossip, such as a ruined tower
or a vanished caravan. A hook clause supplies the intrigue: something is not what it appears to be or harbours a creature no one will name. The tool draws
one entry from each table using the browser’s random number generator and joins
them into a grammatical sentence, then avoids repeating a rumor within a single
batch.
The art of running tavern rumors
How you present rumors matters as much as what they say. A few techniques that work at the table:
Attribute them to someone. “You overhear two merchants at the bar” or “the innkeeper mentions, while refilling your mugs” grounds the rumor in the social fabric. Players are more likely to follow a lead if they feel it came from a person, not a bulletin board.
Make most of them false (or wrong). If every tavern rumor in your campaign turns out to be true, players learn to treat them as quest logs. If most are exaggerated, wrong, or deliberately planted, players have to do actual detective work. A good ratio is roughly one true lead, one distorted truth, and one fabricated noise in every three rumors.
Leave the resolution open. The generator produces setup, not conclusion. “The old monastery on the ridge has been sealed since the monks vanished” is not a solution to anything — it’s an invitation to ask why. Let your players’ questions shape what the truth turns out to be.
Match the source to the information. A barkeep hears rumors from travelers. A blacksmith hears about road conditions and equipment. A merchant’s clerk hears about prices, debts, and who’s buying in bulk. When a rumor comes from a source with good reason to know, it should probably be true (or at least believed).
Worked example
A generated rumor might read: “The barkeep leans in and whispers that the abandoned mine in the hills guards a fortune that has driven men mad.”
A GM could take this in several directions:
- True — the mine contains a cursed treasure that triggers vivid nightmares
- Distorted — there is no treasure, but a cult is using the mine for rituals that have been affecting the local water supply
- False — the “madness” was one delirious miner who survived a cave-in; the mine is empty and anyone spreading the rumor has been paid to keep people away
None of those decisions need to be made before the session. The rumor plants the hook; the truth can follow from whatever direction the players pull.
System compatibility
All generated rumors are system-agnostic. They work as written in D&D 5e, Pathfinder, Shadowdark, OSR systems, Call of Cthulhu (tavern becomes a bar or club), and any game with a social scene where information travels by word of mouth. The subjects and hooks are generic enough to slot into historical, fantasy, and horror settings without modification.