How players install and enable modules

Acquire from Account Modules

A member searches the reviewed module catalog in Account and chooses Acquire. Acquisition creates an active free entitlement and adds the package to the account library. It does not accept release terms, install the package, or activate any contribution.

Install and accept the exact release

In the account library, choose Install, review the offered version, check the terms box, and confirm. The request sends acceptedTerms: true and pins the current available release as acceptedTermsReleaseId together with its manifest SHA-256. Installation requires an active entitlement and still does not activate the module.

Activate an account module

For an account-targeted contribution, choose Activate after installation. Fabled rechecks package, entitlement, installation, exact accepted release, approval, LOW-risk declarative runtime, host compatibility, capabilities, dependencies, signatures, and rollout gates before creating account runtime authority. Subject to those gates, reviewed community publisher ids can use this account-scoped path.

Activate reviewed modules for a campaign

Campaign module mutations are restricted to the exact campaign owner. A promoted, secondary, or non-owner GM cannot activate or disable them. For every admitted package, Fabled still checks installation, accepted terms, the exact release, capabilities, dependencies, host compatibility, signatures, and policy before activation.

Other campaign members receive the same authoritative activation projection. They do not each upload or trust package bytes independently. Account-targeted contributions are supervised in the signed-in member's account runtime.

Disable and recover

Disabling a module removes its contribution generation. Safe mode can remove runtime contributions while core Account, Campaign, Character Sheet, Chat, and VTT surfaces remain usable. Revoked, quarantined, incompatible, stale, or unverifiable releases fail closed instead of keeping old authority alive.