Multiclass Spellcasting

Each spellcasting class on an actor is prepared independently. Classes do not share a pool of prepared spells.

---

Class tabs

The Spell Book shows one preparation tab per spellcasting class. A wizard-enabled class also gets a spellbook tab; see Wizard Spellbook Management.

Unsaved checkbox changes stay on a tab when the player switches to another tab. Save writes the pending changes for every tab. Closing the Spell Book without saving discards them.

---

Spell lists

Each class draws from the spell list assigned to it in Class Rules. A subclass spell list adds to the class list.

A spell on more than one class list appears on each of those tabs. Preparing it for one class does not prepare it for the other. Preparing it for two classes creates a separate spell item for each. When another class already has the spell prepared, the row shows a cross-class tag naming that class.

---

Limits and rules

Each tab’s footer counts that class’s prepared cantrips and spells against that class’s own maximum, including any preparation bonus from Class Rules. Limits are not enforced; see Spell Preparation System.

A class using Cast Any Known Ritual and a class using Cast Rituals Only If Prepared keep separate ritual spell items on the same actor.

After a long rest, a single prompt lists every class whose cantrip or spell swapping is set to Long Rest. See Long rest swapping.

Spell slots, including Pact Magic, are handled by the system.

---

Wizard classes

Each wizard-enabled class keeps its own spellbook tab, spellbook, and free copies. Copying cost and time come from that class’s own Class Rules.

---

Loadouts

Loadouts belong to one class. The Loadouts dialog uses the active tab’s class, and applying a loadout changes only that class’s prepared spells. See Spell Loadouts.

---

Removing a class

Removing a class from a character does not delete that class’s Spell Book data. Its Class Rules and prepared-spell records stay on the actor, and a wizard-enabled class’s spellbook journal stays in the module’s compendium. Adding the class back reuses that data.