gearboy-romhacking

name	gearboy-romhacking
description	Hack, modify, and translate Game Boy / Game Boy Color ROMs using the Gearboy emulator MCP server. Provides workflows for memory searching, value discovery, cheat creation, data modification, sprite/text finding, and translation patching. Use when the user wants to create cheats, find game values in memory, modify ROM data, translate a Game Boy game, patch game behavior, create ROM hacks, discover hidden content, change sprites or graphics, find text strings, apply Game Genie or GameShark codes, do infinite lives or health hacks, search for score or item counters, or reverse engineer data structures in Game Boy or Game Boy Color games. Also use for any ROM hacking, memory poking, or game modification task involving Gearboy.
compatibility	Requires the Gearboy MCP server. Direct tool mode is the default. Before installing or configuring, call debug_get_status to check if the server is already connected. If --mcp-router is enabled, use get_tool_info and execute_tool for routed tools.
metadata	{"author":"drhelius","version":"1.0"}

Game Boy / Game Boy Color ROM Hacking with Gearboy

Overview

Hack, modify, and translate Game Boy and Game Boy Color ROMs using the Gearboy emulator as an MCP server. Search memory for game variables, create cheats, find text strings for translation, locate sprite data, and reverse engineer data structures — all through MCP tool calls. Use save states as checkpoints and fast forward to reach specific game states.

MCP Server Prerequisite

IMPORTANT — Check before installing: Before attempting any installation or configuration, you MUST first verify if the Gearboy MCP server is already connected in your current session. In the default mode, call debug_get_status directly. If Gearboy was intentionally started with --mcp-router, call get_tool_info with {"name":"debug_get_status"}, then call execute_tool with {"name":"debug_get_status","arguments":{}}. A valid response from either workflow means the server is active and ready.

Only if neither workflow is available or the call fails, you need to help install and configure the Gearboy MCP server:

Installing Gearboy

Run the bundled install script (macOS/Linux):

bash scripts/install.sh

This installs Gearboy via Homebrew on macOS or downloads the latest release on Linux. It prints the binary path on completion. You can also set INSTALL_DIR to control where the binary goes (default: ~/.local/bin).

Alternatively, download from GitHub Releases or install with brew install --cask drhelius/geardome/gearboy on macOS.

Connecting as MCP Server

Configure your AI client to run Gearboy as an MCP server via STDIO transport. Example for Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json):

{
  "mcpServers": {
    "gearboy": {
      "command": "/path/to/gearboy",
      "args": ["--mcp-stdio"]
    }
  }
}

Replace /path/to/gearboy with the actual binary path from the install script. Add --headless before --mcp-stdio on headless machines.

---

Core Technique: Memory Search

Memory search is the primary tool for ROM hacking. It uses a capture → change → compare cycle to isolate memory addresses holding game values.

The Search Loop

1. memory_search_capture    → snapshot current memory state
2. (change the value in-game using controller_button, fast forward, etc.)
3. memory_search            → compare against snapshot to find changed addresses
4. Repeat 2-3 until only a few candidates remain
5. read_memory / write_memory → verify and modify the found addresses

Search Operators and Types

memory_search supports these operators: <, >, ==, !=, <=, >=

Compare types:

• previous — compare current value to last captured snapshot (most common)
• value — compare current value to a specific number
• address — compare current value to value at another address

Data types: hex, signed, unsigned

Example: Finding the Lives Counter

1. memory_search_capture                         → snapshot with 3 lives
2. Lose a life in-game (play or use controller_button)
3. memory_search (operator: <, compare: previous) → values that decreased
4. memory_search_capture                         → snapshot with 2 lives
5. Lose another life
6. memory_search (operator: <, compare: previous) → narrow further
7. Or use: memory_search (operator: ==, compare: value, value: 1)
   → find addresses holding exactly 1
8. write_memory on the candidate address to set lives to 99
9. get_screenshot to verify the change took effect

Example: Finding a Score Counter

Score values are often stored as multi-byte (16-bit little-endian on SM83) or BCD-encoded:

1. memory_search_capture                                → snapshot at score 0
2. Score some points in-game
3. memory_search (operator: >, compare: previous)       → values that increased
4. memory_search_capture
5. Score more points
6. memory_search (operator: >, compare: previous)       → narrow down
7. read_memory on candidates — look for values matching current score
8. write_memory to set a custom score

Many Game Boy games store scores as BCD (Binary-Coded Decimal) — each nibble holds a digit 0-9. For example, score 1234 might be stored as bytes $12 $34.

---

Fast Forward for Efficiency

Use fast forward to speed through gameplay when you need to trigger in-game changes:

set_fast_forward_speed (4 = unlimited)
toggle_fast_forward              → enable
(play through the game section)
toggle_fast_forward              → disable

This is essential when you need to reach specific game states without waiting in real-time.

---

Save States as Checkpoints

Save states are critical for ROM hacking — they let you save your position and retry modifications:

select_save_state_slot (1-5)     → pick a slot
save_state                       → save current state
(try modifications)
load_state                       → revert if something breaks

Use different slots for different game states (e.g., slot 1 = start, slot 2 = boss fight, slot 3 = specific level).

list_save_state_slots shows all slots with ROM name, timestamp, and validity.

Rewind as an Alternative

The emulator also records continuous snapshots into a rewind ring buffer. Use get_rewind_status to check availability, then rewind_seek to jump to any recorded point without manual save/load. This is especially useful for quickly reverting after a failed memory write — pause, seek back a few snapshots, and retry.

---

Finding and Modifying Game Data

Text and String Discovery

To find text strings for translation or modification:

