Shattered Codex

Wiki

Modules/SC - The Cauldron

SC - The Cauldron

Foundry v13+System AgnosticPremium

SC - The Cauldron

Overview

SC - The Cauldron is a system-agnostic crafting module for Foundry VTT.

Instead of tying crafting to one sheet system, it lets you define cauldron targets and recipes, then handle the full play loop through a dedicated merge interface.

The module is built around these parts:

  • configurable cauldron targets based on Actors or Items
  • a recipe manager with ingredients, results, and optional per-cauldron restrictions
  • a merge interface that consumes ingredients and creates the crafted result
  • recipe discovery tools such as Check recipes, Known Recipes, and Recipe Overview

At runtime, configured targets can open a dedicated cauldron window instead of the normal sheet.

Installation

This module is premium.

Premium modules require an active Patreon subscription.

Install access is handled through the Shattered Codex Download Hub.

See How to Download Premium Modules from the Download Hub for the full access and installation flow.

This module also requires:

  • lib-wrapper
  • socketlib

After installing:

  1. Enable SC - The Cauldron in your world.
  2. Enable lib-wrapper.
  3. Enable socketlib.
  4. Open Configure Settings > Module Settings > SC - The Cauldron.

Configure Cauldron Targets

The first setup step is defining which documents should behave like cauldrons.

Open Configure Settings > Module Settings > SC - The Cauldron > Configure Targets.

Cauldron Targets configuration window

Each target can point to an Actor or Item and has its own capacity, visual style, slot symbol, colors, speed, and merge sound.

What you can configure per target:

  • the target document itself
  • unlimited slots or a fixed maximum item count
  • the effect preset used by the cauldron UI
  • the empty-slot symbol
  • primary and secondary colors
  • gradient toggle
  • animation speed
  • optional merge sound

Targets can be based on either:

  • an Item, which works well for inventory-based crafting objects
  • an Actor, which works better for world stations, structures, or GM-facing crafting points

Practical behavior from the module:

  • configured item targets can replace the normal item sheet with the cauldron UI
  • actors that own a configured cauldron item can gain a The Cauldron header button
  • configured actor or token-based sources can also open the cauldron interface

Create Recipes

Recipes are configured in Configure Settings > Module Settings > SC - The Cauldron > Configure Recipes.

Recipe manager with recipe configuration

The recipe manager stores the full recipe definition: name, cauldron availability, known players, ingredients, and results.

Each recipe includes:

  • a recipe name
  • one or more ingredients
  • one or more results
  • availability in All Cauldrons or only selected targets
  • the list of players who know that recipe

The manager also supports:

  • duplicate recipe
  • copy recipe ID
  • import recipes
  • export recipes
  • preview recipe overview

Important matching rules from the module:

  • recipe matching uses item name + item type
  • ingredient order does not matter
  • ingredient count does matter
  • result entries must resolve to valid Item documents
  • overlapping duplicate recipes are blocked when the ingredient set is the same and their cauldron scopes overlap

This lets you create both global recipes and station-specific recipes without accidental conflicts.

Craft and Collect

Once a target and recipe are configured, the play loop is simple: drop items, merge, then collect.

Cauldron merge interface with crafting slots

The cauldron window accepts dragged items, shows the configured slot layout, and replaces the ingredients with the crafted result after a valid merge.

Basic flow:

  1. Open the cauldron.
  2. Drag the required items into the merge area.
  3. Click Merge.
  4. If the recipe matches, click Take all to move the result into inventory.

Important runtime behavior:

  • if an ingredient is dragged from an owned actor inventory, the module removes 1 unit automatically
  • if no recipe matches, the merge is blocked with a warning
  • if the recipe result cannot resolve to a valid item document, the merge fails
  • after a successful merge, the slots are replaced with the crafted result entries
  • the configured merge sound can play and a chat message is posted

Collection is also actor-aware:

  • for players, the collector is usually their assigned character
  • when dragging from an owned inventory, that actor can become the collector automatically
  • for GMs, the collector can fall back to the source actor or the currently controlled token

The module also prevents obvious bad targets, such as trying to collect into another document that already opens The Cauldron.

Recipe Discovery

The module includes several ways to expose recipes to players besides the raw crafting window.

Check Recipes on Items

If an item appears in a visible recipe, its sheet can show Check recipes.

That lookup can show:

  • recipes where the item is an ingredient
  • recipes where the item is a result

For players, this only shows recipes they already know.

Known Recipes on Actors

Owned actors can also get a Known Recipes button in the sheet header.

That opens a browsable list of recipes known by the current user.

Recipe Overview and Sharing

GMs can open a Recipe Overview and use Show to Players.

That flow:

  • sends the overview window to selected active players
  • marks the recipe as known for those players

The module also learns recipes automatically when a player successfully crafts them through the cauldron flow.

Notes

Some behavior is worth keeping in mind while building recipes and tutorials around this module:

  • the safest way to build import data is exporting a real recipe first, then using that structure as the template
  • recipes are persisted in world settings, while recipe knowledge is stored per user
  • multiplayer crafting is synchronized through socketlib or a socket fallback so the GM resolves merges centrally
  • this is a crafting system module, not a content pack, so you define the recipes and target documents yourself

If you want a clean first setup, the best order is:

  1. configure your cauldron targets
  2. define the recipes
  3. assign recipe knowledge if needed
  4. test the merge and collect flow in play