Fabled developer documentation
Module Creator
Build declarative packages that extend Fabled while the host keeps rendering, data access, mutations, consent, and recovery under its control.
Beta platform
The contract and tooling are implemented, but npm distribution, CLI pairing, publishing, catalog, installation, activation, and browser runtime can be enabled independently by environment.
01Getting startedInstall the Module CLI, scaffold a valid package, and understand the files it creates.02Manifest and capabilitiesDescribe a module without giving package code direct authority over Fabled.03Validate, pack, inspectProduce deterministic module artifacts and verify exactly what you will submit.04Secure CLI loginCreate a scoped publishing session without copying a browser account token. This opaque flow requires matching source CLI and backend versions; the published npm bootstrap.1 release does not include it.05Publishing and reviewClaim one publisher namespace, submit immutable evidence, and follow the human review lifecycle.06Install and enableUnderstand the player path from an approved catalog release to a running contribution.07Example modulesCompare the live host runtime, interactive contract preview, and representative host exhibits in Module Lab.08Security and limitsDesign inside a fail-closed host boundary and know which checks happen before code can run.09TroubleshootingMap validation, archive, authentication, network, and review failures to a safe next step.10CLI referenceExact commands, accepted options, environment variables, and process exit codes for @fabledgg/module-cli 0.1.x.11Scene encounters (candidate)Author a bounded Living Dungeon with cooperative runes, crystal beams, timed choices and elemental spell reactions.