How 128 KB Contra Managed a Long Storyline on the NES

1. Data‑size intuition

People often cannot estimate how many bytes a piece of data occupies. An 800‑character essay is about 1.6 KB in GBK encoding and 2.4 KB in UTF‑8. A one‑character Word document occupies roughly 10 KB because of file‑system overhead (metadata and block allocation). These examples show that storage formats add hidden bytes.

2. FC‑era graphics techniques

The Nintendo Entertainment System (NES/FC) has a resolution of 256 × 240 px but only 2 KB of video RAM, yet it must render full‑screen scrolling. The hardware supplies a tile‑based system: each screen is built from a limited set of reusable tiles. By storing a tile library once and referencing tiles to compose many screens, the required storage drops dramatically.

3. Audio and code size

Modern audio formats store raw waveforms, consuming kilobytes to megabytes per track. The FC uses the Ricoh 2A03 audio chip, which synthesizes sound. Music is stored as a sequence of notes, each note recording timbre, frequency, and pitch. A typical background melody therefore requires only a few bytes per note, and because most game music loops, the total size is tiny.

The NES hardware also provides built‑in support for tiles, palettes, and audio, effectively acting as the engine layer. Programmers therefore write minimal assembly code, studying the hardware documentation to avoid unnecessary routines. This results in very small code footprints.

4. Result

With 128 KB of ROM, a game can contain a rich storyline, graphics, and music that would be considered extraordinary on modern platforms.

Code example

备注“
gpt
”开通