The prompt
Score 10 of 10, Excellent
Use it when You run a tabletop roleplaying game and need an original hook for your next session that ties into your players' characters.
- {{game_system}}
- {{party}}
- {{session_length}}
- {{campaign_notes}}
- {{player_characters}}
- {{table_limits}}
Full prompt and why it works
Prompt
Write an adventure hook for my next tabletop roleplaying game session, so that I can open the session with a situation my players want to act on and run it with room for their choices. My campaign and my players' characters come first; build on them. Game system, in general terms: {{game_system}} Group: {{party}} Session length: {{session_length}} The campaign so far, and its tone: """ {{campaign_notes}} """ The player characters and their unresolved backstory threads: """ {{player_characters}} """ Our table's lines and veils (content we never include, and content that happens off screen): """ {{table_limits}} """ Use these headings: 1. The hook: what happens or arrives in the first five minutes of play, as a read-aloud passage of under 120 words. 2. Why these characters: how it touches at least two of the player characters' goals or backstories, by name. 3. What is really going on: the truth behind the hook, for my eyes only. 4. Ways in: three to four different approaches the players might take, and where each one leads, so no single path is required. 5. Key characters: two or three non-player characters, each with a want, a secret, a way of talking and a reason to help or hinder. 6. Complication: one twist I can bring in midway if the session needs it. 7. Stakes: what happens if the players ignore the hook or fail. A good hook gives the players a problem, not a plot, with a clear first move and freedom in how they solve it. Keep the challenge level suited to the group I described, and use only general mechanics of the system, such as a skill check, without exact numbers unless I gave them. Respect our lines and veils without exception. Do not use named characters, places, monsters or adventures from published settings or modules; create original ones. Avoid plots that only work if the players make one particular choice. If my notes do not say the characters' level or experience, or a backstory thread is unclear, ask me before building on it, or mark your assumption as [ASSUMED: assumption].
Variables
- {{game_system}}
- The game you play, for example "a fantasy roleplaying game on its current core rules" or "a rules-light system we made up".
- {{party}}
- Number of players and the characters' level or experience, for example "four players, mid-level".
- {{session_length}}
- For example "three hours".
- {{campaign_notes}}
- The campaign so far and its tone.
- {{player_characters}}
- The player characters by name, with their goals and backstory threads.
- {{table_limits}}
- Your lines and veils. Write "none agreed yet" if you have not set them.
Why it works
- Who it's for. The hook ties into at least two player characters by name, so the players have a reason to act.
- What to avoid. Your table's lines and veils are respected without exception, and nothing is taken from published settings or modules.
- What good looks like. A good hook gives the players a problem, not a plot, with several ways in so no single choice is required.