gabrielmoreira Game Story Flow
Core Workflow
- Identify genre, target tone, player role, narrative camera, agency level, branching depth, content budget, and gameplay loop.
- Define the player fantasy and emotional arc before writing scenes. The story should reinforce what the player repeatedly does.
- Treat plot as playable pressure: each beat should create a decision, reveal, risk, relationship change, world-state change, or motivation to act.
- Preserve agency. When the story must constrain the player, provide strong motivation, readable consequences, or interactive expression.
- Track state explicitly: known information, unresolved questions, character goals, relationship changes, promises made to the player, and consequences already paid off.
- Review pacing across gameplay, exploration, dialogue, combat, rest, discovery, and cutscenes. Avoid placing long passive exposition where the player expects control.
Narrative Structures
- Linear story: build clear act turns, escalating stakes, reversible setbacks, and playable transitions between major beats.
- Branching story: define branch intent, divergence cost, merge strategy, remembered variables, and consequences the player can perceive.
- Quest narrative: connect objectives to character motivation, local stakes, world logic, and a meaningful result.
- Environmental storytelling: use spatial order, props, audio, enemy placement, lighting, and interactables to imply events without over-explaining.
- Dialogue: give each speaker a goal, subtext, conflict, and exit condition. Keep choices distinct in intent, not just wording.
Deliverable Shape
For substantial narrative work, produce:
- Premise and player role
- Core conflict
- Character goals and pressure points
- Beat sequence
- Branch or consequence map
- Gameplay integration notes
- Dialogue or scene samples where useful
- Open questions for design, production, or playtesting
References
- Read
references/story-flow-checklist.mdwhen outlining, branching, revising, or reviewing game narrative structure.