THE MAN I INVENTED / Lead Programmer

Persistence system

First-person sci-fi action survival · USC MFA thesis

Explore implementation and demos by engineering responsibility. Footage and captures show their recorded versions.

Persistence system

Gameplay capture of an opened door
Opened door · Gameplay capture

State kept between rounds

Before level travel, the system captures opted-in Actors and restores them by map and identity in the next round.

  • Transform and existence: where an object is, whether it remains in the world, and permanent destruction markers.
  • Interaction state: for example, whether a door is open, its opening direction, and the main power switch state.
  • Actor-specific data supplied through the persistence interface.

These snapshots persist between rounds within the current game process; they are not disk saves that survive quitting.

Persistence system architecture diagram; each stage is explained below
System relationship · Responsibilities explained below

Capture before level travel

Before death or Game Over level travel, GameInstance calls the Subsystem; snapshots are keyed by map package and stable GUID.

Runtime and placed actor restoration

Runtime actors rebuild before World BeginPlay; placed actors restore by GUID in InitializeComponent, including late World Partition registration.

World-state restoration within a session

Stored object state within a game session, reconstructing runtime objects on world reload and retaining their destroyed state.

Designed a component-based, session-scoped world-state framework using GameInstanceSubsystem, persistent instance GUIDs, and custom state interfaces to save transforms and gameplay data. Supports runtime object reconstruction, permanent-destruction records, and state restoration within the session.

Capture before level travel

Before death or Game Over level travel, GameInstance captures world state. A GameInstanceSubsystem keys actor snapshots by map package and stable GUID, including transform, existence and custom data supplied through an interface.

Restore before play begins

Runtime actors are reconstructed before World BeginPlay. Placed actors restore by GUID in their PersistentStateComponent during InitializeComponent, including actors registered later through World Partition.

Session-scoped state

Snapshots live in a GameInstanceSubsystem for the current process; this is not a disk save that survives quitting the game. Permanently destroyed actors mark a tombstone before Destroy.

Destruction and restoration

Actors that persist between rounds record state before destruction. A new round restores objects such as doors and the main power switch by identity. In-memory snapshots disappear when the game process ends.