This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these template messages)
From the earliest games in the 1970s onward, game platform hardware and memory improved, which led to bigger and more complex computer games, which, in turn, tended to take more and more time to play them from start to finish. This naturally led to the need to store in some way the progress, and how to handle the case where the player received a "game over". More modern games with a heavier emphasis on storytelling are designed to allow the player many choices that impact the story in a profound way later on, and some game designers do not want to allow more than one save game so that the experience will always be "fresh".
Game designers allow players to prevent the loss of progress in the game (as might happen after a game over). Games designed this way encourage players to 'try things out', and on regretting a choice, continue from an earlier point on.
Although the feature of save games often allows for gameplay to resume after a game over, a notable exception is in games where save games are deleted when it is game over. Several names are used to describe this feature, including "permadeath", "iron man", and "hardcore", and the feature has developed over the years from being the only kind of save system per game to the more modern 'suspend game' feature among regular save points. For online games, the game's progress is maintained on the remote server. In some games, upon resuming the game from a save game, the software locks or marks the save game. Early examples include Moria and Diablo II's "hardcore" mode where the character save game is managed by the server. The use of saved games is very common in modern video games, particularly in role-playing video games, which are usually much too long to finish in a single session.
Overview and history Edit
Classic arcade video games from the golden age of arcade video games did not save the player's progress towards completing the game, but rather high scores, custom settings, and other features. The first game to save the player's score was Taito's seminal 1978 shoot 'em up title Space Invaders.
The relative complexity and inconvenience of storing game state information on early home computers (and the fact that early video game consoles had no non-volatile data storage) meant that initially game saves were represented as "passwords" (often strings of characters that encoded the game state) that players could write down and later input into the game when resuming.
BYTE magazine stated in 1981, regarding the computer text adventure Zork I's save-game feature, that "while some cowards use it to retain their hard-earned position in the game before making some dangerous move", it was intended to let players play over many weeks. InfoWorld disagreed that year, stating that save games "allow users to experiment with different approaches to the same situation". Home computers in the early 1980s had the advantage of using external media for saving, with compact cassettes and floppy disks, before finally using internal hard drives.
For later cartridge-based console games, such as The Legend of Zelda and Kirby's Adventure, saved games were stored in battery-backed random-access memory on the game cartridge itself. Pop and Chips (1985) for the Super Cassette Vision was the first-ever game to allow saving game progress on a video game console, using an AA battery on the game cassette.
Later game cartridges, such as Mirai Shinwa Jarvas (未来神話ジャーヴァス, Future Legend Jarvas), a role-playing video game released for the Famicom in June 1987 and the Nintendo Entertainment System version of The Legend of Zelda released in August 1987, would use a button cell battery.
In modern consoles, which use disks for storing games, saved games are stored in other ways,[clarification needed] such as by use of memory cards or internal hard drives on the game machine itself. The use of memory cards for saving game data dates back to SNK's cartridge-based Neo Geo arcade system and home console in 1990.
Depending on the game, a player will have the ability to save the game either at any arbitrary point (usually when the game has been paused), after a specific task has been completed (such as at the end of a level), or at designated areas within the game known as save points.
The available ways to save a game affect gameplay, and can represent a practice of players or an explicit decision by designers to give the game a particular feel or alter its difficulty.
Time and location of saving Edit
A video game may allow the user to save at any point of the game at any time. There are also modified versions of this. For example, in the GameCube game Eternal Darkness, the player can save at almost any time, but only if no enemies are in the room. To make gaming more engaging, some video games may impose a limit on the number of times a player saves the game. For instance, IGI 2 allows only a handful of saves in each mission; Max Payne 2 imposes this restriction on the highest level of difficulty.
Some video games only allow the game to be saved at predetermined points in the game, called save points.[according to whom?] (Not to be confused with "checkpoints".) Save points are employed either because the game is too complex to allow saving at any given point or to attempt to make the game more engaging by forcing the player to rely on skills instead of on the ability to retry indefinitely. Save points are also far easier to program, so when a game developer has to rush a game, save points are attractive to develop.
Some games use a hybrid system where both save anywhere and save points are used. For example, Final Fantasy VII permits saving anywhere when the player is traveling on the world map, but once the player enters a location (e.g. town, cavern or forest), saving is only possible at save points.
Overusing saved games may be seen as unfair and in such a context is referred to as '"savescumming." Savescumming makes losing a game impossible because whenever the player loses or is about to lose, a savegame is loaded, effectively turning back time to the situation before the loss. In a video game, this could for example be done when the player loses a battle/race, misses the best performance grading for a level (such as an S-rank) or runs into an unwinnable situation by losing anyone or anything needed to continue and win. For example, in a game that features a casino, the player could save the game and then bet all their in-game money on black at a roulette table. If the outcome is black, their money is doubled and the player saves the game again. If the outcome is red (or green), the player disregards this outcome by reloading their last savegame. This allows for an indefinite winning streak.
Game programmers may defend against savescumming by various means, such as checking timestamps. For example, on multiuser Unix systems, NetHack uses setgid to prevent users from copying save files into the necessary directory. Another technique is to use a deterministic, seeded pseudorandom number generator, so that undesired random outcomes cannot be avoided simply by saving and reloading. In this situation, when the player reloads a saved game, 'random' events will occur identically every time – the only way to get a different outcome is to play differently.
Types of saved games Edit
Game saving does not need to be manual. Some video games save the game in progress automatically, such as after the pass of a fixed amount of time, at certain predetermined points in the game as an extension to the save point concept, or when the player exits.
Some games only permit "suspend saves" in which the game is automatically saved upon exiting and reloaded upon restarting. The aim of a suspend save is only to allow the gameplay to be temporarily interrupted; as such, suspend saves are erased when the player resumes the game. This concept was popularized by Rogue and the namesake genre, which are known for employing the mechanic such that if the player were to die in the game, their save file is deleted and the game must be restarted. The term "perma-death" would come to refer to the concept used for that purpose. It is possible to cheat the system by copying and reusing suspend save files in an act of what is considered to be a form of savescumming.
"Checkpoints" are locations in a video game where a player character respawns after death. Characters generally respawn at the last checkpoint that they have reached. A respawn is most often due to the death of the in-game character, but it can also be caused by the failure to meet an objective required to advance in the game. Checkpoints might be temporary, as they stop working when the player loses their last life, completes or quits the level, especially in platform games. Most modern games, however, save the game to memory at these points, known as auto-saving.
Checkpoints might be visible or invisible to the player. Visible checkpoints might give a player a sense of security when activated, but in turn sacrifice some immersion, as checkpoints are intrinsically "gamey" and might even need an explanation of how they work. Invisible checkpoints do not break immersion but make players unsure of where they will respawn. Usually, if a player does get a game over, then their progress will be lost, and the player would lose all of their checkpoints.
Quick-saving and quick-loading allow the player to save or load the game with a single keystroke. These terms are used to differentiate between the traditional saving mechanism where the player is required to invoke a menu or dialog box, issue save the order, specify a title for the game being saved and, if applicable, confirm whether an old saved game file with the same title should be overwritten. The term "quick save" may be used in video games that lack the traditional saving mechanism altogether.
The advantage of quick saving is its low burden: The player only has to press a button and, if applicable, wait a few seconds. The disadvantage is the automatic loss of the previous quick-saved game. Games that only offer quick saving may be impossible to play by two different players (or more) unless there is a mechanism to distinguish players, such as user accounts. Leaving the decision of when to save up to the player increases the likelihood that a save will be made during a less than favourable game state. A quicksave shortly before an event which kills the player creates what is known as a death loop.
Passwords are a form of saved game not stored on non-volatile memory. Instead, everything needed to reconstruct the game state is encoded in and displayed on-screen as a string of text, usually comprising random alphanumeric characters, and the player can then record or memorize it. The player may later resume play from that point by entering the same password. Passwords were widely used by home console games before the advent of non-volatile memory and later internal and external storage.
Save states Edit
A "save state" is a form of a saved game in emulators. A save state is generated when the emulator stores the contents of random-access memory of an emulated program to disk. Save states enable players to save their games even when the emulated game or system does not support the feature. For instance, save states may be used to circumvent saving restrictions or as a savescumming technique. An associated concept is save state hacking, the practice of which uses a hex editor to modify the save states to alter gameplay conditions, usually in favor of the player. Save states are comparable to snapshots of a computer system's state or hibernation in computing, with save states being a limited form of snapshots.
Save states have started to receive mainstream usage in the early 2010s with Nintendo's Virtual Console. Some Wii U and 3DS Virtual Console titles allow players to save a "restore point," which is like a quick save but has no restrictions on reloading. Although likely derived from quick saves, restore points are functionally identical to save states, and can be used for many of the same purposes.
Game designers often attempt to integrate the save points into the style of the game using skeuomorphism. Resident Evil represents save points with old fashioned typewriters (which require an ink ribbon item for each save), the Grand Theft Auto series used representations appropriate to the era of the setting: cassette tapes for the mid-1980s (Grand Theft Auto: Vice City), 3½-inch disks for the early-1990s (Grand Theft Auto: San Andreas), and compact discs for the late-1990s (Grand Theft Auto: Liberty City Stories).
Although save points are typically seen as boons, some games have traps which use this tendency to fool the player. In Chrono Trigger, attempting to use a fake save point in Magus's castle can actually bring the party into battle.
Some games employ limits to saving in order to prevent players from using them as a primary means of succeeding in the game. In Tomb Raider save points are consumed upon use, Donkey Kong Country 2: Diddy's Kong Quest charges two banana coins to use a save point more than once, and in Resident Evil the player must find and expend an ink ribbon for each save.
Another way saved games interact with each other is through passing along data to sequels. A famous example of this is the first three installments of the Wizardry series. To play the second and third installments, players needed to import the characters they'd used in the previous installment, which retained all experience and equipment gained in that installment. Later versions of the games made this feature optional, as do franchises such as the Fire Emblem, Shenmue and .hack series. Video games may also take the saved games of other video games into account; for example, the character Rosalina becomes available on Mario Kart Wii if there is a Super Mario Galaxy save on the console. The save game of Midnight Club 3: DUB Edition can be imported to the Remix version of the game.
Save sharing Edit
For many years,[vague] sharing game saves among friends has been very common. From trading passwords to swapping memory cards, gamers have always been able to help each other out to unlock features in a game. With the growing popularity of the Internet, many people upload their game saves to help out their online friends. However, with the inclusion of a progress meter or "gamerscore" that tracks player progress in games for the Xbox 360, many players are beginning to view those who load other people's files onto their systems as "cheaters". Some games such as Grand Theft Auto IV attempt to prevent the use of saved games made by other users. In contrast, The Legend of Zelda: Oracle of Seasons and Oracle of Ages actively encourages players that have completed the game to share their progress with others via a password swapping side quest that is available after finishing the main story.[original research?]
Arcade games Edit
This section needs expansion. You can help by adding to it. (February 2011)
Saved games have generally been rare at arcades,[according to whom?] but have found some use, notably in the Konami e-Amusement system, or by the use of PlayStation cards, as in Dance Dance Revolution. These generally use either a magnetic card to store the data, or network (internet) connection, or some combination thereof. Similarly, passwords have generally been rare at arcades, with occasional exceptions, such as Gauntlet Legends.
See also Edit
- Geddes, Ryan; Hatfield, Daemon (2007-12-10). "IGN's Top 10 Most Influential Games". IGN. Archived from the original on June 4, 2012. Retrieved 2008-07-11.
- Liddil, Bob (February 1981). "Zork, The Great Underground Empire". BYTE. pp. 262–264. Retrieved 18 October 2013.
- Barry, Tim (1981-05-11). "In Search of the Ultimate Computer Game". InfoWorld. pp. 11, 48. Retrieved 2019-04-17.
- "Bravo World Record!". Famicom Tsūshin (in Japanese). No. 226. 16 April 1993. p. 91.
- "This Fall Everything Turns To Gold With Neo-Geo: The Player's Gold Card Keeps Them Coming Back For More". RePlay. Vol. 16, no. 2. November 1990. pp. 26–7.
- Moran, Chuk (2010). "Playing with Game Time". Fibreculture. 16. Retrieved 16 July 2012.
- Geerts, Femke Lucienne (2017). Saving the Game is Shaping the Game: Defining and Understanding the Save Mechanic (PDF) (Thesis). Utrecht University. p. 13–14, 20–21. hdl:1874/351188. Archived from the original (PDF) on 2021-11-17. Retrieved 2021-11-17.
- Harris, John (2020). "6.1 Permadeath Defined". Exploring Roguelike Games. CRC Press. p. 55. ISBN 978-1-000-16949-2. Retrieved 2021-11-17.
- Ernest, Adams (2010-04-07). Fundamentals of Game Design. New Riders. p. 403. ISBN 978-0132104753. Retrieved 2014-11-26.
- Rogers, Scott (2014-04-16). "A nice little calm spot". Level Up! The Guide to Great Video Game Design. John Wiley & Sons. ISBN 978-1118877197. Retrieved 2014-11-26.
- Aniko, Angyal (2019-01-02). "Deathloop: What is Zenimax planning?". The Geek. Retrieved 2020-02-13.
- Lowood, Henry; Guins, Raiford (2016). "45 Save". Debugging Game History: A Critical Lexicon. MIT Press. pp. 385–387. ISBN 9780262331951. Retrieved 2021-11-17.
- Altice, Nathan (2015). "8 Tool-Assisted". I Am Error: The Nintendo Family Computer / Entertainment System Platform. MIT Press. pp. 312–313. ISBN 978-0-262-32840-1. Retrieved 2021-11-17.
- Cazares, Sergio (2013-12-15). "Restore Point or No Restore Point". 30PLUSGAMER. Archived from the original on May 28, 2015. Retrieved 2015-05-28.
- Grant, Christopher (2008-03-25). "Cheaters Branded on Xbox Live, Gamerscore Reset, Joystiq". Joystiq. Archived from the original on June 20, 2013. Retrieved 2011-08-29.