1. Determine the character encoding — many Game Boy games use custom character maps, not ASCII
2. read_memory across ROM banks (ROM0, ROM1) scanning for known byte patterns
3. Use memory_find_bytes to search for specific byte sequences across memory
4. Set read breakpoints on suspected text addresses with set_breakpoint (type: read) to confirm they're used for rendering
5. get_screenshot to correlate displayed text with memory contents

Sprite and Graphics Data

1. list_sprites to see all 40 OAM sprite entries (position, tile, attributes)
2. get_sprite_image to render individual sprites as PNG
3. read_memory on VRAM ($8000-$9FFF) to inspect raw tile data
4. get_lcd_registers to check LCDC (tile data area, tile map area, sprite size)
5. Set read breakpoints on tile data addresses to find the rendering code
6. get_screenshot before/after modifications to see visual changes

Tile Maps and Backgrounds

1. read_memory on VRAM tile map areas ($9800-$9BFF or $9C00-$9FFF depending on LCDC)
2. get_lcd_registers to check SCX/SCY (scroll), WX/WY (window position)
3. Cross-reference tile map entries with tile data to understand the display layout

Data Tables and Structures

1. debug_pause → get_disassembly around code that loads data
2. Look for LD instructions with absolute or indexed addressing — these point to data tables
3. read_memory at the target addresses to dump the table contents
4. add_memory_bookmark to mark discovered data regions
5. add_symbol to label data table entry points for future reference

---

Creating Cheats

Infinite Lives / Health

1. Find the address using the search loop (above)
2. Set a write breakpoint: set_breakpoint (type: write) on the address
3. debug_continue → when it hits, get_disassembly to see the decrement code
4. Note the instruction (e.g., DEC [HL] or LD [addr], A)
5. Option A: Periodically write_memory to reset the value (simple poke cheat)
6. Option B: Identify the decrement routine for a NOP patch

Game Genie / GameShark

Gearboy has built-in Game Genie and GameShark cheat support. Use the memory search workflow to discover addresses and values, then convert them to cheat codes:

• Game Genie (ROM patches): format encodes a ROM address and replacement value
• GameShark (RAM patches): format encodes a RAM address and value to continuously write

Watching Values in Real-Time

Use add_memory_watch on discovered addresses. Watches appear in the emulator's GUI memory editor, letting you monitor values as the game runs — useful for verifying cheats work across different game situations.

Write Breakpoint Technique

The most powerful cheat-finding technique:

1. Find the variable address via memory search
2. set_breakpoint (type: write) on that address
3. debug_continue — the emulator stops when the game writes to that address
4. get_cpu_status + get_disassembly reveals the exact code modifying the value
5. get_call_stack shows what triggered the write
6. You now know exactly where and how the game manages that variable

---

Translation Workflow

1. Identify the Font System

1. get_screenshot of a screen with text
2. read_memory on VRAM to find tile data used for font characters
3. Find text rendering code by setting read breakpoints on tile map areas
4. Trace back to find the character mapping table
5. add_symbol to label the font table and rendering routine

2. Find String Data

1. Look for sequential text bytes in ROM banks using read_memory with large ranges on ROM0 and ROM1
2. Use memory_find_bytes to search for known byte patterns
3. Cross-reference with the character table to decode strings
4. add_memory_bookmark to mark each string location

3. Measure Space Constraints

ROM hacking translations must fit within existing space:

1. read_memory to determine how much space each string occupies
2. Check for string terminators (commonly $00, $FF, or length-prefixed)
3. If the translation is longer, look for unused ROM space or abbreviate

4. Apply and Test

1. write_memory to patch translated strings into memory
2. get_screenshot to verify rendering
3. save_state before each change so you can load_state if it breaks
4. Test all screens that display modified text

---

Memory Map Quick Reference

Use list_memory_areas to get the full list:

Area	CPU Address	Use
ROM0	$0000-$3FFF	Fixed ROM bank, interrupt vectors, header
ROM1	$4000-$7FFF	Switchable ROM bank (MBC-dependent)
VRAM	$8000-$9FFF	Tile data, tile maps, CGB has 2 banks
RAM	$A000-$BFFF	Cartridge external RAM (battery-backed saves)
WRAM0	$C000-$CFFF	Work RAM bank 0
WRAM1	$D000-$DFFF	Work RAM bank 1-7 on CGB
OAM	$FE00-$FE9F	Sprite attribute table (40 sprites × 4 bytes)
IO	$FF00-$FF7F	Hardware I/O registers
HIRAM	$FF80-$FFFE	High RAM (fast, used for DMA routine, variables)

When SGB mode is active, additional areas are available:

Area	Description
SGB_TILES	Border tile patterns (8192 bytes)
SGB_MAP	Border tilemap 32×32 (2048 bytes)
SGB_BPAL	Border palettes 4×16 colors (128 bytes)
SGB_SPAL	System palettes 512×4 colors (4096 bytes)
SGB_ATF	Attribute files 45×90 bytes (4050 bytes)
SGB_AMAP	Attribute map 20×18 (360 bytes)
SGB_EPAL	Effective palettes 4×4 colors (32 bytes)

WRAM and HIRAM are the most common locations for game variables (lives, health, score, position).

---

Bookmarks and Organization

Keep your hacking session organized:

• add_memory_bookmark — mark discovered data regions, variable locations, string tables
• add_memory_watch — track values that change during gameplay
• add_symbol — label addresses in disassembly for readability
• add_disassembler_bookmark — mark code routines you've identified

Use list_memory_bookmarks, list_memory_watches, list_symbols, list_disassembler_bookmarks to review.

---

Persisting Changes

Changes made via write_memory to ROM areas are applied to the emulator's in-memory copy only — they are not persisted to the ROM file on disk. To create a permanent patch, use command-line tools (e.g., a binary patch script) to apply the discovered modifications to the actual ROM file.