Why persistence stores player progress in Unity - Visual Breakdown

Concept Flow - Why persistence stores player progress

Player plays game

↓

Game state changes

↓

Save progress triggered

↓

Write data to storage

↓

Data saved

↓

Player quits or reloads

↓

Load saved data

↓

Restore player progress

This flow shows how the game saves player progress by writing data to storage and later loads it to restore the player's state.

Execution Sample

Unity

void SaveProgress() {
  PlayerPrefs.SetInt("Level", currentLevel);
  PlayerPrefs.SetFloat("Health", playerHealth);
  PlayerPrefs.Save();
}

This code saves the player's current level and health to persistent storage.

Execution Table

Step	Action	Data Saved	Storage State	Result
1	Player reaches level 3	None	Empty	Progress not saved yet
2	Call SaveProgress()	Level=3, Health=75.5	Level=3, Health=75.5	Data written to storage
3	Player quits game	Level=3, Health=75.5	Level=3, Health=75.5	Data persists after quit
4	Player reloads game	None	Level=3, Health=75.5	Data loaded from storage
5	Restore player state	None	Level=3, Health=75.5	Player progress restored

💡 Execution stops after player progress is restored from saved data.

Variable Tracker

Variable	Start	After SaveProgress	After Quit	After Reload	Final
currentLevel	1	3	3	3	3
playerHealth	100.0	75.5	75.5	75.5	75.5
Storage (PlayerPrefs)	Empty	Level=3, Health=75.5	Level=3, Health=75.5	Level=3, Health=75.5	Level=3, Health=75.5

Key Moments - 3 Insights

Why does the game save data before quitting?

Because without saving, all progress would be lost when the game closes, as shown in step 3 of the execution_table.

What happens if the game tries to load progress but no data was saved?

The game will load default values or no progress, meaning the player starts fresh, unlike step 4 where saved data exists.

Why is PlayerPrefs.Save() important?

It ensures data is actually written to storage immediately, preventing loss if the game crashes or closes unexpectedly, as seen in step 2.

Visual Quiz - 3 Questions

Look at the execution_table, what data is saved at step 2?

A Level=1, Health=100.0

B No data saved yet

C Level=3, Health=75.5

D Level=5, Health=50.0

💡 Hint

Check the 'Data Saved' column at step 2 in the execution_table.

At which step does the player progress get restored?

A Step 3

B Step 5

C Step 1

D Step 2

💡 Hint

Look at the 'Result' column to find when progress is restored.

If PlayerPrefs.Save() was not called, what would likely happen?

A Data might not be saved before quitting

B Data would still be saved correctly

C Game would crash immediately

D Player progress would reset to level 10

💡 Hint

Refer to the explanation in key_moments about PlayerPrefs.Save() importance.

Concept Snapshot

Persistence stores player progress by saving game data to storage.
Use functions like PlayerPrefs.SetInt and PlayerPrefs.SetFloat to save values.
Call PlayerPrefs.Save() to write data immediately.
On game reload, load saved data to restore progress.
Without saving, progress is lost when quitting.

Full Transcript

This visual trace shows how persistence works to save and restore player progress in a game. The player plays and reaches a new level, then the game saves the current level and health to storage using PlayerPrefs. This data remains saved even after the player quits the game. When the player reloads the game, the saved data is loaded back, restoring the player's progress. Key moments include why saving before quitting is necessary, what happens if no data is saved, and the importance of calling PlayerPrefs.Save() to ensure data is written. The quiz questions help check understanding of these steps.