The Problems You Face
Sound familiar? These are the challenges narrative designers deal with every day.
Story docs scattered across tools
Your narrative bible is in Google Docs, character sheets in Notion, dialogue trees in a custom tool, and world-building notes in a wiki. When someone asks "what is this character's motivation?", you spend 20 minutes finding the right document in the right tool.
No branching for alternative narratives
You want to explore two different endings for Act 3, but your only option is to duplicate the doc and rename it. You end up with "Act3_ending_B_v2_REVIEW.docx" and nobody knows which version the voice actors are recording from.
Hard to track character and lore changes
When someone renames a character or changes a key plot point, every document that references it needs updating. But finding all those references means manually searching through dozens of files, and you always miss one.
No review process for story changes
A writer changes a major plot point in the narrative bible, and the rest of the team discovers it a week later when the dialogue no longer makes sense. There is no notification, no diff, and no approval step.
How Gameframe Solves This
Purpose-built features for narrative designers who need more than a general-purpose tool.
Rich document editor built for narrative
Write in a distraction-free editor with full formatting support. Headings, bold, lists, and inline comments. Every save is a versioned snapshot you can compare with any previous version.
AI entity extraction for characters and lore
Gameframe automatically identifies characters, locations, items, and lore references across all your documents. Rename a character once and see every document that needs updating.
Branching for narrative experiments
Branch your entire narrative document set to explore alternative storylines. Write two different endings in parallel branches, playtest both, and merge the one the team chooses.
Inline comments and change prompts
Leave inline comments for your writing team and require change descriptions on every edit. The narrative lead can review diffs of story changes before they become canon.
Your Workflow with Gameframe
From setup to shipping, here is how it works.
Build your narrative vault
Create documents for your narrative bible, character sheets, quest outlines, and dialogue notes. Import existing Markdown files or start from narrative-focused templates.
Write with entity awareness
As you write, Gameframe extracts characters, locations, and lore references automatically. You build a connected knowledge graph of your game world without any extra work.
Branch for story experiments
Before committing to a major plot change, branch your narrative docs. Write the alternative version, share it with the team for feedback, and iterate without risking the main storyline.
Review, merge, and track impact
The narrative lead reviews diffs of story changes. When a branch is merged, the entity graph updates automatically so you can see how the change ripples across your world bible.
Frequently Asked Questions
Common questions from narrative designers.
Want to see all use cases?
View All Use CasesReady to try version control for your game design?
Import your existing docs and experience branching, visual diffs, and structured export. 14-day trial, cancel anytime.
Credit card required for the 14-day team trial. Cancel anytime.