View source for Save-Load Cycles

[[Category:Gameplay Adaptability Patterns]]
[[Category:Patterns]]
[[Category:Dynamic Patterns]]
[[Category:Needs revision]]
[[Category:Needs references]]
[[Category:To be Published]]
''The actions of saving and loading game states to help get the game state one wishes.''

Many computer games allow players to save their game state. This can let them divide game instances into multiple game sessions and be able to turn of the game programs in-between. It can also let players store game state when they are in good positions or before they try potentially dangerous actions so they can go back to that game state if things went bad. Doing so repeatedly while playing causes players to engage in [[Save-Load Cycles]].

=== Examples ===
Examples of games that allow [[Save-Load Cycles]] include the [[Assassin's Creed series]], the [[Baldur's Gate series]], the [[Deus Ex series]], the [[Doom series]], the [[Dragon Age series]], the [[Elder Scrolls series]], the [[Europa Universalis series]], [[Mirror's Edge]], [[Sid Meier's Alpha Centauri]], the [[X-COM series]], and the [[Zork series]]. Of these, [[Europa Universalis series]] and [[X-COM series]] provide "ironman modes" in which the [[Save-Load Cycles]] are forbidden to make the games more challenging.

== Using the pattern ==
While it is used both for [[Turn-Based Games]] and [[Real-Time Games]], the presence of [[Save-Load Cycles]] affect the latter more through allowing [[Game Pauses]] in them which otherwise would not be present ([[Turn-Based Games]] have the opportunity for [[Game Pauses]] between each turn naturally). The primary challenge of [[Save-Load Cycles]] is the technical need of being able to store whole game states and quickly replace current ones with saved ones. This is typically solved by having games that support [[Save Files]] or are run by [[Dedicated Game Facilitators]]. [[Save Points]] can be used to make this easier but can also be used to require players to get to certain point in the gameplay before being allowed to save. 

[[Save-Load Cycles]] can difficult to combine well with [[Multiplayer Games]] since this requires that all players can easily come to agreements on when to abandon current play sessions and replace the current game state with a saved one. This becomes a practical impossibility in [[Massively Multiplayer Online Games]] since these typically wish to provide [[Persistent Game Worlds]] for all players. 

Some [[Difficulty Levels]], typically called "ironman mode", forbid the use of [[Save-Load Cycles]]. This is typically done too make the games more difficult but there are other reasons to consider not providing [[Save-Load Cycles]]. They void [[Irreversible Events]] and make [[Penalties]] such as [[Death Consequences]] and [[Permadeath]] avoidable. Further, they let players experience [[Leaps of Faith]], [[Surprises]], and [[Tension]] once and then reload a play again without having to be affect by these emotionally. They can also make [[Time Limited Game Instances]] pointless at least from a planning perspective and stop [[Scores]] from representing how well players played in a continuous series of play sessions.

=== Diegetic Aspects ===
[[Save-Load Cycles]] are typically not explained through a game's diegesis. An exception can be found in the [[Assassin's Creed series]]. 

=== Interface Aspects ===
While access to "quick-save" and "quick-load" functionality may be enabled through the primary interface of a game, the main functionality for [[Save-Load Cycles]] is typically provided in [[Secondary Interface Screens]]. 

=== Narration Aspects ===
Besides potentially making the presence of [[Irreversible Events]], [[Leaps of Faith]], and [[Surprises]] mute regarding gameplay, [[Save-Load Cycles]] can do the same for narration aspects of a game.

== Consequences ==
The actual actions of saving and loading are [[Extra-Game Actions]] and cause some [[Downtime]] for players. However, more interesting is the many effects on gameplay [[Save-Load Cycles]] have. The first most basic consequences is that it allows for [[Interruptibility]] since players can have [[Game Pauses]] and this gives players a [[Freedom of Choice]] when to play since the pattern in practice gives them [[Negotiable Play Sessions]]. Player can also use the interludes between play sessions to plan, so the pattern also provides [[Stimulated Planning]]. However, the use of the pattern in a game breaks [[Temporal Consistency]] of the diegesis as compared to the sequence of gameplay actions players perform.

The ability to load after something unwanted has occurred gives players a form of [[Reversibility]] and [[Extra Chances]], and since players can learn from previous attempts [[Save-Load Cycles]] provide [[Trans-Game Information]] between play sessions and can let players create [[Fudged Results]] for themselves. Games providing [[Direct Information]] are affected by [[Save-Load Cycles]] as players can use the information provided as [[Trans-Game Information]] to make use of it earlier than they were supposed to have knowledge of it. The same applies for information provided by [[Near Miss Indicators]]. This can be seen as a form of [[Game Time Manipulation]] done through non-gameplay actions and allowing for local [[Replayability]] inside game instances. Extensive use of these possibility provided by [[Save-Load Cycles]] can lead to [[Save Scumming]] (which can be especially likely in games with [[Mini Games]]).

While the pattern is most often used in [[Single-Player Games]], in these specifically [[Save-Load Cycles]] can encourage player to do [[Experimenting]] since the cost of testing something may at most be some [[Downtime]]. The ability to instantly mitigate bad effects of gameplay actions which [[Save-Load Cycles]] provide can let players have [[Smooth Learning Curves]] when trying to learn something about a game.

== Relations ==
=== Can Instantiate ===
[[Downtime]], 
[[Extra Chances]], 
[[Freedom of Choice]], 
[[Fudged Results]], 
[[Game Time Manipulation]], 
[[Game Pauses]], 
[[Interruptibility]], 
[[Negotiable Play Sessions]], 
[[Replayability]], 
[[Reversibility]], 
[[Save Scumming]], 
[[Smooth Learning Curves]], 
[[Stimulated Planning]], 
[[Trans-Game Information]] 

==== with [[Single-Player Games]] ====
[[Experimenting]]

=== Can Modulate ===
[[Real-Time Games]]

=== Can Be Instantiated By ===
[[Dedicated Game Facilitators]], 
[[Extra-Game Actions]], 
[[Save Files]]

=== Can Be Modulated By ===
[[Direct Information]], 
[[Near Miss Indicators]], 
[[Save Points]], 
[[Secondary Interface Screens]]

=== Possible Closure Effects ===
-

=== Potentially Conflicting With ===
[[Death Consequences]], 
[[Difficulty Levels]], 
[[Irreversible Events]], 
[[Leaps of Faith]], 
[[Penalties]], 
[[Permadeath]], 
[[Multiplayer Games]], 
[[Scores]], 
[[Surprises]], 
[[Temporal Consistency]], 
[[Tension]], 
[[Time Limited Game Instances]]

== History ==
An updated version of the pattern ''Save-Load Cycles'' that was part of the original collection in the book ''Patterns in Game Design''<ref name="Bjork & Holopainen 2004"/>.

== References ==
<references>
<ref name="Bjork & Holopainen 2004">Björk, S. & Holopainen, J. (2004) ''Patterns in Game Design''. Charles River Media. ISBN1-58450-354-8.</ref>
</references>

== Acknowledgements ==
-