# A save file made of handwriting, not a chip

> Before save batteries, progress was a string of characters copied by hand onto whatever paper was nearest, and one wrong letter cost the run.

August 21, 2026 · https://justog.club/stories/the-password-on-the-back-of-an-envelope

A password, copied out in ballpoint, four blocks of four: `7JKM 4NQT W2XZ D9BB`. One character in
the third block is circled, its correction written small above the line in a redder ink. Below the
whole string, one word in that same red: `again`.

The envelope it's written on was torn open for something else entirely. It was just the nearest paper.

## Why was progress ever a string of characters?

Because there was nowhere on the machine to keep it.

Before a battery could hold a save inside the cartridge, the only durable record of where you'd
got to was one the game could generate and a person could read back in: a code that encoded a
level, a score, an inventory, sometimes just a number of lives. Type it in at the start and the
machine reconstructed the state from it. The paper was the storage.

That's a genuinely strange thing to ask of a stranger — memorise or transcribe sixteen characters
correctly, with no formatting help beyond spacing.

## Why is the circled correction the whole point?

Because it's the entire failure mode of the system, caught in one mark.

A save file on a chip either matches or it doesn't; there's no visible moment where it almost
matched. A handwritten password has one, right there — a character copied wrong, noticed later,
fixed in a different pen because the first pass is over and this is a correction to the record, not
part of it. That circle is the only physical trace a save-corruption bug ever leaves.

`again` under it is the rest of the story: whatever ran before the correction, it failed, and
somebody sat back down and copied the string a second time.

## Why four blocks of four, and why so easy to get wrong?

The spacing is a memory aid; the wide alphabet is the risk.

The game only required sixteen characters in order — the gaps are something the person copying it
added, the way anyone reads a long number back by breaking it into fours. But a wider character set
packs more state into fewer characters, and that's where the trouble starts: a zero and an O, a one
and a capital I, look identical in most handwriting and identical again in most typefaces. The
system that made the code shorter is the same one that made it easier to lose.

## Can I print an actual password from a real game?

The string itself isn't the obstacle — the game it belongs to is.

A password is a functional output, generated by an algorithm, the same category as a phone number
or a postal code: that alone isn't the kind of thing copyright reaches. What attaches is the game
it's known to unlock — a recognisable code from a well-known title reads as merchandise for that
title, and that's a permission question, not a design one. An invented string sidesteps it
entirely and costs the design nothing, because the string was never the interesting part — the
same case
[a fifth-generation copy of an instruction page](/stories/the-guide-photocopied-five-times)
makes about the words on it.

## Does this work for something other than a game code?

Anything that was ever copied by hand under pressure, at a bad hour, onto whatever was near.

A wifi password on a card that's been handed around a house for years. A recipe measurement
corrected mid-write. A phone number taken down without a pen ready, patched with a different ink
once a proper one turned up. The format is the correction, not the specific string — what matters
is that it's real handwriting, on real paper, with a real mistake left visible.

## Isn't this just sixteen random letters on a shirt?

It's sixteen letters with a correction and a torn edge, which is a different object entirely.

Random characters alone read as noise. What makes this legible as a story is everything around the
string: the envelope stock, the circle, the second ink, the single word underneath. Strip any one
of those and it stops being a password on the back of an envelope and becomes a password.

## Does it print well?

Yes, with the correction kept as a second colour, not folded into the first.

Ballpoint on paper has enough tonal variation to reproduce cleanly at print size, and the torn edge
of the envelope should stay ragged rather than being squared off — it's the detail that says this
paper wasn't chosen, it was grabbed. The circle and the red correction need their own ink; if they
print in the same black as the rest, the whole point disappears.

Cream or unbleached stock with black ballpoint and one red accent. Two inks.

## How do I get one made?

Describe the string at [JustOG](/) — how many blocks, where the correction sits, what the second
word says. Pick a direction, drag the crop frame, see it composited on the real garment, and it's
made to order and shipped.

Designs other people have published are in the [shop](/shop).

The rest of the game — like
[the level a run stopped at](/stories/the-level-that-stopped-everyone) or
[the sequences that broke it on purpose](/stories/cheat-code-page) — travelled the same way:
by hand, on paper, imperfectly.

Whatever came after `again` worked, or there'd be a third ink.