The itty, bitty, tiny bytes that make up a Pokemon!
summary
Claim: a full Pokémon fits in 232 bytes per Pokémon, and that density is why Japan flooded PokéBank overload and delayed its global launch. Walks through exact binary→hex→encoding offsets, shows how generations remap and when encryption breaks editing, and uses a hex editor/homebrew workflow to build a Gen‑3 Squirtle, save it, and open it back up — demonstrating which fields are pointers, which are fixed‑length, how compatibility survived across four consoles, and where surprises crop up.
AI-written summary · about
chapters (4)
related talks
11mChanging a Single Byte Saves Me Seconds Every Day!
40mGame Development in Eight Bits
40mThe Old Man Glitch - Bug Escalation in Pokémon
10mEnter the Minus World! Nintendo Cartridges Share Secrets!
29mPlaying Pokemon Together With Node.js
11mEarthBound’s almost-Turing-complete text system!
11mba-ding!
36mPlayable Quotes for Game Boy Games