FLYGAME / PLAYER & ENGINEERING REFERENCE
The Cartridge Glossary — Game Boy Terms Explained
THE CARTRIDGE GLOSSARY · A beginner's translation guide for FlyGame's engineering stories · November 15, 2026
You don't need to be a programmer to follow FlyGame's development. These terms explain why a small cartridge can contain a surprisingly complex world—and why a passing compile is not quite the same thing as a successful adventure.
The hardware
- DMG: the original monochrome Game Boy hardware family. FlyGame's primary platform target.
- GBDK 2020: the open-source development toolchain used to compile the C-based game and supporting code for Game Boy.
- 160×144: the Game Boy's display resolution in pixels; a reason art and readability are designed at native scale.
- ROM: the cartridge's stored program, maps, graphics and data. It remains available without power.
- ROM0: the fixed 16 KiB ROM area (address 0x0000–0x3FFF) that is always mapped. Critical startup and core functions must fit there.
- ROMX / bank switching: the cartridge maps different ROM data banks into the switchable window so a much larger world can exist than fits in one address window.
- WRAM: working RAM used while the game runs; much smaller than the modern computers that build FlyGame.
- VRAM: video memory for the tiles and backgrounds shown on the screen.
- OAM: the Game Boy's object attribute memory for positioned hardware sprites.
- SRAM / battery save: cartridge RAM intended to preserve game progress while power is off. The emulator must use the correct private save location during destructive tests.
How the world is assembled
- Tile: a small pixel graphic unit. Background scenes are constructed from reused tiles rather than full-screen images.
- 16×16 chunk: an authored unit in FlyGame's streamed-world tooling. Larger locations can consist of multiple chunks.
- Streaming: moving only the nearby world data into active display/map buffers as a player travels.
- Indoor floor / room: an authored scene cataloged separately from the outdoor streamed environment, with its own room identity and transitions.
- Persistence flag: a compact bit recording something that should remain true, such as a solved puzzle or claimed unique reward.
- Generated content: data produced by tooling from authored designs, such as room registries, object graphics and weather-response tables.
What our evidence labels mean
- Static test: checks source, generated data or deterministic models without running an actual cartridge game.
- Object compile: a compiler successfully produces code for a source unit; this can reveal memory-layout changes without proving full gameplay.
- Full ROM link: all parts combine into a cartridge image. It does not establish that every route runs correctly.
- ROM hash: a fingerprint that identifies a particular output cartridge. Two builds with different hashes may behave differently.
- NOI file: debugger symbols for the built ROM; useful for identifying program memory and routine locations.
- Mesen: a multi-system emulator/debugger used for FlyGame development validation, including source-matched Game Boy runtime tests.
- Loaded-ROM identity: proof that the emulator is actually executing the intended ROM rather than a stale debug build.
- Ordinary gameplay pass: the intended player-controlled sequence was observed in an identified, isolated ROM session—not merely simulated in a script or reached by debug warp.
- BASELINE-PS1: the project's named first playable-slice acceptance goal, still pending full verification in the current source snapshot.
Keep exploring
See Engineering Bench for accessible deep dives, The Great Temple for a tangible example of streamed rooms and persistent states, and Questions & Answers for quick answers.
Editorial note: explanations simplify the technical language while staying faithful to the project’s current GBDK, indoor runtime and save-system sources; they are not a hardware specification.