Toolkit

Emulators

Everything you need to run your patched adventures on any device.

Choose by game format first

An emulator recreates a console environment; it does not turn every fan game into a console game. A GBA release needs GBA support, while a standalone desktop game uses its own application and installation instructions. A ZIP archive is only a container. Read the release notes to identify what is inside before choosing software.

For patch releases, apply the patch to the exact base-game revision specified by the creator before opening the result in your emulator. A patch file is not itself a playable game. Obtain required game files lawfully; the emulator projects below do not grant distribution rights to commercial games.

Official projects and documentation

mGBA

A Game Boy Advance emulator with desktop builds. Start with the official download page and select the build for your operating system. Check a hack's release notes for emulator-specific requirements; GBA support does not guarantee compatibility with every modification.

mGBA official website and downloads

Delta

For players considering Delta on Apple mobile devices, use the official user guide to check supported systems, installation options and importing games. Availability can depend on your device and region. Read the save-management instructions before moving an existing playthrough.

Delta official user guide

These are project documentation links, not mirrors or paid placements. This guide does not claim that PokéSmith has tested every hack on these emulators.

A first-session checklist

  1. Record the game release version, emulator version and creator-recommended settings. Begin with cheats disabled so you have a clean baseline.
  2. Reach a save point, make an in-game save, close the game normally and reopen it. Confirm that progress loads before investing hours.
  3. Find the save export or backup function. Keep a separate copy labelled with the game version. An emulator save state is not a substitute for an in-game save when migrating between releases.
  4. Change one setting at a time when troubleshooting. Test ordinary speed before fast-forward, shaders or other optional features so you can identify which change affects the result.

If the game will not start

First distinguish a patching problem from an emulator problem. Recheck the patch format, required base revision and checksum if provided. Do not stack patches unless the release explicitly requires it. If a cleanly patched game still fails, consult the project's known-issues notes and emulator recommendations.

For a useful bug report, include the exact game and emulator versions, device, steps that reproduce the issue and whether it occurs with cheats disabled. Share the error message and relevant settings; do not attach commercial ROM files. For missing saves, check the import instructions and filename association before overwriting files.

First time patching?

Start with a clean base game

Grab an emulator, apply a patch to your own copy, and you are playing in minutes.