Choose only the rules you need
Start with a story and choices, then add the rules your game needs. Blank projects and A Small Errand do not automatically include d20 components or external SRD rule packs.
The current demo still includes d20-based samples and optional components. A dice-free story template is also available. The official pack catalog and automatic notice generation described below remain planned.
Which rules do you need?
| Choice | Purpose |
|---|---|
| Basic story / empty project | Start with scenes, choices, conditions, resources, and effects without requiring random checks |
| 20-sided Die (d20) Check | Explicitly add independently authored examples and expressions using a twenty-sided die |
| Source-identified SRD pack | Track a specific edition’s permitted material, license, and attribution |
| OGL-based external pack | Review that pack’s original notices and identified open content |
| ORC-based pack | Review ORC notices, upstream attribution, the creator’s contribution, and licensed/reserved material scopes |
| Creator-authored ORC rules | Choose to publish rules the creator has rights to license after reviewing the scope and conditions |
Entering 1d20 will not activate an external ruleset or automatically add OGL or ORC notices. Calculations are tracked separately from imported rule text, data, and artwork.
Planned workflow
- Start with an empty project or basic story template.
- Review a pack’s content, source, edition, dependencies, and distribution conditions.
- Preview changes and notices before applying them.
- Connect characters, scenes, and actions, then test the result.
- Review notices for the material actually included in the export.
Copied or modified material should retain its source even if the original pack is later removed. A notice tool can collect attribution, but you still need permission to use the content.
Follow the selected pack’s conditions
New official SRD packs are planned to prioritize CC BY 4.0. The official SRD 5.2.1 specifies CC BY 4.0 and a required attribution statement. Official SRD 5.2.1
CC BY 4.0 requires appropriate attribution, a license link, and an indication of changes, among its conditions. It is not a blanket rights warranty for a complete game. Official Creative Commons terms
OGL material has a separate planned workflow for the license text, copyright notices, and identified open content. This page does not announce an official pack release or completed rights review of existing demo materials.
Planned ORC support
ORC (Open RPG Creative License) packs are planned as explicit choices after reviewing their source, edition, and notices. The workflow covers the ORC Notice, attribution for upstream sources and the creator’s contribution, Reserved Material, and expressly designated additional Licensed Material. The scope preview must consider new and adapted rules in the applicable work as well as imported files. Final ORC License
Notices are planned for Game information → Licenses and the bundled ORC-NOTICE.txt. A separate ORC.txt copy is provided for offline convenience; reproducing the full license is not itself an ORC requirement. OGL-only material will not automatically become ORC material. Combining CC BY material with ORC material must preserve the original attribution and conditions. Official ORC AxE
Creators may also choose to publish their own rules under ORC after confirming their rights, the scope, and the irrevocable license grant. Additional sharing of eligible Reserved Material, such as their own lore and artwork, is off by default. This does not relicense the entire engine or require disclosure of all software source code. ORC notice generation, scope validation, and the pack catalog remain planned.
Other licenses and release formats
We are preparing tools to record sources, explain conditions, generate notices, and check permitted release formats for the licenses below. Being listed does not grant permission to distribute a standalone video game or publish through every store.
| Profile | Planned handling |
|---|---|
| CC BY 3.0/4.0 | Preserve the original version’s attribution, license, and modification notices |
| CC BY-SA | Check the scope of adapted material and the required same-license or recognized compatible path |
| CC0 | Retain dedication and source records; public credit remains optional |
| CC NC/ND conditions | Check commercial purpose and sharing of adapted material, including BY-NC-SA/BY-NC-ND combinations |
| YZE FTL | Track the designated SRD, notices, and print/PDF/VTT paths; video games are excluded |
| CSOL | Track the CSRD, compatibility notices, and tabletop/online character-generator/VTT paths; separately review standalone game rights |
| DPCGL | Check the agreement version, permitted material/formats, approved VTTs and noncommercial conditions, notices, and logos |
| Community content agreements | Track Miskatonic Repository program terms, material, notices/logos, permitted formats, and publishing channels |
CC profiles preserve the exact original license and version. Free distribution does not automatically mean noncommercial use, and a technical format conversion is not automatically an adaptation. Creators may also choose a CC license for their own material after reviewing their rights, scope, and conditions. CC license overview
FTL, CSOL, DPCGL, and community agreements have different scopes. For example, FTL excludes video games, and DPCGL imposes noncommercial conditions even on approved VTT sharing. Miskatonic Repository document and specific VTT connection paths do not grant permission to distribute software or apps. FTL, CSOL FAQ, DPCGL, Miskatonic guidelines
Pack details and export checks will show Conditions met / Review needed / Outside permitted scope with the source of each issue. PDF and print documents, VTT modules, and tools also need their own exporters. Completing a license review does not make an exporter available. Export features, official packs, and external approvals are still being prepared.
Review the complete output
The plan checks source conditions across editor, export, and distribution. Software protection must not add restrictions that conflict with the rights granted for included open material. Removing unused assets does not by itself resolve work-level notice or sharing obligations.
Starter images are AI-generated. A destination may impose additional content rules: for example, new Miskatonic Repository titles prohibit AI art. Select suitable artwork for the destination as well as checking the rule license. Official program guidelines
Add rules in the current demo
Explicitly select story, check, or combat Components, or write Rules and expressions yourself. Use Game data abilities, costs, and proficiency only where your game needs them.