Sleeper's Artifice

We’ll Pick Up Next Week · Vol. 10

The clue your players already forgot

Six ways to hand your table the same clue twice without anyone noticing, a GM in Melbourne on the gentle no, and a digest that wants your stories.

Hey y’all,

Welcome to Volume 10, and welcome back to the workshop.

The clocks went back this week for a lot of us, it’s dark by dinner, and the holiday calendar is about to start eating game nights. Two weeks between sessions turns into three pretty fast this time of year, and that’s exactly the stretch where your players forget the one thing you need them to remember.

You all know the feeling. The party found a note in the dead merchant’s office with the name of the man who’s been paying the bandits. You read the name out loud, heck, one of them maybe even wrote it down. Three sessions later they’re standing in front of that same man, shaking his hand and taking a quest from him, and nobody at the table so much as blinks. You can see the whole plot sailing right past them.

We’ve all been there, and it’s maddening from behind the screen, because you DID tell them. It stinks for the players too, because they can usually tell they’re missing something, and they have no idea what it is.

Here’s the thing, though. Your players aren’t bad at paying attention. They hear a few hundred details a night and have to guess which ones matter, and from where they sit, that note looked exactly like the rest of the mundane stuff like furniture laying around the room. The fix is to say the important thing more than once, and the trick is to say it differently each time, so it never sounds like a repeat.

The letter · Free, on Substack Subscribe

THE PROMPT: six ways to say it again

Pick the one clue your table has to carry out of tonight’s session. Then roll a d6 (or just pick one that you like) for how it shows up a second time, and roll again for a third.

  1. Somebody else says it, but badly. The drunk at the inn has the same story with all the names wrong, and your players will correct him, which means they just said the clue out loud themselves.

  2. It’s written down somewhere they’re already searching. A torn note in a dead man’s coat, a name scratched into the inside of a chest lid, or a line in a ledger they were flipping through for something else entirely.

  3. A kid has it. Children in your world repeat whatever the adults say, usually at the worst possible moment, and nobody at the table ever suspects a kid of being plot relevant.

  4. It’s a song, a rhyme, or a bit of graffiti. You know, the thing that got scratched into the well stone and has been there for weeks, and once they know what they’re looking at, they’ll start seeing it everywhere.

  5. Someone asks them about it. An NPC who assumes the party already knows walks up and asks what they plan to do about it. There is no faster way to make a table realize they missed something.

  6. The consequence shows up first. The bridge is already out, the wagon is already gone, or the man they were warned about is already at the bar buying everyone a round. NOW the clue is a problem. People remember problems.

Here’s what that looks like in practice. The clue is that the miller’s son went north with a mercenary company. It’s important because that company is who the party is about to get hired to hunt. Session one, the miller mentions it while he’s grinding flour, but nobody writes it down. Session two, the party finds a child’s chalk drawing on the side of the village well: a wagon, a line of soldiers, and a little figure in a floury apron waving goodbye. The rogue asks about it, and a kid tells her the whole story, just in the wrong order. Session three, the mercenary captain shakes the fighter’s hand and mentions he’s got a local boy in his company who knows the roads. Now the whole table knows, and nobody feels like they were told twice, because they weren’t. They were told three different things that all pointed the same direction.

If they still sail past it, don’t panic, and don’t make the clue bigger and louder. Reach for number six from above and let the consequence walk into the room. A clue they missed is just a surprise they haven’t had yet, and your table was going to enjoy that surprise anyway.

I’m not saying narrate every clue three times like a tour guide (your players will notice THAT, and it won’t be a compliment). What I’m saying is pick the one thing that has to land each session, give it three ways to be heard, and let the table find it on their own. They get to feel clever for catching it, and you get to sit back and watch them do it.

THE FIND

This week’s Find is Meg’s TTRPG Cafe, a newsletter out of Melbourne that’s only about three months old and already posting twice a week. Megan spent years making video games before she started running tables, and she also teaches in-person GM workshops, so her Sunday GM Thoughts posts read like notes from someone who has to explain this stuff to new GMs out loud. Start with her September post on the social contract at the table. Her comparison is a library, where nobody has to be told not to run around or shout, and she wants your table to work the same way, with everyone agreeing up front not to talk over a player’s turn or a GM mid-explanation. My favorite part is what she calls the gentle no. Instead of telling a player they can’t do something, you lay out the scene so they can see the consequence for themselves, like pointing out that poking the red dragon at level three is going to get them a fire attack at close range. She also has a couple of good questions for pulling a quiet player back in, like “What’s your take on this?” Her newest post went up Sunday, on lethal systems and the art of a linear path. Go read it, then subscribe while you’re there. It’s free: Meg’s TTRPG Cafe.

ALSO WORTH YOUR INBOX

Role Player’s Digest. Niamh Celeste puts out a monthly roundup of what’s happening across the hobby, and every issue carries one feature from a guest writer. Last week’s feature is Riley Clark on consequences, and his point is that the interesting part of a character’s death is the why, the when, and what the story does afterward, and that a consequence can just as easily be losing a friend or retiring with one eye. It’s a good companion to number six up top. They take submissions too, so if you write about this stuff, they want to hear from you: Role Player’s Digest.

FROM THE WORKSHOP

The one clue that has to land tonight deserves a spot at the top of your prep, and The Night’s Ledger is where I’d put it. It’s two quick prep sheets for game night, and it’s always free: The Night’s Ledger.

The d6 up top is one table. Story Seeds is a whole book of them, the thing you flip open when the party wanders off your map and you need something true to happen right now: Story Seeds.

The rest of the always free stuff: the Player Cheat Cards, which keep the rules in a player’s hand instead of in three different books; The Sundered Page, our whole one-page game you can run tonight; the Encounter Complications sample, six cards from the deck so your table can try it out; and The Dreaming Court, a warlock subclass that’s pay what you want. Grab them at Player Cheat Cards, The Sundered Page, six-card sample, and The Dreaming Court.

The entire shelf of free and paid stuff all lives at sleepersartifice.com.

Thanks for hanging with me this week. If this was useful, forward it to someone at your table. That’s how this thing grows. And if you write a newsletter too and this feels like a fit, hit reply. I’m always looking for good neighbors to recommend. We’ll pick up next week.

-J

Newsletter · free, weekly

We’ll Pick UpNext Week

We’ll Pick Up Next Week is our free newsletter, out every Tuesday. Get the next issue by email.

SubscribeThe Letter

The letter’s home is on Substack, at sleepersartifice.substack.com