Load Pokémon cheats for the right game

Prepare the file and expose the menu

1. Use the Libretro database named by Onion as its recommended cheat-file source. Inspect the relevant console folder under cht.
2. Copy the relevant files to RetroArch/.retroarch/cheats on your SD card. Show hidden folders if .retroarch is missing from the file manager.
3. Back up RetroArch/.retroarch/retroarch.cfg before editing. Onion says to set quick_menu_show_cheats = "true" if the menu is hidden.
4. Eject the card normally, return it to the handheld and launch the intended game.

This is Onion's RetroArch path. A standalone emulator or stock Miyoo firmware can use a different procedure.

Load and enable one code

Press MENU + SELECT, open Cheats → Load Cheat File (Replace) and select the file. Onion's documented next step is to choose a listed cheat and turn its Enabled switch on.

Use a disposable session first. Record the file, code name and expected effect, then test one change in a scene where you can recognize the result. Follow any additional instructions supplied with that specific code rather than combining several guesses.

Read Onion's cheat setup instructions if your installed menu differs.

Original game versus ROM hack

Do not choose a cheat solely because a hack is based on FireRed or Emerald. Base-game identification and hack identification are separate checks; the local ROM checker helps investigate a source file, not cheat compatibility.

No effect, crash or unexpected progress?

Stop enabling additional codes. Disable the experiment, retain the original game and backup, and compare a clean session with the same build and core. Keep the untouched save separate while investigating; turning a switch off does not by itself prove that already-written progress reverted.

For missing Continue, use the save-not-loading checklist. For a resumed black screen, use the Onion recovery guide.

Diagnose the stage where the process stops

Do not troubleshoot a missing file by inventing a code. Once the intended entry loads, check its game requirements.

Manually enter a code with the documented application step

Libretro documents a separate manual route in Quick Menu → Cheats: choose Add New Code to Top or Add New Code to Bottom, open the new entry, enter its Code and optionally Description, enable it, then return one level and select Apply Changes.

That last step matters when following the manual workflow. The Onion FAQ's file-loading instructions and Libretro's manual instructions are related routes, but a selected entry is not automatically a verified game effect. Check the installed menu and the code's own requirements.

Libretro's cheat reference also distinguishes codes handled by the emulator/core from codes handled by RetroArch. Do not infer that a format accepted by another app will be handled the same way here.

Check the cheat handler and active core

Libretro distinguishes Emulator Handled codes passed to the core from RetroArch Handled codes applied by RetroArch to exposed memory. That distinction matters before you interpret a visible cheat entry as a supported action.

Native-cheat support and the existence of RetroArch’s Cheats menu are separate observations.

Before trying another code

1. Identify the core actually running this game, including a custom per-game selection.
2. Record which handler the entry expects. If its format or requirements are unclear, resolve that first.
3. Compare the code’s exact game/build requirement with your prepared game.
4. Only after establishing those checks, use the documented application route on disposable progress and observe the stated effect.

Example: an entry was written for a different emulator’s code mechanism. Changing only its Enabled switch cannot settle the handler mismatch.

Do not convert a code by changing its title, file extension or handler label. A real conversion would need supported semantics and matching memory behavior, which this guide has not established. Keep the original cartridge-save backup outside the experiment and stop if the result changes an unintended part of the adventure.

Worked example: the list opens but an item code has no effect

1. Record the entry's exact name and its required game, region, revision and activation instructions.
2. Confirm that you are playing that game rather than a patched derivative. Keep the current game and core unchanged.
3. Check the enabled state and documented application steps for the route used.
4. Repeat only the code's stated test in disposable progress. Do not add unrelated codes to see whether something happens.

If you cannot establish a match, stop treating the entry as a recommendation. The Inclement Emerald guide records one specific maker warning about ordinary Emerald codes, with its source snapshot date.

Keep the original adventure outside the experiment

Before enabling a code, preserve a known cartridge save and identify it by trainer, team and location. Keep a state too if it contains progress absent from that save. Do not rename or overwrite the only known good copy while testing.

After an unexpected effect, disabling the code is the first comparison step. It is not proof that an already-written item, event or party change reverted. Inspect the original backup separately and work with copies if you need to restore progress.

A clean launch and a resumed state can produce different observations. Use the GameSwitcher clean-start comparison to understand that difference before writing another in-game save.

