Multiple Pokémon saves on Steam Deck with standalone mGBA

Open the documented player-save choice

1. Back up your established game and cartridge save before experimenting.
2. With the game open, EmuDeck documents Start + L3 to reach the emulator interface.
3. Open File → Save Games, then choose the intended Use Player # save game entry.
4. Inspect the game's title screen or loaded progress before creating a new adventure.

Follow EmuDeck's standalone mGBA multiple-save instructions. Check your installed software and controller profile if the shortcut does not reach the menu. Do not guess a replacement shortcut that could write or load a state.

Keep a simple playthrough record

Do not assume a chosen player entry is empty or belongs to someone else. Inspect it before saving. Keep different adventures distinguishable in your notes rather than relying on memory of a slot number.

Verify a second playthrough

On disposable progress, choose the intended player file, create or load the adventure and save through Pokémon's own menu. Close normally, reopen the game with that player-save choice and verify Continue.

Then select the original player file and inspect its original progress. Repeat the close-and-reopen check for both. This is a proposed check; Pocket Deal Radar has not run two campaigns on a physical Steam Deck.

A save state is a different choice

Do not treat a state-slot number as the player cartridge-save selection. A resumed state can show progress without demonstrating which in-game file Continue reads. Preserve both file types while checking, and use an ordinary start for the cartridge-save verification.

For a ROM-hack update, consult that project's maker before carrying a player file to another build. Extra file choices do not make an incompatible old save compatible.

Player file, state slot and game build: three separate choices

Write all three when investigating an unexpected adventure. “Slot two” is ambiguous unless you specify whether you mean the player file or an emulator state. Do not use a snapshot of one playthrough as proof that a different player file was selected correctly.

Create a second adventure with a visible identity check

1. Secure the first adventure: make an in-game save, reopen through Continue and preserve a separate copy with the game build recorded.
2. Select the intended second player entry: follow the documented File → Save Games menu. Inspect what it contains before starting anything new.
3. Use distinguishable progress: for a disposable verification, record a different trainer or recognizable team/location. Do not use only identical opening scenes as evidence.
4. Save inside the game: wait for completion, exit normally and reopen with that same intended player choice.
5. Compare both: confirm the second Continue, then select and inspect the original adventure again before another write.

This is a proposed verification routine. It does not assert that a previously used player entry is empty, or that Pocket Deal Radar completed a two-adventure test on a physical Deck.

Worked example: two adventures with the same starter

Use trainer name, team details and a recorded player-file choice together. Before either player saves, check those details in the active adventure. At handover, close normally and select the intended file deliberately rather than relying on the last resumed picture.

If you cannot tell which adventure is open, stop before saving. Keep both known files and compare Continue using the recorded game build. Distinguishable notes help without requiring you to rename files blindly.

If the wrong adventure appears

Change one variable at a time. Correct the selected adventure before changing emulator version or storage. If you restore a file from backup, do it on a working copy and verify team/location before retiring the source.

Back up adventures so you can tell them apart later

Preserve cartridge files from the location your installation actually uses. EmuDeck documents standalone mGBA saves under Emulation/saves/mgba/saves and states in the separate Emulation/saves/mgba/states folder; the Emulation root depends on where you installed it.

Keep a short note with each backup: game release, intended player entry, trainer, recognizable progress and backup date. Copy before reorganizing. A folder label helps identify a backup but does not change its compatibility or the emulator's expected filename.

After an update, verify each adventure independently. One file opening successfully does not establish that another player file survived migration. Keep the previous build until both intended Continue checks pass.

A launch-test copy is not automatically another adventure

Copying a game to test a Steam filename problem creates another game output, not a verified independent player save. Keep the experiment’s filename, selected player file and visible progress separate in your record.

Example: a plain-name test entry reaches the title but has no Continue. Stop before starting a new adventure. Reopen the preserved original and check the established player file. The test narrowed the launch problem; it did not establish a progress migration.

