Battery-Backed Save File
Battery-backed saving puts a small amount of powered memory inside the cartridge so a game can record its own state, allowing play to be suspended and resumed at will.
Cartridge carries RAM and a coin cell that keeps it alive when the console is off, plus logic to write and verify a save file. Because the game controls what is written, it can store far more than a password could carry, including world flags, inventories, positions and multiple slots. Fragility is physical: batteries expire after years, and a dead cell erases a file that exists nowhere else.
Nintendo R&D4 shipped The Legend of Zelda in 1986 with battery memory, in a game explicitly designed around exploring a large world across many sessions. Hardware cost was the obstacle, since a battery raises the price of every cartridge, and the decision only makes sense for a game whose length is the point. Multiple save slots also made the console a shared household object rather than a personal one.
Saving invented the campaign as we now understand it: stories that unfold over dozens of hours, worlds that remember, and progress belonging to a player rather than to a session. It also created a class of design problems games still argue about, including where saving is allowed, whether it can be used to undo mistakes, and what it means when a game deliberately withholds or manipulates the file.
Lineage — traced back to a root
Every mechanic in this dataset resolves to an ancestral chain. This one is 4 steps deep, beginning with Numeric Score in 1972.
Descends directly from
Forked into
Final Fantasy used it for long party campaigns, Pokémon Red and Blue tied a single file to trading, and Animal Crossing made the save a place that keeps running.
Carried forward by 28 later games
Look this mechanic up elsewhere
Also called: save file, cartridge save, battery save