How to Use the Indie TTRPG One-Shot Prompt to Fit a Honest Three Hour Convention Slot
Write an indie tabletop one-shot that fits a real 3 hour convention slot: cold open hook, timed scene budget, memorable NPCs, Lines Veils and X card safety tools, and a GM prep checklist that keeps the table moving without railroading.
A convention slot is not a home campaign night. You have about three hours including intros, safety, and debrief, and the table needs a clean ending. The Indie TTRPG One-Shot Adventure Writer: Hooks, Scene Budget for a 3 Hour Runtime, NPCs, Safety Tools, and a Convention Prep Checklist prompt writes an indie one-shot with a cold open, a timed scene budget, NPCs with wants, Lines Veils and X card scripts, branching middles that still meet a finale clock, and a GM prep checklist.
What the prompt produces
- A cold open hook that starts play in the first ten minutes.
- A scene budget table with fail forward exits.
- Four NPCs with want, leverage, and a visible tell.
- Safety tools language ready to read aloud.
- Two branches that reunite before the finale.
- Three ending shapes plus a short debrief.
- A prep checklist for props and spotlight rotation.
- Content warnings for the event listing.
How to fill the inputs
GameProfile should name player count, tone, and whether you are rules light or system specific.
SettingAndBans needs a two sentence pitch and hard bans. Ban lists make Lines easy.
SafetyTools should state how firm the pause is. Immediate pause on X is the default here.
RuntimeBudget defaults to 180 minutes. Include intro and debrief so the adventure does not steal them.
HookSeeds are optional ideas you already like; the prompt will weave them without stretching to four hours.
Reading the example output
The sample is a cozy mystery ferry town with peppermint oil and dark lanterns.
- Safety bans graphic injury and harm to kids or animals up front.
- Scene budget returns to the ferry if the town square runs long.
- Endings include graceful retreat so a late table still feels complete.
Tips for better results
- Print the scene budget and watch the clock at minute 100.
- Ask for Lines and Veils before character hooks.
- Keep publisher IP out unless you have rights; stay original.
Mistakes to avoid
- Do not write a six hour dungeon and call it a one-shot.
- Do not skip debrief after heavy themes.
- Do not invent celebrity lookalike NPCs.
Who it is for
Indie GMs, convention organizers, and designers playtesting a short scenario.
Related PromptDig links
Open the Indie TTRPG One-Shot Adventure Writer: Hooks, Scene Budget for a 3 Hour Runtime, NPCs, Safety Tools, and a Convention Prep Checklist prompt with your tone and bans. For more creative prompts, Browse more prompts. If your three hour slot ended on time with smiles, Share a prompt.
Running the slot at a convention
Arrive with the scene budget on an index card beside your GM screen. When minute 100 hits, cut to the ferry even if a clever side scene is blooming. Players remember a finished story more than an unfinished brilliant digression.
Read safety tools before character introductions. Pass the X card. Confirm Lines from your event listing. If someone adds a Line at the table, write it down in front of everyone.
After the finale
Use the ten minute debrief. Ask for a rose, a thorn, and whether any beat needs a private follow up. Thank the table for using safety tools. If you want to publish the adventure later, strip player specific jokes and keep the budget table as the spine of your draft.
Adapting tone without blowing the clock
If the table leans funnier than spooky, keep the peppermint crate and drop the optional ghost beat. If they lean spookier, keep the fog and make Mara's tell feel uncanny, still without graphic injury. The scene budget stays the spine either way.
When a player invents a brilliant plan that needs twenty minutes you do not have, use fail forward: the plan works enough to unlock the finale clue, then the ferry horn forces the move. Honor creativity without rewriting the night.