Save & load

Persistence uses a USaveGame object: put the data to persist in UPROPERTY members, then write the object to a named slot and read it back. The slot API lives in UGameplayStatics; the actual file I/O is delegated to ISaveGameSystem, which is swapped per platform.

When to use this skill

• Saving and restoring player progress, inventory, world flags, or per-player settings.
• Checking whether a save slot exists; deleting or enumerating slots; multiple slot/profile flows.
• Serializing runtime actor state (dynamic objects) into a byte array inside a SaveGame object.
• Migrating save data after adding or removing fields.
• Understanding what goes in a USaveGame vs. config (UGameUserSettings/.ini).

Mental model