Difference between revisions of "Save scumming"
(→Experience) |
(Some rearrangements in grammar; mention setgid situation on multiuser systems.) |
||
| Line 1: | Line 1: | ||
| − | When playing NetHack on a local machine (ie. not on a server such as [[NAO]]), it is possible to sidestep the feature that makes | + | When playing NetHack on a local machine (ie. not on a server such as [[NAO]]), it is possible to sidestep the feature that makes the game so difficult: the permanence of death. |
| + | |||
| + | The concept of '''save scumming''' is simple: exit NetHack via the Shift-S save command, then copy the saved game from NetHack's [[playground]] to a different directory. Run NetHack again, and continue playing until you [[die]]. At this point, restore the saved files, copying them back from the temporary directory to the playground, and restart the game. Assuming the correct files were copied, the game continues as it was. This process is [[cheating]], especially because the legitimate way to sidestep death is [[explore mode]]. On a few systems, though, it might be necesssary to guard against game or system crashes, because some copies of NetHack lack a working [[recover]] program. | ||
==Criticism== | ==Criticism== | ||
| Line 6: | Line 8: | ||
===Player skills=== | ===Player skills=== | ||
| − | While savescumming may allow a new player to go farther in the dungeon than he or she has before, | + | While savescumming may allow a new player to go farther in the dungeon than he or she has before, it will ultimately create a weaker [[player]] than if he or she had toughed it out. By saving and restoring games, the savescummer avoids the learning of the intricacies of NetHack, and will never learn the art of extracting him or herself from difficult positions. [[Death]] is part of the game, and a player who savescums to avoid death is not truly playing NetHack. |
There are many roleplaying games that allow you to avoid death by saving and restoring your game. By savescumming, a player is missing out on the true fun of the game, at which point NetHack is hardly superior to any other RPG available. | There are many roleplaying games that allow you to avoid death by saving and restoring your game. By savescumming, a player is missing out on the true fun of the game, at which point NetHack is hardly superior to any other RPG available. | ||
| Line 12: | Line 14: | ||
==Methodology== | ==Methodology== | ||
| − | The methods by which NetHack saves games differ per version. Similarly, the saved games are not necessarily compatible between [[ | + | The methods by which NetHack saves games differ per version. Similarly, the saved games are not necessarily compatible between [[version]]s or between [[platform]]s. |
The easiest way to savescum is to start a brand new game. Once it is started, examine the directories in which NetHack is storing data and find one with a name similar to "save". Now save and exit the game. Examine the directory again, and see what files have appeared. Make a list of the files and the filename syntax (usually the player name with a number). Now restart the game and let the character die. Once again, examine the directory and see which files dissapeared. After doing this you should have a good idea of what files hold the game's information. | The easiest way to savescum is to start a brand new game. Once it is started, examine the directories in which NetHack is storing data and find one with a name similar to "save". Now save and exit the game. Examine the directory again, and see what files have appeared. Make a list of the files and the filename syntax (usually the player name with a number). Now restart the game and let the character die. Once again, examine the directory and see which files dissapeared. After doing this you should have a good idea of what files hold the game's information. | ||
| − | + | One can write scripts to speed this process up. | |
| + | |||
| + | NetHack provides no way to save a running game, as the game file is only created when you save and exit. | ||
| + | |||
| + | === On multiuser systems === | ||
| + | On multiuser [[Unix]] systems, a typical configuration installs NetHack as [[setgid]] so that users are unable to copy save files into NetHack's [[playground]]. | ||
| − | + | {{stub|Is it possible to use the [[shell escape]] to bypass this?}} | |
==See also== | ==See also== | ||
* [[Cheating]] | * [[Cheating]] | ||
| + | * Other forms of [[scumming]] | ||
[[Category:Articles]] | [[Category:Articles]] | ||
Revision as of 23:50, 30 August 2006
When playing NetHack on a local machine (ie. not on a server such as NAO), it is possible to sidestep the feature that makes the game so difficult: the permanence of death.
The concept of save scumming is simple: exit NetHack via the Shift-S save command, then copy the saved game from NetHack's playground to a different directory. Run NetHack again, and continue playing until you die. At this point, restore the saved files, copying them back from the temporary directory to the playground, and restart the game. Assuming the correct files were copied, the game continues as it was. This process is cheating, especially because the legitimate way to sidestep death is explore mode. On a few systems, though, it might be necesssary to guard against game or system crashes, because some copies of NetHack lack a working recover program.
Contents
Criticism
Experience
NetHack is designed so that death is permanent (except for the amulet of life saving, of course). This adds difficulty to the game, but also adds depth. When making a mistake might cost a week of gameplay, one thinks longer about each action, and investigates more fully the possible repercussions. It also adds excitement: taking risks with a careful cultivated character becomes more exhilarating when the stakes are higher.
Player skills
While savescumming may allow a new player to go farther in the dungeon than he or she has before, it will ultimately create a weaker player than if he or she had toughed it out. By saving and restoring games, the savescummer avoids the learning of the intricacies of NetHack, and will never learn the art of extracting him or herself from difficult positions. Death is part of the game, and a player who savescums to avoid death is not truly playing NetHack.
There are many roleplaying games that allow you to avoid death by saving and restoring your game. By savescumming, a player is missing out on the true fun of the game, at which point NetHack is hardly superior to any other RPG available.
Methodology
The methods by which NetHack saves games differ per version. Similarly, the saved games are not necessarily compatible between versions or between platforms.
The easiest way to savescum is to start a brand new game. Once it is started, examine the directories in which NetHack is storing data and find one with a name similar to "save". Now save and exit the game. Examine the directory again, and see what files have appeared. Make a list of the files and the filename syntax (usually the player name with a number). Now restart the game and let the character die. Once again, examine the directory and see which files dissapeared. After doing this you should have a good idea of what files hold the game's information.
One can write scripts to speed this process up.
NetHack provides no way to save a running game, as the game file is only created when you save and exit.
On multiuser systems
On multiuser Unix systems, a typical configuration installs NetHack as setgid so that users are unable to copy save files into NetHack's playground.
- This page is a stub. Should you wish to do so, you can contribute by expanding this page.
A user has suggested improving this page or section as follows:
"Is it possible to use the shell escape to bypass this?"
