Faction play
Faction Rumor Table Guide
A rumor is stronger when it tells the table who is moving, who is afraid, and what might happen next. ReadyScene can generate rumors and hidden problems for a venue; this guide helps you turn those sparks into faction signals without writing a full political map.
Start with what the faction wants
Before writing rumor text, decide what the faction is trying to gain, hide, protect, punish, or delay. A faction can be a guild, crew, family, gang, court office, salvage convoy, station authority, shrine circle, or informal group of regulars.
Keep the want concrete. "Control the old ferry route" is easier to use than "gain power." Concrete wants create visible rumors: missing toll books, nervous ferrymen, sudden road fees, and patrons arguing over maps.
Give each rumor a job
Not every rumor should reveal the truth directly. Mix rumors that point, distort, threaten, and invite action. When a player hears a rumor, they should understand at least one possible next move.
- Signal: shows that a faction is active nearby.
- Offer: tempts the party with a job, favor, shortcut, or bargain.
- Warning: marks a route, person, room, or resource as risky.
- Cover story: hides a faction move behind a simpler public explanation.
Use false rumors carefully
A false rumor should still teach something true. It might name the wrong culprit but reveal who benefits from the accusation. It might describe the wrong location but expose which road the faction wants people to avoid.
Avoid rumors that only waste time. Better false rumors redirect attention, create a cost, or show who planted the story.
Faction rumor table pattern
Faction
Who is moving through this venue: guild, crew, office, convoy, family, gang, shrine, court, or station authority?
Visible sign
What changed in the room: badge, price, route, guest list, posted notice, locked door, missing regular, or new guard?
Rumor job
Signal, offer, warning, cover story, accusation, recruitment pitch, threat, or plea for help.
Escalation
What happens if nobody acts: debt collected, route closed, witness moved, cache stolen, rival framed, or deal completed.
Make rumors change after play
Faction rumors should react to the party. If the characters help, the next rumor might name them as useful. If they expose a lie, the next rumor might become quieter, sharper, or more dangerous.
Track one change after each session: who heard what the party did, who lost face, and which rumor will be different when the party returns.
Example: the toll guild's quiet road
Faction: a toll guild wants to control an old bridge before the spring caravans arrive.
Signal rumor: "The bridge keeper retired suddenly, but nobody saw him leave." Cover story: "The old road is cursed, so the guild is closing it for everyone's safety." Warning: "Anyone asking about the ferry bell gets charged double at the next gate."
Escalation: if nobody interferes, the guild posts armed collectors at both crossings and pays the innkeeper to deny the party ever stayed there.
Next reads
Worldbuilding Prompts
Turn faction rumors into local history, faction pressure, secrets, and timeline movement.
Recurring NPC Guide
Attach faction rumors to keepers, regulars, rivals, and informants who can return later.
Random Tavern Rumors
Start with ordinary rumor seeds, then decide which ones become faction pressure.
Mystery Clue Scene Prep
Use rumors as clues, cover stories, or pressure that moves an investigation forward.
Solo Journaling Prompts
Use faction rumors as solo prompts when one character follows a lead alone.