STEP 58 OF 67 · YOU ARE THE GAMEPLAY PROGRAMMER
Build the interface and save system
Main menu, pause, health, objectives, settings and quit. Save checkpoints, objectives, equipment and settings, and test quitting mid-save and missing save files.
How to do it
- Build the menus and HUD.
- Save and load everything the player expects.
- Test quitting mid-save and a deleted save file.
How AI speeds this up
Ask Duke to design the SaveGame structure for your systems.
Example from a sample game
Ashfall: 3 save slots, autosave at campfires.
Before you move on
In Duke Forger, this step's gate checks:
- Verified by DukeMain menu title set
- You confirm itQuitting mid-save does not corrupt progress
- You confirm itA missing save file is handled
Words to know
- HUD
- Heads-up display: health, ammo, objectives and minimap drawn over the game.
- Save game
- The stored progress of a player: checkpoints, items, settings.
Do step 58 on your own game
Start freeIncluded in Creator, Academy and Studio. Duke drafts it with you and checks it before step 59 opens.