Skip to main content

Cauldron

Cauldron is Castle's web-based way to make games. A Cauldron deck is a web project, with Castle's editor, its AI assistant Operator, and publishing built around it. That lets a deck do things classic decks can't: use 3D engines, npm packages and WebGL, and run its own multiplayer server.

Cauldron is early and changing quickly. It's invite-only for now; request access on castle.xyz.

How Cauldron decks differ from classic decks​

Classic decks are built from cards, actors, rules and Lua scripts. Cauldron decks don't use any of those, so the rest of Castle's docs don't apply to them; these Cauldron pages do. Some kits bring back familiar ideas like actors, blueprints and behaviors, but they work differently in Cauldron.

  • A Cauldron deck is made of files. Scenes, art, blueprints, code and other assets each live in their own file, the way a web project is laid out.
  • It runs on the web platform. A deck is HTML, CSS and JavaScript. It can use npm packages, Canvas, WebGL (three.js, PixiJS), React and WebAssembly. The official kits are written in JavaScript, but a deck can use other languages that build for the web.
  • The editor comes with the deck. A deck starts from a kit, and the kit brings the editors that suit it: the 2D kit has a scene editor, a pixel-art sprite editor, blueprints and physics. A deck can add editors of its own.
  • Code comes first. Classic Castle started with code-free tools and added code later. Cauldron goes the other way: it starts from code and layers tools and editors on top. Most creators build by asking Operator to write and change the deck for them.
  • Decks can build on each other. In the Castle app you can view the source of a Cauldron deck and remix it, and one deck can import another as a dependency.

Players don't need to know any of this. A public Cauldron deck can show up in the feed and on castle.xyz like any other deck.

Where to go next​

  • Getting started: make your first Cauldron deck.
  • Kits: the starting points for a new deck, and what each includes.
  • How decks run: the card, assets, fonts, touch controls and other rules every deck follows.
  • Multiplayer: how a deck becomes multiplayer, and the server it runs.
  • A/B tests: show different players different versions of your deck, and compare the results.
  • SDK reference: the JavaScript API for saving data, leaderboards, selling passes, portals to other decks, and other Castle services.
  • Local development: build decks on your own computer with the castle-web command-line tool.

Questions and feedback are welcome in our Discord.