generally erased or overwritten, preventing players from restarting at that same state. They work around this by backing up save files, but this tactic, called "save scumming", is considered cheating. The use of the permadeath mechanic in roguelikes arose from the namesake of the genre, Rogue. The developers initially did not implement save capabilities, requiring players to finish the game in one session. When they added a save feature, they found that players would repeatedly reload a save file to obtain the best results, which was contrary to the game design—they "wanted [realism]"—so they implemented code to delete the save file on reloading. This feature is retained in nearly all derivatives of Rogue and other games more loosely inspired by its gameplay. Implementations of permadeath may vary widely. Casual forms of permanent death may allow players to retain money or items while introducing repercussions for failure, reducing the frustration associated with permanent death. More hardcore implementations delete all progress made. In some games, permadeath is an optional mode or feature of higher difficulty levels. Extreme forms may further punish players, such as The Castle Doctrine, which has the option of permanently banning users from servers upon death. Players may prefer to play games with permadeath for the excitement, the desire to test their skill or understanding of the game's mechanics, or out of boredom with standard game design. When their actions have repercussions, they must make more strategic and tactical decisions. At the same time, games using permadeath may encourage players to rely on emotional, intuitive or other non-deductive decision-making as they attempt, with less information, to minimize the risk to characters which they have bonded with. Games using permadeath more closely simulate real life, though games with a strong narrative element frequently avoid permadeath. Permadeath of individual characters can be a factor in party-based tactical role-playing games. In these games, the player generally manages a roster of characters and controls their actions in turn-based battles while building their attributes, skills, and specializations over time. If these characters fall in combat, the character is considered dead for the remainder of the game. It is possible to return to a previous save game state in these games before the death of the character, but require the player to repeat the battle to continue, risking the loss of the same or other characters. Square's 1986 fantasy shoot 'em up game King's Knight