diff --git a/docs/concepts/save-states.md b/docs/concepts/save-states.md index c53d26c3..5fd44be5 100644 --- a/docs/concepts/save-states.md +++ b/docs/concepts/save-states.md @@ -1,11 +1,129 @@ -TODO +A real game console +is a complex piece of hardware, +with electricity flowing through it +in complex patterns that can't easily +be paused or recorded. +However, +an emulated console is pure software: +it only changes when the emulation software +deliberately updates it, +so the emulator software can save +the entire state of the emulated console +to disk, +and weeks or months later +bring it back to life +as though nothing had ever happened. Save states versus in-game saves -------------------------------- +Some games include their own systems +for saving and restoring the player's progress. +Here are some of the differences +between save states and in-game saves: + +
Save states | +In-game saves | +
---|---|
+ Work exactly the same way + in every game + | ++ Works differently in different games, + some games don't support it at all + | +
+ Save at any time, + anywhere in the game + | ++ Save only at special save-points + | +
+ Loading a save + puts the game back exactly how it was + when you pressed save + | ++ Loading a save + restores some things + (like the player's inventory + or remaining lives), + but may + forget others + (like taking you back to the beginning of the level) + | +
+ You can have dozens of save states + | ++ Most games limit you to about 3 saves + | +
+ Can only be loaded + by the same version of the same emulator + that created it + | ++ Works with any version of any emulator, + can sometimes even be copied to or from physical cartridges + | +