Product history & roadmap
How LoreForge Works is evolving.
LoreForge Works began with a specific problem in mind: tabletop sessions need clearer table flow, better shared state, and less mechanical friction without removing GM control. The roadmap tracks how that idea is taking shape across active alpha testing and system-specific refinement.
Phase 1Foundation and live table clarity
The initial product focus was on core table-state tracking, initiative flow, and a cleaner shared GM/player surface. This phase established the baseline for smoother combat turns, easier status tracking, and more visible session management.
Phase 2SWADE-focused alpha validation
SWADE became the primary active test surface because it benefits strongly from fast initiative flow, conditions tracking, bennie awareness, and real-time GM oversight. The objective was to stress-test the system under actual play, not just in isolated prototypes.
Phase 3System expansion and refinement
D20, Cypher, and Genesys entered the product roadmap as additional surfaces for interaction design, scene tracking, and system-aware feature mapping. The goal was not broad rollout, but focused refinement based on active table feedback.
Phase 4Usability, stability, and larger access
The next roadmap step is broader usability work: cleaner status handling, more resilient table flow, and the features that make alpha tools easier to use without interrupting the fiction at the table. This phase is designed to make the product more stable before wider access.
What the roadmap means for users
For players and GMs looking for a tabletop RPG session manager, the roadmap reflects a practical product strategy: work on table-state clarity first, test it under real play, and expand carefully to the systems that benefit most from a shared flow surface. The result is a focused roadmap rather than a generic feature dump.