Homebrew dice & JSON transfer

Create a dice profile

1. Create an entry in a permitted collection with Content type set to Dice roll and choose its registered game.
2. Open Configure dice system & test faces.
3. Select Vampire V5, Werewolf V5, Success pool, or Sum of dice.
4. For a generic engine, set Sides per die, the success threshold where relevant, and whether highest-face pairs grant the supported extra successes.
5. Enter sample regular faces, special faces only for a suitable V5 engine, and a test Difficulty. Run the test, inspect the result, then save the profile.

Supported pools contain 1–100 dice with 2–100 sides. The V5 adapters retain d10s, success on 6+, and their critical-pair rules; they are not arbitrary reskins of another die system. Generic success pools and sums do not define Hunger or Rage dice.

The test bench also accepts Difficulty 0. A die-face success threshold is a different setting: it must remain within the valid faces for that die.

Make the profile available in play

A draft never appears in live dice choices. Release it through the appropriate private or public workflow, obtain Chronicle approval, and enable its exact revision in that Chronicle's content configuration. It can then appear in /dice and the web roller.

This integration resolves the supported dice profile. It does not implement a new game's character sheet, spell system, turn economy, or arbitrary uploaded code.

Try a small definition

The following is an original, illustrative definition for Fields & mechanics → Advanced JSON. It is not an official V5 rule and is not an entry-import package. Load it into the visual editor, save, then run the calculation test bench. With Focus at 2, its result is 3.

{
  "version": 1,
  "fields": [
    {
      "key": "focus",
      "label": "Focus",
      "type": "number",
      "minimum": 0,
      "maximum": 5,
      "initial": 2,
      "section": "Example resources"
    }
  ],
  "mechanics": [
    {
      "name": "Focus plus one",
      "explanation": "An illustrative calculation for the test bench; this is not an official game rule.",
      "expression": {
        "op": "add",
        "args": [
          {
            "symbol": "focus"
          },
          {
            "literal": 1
          }
        ]
      }
    }
  ],
  "steps": []
}

Use unique lowercase field keys with letters, digits and underscores. Each formula references declared keys. Supported operators include add, subtract, multiply, divide, min, max, numeric comparisons, and boolean all, any and not. Unsupported expressions, undeclared symbols, and excessive sizes are rejected.

Definitions use version 1 with fields, mechanics and steps. Each list is limited to 100 entries and the definition must remain below 100 KB. Keep large designs in several clearly related entries.

Export an entry

1. Open the entry's Releases tab.
2. Select Export entry JSON.
3. Keep the export with its revision context. The package includes its descriptive fields and owned components, including a custom definition and dice profile when present.

Exports use the chargen.brewery.entry format, version 1. External references are dependencies, not automatically bundled full copies of every linked entry.

Import an entry

1. Open a collection you can edit and choose its JSON import tool.
2. Provide a compatible exported entry package.
3. Read the validated preview: check the name, destination collection and component count.
4. Select Import draft within the confirmation window.
5. Open the new draft, inspect every relationship and rewrite any imported explanatory text that has not been independently authored and reviewed.

The confirmation expires after 30 minutes and is bound to the account and destination. Import creates a new unpublished draft; it does not overwrite an existing identity or publish a release.

The current import limits are 500 KB and 300 component rows. Referenced entries must already exist and be accessible. Missing references, unknown components, protected fields and invalid definitions are rejected.

If a test fails

Check field keys, bounds, operator spelling, required game references, die-face limits, and whether the draft has changed in another tab. Reload before editing a stale draft. Fix the cause rather than removing prerequisites or treating an error as a successful calculation.