Integrations
Review draft. This source page has not completed website editorial and release-specific verification.
Core boundary
Section titled “Core boundary”SaveGame Director Runtime and Editor modules are standalone. They do not depend on Inventory Director, World State, SignalBus, DirectorBridge, or another Director product. SaveGame Director exposes its contributor API for optional persistence adapters.
Director-to-Director communication is owned by DirectorBridge. The adapter may depend on both participant runtimes; neither Director core adds a direct cross-Director dependency. Do not add another Director module to a SaveGame Director Build.cs to enable an integration.
Inventory persistence
Section titled “Inventory persistence”The canonical Inventory/SaveGame adapter is the DirectorBridgeInventorySaveGame Runtime module in DirectorBridge. It registers IntegrationId Inventory.SaveGame with ContractVersion 1 when the required participant products are available. The adapter connects Inventory persistence to SaveGame Director through the contributor contract.
Enable the adapter when the project needs Inventory state included in SaveGame Director operations. SaveGame Director core remains usable without Inventory Director or DirectorBridge. Consult the installed DirectorBridge and Inventory Director documentation for adapter availability and project configuration.
World State persistence
Section titled “World State persistence”The optional WorldState.SaveGame adaptation lives in DirectorBridge and uses the host-provided authoritative World State owner’s public snapshot API. SaveGame Director core does not vendor World State or acquire a World State dependency.
SignalBus commands and lifecycle
Section titled “SignalBus commands and lifecycle”Optional Save/Load command and operation-lifecycle integration with SignalBus is provided by DirectorBridge. SaveGame Director does not vendor SignalBus; the host supplies and enables SignalBus when that integration is required.
Other products
Section titled “Other products”Other Directors can provide their own DirectorBridge adapters over the public contributor API. A currently registered Required contributor without a saved record causes a V1 restore failure. Optional contributor records may be skipped with a warning. See Contributor Guide for the contributor contract and Restore Lifecycle for ordering and failure behavior.