Why persistence stores player progress in Unity - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to save the player's score using PlayerPrefs.

Unity

PlayerPrefs.SetInt("PlayerScore", [1]);

Drag options to blanks, or click blank then click option'

Ascore

Bpoints

CscoreValue

DplayerScore

Attempts:

3 left

💡 Hint

Common Mistakes

Using a variable name that is not defined.

Forgetting to use quotes around the key name.

We use playerScore as the variable holding the player's current score to save it.

2fill in blank

medium

Complete the code to load the player's score from PlayerPrefs.

Unity

int loadedScore = PlayerPrefs.[1]("PlayerScore", 0);

Drag options to blanks, or click blank then click option'

AGetInt

BSave

CSetInt

DGetString

Attempts:

3 left

💡 Hint

Common Mistakes

Using GetString instead of GetInt.

Using SetInt which saves data instead of loading.

We use GetInt to retrieve an integer value saved with PlayerPrefs.

3fill in blank

hard

Fix the error in the code to save the player's level progress.

Unity

PlayerPrefs.SetInt("PlayerLevel", [1]); PlayerPrefs.[2]();

Drag options to blanks, or click blank then click option'

ASave

BLoad

CplayerLevel

DGetInt

Attempts:

3 left

💡 Hint

Common Mistakes

Using the same option for both blanks.

Not calling Save() after setting values.

The first blank should be the variable playerLevel to save the level number. The second blank should be Save to write changes.

4fill in blank

hard

Fill both blanks to check if a saved score exists and then load it.

Unity

if (PlayerPrefs.[1]("PlayerScore")) { int score = PlayerPrefs.[2]("PlayerScore"); }

Drag options to blanks, or click blank then click option'

AHasKey

BGetInt

CSetInt

DDeleteKey

Attempts:

3 left

💡 Hint

Common Mistakes

Using SetInt instead of GetInt.

Not checking if the key exists before loading.

Use HasKey to check if the key exists, then GetInt to load the score.

5fill in blank

hard

Fill all three blanks to save player's name, score, and then save changes.

Unity

PlayerPrefs.[1]("PlayerName", playerName); PlayerPrefs.[2]("PlayerScore", playerScore); PlayerPrefs.[3]();

Drag options to blanks, or click blank then click option'

ASetString

BSetInt

CSave

DGetString

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up SetString and SetInt.

Forgetting to call Save().

Use SetString for the name, SetInt for the score, and Save to write changes.

Practice

1. Why is persistence important in a Unity game for player progress?

easy

A. It changes the game graphics automatically.

B. It saves player progress so it is not lost between game sessions.

C. It makes the game run faster during play.

D. It prevents the player from quitting the game.

Solution

1. Step 1: Understand what persistence means in games

   Persistence means saving data so it stays even after the game is closed.

2. Step 2: Connect persistence to player progress

   Saving progress means players can continue where they left off next time.

3. Final Answer:

   It saves player progress so it is not lost between game sessions. -> Option B

4. Quick Check:

   Persistence = Save progress [OK]

Hint: Persistence means saving progress between sessions [OK]

Common Mistakes:

• Confusing persistence with game speed
• Thinking persistence changes graphics
• Believing persistence stops quitting

2. Which of the following is the correct way to save an integer score using PlayerPrefs in Unity?

easy

A. PlayerPrefs.Set("score", 100);

B. PlayerPrefs.SaveInt("score", 100);

C. PlayerPrefs.SetInt("score", 100);

D. PlayerPrefs.Save("score", 100);

Solution

1. Step 1: Recall PlayerPrefs method for saving integers

   The correct method is SetInt with key and value parameters.

2. Step 2: Check method names in options

   Only PlayerPrefs.SetInt("score", 100); matches the correct syntax.

3. Final Answer:

   PlayerPrefs.SetInt("score", 100); -> Option C

4. Quick Check:

   SetInt saves integer values [OK]

