Password Systems
Save without battery
Password systems encoded game progress into alphanumeric strings, allowing players to resume without expensive battery-backed save RAM in their cartridges.
Overview
Write it down. Password systems encoded player progress — level reached, items collected, stats gained — into strings of letters, numbers, or visual symbols. No battery backup needed in the cartridge, but players managed notebooks full of codes. Some systems were elegant (Mega Man’s 5×5 dot grid), others tedious (long alphanumeric sequences with confusable letters). All served the same purpose: persist progress without the per-cartridge cost of battery-backed SRAM.
Fast facts
- Purpose: Save progress without battery RAM.
- Method: Encode game state as a string or symbol grid.
- Cost benefit: A few cents per cartridge cheaper than battery-backed SRAM.
- Player burden: Must transcribe and re-enter codes correctly.
- Era: Mid-1980s through mid-1990s; declined as battery prices fell.
How passwords encode data
The password is a serialised game state. Designers choose:
| Data type | Encoding |
|---|---|
| Level number | Few bits (4-6) |
| Items collected | Bit flags (one bit per inventory slot) |
| Stats (HP, weapons, scores) | Numeric encoding (8-16 bits each) |
| Position / world state | Bit-packed |
| Checksum | 4-8 bits to catch typos |
The total state — say 60-100 bits for a typical NES game — is then encoded into a printable character set:
- Base-32 (5 bits per character) — most common; uses A-Z and digits 2-7 to avoid confusables.
- Base-64 (6 bits per character) — denser, but uses lower-case + symbols, more error-prone.
- Symbol grids — specific to games like Mega Man, where 25 dot positions = 25 bits of state.
A 60-bit state: 12 base-32 characters, or 10 base-64 characters, or one 5×5 grid. Designers picked based on the data shape and what felt natural to enter.
Famous password systems
| Game | Format | Length | Notes |
|---|---|---|---|
| Metroid (1986) | 24 alphanumeric characters in 4 rows of 6 | 24 chars | Iconic; JUSTIN BAILEY exposes Samus armourless; NARPAS SWORD enables debug invincibility |
| Mega Man 2-6 | 5×5 dot grid (positions A-E across × 1-5 down) | 6 grid coordinates | Visual-spatial; no character entry |
| Kid Icarus (1986) | 24 alphanumeric characters | 24 chars | Same engine family as Metroid |
| Castlevania II: Simon’s Quest (1987) | 16 alphanumeric characters | 16 chars | Used letter-only set |
| Blaster Master (1988) | 16-character codes | 16 chars | |
| Phantasy Star Online (2000) | “Magic Item Codes” | 13-char codes | Late example; password-style codes for collectibles |
| Fire Emblem: Sacred Stones (2004) | Link Arena codes | Long codes | One of the last commercial uses |
Mega Man’s grid
Mega Man’s password is a 5×5 dot grid, with letters A-E across the top and 1-5 down the side. A “password” is a list of grid positions like B5, A3, C1, E2, D4. This was a deliberate design choice:
- Easier to copy — visual pattern recognition rather than character-by-character spelling.
- Less error-prone — no confusable letters/numbers.
- Compact — 5×5 grid = 25 bits (one bit per dot position) = enough state for level + bosses defeated + weapons.
- Genre-specific — Capcom’s UI design choice that became a series trademark.
Cheat codes
Password systems gave rise to the concept of cheat codes — passwords that decoded to game states never reachable in normal play:
| Game | Code | Effect |
|---|---|---|
| Metroid | JUSTIN BAILEY |
Samus without suit, armed |
| Metroid | NARPAS SWORD |
Debug mode, invincible, max equipment |
| Mega Man 2 | A1, B2, C3, D4, E5 |
All weapons (specific to that game) |
| Castlevania II | (Various trinity codes) | Skip to specific castle |
The cheat-code culture of the 1980s-90s grew directly from password systems — once players realised the format was a serialisation of state, they started experimenting with arbitrary inputs.
Design considerations
Length vs convenience
Longer passwords store more state but become tedious. Designers balance:
| Choice | Trade-off |
|---|---|
| Short passwords (8-12 chars) | Easy to write down, limited state |
| Medium (16-24 chars) | The mainstream sweet spot |
| Long (32+ chars) | Used when battery-save was rejected on cost |
Character set
| Approach | Trade-off |
|---|---|
| Alphanumeric (A-Z, 0-9) | Universal, human-readable |
| Exclude confusables (no O/0, I/1, S/5) | Slightly longer code, much fewer typos |
| Case-sensitive | Twice the alphabet, half the length, 4× the typos |
| Symbol grids | Best UX for fixed-length state, requires custom UI |
Most successful password games use 32-character “no confusable” alphabets — typically ABCDEFGHJKLMNPQRSTUVWXYZ23456789 (no O, I, 0, 1).
Checksums
Without a checksum, a single typo produces a valid-looking invalid password. Players might play through with corrupted state. Most password systems include 4-8 checksum bits to reject invalid codes immediately.
Anti-exploitation
Players reverse-engineering password formats can craft “impossible” states (max stats from level 1, locked items revealed, etc.). Some games add validation: the password must be reachable from a known starting state, or specific bit patterns are forbidden. Most don’t bother — exploiting passwords is part of the appeal.
Password vs battery backup
| Aspect | Password | Battery |
|---|---|---|
| Cartridge cost | Free | Battery + SRAM chip + circuitry |
| Convenience | Manual transcription | Automatic |
| Reliability | Always works (on paper) | Battery dies eventually |
| Shareability | Codes shared with friends, magazines | Cannot be shared |
| Cheat-code potential | High — codes reveal the system | Low — savefile is opaque |
| Lifetime | Permanent | 10-25 years |
Both coexisted through the late 80s and early 90s. Larger games (Final Fantasy, Zelda) needed batteries; smaller games (Mega Man 2, Castlevania III) used passwords. Some games used both — Game Boy Pokémon uses battery save, while the Game Boy Color Pokémon Pinball uses password-only save for some modes.
Player experience
| Pro | Con |
|---|---|
| No battery failure | Must transcribe every save |
| Shareable progress | Long sequences error-prone |
| Cheat codes possible | Confusable characters cause mistakes |
| Save your friend’s progress | Notebook required |
| Permanent record | Lose the notebook, lose all progress |
The “lost the password notebook” experience is its own genre of gaming nostalgia — most NES-generation gamers can recall a specific lost-progress moment.
Modern legacy
Password systems persist in modified form:
- Daily challenge codes in modern games (Spelunky, Wordle) — short codes encoding a seed.
- Streetpass / Spotpass on Nintendo handhelds — passive code exchange replacing manual passwords.
- Game-share codes (Animal Crossing island codes, Minecraft world seeds) — designed-in shareability of game state.
- Cheat codes survive in nearly every modern game with developer-mode access; the Metroid / NARPAS SWORD tradition is alive and well.