Save slot management in Unity - Step-by-Step Execution

Concept Flow - Save slot management

Start Game

↓

Display Save Slots

↓

Player Selects Slot

↓

Check Slot Exists?

No→Create New Save

↓

Save Data Initialized

↓

Load Save Data

↓

Player Plays Game

↓

Player Plays Game

↓

Player Saves Progress

↓

Player Saves Progress

↓

Update Save Slot Data

↓

Return to Save Slots or Exit

The game starts by showing save slots. The player picks one. If it exists, load it; if not, create new. Player plays and saves, updating the slot.

Execution Sample

Unity

void SaveGame(int slot) {
  if (SaveExists(slot)) {
    LoadSave(slot);
  } else {
    CreateNewSave(slot);
  }
  // Player plays and saves
  SaveData(slot);
}

This code checks if a save slot exists, loads or creates it, then saves player data.

Execution Table

Step	Action	Slot	Condition	Result	Output
1	Player selects slot	1	N/A	Slot 1 selected	Display slot status
2	Check if save exists	1	SaveExists(1)?	False	Create new save
3	Create new save	1	N/A	New save created	Initialize data
4	Player plays game	1	N/A	Game running	Player progress ongoing
5	Player saves progress	1	N/A	SaveData(1) called	Data saved to slot 1
6	Player selects slot	2	N/A	Slot 2 selected	Display slot status
7	Check if save exists	2	SaveExists(2)?	True	Load save data
8	Load save data	2	N/A	Data loaded	Player continues from save
9	Player plays game	2	N/A	Game running	Player progress ongoing
10	Player saves progress	2	N/A	SaveData(2) called	Data saved to slot 2
11	Exit	N/A	N/A	End of session	Game closes or returns to menu

💡 Execution stops when player exits or returns to main menu.

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 5	After Step 7	After Step 8	After Step 10	Final
slot	N/A	1	1	1	2	2	2	N/A
SaveExists(slot)	N/A	False	False	True	True	True	True	N/A
SaveData(slot)	N/A	N/A	N/A	Saved	N/A	N/A	Saved	N/A
GameState	Empty	Empty	Initialized	Playing	Loaded	Playing	Saved	N/A

Key Moments - 3 Insights

Why do we check if a save slot exists before loading?

Because if the slot doesn't exist (see step 2 in execution_table), we must create a new save to avoid errors.

What happens if the player selects a slot with existing data?

The game loads the saved data (step 7 and 8), so the player continues from where they left off.

When is the save data actually written to the slot?

After the player finishes playing and chooses to save (steps 5 and 10), the data is saved to the slot.

Visual Quiz - 3 Questions

Look at the execution table, what is the result of SaveExists(1) at step 2?

A Error

B False

C True

D Not checked

💡 Hint

Check the 'Condition' and 'Result' columns at step 2 in the execution_table.

At which step does the game create a new save slot?

A Step 1

B Step 7

C Step 3

D Step 10

💡 Hint

Look for the action 'Create new save' in the execution_table.

If SaveExists(2) was false, how would the execution_table change at step 7?

A It would create a new save

B It would load save data

C It would skip saving

D It would exit the game

💡 Hint

Compare step 2 and 7 actions for when SaveExists is false.

Concept Snapshot

Save Slot Management in Unity:
- Show save slots to player
- On slot select, check if save exists
- If yes, load save data
- If no, create new save
- Player plays and saves progress
- Save updates slot data
- Repeat or exit game

Full Transcript

This visual execution shows how save slot management works in Unity. The game starts by displaying save slots. When the player selects a slot, the program checks if a save exists. If not, it creates a new save. The player then plays the game and can save progress, which updates the save slot data. This cycle repeats for different slots until the player exits or returns to the main menu.

Practice

1. What is the main purpose of save slots in a Unity game?

easy

A. To let players save and load their game progress in different places

B. To increase the game's frame rate

C. To change the game's graphics settings

D. To add new characters automatically

Solution

1. Step 1: Understand what save slots do

   Save slots store player progress so it can be saved and loaded later.

2. Step 2: Identify the correct purpose

   Only To let players save and load their game progress in different places describes saving and loading progress, which is the main use of save slots.

3. Final Answer:

   To let players save and load their game progress in different places -> Option A

4. Quick Check:

   Save slots = save/load progress [OK]

Hint: Save slots store player progress, not graphics or performance [OK]

Common Mistakes:

• Confusing save slots with graphics or performance settings
• Thinking save slots add new game content automatically

2. Which of the following is the correct way to declare a save slot variable in C# for Unity?

easy

A. int = saveSlot 1;

B. saveSlot int = 1;

C. int saveSlot = 1;

