
6.S185
Retro Game Development:
Making Games for the Game Boy
this is a class running in IAP 2027, about making homebrew games for the Nintendo Game Boy handheld game console (the original one, from 1989). the focus of the class will be a mix of Game-Boy-specific stuff, and game design more generally. we'll explore these things by making a few small games from the ground up in SM83 assembly, which will be playable in Game Boy emulators or on the Game Boy itself.
everyone who finishes the class will leave with a cartridge containing one of their games, playable on original hardware.
prerequisites
this class is mainly aimed at students with a decent programming background but who have never programmed for the Game Boy before, though you're certainly welcome even if you do have prior retro game development experience.
-
programming background: you'll probably need either 6.190 or
6.101, and i'd strongly recommend having both (or
substantial other programming experience). the more programming
background you have, the easier the process is going to be.
- 6.190 is good because we're going to be writing assembly. while the assembly we'll be writing here is a different flavor to what you saw in 6.190, prior exposure to that kind of low-level thinking is still going to be really useful. i'm also not going to spend too much time on, like, binary representations of numbers and stuff like that; i'll assume you've seen it before.
- 6.101 is good because without a fair amount of prior programming experience, i think you're likely to have a difficult time. even though writing assembly is quite different from writing Python, many of the ideas from 6.101 about organizing code, good style, good choice of data structures, etc, are just as relevant in assembly as they are in Python (maybe even moreso).
- time: we're going to try to do a lot of stuff in a short amount of time, so you should plan on spending time in the lab. if you're also doing like a big competition class or something, maybe it isn't a good idea also to try to do this. i'm also going to strongly recommend coming to lab and working with me and with your classmates, rather than working alone in your dorm room; your physical presence on campus is a must.
-
hardware: you do not need to own a Game Boy (most of our
testing will be done in an emulator, and i'll bring several consoles
to lab for testing as well). that said, if you think it's cool to have
your own, you can find them on eBay or other second-hand stores
(though they are unfortunately quite pricey if they're in working
order, something like $50-$150 depending on the variant you want and
the condition it's in). the games we make in class should work fine
on any of these consoles:
- Game Boy (DMG-01)
- Game Boy Pocket (MGB-001)
- Game Boy Light (MGB-101)
- Game Boy Color (CGB-001)
- Game Boy Advance (AGB-001)
- Game Boy Advance SP (AGS-001 or AGS-101)
there are also modern FPGA-based Game Boy clones like the Game Bub (which is open source!), or the FunnyPlaying FPGBC or the Analogue Pocket or the ModRetro Chromatic; i won't be testing any of those, but i expect all of our games will work with them as well.
textbook / reference
we'll make heavy use of the following fantastic resources from the folks in the Game Boy Development Community:
- the RGBDS documentation will be our reference for the specific flavor of assembly we'll be writing.
- the Pan Docs will be our reference for details of the Game Boy's interfaces, inner workings, and quirks.
everything else you need will be provided in class or through this website.
software
we're going to use the following tools, all of which are Free/Libre Software:
- RGBDS (version 1.0.x)
- an accurate emulator with debugging support, such as Mesen
- a POSIX-compliant shell (e.g., GNU Bash)
- Python (any recent version will work)
- Git
these tools should all be readily available on GNU/Linux and Mac; if you're running on Windows, your best bet is probably using WSL.
open hardware
the cartridge pcb distributed at the end of the class (available under a CC-BY-SA license) was made in KiCad, with thanks to Jay van Hutten for providing the outline and edge connector in this template. you can download the source here: cartridge_pcb.zip
the plastic shells for the cartridges (also available under CC-BY-SA) are a very slight modification of a design by Dave Parker, edited in OpenSCAD to remove geometry that would otherwise obscure the silkscreen image on the pcb. you can download the source code here: cartridge_shell.scad
the cartridge was designed to be re-flashable using software like FlashGBX, so it should be easy to update it if you continue working on your games after iap ends. i've only tested these cartridges with the GBxCart RW, but i expect they would work with other flashers as well. note, though, that it only supports cartridge type 0 (32kB ROM only, no MBC).
ai policy

this class is intended for humans. i don't care at all if claude can make a Game Boy game; i want to help you learn to make them. making games, especially on such a constrained platform, is both a fun technical challenge and a fantastic outlet for creative expression; i hope for you to be able to take pride in developing a deep understanding of a system, and in using that understanding to build something that is uniquely yours, essentially from scratch.
even if we were to ignore the ethical, legal, societal, environmental, economic, political, educational, and humanitarian concerns raised by generative ai and pretend like llms and the like are just neutral tools with no downsides, they still wouldn't be a fit here, since using them would undercut all of the goals of the class. as such, using generative ai is not allowed for any part of the class (including code, graphics, audio, documentation, debugging, optimization, brainstorming game ideas, etc.). this includes advanced code-completion tools like copilot, not just llm's.
contact
if you're interested in taking the class or have questions about it, feel free to drop me a line: hz@mit.edu.