Probability Director Integrations
Probability Director remains a standalone plugin. It owns its streams, random algorithms, resolution operations, and persistence payload. A host game or save system decides when to save and where to store the payload.
DirectorBridge
Section titled “DirectorBridge”When another Director product needs Probability Director data, use the optional DirectorBridge integration. Director-to-Director communication is routed through DirectorBridge; products do not depend directly on one another. Probability Director does not require DirectorBridge for standalone use.
SaveGame Director
Section titled “SaveGame Director”The optional integration identifier is Probability.SaveGame. SaveGame Director owns save and restore orchestration and contributor policy. Probability Director owns its persistence APIs and payload semantics. DirectorBridge adapts between those products.
Projects that do not use SaveGame Director can call Probability Director persistence APIs from their own save system; no pairwise adapter is required. See Persistence and Anti-Save-Scumming.
Other gameplay systems
Section titled “Other gameplay systems”A gameplay system can call Probability Director’s public APIs directly for its own probability operations. If that system is another Director product, route cross-Director communication through DirectorBridge. Probability Director does not directly integrate with Dialogue Director, WorldState Director, or SignalBus.