D. var saveSlot 1;

Solution

1. Step 1: Recall C# variable declaration syntax

   In C#, the type comes first, then the variable name, then the value with '='.

2. Step 2: Check each option

   int saveSlot = 1; follows correct syntax: 'int saveSlot = 1;'. Others have wrong order or missing '='.

3. Final Answer:

   int saveSlot = 1; -> Option C

4. Quick Check:

   Type name = value; is correct syntax [OK]

Hint: Remember: type first, then name, then = value [OK]

Common Mistakes:

• Putting variable name before type
• Missing the '=' sign
• Using 'var' without '=' and value

3. What will be the output of this Unity C# code snippet managing save slots?

int currentSlot = 2;
switch (currentSlot) {
  case 1:
    Debug.Log("Loading slot 1");
    break;
  case 2:
    Debug.Log("Loading slot 2");
    break;
  default:
    Debug.Log("Slot not found");
    break;
}

medium

A. Loading slot 1

B. Loading slot 2

C. Slot not found

D. No output

Solution

1. Step 1: Identify the value of currentSlot

   currentSlot is set to 2.

2. Step 2: Follow the switch-case logic

   Case 2 matches currentSlot, so it logs "Loading slot 2".

3. Final Answer:

   Loading slot 2 -> Option B

4. Quick Check:

   Switch case 2 matches currentSlot 2 [OK]

Hint: Match switch value to case labels to find output [OK]

Common Mistakes:

• Choosing default case instead of matching case
• Confusing case numbers
• Ignoring break statements

4. Identify the error in this Unity C# code for saving a slot:

void SaveGame(int slot) {
  PlayerPrefs.SetInt("SaveSlot", slot);
  PlayerPrefs.Save();
}

SaveGame();

medium

A. Missing argument when calling SaveGame()

B. PlayerPrefs.SetInt cannot save integers

C. PlayerPrefs.Save() is not needed

D. Function SaveGame should return a value

Solution

1. Step 1: Check function definition and call

   SaveGame requires an int argument 'slot'.

2. Step 2: Check function call

   SaveGame() is called without any argument, causing an error.

3. Final Answer:

   Missing argument when calling SaveGame() -> Option A

4. Quick Check:

   Function parameters must be provided when called [OK]

Hint: Always pass required arguments when calling functions [OK]

Common Mistakes:

• Calling function without required parameters
• Thinking PlayerPrefs can't save ints
• Assuming SaveGame must return a value

5. You want to save multiple player data in different save slots using PlayerPrefs in Unity. Which approach correctly saves player name and level for slot 3?

hard

A. PlayerPrefs.SetString("PlayerName", "Alex"); PlayerPrefs.SetInt("PlayerLevel", 3); PlayerPrefs.Save();

B. PlayerPrefs.SetString("PlayerName3", "Alex"); PlayerPrefs.SetInt("PlayerLevel3"); PlayerPrefs.Save();

C. PlayerPrefs.SetString("3_PlayerName", "Alex"); PlayerPrefs.SetInt("3_PlayerLevel", 10);

D. PlayerPrefs.SetString("PlayerName_3", "Alex"); PlayerPrefs.SetInt("PlayerLevel_3", 10); PlayerPrefs.Save();

Solution

1. Step 1: Understand how to separate save slots

   Use unique keys per slot, like "PlayerName_3" and "PlayerLevel_3" for slot 3.

2. Step 2: Check each option for correct syntax and key naming

   PlayerPrefs.SetString("PlayerName_3", "Alex"); PlayerPrefs.SetInt("PlayerLevel_3", 10); PlayerPrefs.Save(); uses correct keys and calls PlayerPrefs.Save(). PlayerPrefs.SetString("PlayerName", "Alex"); PlayerPrefs.SetInt("PlayerLevel", 3); PlayerPrefs.Save(); overwrites slot data. PlayerPrefs.SetString("3_PlayerName", "Alex"); PlayerPrefs.SetInt("3_PlayerLevel", 10); misses Save(). PlayerPrefs.SetString("PlayerName3", "Alex"); PlayerPrefs.SetInt("PlayerLevel3"); PlayerPrefs.Save(); misses value for SetInt.

3. Final Answer:

   PlayerPrefs.SetString("PlayerName_3", "Alex"); PlayerPrefs.SetInt("PlayerLevel_3", 10); PlayerPrefs.Save(); -> Option D

4. Quick Check:

   Unique keys per slot + Save() = correct save [OK]

Hint: Use unique keys per slot and call PlayerPrefs.Save() [OK]

Common Mistakes:

• Overwriting data by using same keys for all slots
• Forgetting to call PlayerPrefs.Save()
• Missing value argument in SetInt