Hint: Use PlayerPrefs.SetInt for integers [OK]

Common Mistakes:

• Using incorrect method names like SaveInt
• Using Set instead of SetInt
• Confusing Save with Set

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

PlayerPrefs.SetInt("level", 3);
int currentLevel = PlayerPrefs.GetInt("level", 1);
Debug.Log(currentLevel);

medium

A. 3

B. Error

C. 0

D. 1

Solution

1. Step 1: Understand PlayerPrefs.SetInt and GetInt

   SetInt stores the value 3 with key "level". GetInt retrieves it, defaulting to 1 if not found.

2. Step 2: Since "level" was set, GetInt returns 3

   Therefore, Debug.Log prints 3.

3. Final Answer:

   3 -> Option A

4. Quick Check:

   Set then Get returns stored value [OK]

Hint: GetInt returns stored value if set, else default [OK]

Common Mistakes:

• Assuming default value is always returned
• Confusing SetInt with GetInt
• Expecting an error from PlayerPrefs

4. Identify the error in this Unity C# code that tries to save player health:

PlayerPrefs.SetFloat("health", 75);
// Missing PlayerPrefs.Save() call

medium

A. PlayerPrefs.SetFloat cannot save float values.

B. PlayerPrefs.SetFloat requires a string value, not a number.

C. The key "health" must be an integer.

D. PlayerPrefs.Save() must be called to ensure data is written.

Solution

1. Step 1: Check PlayerPrefs.SetFloat usage

   SetFloat correctly saves float values with a string key.

2. Step 2: Understand importance of PlayerPrefs.Save()

   Without Save(), data may not be written immediately and can be lost on crash.

3. Final Answer:

   PlayerPrefs.Save() must be called to ensure data is written. -> Option D

4. Quick Check:

   Always call Save() after setting PlayerPrefs [OK]

Hint: Call PlayerPrefs.Save() after setting values [OK]

Common Mistakes:

• Thinking SetFloat can't save floats
• Believing keys must be integers
• Confusing data types for PlayerPrefs

5. You want to save a player's name and highest score so progress is kept between sessions. Which approach correctly saves and retrieves this data in Unity?

hard

A. PlayerPrefs.SetString("playerName", "Alex"); PlayerPrefs.SetInt("highScore", 500); PlayerPrefs.Save(); string name = PlayerPrefs.GetString("playerName"); int score = PlayerPrefs.GetInt("highScore");

B. PlayerPrefs.SaveString("playerName", "Alex"); PlayerPrefs.SaveInt("highScore", 500); string name = PlayerPrefs.LoadString("playerName"); int score = PlayerPrefs.LoadInt("highScore");

C. PlayerPrefs.Set("playerName", "Alex"); PlayerPrefs.Set("highScore", 500); string name = PlayerPrefs.Get("playerName"); int score = PlayerPrefs.Get("highScore");

D. PlayerPrefs.SetString("playerName", "Alex"); PlayerPrefs.SetInt("highScore", 500); string name = PlayerPrefs.GetString("playerName"); int score = PlayerPrefs.GetInt("highScore");

Solution

1. Step 1: Identify correct PlayerPrefs methods for saving data

   Use SetString for strings and SetInt for integers, then call Save() to write data.

2. Step 2: Retrieve data with GetString and GetInt methods

   These methods get the saved values correctly.

3. Final Answer:

   PlayerPrefs.SetString("playerName", "Alex"); PlayerPrefs.SetInt("highScore", 500); PlayerPrefs.Save(); string name = PlayerPrefs.GetString("playerName"); int score = PlayerPrefs.GetInt("highScore"); -> Option A

4. Quick Check:

   Set + Save then Get methods for persistence [OK]

Hint: Set values, call Save(), then Get values to persist data [OK]

Common Mistakes:

• Using non-existent SaveString or LoadInt methods
• Forgetting to call PlayerPrefs.Save()
• Using generic Set or Get methods incorrectly