Built in the open.
Shaped by the community.
Every item here came from someone who used Fabletoria and asked for more. Open an issue to shape what gets built next.
Now
4 itemsIn active development
Export: JSON, Twine, Ink
Import works. Export — JSON, Twine, and Ink — ships in the next build.
WebRTC collaboration: beta → stable
Peer-to-peer sync works but drops on reconnect and can't resolve conflicts. Making it stable enough to trust for real team sessions.
Full keyboard navigation
Node creation, edge drawing, playback, zoom — all reachable without touching the mouse. A11y requirement and power-user essential.
Large-graph performance
Graphs past 200 nodes stutter on mid-range hardware. A virtualization pass to keep the canvas fast at any scale.
Deciding
2 itemsCommunity input needed
Version history & snapshots
Auto-save with point-in-time restore. Still deciding: local-only or synced, and manual triggers vs. automatic — tell us what you'd want.
Share your thoughtsMobile & tablet support
A canvas rebuilt from scratch for touch — iPad and Android. If you'd use Fabletoria on a tablet, tell us how.
Tell us your use caseLater
5 itemsOn the horizon
Game engine runtime bridges
Native readers for Unity, Godot, and Unreal — ship your narrative graph straight into the engine, no conversion step.
Vote to accelerateScript export: Fountain
.fountain is the screenplay industry standard. Export your narrative graph as a properly formatted script, ready to send.
Vote to accelerateAI pacing & arc analysis
Tension arc mapping, beat distribution, narrative rhythm — an AI layer that reads your whole graph and tells you where it drags.
Vote to accelerateConditional logic editor
Set flags, check conditions, build dynamic paths — all without writing code. Visual branching for stories that remember choices.
Vote to accelerateOptional public gallery
Publish your narrative graph, browse what the community built. Opt-in, privacy-first, no account required to view.
Vote to accelerateShape what comes next.
Every item on this page started as a GitHub issue. If you have a workflow that Fabletoria doesn't support yet, opening an issue is the direct path to getting it built.
Open a Feature Request Browse open issues and voteSearch before opening
Your idea might already exist. Search open issues first — if it does, a 👍 reaction is a vote. Issues with the most reactions get prioritized into Now.
Use the Feature Request template
The template asks the right questions. Don't skip the "Why" section — it's the part that moves issues from Later to Deciding.
Describe the scenario, not the solution
"I want an export button" is weak. "When I hand off to a Godot developer, there's no way to share the graph" is strong. Concrete workflows get built. Vague requests don't.
Community decides priority
Issues that gain engagement get pulled into Deciding. Issues in Deciding that reach consensus move to Now. You can vote on any issue, not just ones you opened.