The manual-entry steps use Libretro's primary cheat documentation, checked 6 Oct 2026.

Related setup and evidence boundary

Mini Plus overview · Fast-forward controls · Heart & Soul setup.

Onion 4.3 documentation checked 6 Oct 2026. No code effect, physical-unit test or specific hack cheat compatibility has been verified here.

Prepare an untouched progress copy

Record the game's build, region where relevant, emulator version and intended code effect. Preserve its cartridge-save backup outside the working installation. Keep your experiment distinguishable from the established adventure.

If you use separate mGBA player saves, inspect the active player file before testing. The multiple-playthrough guide explains that choice; it is separate from a state-slot number.

Add the code in Desktop Mode

1. Open standalone mGBA and load the intended game.
2. Choose Tools → Cheats → Add New Code, following the code's own instructions for its required format.
3. Test one code in a disposable session where its expected effect can be recognized.
4. Record the observation before adding another code or saving over established progress.

The EmuDeck standalone mGBA guide supplies the menu path. This article does not supply a universal Pokémon code or validate an external code list.

Open the selection menu in Game Mode

EmuDeck documents the left trackpad's Cheats icon for selecting cheats. If the menu is missing, check the active Steam Input profile. Its hotkey table also lists Start + DPad Right for opening Cheats under the documented profile.

Use the mGBA hotkey guide to identify direct Steam versus frontend profiles. Do not infer that a custom controller layout retains the same actions.

A ROM hack needs its own compatibility evidence

The Inclement Emerald preparation guide records a specific creator warning about original Emerald codes. Do not extrapolate one project's rules to every other hack.

Choose the software path before copying instructions

Check the emulator opened by your shortcut. A game with the same title in two launchers is not sufficient identification. Keep the actual emulator name and version alongside your code record.

Compare Desktop Mode and Game Mode without changing the code

1. Confirm Desktop access: load the intended game and inspect Tools → Cheats. Record the entry name and its current state.
2. Test the stated effect: use disposable progress and one code whose exact requirements you can verify. Record the observation.
3. Close normally: retain the unchanged code record and original save before opening Game Mode.
4. Inspect the Game Mode entry: confirm that it launches the same standalone emulator and game file.
5. Check menu access: use the shortcut or menu supplied by the profile you selected, then inspect the intended entry again.

If Desktop access works and Game Mode access does not, investigate the launch entry's Steam Input profile before changing code text. A controller action that never opens a menu is a different failure from a listed code that produces no effect.

The old trackpad menu and newer button profiles

EmuDeck's documentation describes both button-combination profiles and an optional radial-menu profile. The presence of a particular trackpad icon therefore depends on your chosen layout. Do not treat a missing older menu as proof of damaged cheat files.

Follow the controller-profile selection steps for the actual Steam shortcut or frontend. Record the previous layout before changing it. Verify an innocuous emulator action and ordinary Pokémon movement before returning to the cheat experiment.

This separates three layers: a controller profile opens the menu, the emulator contains the code entry, and the game must meet its requirements. Repair the layer that failed rather than replacing all three.

Worked example: the menu opens, but the result is wrong

Disable the experiment and record the exact game build, code text and stated requirements. Check whether the instructions were written for an original game, another region or a different hack release. Do not rewrite the code from a similarly named guide without evidence.

Repeat a clean comparison with the same game and emulator on disposable progress. Keep the known adventure untouched. If the code's requirements cannot be established, the useful outcome is to stop recommending it, not to force an effect through additional guesses.

Keep a short record for a reproducible result

• Game identity: actual file, release and edition rather than just “Emerald.”
• Software: standalone mGBA version and direct or frontend launch.
• Code: exact text, description and the source's activation instructions.
• Observation: scene and result with the code disabled, then enabled.
• Progress: the untouched cartridge-save backup used as a baseline.

This record is more useful for later support than reporting only that a cheat “does not work.” It also lets you distinguish a future profile change from an incompatible game update.

Stop an unsuccessful experiment

Disable the code and compare a clean session using the same game and emulator. Keep the untouched backup separate; turning a code off does not prove that already-saved changes disappeared. If restoring progress, work with copies and verify team and location before another write.

Steam Deck overview. EmuDeck documentation checked 6 Oct 2026. No code effect or physical-device result is verified here; this guide covers the menu workflow only.