Pokémon Crystal Legacy
Pokémon Crystal Legacy is a Crystal ROM hack by TheSmithPlays and cRz Shadows. Its 1.3.1 patch package supports two English Crystal bases; compiling source code is not required for that route.
This page covers the inspected 1.3.1 patch package. It does not certify the newest release across every creator channel, a dated development status or save compatibility.
Checked 19 Oct 2026 against Crystal Legacy creator README.
Written by AI from the linked creator README, official patch-package instructions and our save-comparison code and our save-tool code; checked against those sources, the displayed record and built HTML, not by playing. How we check
Game facts
| Fact | Creator statement | Source |
|---|---|---|
| Creators | TheSmithPlays & cRz Shadows | README creator credits |
| System and type | Game Boy Color ROM hack | README Crystal project; package .gbc output instructions |
| Distribution | BPS patches for the player’s own matching base, not a source-only release. | Inspected 1.3.1 package instructions |
| Base choices | Crystal (USA) 1.0 or Crystal (USA, Europe) 1.1; match the corresponding patch | Two revision-specific SHA-1 requirements |
| Languages and English version | Not stated by the creator | English base requirements do not establish the game’s full language list |
Match the base revision, not just the game name
We opened the creator-owned 1.3.1 patch package in memory (521,503 bytes) and read its patching instructions. They specify two base revisions and BPS files. The table transcribes those requirements; it is not a checksum calculated from a base ROM we hold. No game was compiled, patched or played.
| Your base | Required SHA-1 | Match to |
|---|---|---|
| Crystal (USA) 1.0 | f4cd194bdee0d04ca4eac29e09b8e4e9d818c133 | The patch for base 1.0 |
| Crystal (USA, Europe) 1.1 | f2f52230b536214ef7c9924f483392993e226cfb | The patch for base 1.1 |
- Keep an untouched copy of your legally obtained base and extract the intended patch package. A ZIP or source archive is not the playable game.
- In the creator-recommended Rom Patcher JS, select your base and compare its SHA-1 with the table. Choose the patch for that base revision; 1.0 and 1.1 here identify Crystal, not the Legacy update.
- Stop on a mismatch. Do not use a previous Legacy output as the clean base or disable checksum validation. Keep the separate output named for the game, without an update number, while keeping older versions in backup folders.
Open the creator-recommended Rom Patcher JS
Our ROM checker and patcher accept GBA files, not this GBC base. Use the creator-recommended tool for this route. Matching a required hash does not prove a successful game launch, save migration or device setup.
Keep your working save before an update
Preserve the working game and its actual in-game save together before replacing either. Patching the correct base does not establish whether an older save carries over.
The reviewed explanations do not establish save migration between Legacy versions. Keep the working pair if you cannot establish the new version’s save requirements.
Open the local save comparison to check copies you already have. Files stay in your browser and are not modified.
- Make an untouched copy of your identified in-game save before changing the game, save name or emulator.
- Compare the original and backup locally, each at most 16 MiB. Leave the optional GBA size reference unset: this page does not establish GBC save layout or trailing clock data.
- If the copies match, preserve that pair separately. If they differ unexpectedly, stop and make a fresh copy from the identified original.
The comparison only checks the selected bytes. It does not locate a save, convert a state, fix a clock or prove an update accepts progress. No Crystal Legacy save transfer, game or handheld has been tested here.
For the game’s own explanations, read Crystal Legacy creator README. We do not host game packages or link package pages and file hosts.