t1k:designer:rpg:quest
| Field | Value |
|---|---|
| Module | rpg |
| Version | 1.7.2 |
| Effort | medium |
| Tools | — |
Keywords: design, mission, objective, quest
How to invoke
Section titled “How to invoke”/t1k:designer:rpg:questGame Quest Design
Section titled “Game Quest Design”When This Skill Triggers
Section titled “When This Skill Triggers”- Designing quests, missions, or objectives
- Writing dialogue trees or NPC conversations
- Planning reward pacing and power spikes
- Structuring main/side/ambient quest chains
- Designing skill checks, stat gates, or dialogue conditions
- Balancing quest variety and player motivation
Core Quest Design Concepts
Section titled “Core Quest Design Concepts”Quest Taxonomy
Section titled “Quest Taxonomy”8 base quest types — combine for variety:
| Type | Core Loop | Best For |
|---|---|---|
| Fetch | Go → Get → Return | Tutorial, errand, economy |
| Kill | Find → Defeat → Report | Combat gates, bounties |
| Escort | Guide → Protect → Deliver | Tension, character bonding |
| Defend | Hold position → Survive waves | Tower defense feel, emergencies |
| Explore | Discover → Map → Report | Open world, curiosity rewards |
| Puzzle | Analyze → Solve → Unlock | Environmental storytelling |
| Dialogue | Persuade → Learn → Act | Faction mechanics, info gathering |
| Moral Dilemma | Choose → Commit → Live with it | Narrative weight, replay value |
→ See references/quest-patterns.md for advanced patterns (arrowhead, deja vu, deadline, hidden quests)
Quest Chain Structure
Section titled “Quest Chain Structure”- Main quest (spine): gates progression; always completable without side content
- Side quests (ribs): enrich world; reward optional power or lore
- World quests (ambient): radiant/repeatable; fill open world, support economy
- Pacing: 1 main + 2 side per chapter; difficulty staircase within chain
- Non-linear completion: design 2-3 valid solutions per quest (combat, stealth, dialogue, puzzle)
→ See references/quest-patterns.md for failed-quest states and world-reaction design
Dialogue Systems
Section titled “Dialogue Systems”- Tree structure: nodes (NPC text) → edges (player choices) → conditions (flags/stats)
- Branching budget: max 3 choices per node; converge within 4 exchanges
- Hub-and-spoke: central greeting → branch to topics → return to hub
- Bark system: one-liners triggered by game state (combat, idle, discovery)
- Skill checks:
[Strength 15] "I'll break down the door"— show requirement inline
→ See references/dialogue-systems.md for tone consistency, voice sheets, writing tips
Reward Pacing
Section titled “Reward Pacing”- Reward types: XP, items, currency, story reveals, abilities, area access, reputation
- Power spike cadence: major reward every 3-5 quests (weapon tier, ability unlock)
- Breadcrumb design: each reward hints at next quest or area
- Avoid inflation: scale rewards with difficulty, not time investment
→ See references/reward-pacing.md for reward schedule, pity systems, completion vs participation rewards
Anti-Patterns
Section titled “Anti-Patterns”| # | Anti-Pattern | Problem | Fix |
|---|---|---|---|
| 1 | Fetch quest padding | Players feel disrespected | Add story context + optional alternate solutions |
| 2 | Unclear objectives | Player stuck, frustrated | Show objective in UI; add map marker or NPC hint |
| 3 | Reward inflation | Power curve collapses | Gate major rewards behind content difficulty, not quantity |
| 4 | Single solution quests | Feels on-rails | Always offer: fight OR talk OR sneak as alternatives |
| 5 | World ignores failures | Choices feel meaningless | Failed/ignored quests must visibly change world state |
Cross-References
Section titled “Cross-References”game-narrative-design— narrative arc, character motivations delivered through questsgame-worldbuilding— faction reputation systems, lore delivery via quest rewardsrpg-game-design— skill check thresholds, XP reward curves, item power budgetsgame-design-document— quest flowchart templates and tracker sheets
Reference Files
Section titled “Reference Files”| File | Coverage |
|---|---|
references/quest-patterns.md | Quest taxonomy, advanced patterns, chain structure, non-linear solutions, failed states |
references/dialogue-systems.md | Tree structure, hub-and-spoke, bark system, skill checks, tone/voice consistency |
references/reward-pacing.md | Reward types, power spike cadence, breadcrumb design, schedule, inflation prevention |
Gotchas
Section titled “Gotchas”- Fetch quests are not bad — boring fetch quests are bad — add a narrative hook, escalate the ask, or layer a moral dilemma on top.
- Dialogue trees with >4 options at one beat overwhelm — limit per-beat choices and use follow-ups for depth.
- Reward pacing must match quest cost — a 3-step quest yielding a single common item kills future quest engagement.