Password Continuation
Password continuation encodes a player's progress as a string of characters they write down, letting a game remember its state without any storage hardware inside the cartridge.
State is packed into a bit field, obscured, and printed as letters and numbers; typing it back reconstructs the game's variables. Length of the password is a direct measure of how much the game remembers, and designers economise by discarding details such as exact position or partial inventory. Since the code is data, invented or mistyped passwords sometimes produce valid but unintended states, which players quickly turned into a hobby.
Nintendo R&D1 used the technique in Metroid in 1986 for a game far too long to finish in one sitting, on a cartridge with no memory to spare for saving. Passwords cost nothing but a little ROM and some arithmetic. Trade-off was accepted across the era, because the alternative was either an unreasonably short game or a battery, which added expense to every cartridge manufactured.
Portable state made long-form console games viable a generation before saving became standard, and it created an accidental culture: codes shared in magazines, traded in playgrounds, and discovered to unlock debug conditions their authors never advertised. Friction was the cost, since a transcription error erases an evening and nothing carries over that the designer chose not to encode. Batteries retired the format quickly once they became affordable.
Lineage — traced back to a root
Every mechanic in this dataset resolves to an ancestral chain. This one is 3 steps deep, beginning with Numeric Score in 1972.
Descends directly from
Forked into
Kid Icarus became notorious for the strings players discovered, Dragon Quest presented them as spoken spell words, and Mega Man 2 reduced them to a grid of dots.
Carried forward by 5 later games
Everything downstream
2 mechanics ultimately descend from this one.
Look this mechanic up elsewhere
Also called: passwords, continue codes, password save