The traditional way of sharing or customizing tabletop RPG rules—printing PDFs, manually cutting and pasting content, or maintaining separate homebrew documents—is too slow, too clumsy, and too isolated for today’s creators and players.
Our goal is to build a flexible, creator-friendly system that makes it easy to curate, remix, and share not only rules, but also lore, maps, worlds, and modular content. Whether a user wants to create a complete player’s handbook with custom Domains and cultures, or simply download someone else's streamlined hack of the rules, the system should support it natively.
This is about more than software—it’s about supporting a creative economy around RPG content, one that’s non-custodial, permissionless, decentralized, and ultimately player-controlled.
The system must support all of the following:
Every rule or lore element—be it a single spell, Domain feature card, or an entire campaign setting—is stored as a modular data object, ideally using a consistent, parseable format.
We support and encourage:
A custom DSL is a purpose-built mini-language designed to express specific types of content (like rules or maps) in a human-friendly and parseable way. Think of something like INI files, YAML, or Magic: the Gathering syntax—but tailored to our system’s needs.
The system must support low-friction payments, including:
Requirements:
Preferred Options:
⚠️ We stay crypto-agnostic: users and creators can choose whichever option best suits their audience, as long as it’s technically feasible and fits our non-custodial design.
The goal is to avoid centralized dependencies. This includes:
Optional: explore local-first syncing and conflict-free collaboration via CRDTs.
Support both:
Build or support tools for:
This is the high-level vision. Technical specifications (schemas, formats, protocols) will be developed and documented in dedicated sub-pages.