Follow the launch guide’s progress handoff for that branch. Keep the original save and state copies until the exact intended adventure has been identified, regardless of how many Steam entries appear in the library.

Did the working copy change before the first launch?

If you only copied or renamed the ordinary save, use the local byte-for-byte comparison to compare the source backup with the working copy. It reads your two selected files in the browser and does not upload or modify them. Identical bytes establish an unchanged copy, not the right trainer, accepted format or compatible game build.

Compare before launching when your question is whether copying changed the contents. After an in-game save or a documented conversion, different contents may be expected. Keep originals, record which stage you are comparing and use Continue to check recognizable progress. A byte difference alone does not establish corruption or identify the newer adventure.

Record a transferred adventure before retiring the source

Once you have established the ordinary-save format and the game/build compatibility, use the save-transfer observation record. For Steam Deck standalone mGBA, include the player-specific game copy, runtime and intended Steam or direct launch. Give the expected checkpoint a recognizable detail rather than recording only “the game opens”.

Keep independent backups, open Continue without relying on a state, then save inside the intended game and check Continue after closing normally. The tool keeps a missing or different result separate from a matching result and lets you download the attempt. It records what you report; it does not locate files or establish compatibility.

Back up the actual save target, not only a link

EmuDeck’s save-management reference distinguishes a Symlink from its Target and directs backups to the Target. A link points to another location; retaining that pointer alone does not preserve the save contents.

1. Identify the ordinary-save file for the intended adventure and close its runtime normally.
2. If the listed location is a link, inspect its target rather than copying only the link itself.
3. Copy the actual file contents to an independent destination.
4. Inspect the backup outside the working installation: real filename, nonempty contents and the adventure/build note.
5. For a copying-only check, compare the two actual files using the local byte comparison.

Example: a backup folder contains an item with the familiar save name, but it points back to the working card. That entry is not yet evidence of an independent copy. Locate the target and preserve its contents before reorganising the card or internal storage.

Equal bytes establish an unchanged copy, not a compatible destination or the correct trainer. If you later change the save through play or conversion, keep that later comparison separate. Use Continue to confirm adventure identity, and retain states independently if they contain progress absent from the ordinary save.

Prepare an inventory before using EmuDeck import/export

The official import/export tool page describes moving game files, firmware files and saves between devices, with SteamOS/Linux as its supported scope. That description is not a universal Windows import procedure or a save-format converter.

A tool’s category list does not establish that every external configuration, custom player file or emulator state is included in your particular export. Inspect the produced inventory and retain independent progress copies. Do not retire the source because the export operation finished.

Example: the destination opens the right game but shows a different adventure. Compare the selected player file and ordinary-save identity before exporting the whole library again. Once Continue matches, save in-game on the working destination and verify it after a normal reopen. That confirms persistence for the checked setup.

Local trading is a separate workflow

Two playthroughs do not by themselves establish that the game supports trading. The local GBA trading guide covers EmuDeck's documented multi-window path and its limitations. Check the exact game's link support separately.

Steam Deck setup · GBA handheld paths. Documentation checked 6 Oct 2026; save migration, hack compatibility and completed playthroughs were not tested here.

Label each adventure with visible progress

Give each adventure a human-readable label and pair it with the exact game build, ordinary-save file and launch entry. Record an in-game identifier after loading each one. Two filenames are not enough to show that two separate adventures are working: you need to check the progress each selected file opens. Keep state-file notes separate from the ordinary save.

For example: adventure A opens the intended trainer, while adventure B opens the same trainer at the same location. Pause before continuing either adventure and inspect the selected player file using the steps above. Do not infer independent progress from two desktop shortcuts. Once the second adventure opens the expected progress, record which entry you used so the next session starts with a known selection.

Use the local GBA session notebook to download a plain-text record of your attempt. Blank fields stay unrecorded; the notebook does not diagnose your setup.