# Game Save System First Draft

Plan the first save file around the minimum state needed to resume a prototype.

## Outcome
Save and reload one small game state without inventing a full account system.

## Safe first step
List the exact state that must survive closing the game.

## Ladder steps
### 1. Choose save scope
Learn to choose save scope as one discrete move in the project path.

Check: You can explain or demonstrate: choose save scope.

### 2. Write plain data
Learn to write plain data as one discrete move in the project path.

Check: You can explain or demonstrate: write plain data.

### 3. Load into a clean scene
Learn to load into a clean scene as one discrete move in the project path.

Check: You can explain or demonstrate: load into a clean scene.

### 4. Test missing or corrupt files
Learn to test missing or corrupt files as one discrete move in the project path.

Check: You can explain or demonstrate: test missing or corrupt files.

## Examples
### Practice save current level id
```sh
Save current level id
```
Expected signal: A visible result you can compare before moving on

### Practice save player position
```sh
Save player position
```
Expected signal: A visible result you can compare before moving on

### Practice load default state if missing
```sh
Load default state if missing
```
Expected signal: A visible result you can compare before moving on

## Common traps
- Saving every runtime object.
- Depending on a cloud account before local save works.
- Never testing a corrupted save file.

## Practice task
Create a small practice case for game save system first draft and write what each step proves before moving to the next one.

## Next steps
- Download the Obsidian note.
- Review the Anki cards.
- Pick one related ladder and do the practice task.

## Related
- [Browse topic clusters](/topics/)
- [All learning ladders](/learn/)