unreal-save-load

Create a USaveGame subclass with value-type properties, then call AsyncSaveGameToSlot and AsyncLoadGameFromSlot through a coordinator subsystem. Persist stable domain IDs rather than live Actor pointers, and validate version and type before applying loaded state.

Use a monotonic schema version and run pure data transforms from version N to N+1 repeatedly until current, validating invariants at each step. Keep fixtures for every released version and never overwrite a newer-version save automatically.

No. In UE 5.8, AsyncSaveGameToSlot still serializes the SaveGame object on the game thread and only moves the platform write to a worker. Large object graphs can still cause hitches, so keep snapshot cost bounded and measure with Unreal Insights.

Use ULocalPlayerSaveGame for per-local-player state since it binds a SaveGame to a Local Player and provides load/create, version, and async lifecycle helpers. Use a custom USaveGame schema for playthrough and world progress, and UGameUserSettings for graphics options.

Failures come from changed serialized layouts without version bumps, missing content definitions, or interrupted writes. Classify results separately, preserve original bytes, validate headers before applying, and test real previous-version files plus power-loss scenarios on target hardware.

No. Local save data is untrusted for competitive authority, paid entitlements, or server economy. The server must own shared world state and progression, persisting authenticated account records with idempotency and version checks.