Progress saving

Requirement 1.9

In games with internal progress (like new levels, records, achievements, and skills), changes are saved right after the user performs an action or when they press the save button. Refreshing the page shouldn't affect the saved data.

The key rule is that the user must be able to continue the gameplay after refreshing the game page without losing their achievements or records. The progress must be saved after each user action or by a special button; other saving methods must be described in the developer's note.

When to save progress

Progress must be saved in games where users can set records or earn achievements, such as scoring a win, completing a level, or obtaining an item. Then the user will be able to continue playing from the exact point where they left off in their previous session.

There's no need to save progress in simple games where progress is absent or doesn’t affect the gameplay. For example, this is common in simple coloring books, puzzles, and quizzes.

Examples

Save required

Save not required

The player must finish the current level to unlock the next one.

All in-game levels are accessible immediately.

The player can set records, gain achievements, or score a win in the game.

The game doesn't feature records, achievements, or the possibility to win.

The difficulty level increases as the player progresses through the game.

The difficulty level isn't affected by the player's progress.

It may take a few average gaming sessions to finish a level.

Each level can be completed in one average gaming session, and all levels are available from the start.

Save mechanics

Game progress must be saved:

  • Immediately after a player performs an action or by pressing a specific button.

    Note

    If the game has other save methods, please provide a detailed explanation in the developer's note.

  • Regardless of whether the player is logged in or not.

  • When the device orientation changes (for mobile games).

If saving is set up correctly, refreshing the page at any time (after clicking the save button, if applicable) will ensure that the player's progress is exactly as it was before the refresh.

For mobile games, it's crucial that progress isn't lost when the device orientation changes. The game state after the orientation change should be exactly as before.

Examples

Correct

Incorrect

After refreshing the game page, records or progress are restored.

Records or the user's progress are not restored after the game page is refreshed.

Progress is saved immediately after the player's action or by pressing the save button.

Progress is saved at intervals.

Progress is saved at the end of a completed level or after earning an achievement within a level.

The game doesn't save user records or progress.

There is no progress in the game: no levels, difficulty increase, or records, so progress isn't saved.

The player is making progress in the game, but it's not being saved.

The game state is maintained across device orientation changes.

The game state isn't restored after the device orientation changes.

Progress isn't automatically saved after a player action or by pressing the save button. The save methods are described in the developer's note.

The game uses other save methods, but they aren't described in the developer's note.

Progress is saved for all users, whether they are logged in or not.

The player's scores are only saved on the leaderboard.