Save data and persistence

Save-data layers

• FRicSlotSaveData: slot index, item definition, tag stacks, nested container data, and item GUID.
• FRicContainerSaveData: container definition, slots, and container GUID.
• FRicContainerManagerSaveData: manager ID and root-container data.
• FRicActorSaveData: manager data and quick-slot data.
• FRicSaveData: snapshots for the registered inventory owners.

These are the plugin's in-memory snapshot structures. They are not a complete file-storage service.

Capture a snapshot

Call GetSaveData() on the manager for one inventory, or on the world's URicInventorySubsystem for registered managers and their owners' quick slots.

Capture authoritative inventory state when saving a multiplayer game. Predicted UI copies can contain unconfirmed changes.

Restore a snapshot

1. Create the inventory-owning actors and their manager components.
2. Give each manager the same stable ID used by its saved record.
3. Wait until the managers have registered with the inventory subsystem.
4. Call LoadFromSaveData on the appropriate manager or subsystem on authority.
5. Refresh client-facing views after restored state reaches the client.

Subsystem restoration matches records with FindContainerManagerByID. It does not spawn a missing actor. Manager restoration replaces the existing container tree; invalid or missing definitions are skipped.

The subsystem restores a manager's containers first, then its owner's quick slots.

Durable disk storage

Serialization requires an adapter in 1.0

Several nested snapshot fields, including slot indices, tag maps, nested arrays, and GUIDs, are plain C++ members without UPROPERTY. Do not assume that putting FRicSaveData into a USaveGame property will serialize the entire hierarchy correctly.

For reliable disk saves, implement an explicit serializer or map snapshots to your own fully serializable save schema. Include manager IDs, container and item GUIDs, slot indices, tag counts, hierarchy, quick-slot mappings, and stable asset references.

Resolve definition assets before converting disk data back into runtime snapshots. Add a schema version to your own save format; the site's documentation version selector does not migrate saved game data.

Restoration checks

Round-trip a nested bag, partial stacks, rotation stats, and quick-slot assignments through a real disk save. Compare the restored hierarchy and GUIDs, not just the top-level container count.