1.1.2-pre-release

PKSE Release 1.1.2 - Pre-Release Notes

Version 1.1.2-pre-release-debug (test build)

This is a pre-release test build, not a finished release. It exists so that the people who
reported being unable to save can confirm the fix before 1.1.2 ships properly.

If saving to your game failed with a "Failed to copy" error and your edits disappeared, this build
is for you. There are steps at the bottom for checking whether it works now.

Fixed - save writing

• Fixed an issue where writing your edits into the game failed completely if your save did not
  contain every file the editor expected to find. Not every Sword/Shield save has a poke_trade
  file — it holds a Surprise Trade result that has not been collected yet — and the editor treated
  its absence as a fatal error, abandoning the whole save and discarding your edits.
• Fixed the same failure on Brilliant Diamond/Shining Pearl, where a save may have no Backup.bin
  beside its SaveData.bin.
• Fixed an issue where Legends: Arceus never wrote its second save file back to the game.
• Scarlet/Violet, Legends: Arceus and Legends: Z-A now write their companion save files back to the
  game alongside the main one, rather than the main one on its own.

No save data was ever lost or damaged by this. The write was abandoned before it was committed
to the console, so your game save was left exactly as it had been — the edits simply never arrived.

Please note

• This is a debug build, and it writes logs to your SD card under PKSE/logs/. That is
  deliberate: if saving still fails, the log will say why. Switch back to a normal release build
  once you have finished testing.
• The version reads 1.1.2-pre-debug on the home menu but 1.1.2-pre-release-debug inside the app.
  That is expected, not a fault — the console's version field is too small for the longer name.

How to help

1. Copy PKSE.nro into the switch folder on your SD card, replacing the old one.
2. Open PKSE and load your save from the game. PKSE takes its own backup as it loads.
3. Make a small, obvious change — renaming a Pokémon is ideal.
4. Save, and choose Game save as the destination.
5. Start the game and check the change is really there.
6. If anything fails, attach the newest file from PKSE/logs/ when you report back.

Sword/Shield and Brilliant Diamond/Shining Pearl are the most useful to hear about, since those are
the two games the failure was actually confirmed on. Scarlet/Violet, Legends: Arceus and Legends:
Z-A are worth hearing about too — their save-writing changed in this build and has had the least
testing so far.