Difference between revisions of "Save Files"

From gdp3
Jump to: navigation, search
(Using the pattern)
Line 14: Line 14:
  
 
=== Examples ===
 
=== Examples ===
 
+
Most [[:Category:Computer Games|Computer Games]] provide support for [[Save Files]], e.g. the [[Doom series]], the [[Tomb Raider series]], the [[Mass Effect series]], and the [[Europa Universalis series]].
==== Anti-Examples ====
+
optional
+
  
 
== Using the pattern ==
 
== Using the pattern ==
Line 31: Line 29:
  
 
== Relations ==
 
== Relations ==
 +
[[Game Pauses]]
 +
 
=== Can Instantiate ===
 
=== Can Instantiate ===
 
[[Extra-Game Actions]],  
 
[[Extra-Game Actions]],  
Line 42: Line 42:
  
 
=== Can Modulate ===
 
=== Can Modulate ===
-
+
[[Game Pauses]]
  
 
=== Can Be Instantiated By ===
 
=== Can Be Instantiated By ===

Revision as of 12:00, 10 November 2015

The one-sentence "definition" that should be in italics.

This pattern is a still a stub.

Examples

Most Computer Games provide support for Save Files, e.g. the Doom series, the Tomb Raider series, the Mass Effect series, and the Europa Universalis series.

Using the pattern

Supporting Save Files in games consist creating the technical infrastructure that stores the game states and allows the game to take previously created Save Files and load these game states into games. From considering players' experiences, creating Save Files mainly consist of if they are created through Extra-Game Actions, Save Points, automatic saving, or all three. Care also needs to be taken supporting the Extra-Game Actions related to destroy and loading Save Files. Resource Caps can be put on Save Files to limit either the number of simultaneous files that can be used, making them into a form of Resource.

While there is typically a need or wish to have Save Files store complete game states, these can sometimes be quite small due to gameplay being partitioned into Levels or other smaller units. A special case of this is when the only information that needs to be saved is how long players have progressed and in this case Password Save Files can be sufficient.

The presence of Unwinnable Game States can cause players to create Save Files from which they will always lose Lives, fail Quests, or lose entire game instances.

Consequences

The possibility of creating Save Files can lead to Save-Load Cycles and Save Scumming, which both lead to gameplay when intended Surprises no longer work. While creating and loading Save Files are Extra-Game Actions, the presence of Save Files can give rise to additional Extra-Game Actions in the form of Game Element Trading and Game State Editing.

When the number of Save Files are limited, i.e. when Resource Caps are applied on them, they become Resources that players need to consider for gameplay reasons.

Relations

Game Pauses

Can Instantiate

Extra-Game Actions, Game Element Trading, Game State Editing, Save Scumming, Save-Load Cycles

with Resource Caps

Resources

Can Modulate

Game Pauses

Can Be Instantiated By

Extra-Game Actions, Password Save Files, Save Points

Can Be Modulated By

Resource Caps, Unwinnable Game States

Possible Closure Effects

-

Potentially Conflicting With

Surprises

History

New pattern created in this wiki.

References

-

Acknowledgements

-