Verified against ChatGPT · 2026-08-11
Design an RPG side quest with a moral choice that has genuinely different consequences, not just different flavor text
Produces a complete side-quest design brief — objectives, NPCs, branch points, and rewards — built around a choice where each outcome changes something mechanical or narrative downstream, not just the dialogue the player hears at the end.
The prompt
Ready to copy — highlighted parts are example details you can swap.
Design a side quest for the RPG described below. The failure I want to avoid is a quest with a "moral choice" where every option leads to the same reward and the same next state, just with different flavor text read aloud — I want the choice to actually branch something. GAME AND SETTING A grounded fantasy RPG set in a war-torn border region between two kingdoms, mid-game. QUEST GIVER AND HOOK A refugee camp elder asks the player to retrieve medicine stolen by a group of deserters hiding in the nearby hills. CENTRAL DILEMMA The deserters stole the medicine because the camp's own quartermaster has been secretly rationing it to sell on the black market — turning in the deserters means the corrupt quartermaster keeps control of supplies. PLAYER LEVEL / POWER CONTEXT Mid-game player, level 18 of 40, already has a base camp reputation system active. RULES Define the quest giver, the hook that draws the player in, and at least one complicating piece of information the player only learns partway through that recontextualizes the dilemma — a side quest that presents its full moral complexity in the opening briefing gives the player nothing to discover. Present the central dilemma as a genuine trade-off where the "obviously good" option has a real, stated cost, and the "obviously bad" or self-interested option has a real, stated benefit beyond just reward gold — a choice where one option is purely worse in every dimension isn't actually a choice. For each resolution path, specify what changes beyond the immediate scene: a reward difference, a reputation or relationship change with a specific NPC or faction, or a change in what's available later (a vendor, an ally, a location) — state these concretely rather than leaving them as "the story continues differently." Include one twist or complication that could occur regardless of which path the player takes, so the quest isn't purely a fork with no shared texture — for example, a consequence that lands on the player no matter what they chose, forcing them to live with an outcome they didn't fully control. WHAT NOT TO DO Do not make any resolution path strictly better than the others in every measurable way (reward, reputation, and story outcome all at once) — every path needs a real cost attached to its benefit. Do not resolve the dilemma with a clearly telegraphed "correct" choice signposted by which NPC seems more trustworthy; bury the actual trade-off in genuine ambiguity. OUTPUT FORMAT 1. Quest giver, hook, and the mid-quest complicating reveal. 2. The central dilemma stated as a real trade-off. 3. A table of resolution paths: Path | Immediate Outcome | Downstream Change | Cost. 4. The shared complication that occurs regardless of path chosen.
Customize
Optional — swap in your own details for the highlighted parts above.
Why this works
The single most common defect in generated RPG quest design is a moral choice that's cosmetically branching but mechanically flat — every path awards the same gold and item, and the only thing that differs is the line of dialogue the NPC delivers at the end, because generating genuinely different downstream game states (reputation changes, unlocked or locked vendors, altered NPC availability) is significantly harder than generating different flavor text, and a model will gravitate toward the cheaper version unless the downstream table is explicitly required. Requiring a stated cost for the "obviously good" option and a stated benefit for the self-interested one directly targets a specific model habit: default moral framing in generated content tends to make the altruistic choice strictly dominant so the player is never punished for being kind, which flattens the dilemma into a non-choice — real quest tension requires the good option to actually hurt in some dimension the player cares about. Requiring a mid-quest complicating reveal rather than presenting full moral complexity in the opening briefing matters because a quest that shows its whole hand immediately gives the player nothing to discover mid-play, which is a pacing defect distinct from the choice-design defect but equally common in a single-pass quest generation. Requiring a shared complication that lands regardless of path chosen prevents the quest from reading as a pure binary fork with two disconnected outcome trees, and mirrors how real narrative design uses a consequence the player can't fully avoid to make the choice feel like it happened inside a living world rather than a menu of options with no bleed-through between them. The explicit table format for downstream changes forces the concrete specificity (a named NPC's reputation, a specific vendor's availability) that prevents the vague "the story continues differently" hand-wave a model will otherwise default to.
What you get back
Path: Expose the quartermaster | Immediate Outcome: deserters cleared, medicine returned | Downstream Change: camp reputation +15, but the quartermaster's black-market contact (a recurring merchant NPC) refuses to trade with the player for the rest of the game | Cost: loses access to that merchant's discounted rare crafting materials entirely.
Verified against
ChatGPT GPT-5.1 · 2026-08-11
Changelog
- 2026-08-11 — Initial publish, verified against ChatGPT GPT-5.1.
Need this built into your business?
If a prompt isn't enough — what Scult builds, built and maintained for you — that's Scult's day job.
EXPLORE WHAT SCULT BUILDS
