← All documentation

Homebrew authors · Chronicle staff

Release, review & adopt homebrew

Move a draft through private playtesting or public review without losing revision history.

Checked against the live application · 2026-09-28

Prepare a release

  1. Save the entry and all related mechanics.
  2. Preview the readable content, follow its relationships, and test supported calculations.
  3. Check requirements, source credits, and independent wording. Resolve validation errors.
  4. Open Releases and enter release notes or reviewer context.
Back to top ↑

Share a private playtest

  1. Confirm original wording and select Seal private playtest.
  2. Under Share a private playtest, select one of your Discord Chronicles and choose Share revision.
  3. The Chronicle's approved, locally authorized Storytellers can inspect the exact revision without becoming collection editors.
  4. An authorized Storyteller chooses Approve for a Chronicle when ready.

Revoke invitation removes pre-adoption sharing access. It does not silently remove an already adopted rules selection. To change the content, create the next revision rather than editing a sealed playtest.

Back to top ↑

Publish publicly

  1. Use a public collection, save all descriptions and mechanics, and check linked dependencies.
  2. The owner or an authorized author selects Publish reviewed entries on the collection, chooses the entries, records release notes and confirms independently written prose.
  3. For work submitted from a fork, open Contributions. Inspect the proposed descriptions and complete entry pages, then approve, request changes or reject with a reason.
  4. Approval creates fixed public revisions. Later edits use new drafts.

A contributor cannot approve their own submission. Only the primary owner grants author access and decides whether added authors may publish. The separate independent Brewery Reviewer route remains available from an entry's Releases tab.

Back to top ↑

Publish a playable collection update

  1. For a collection with a registered game adapter, publish its reviewed entry changes first.
  2. Select Prepare playable update, describe the release and confirm your review.
  3. The new release pins its definitions and linked dependencies. Choose Use in a Chronicle to adopt that release through the Chronicle's authorized staff.
  4. Existing characters and Chronicles retain their prior versions. Contribution approval alone does not migrate their sheets.
Back to top ↑

Activate the release in a Chronicle

  1. Obtain Chronicle approval for the exact sealed revision through Releases.
  2. Open the Chronicle's rules configuration and enable that revision in Sources & homebrew together with its required game, category, collection, and sources.
  3. Preview and save the configuration.
  4. Check Rules & allowed content or the relevant selection tool to confirm availability.
Back to top ↑

Compare and moderate

Use Compare with the previous revision and Version history on Releases to inspect changes before adopting an update. Existing links identify particular revisions, which makes the rule used in a past decision traceable.

An authorized Brewery Moderator can withdraw a public release with a recorded reason. Withdrawal retains the release and history for audit; it is not permanent data erasure.

Back to top ↑