Kaphotics

Save file sizes should be twice that size (64KB -> 128KB). Brief inspection of the save data shows that save sectors 8 & 9 are duplicated; shifting the duplicate to the end allows the save to be recognized. 005 Pokemon Leaf Green.sav

More tweaks pushed https://github.com/kwsch/PKHeX/commit/e0940f167948eae5a1a519c97947c83814e34295

I repeat; if PKHeX shows all of your edited changes when you reload the file, and the game does not, then you are not importing your edited save file correctly back into the game. It isn't an issue with the save editor. I suggest following a guide to see what you're missing.

Thanks, missing event handling added. https://github.com/kwsch/PKHeX/pull/4059/commits/b43d8bfc2b8a43d6f06f4f6da3f981f40a456152

Try changing your $ within PKHeX and trying to import that file. If you money did not change in-game, then you're not importing your save data correctly.

If the edited save file shows the correct data in PKHeX, then you're not importing your edited file into the console correctly. Data doesn't magically revert. I assume you're not importing the modified file correctly.

If you reopen your edited save file, are all your changes still there? Did you set the modified Pokemon data to a box slot prior to exporting the entire save?

https://projectpokemon.org/home/forums/topic/40006-issues-with-pkhex-read-this-first-sv-update/

Import your modified save file back to your console's savedata with the same homebrew app you used to export the savedata in the first place

ty, fixed on latest commit: https://github.com/kwsch/PKHeX/commit/40b6c9735803c4b93023a738a878b8e27e5f21dd

It's a WIP branch, but yeah I know what the issue is (math clamp) when the initial form size is bigger than the requested extra text size. I'll fix it later as I continue to revise the design of that form

It's relevant when the PKM format has data that is normally updated by the game when traded. Current friendship (Gen2+) gets updated, eggs get their met location set to Link Trade (Gen4+), handling trainer data gets updated (Gen6+). PKHeX gives you the option of skipping the game's trade updates when importing the data. Skipping it can result in mismatched data, but will keep the data exactly as it was stored in the PKM file.

Did you first load a save file?

There's no need to run emunand on the switch, everything can be done (homebrew menu / apps) with just atmosphere cfw on startup.

Open your save file in a hex editor. It's all FF; you haven't saved and exported properly.

Did you save in game prior to exporting the save data? Save states are not saving via the in-game menus.

>PKHeX, Version=23.8.23.0 Does the behavior persist on the latest release? If you don't mind, can you attach/DM your save and let me know what the play time should instead be?

https://github.com/kwsch/PKHeX/blob/5708310f6f075dd29b9b28e5131c2b9a676cb881/PKHeX.Core/Saves/SAV3.cs#L51-L54 https://github.com/kwsch/PKHeX/blob/5708310f6f075dd29b9b28e5131c2b9a676cb881/PKHeX.Core/Saves/SAV3.cs#L304-L354 1. Download a hex editor (ex. HxD) 2. Based on the structure of Gen3 save files, you need to locate where the Trainer Name is stored. Referring to PKHeX's code, the OT Name is stored at the start of the Small structure block, occupies 8 bytes, and is immediately followed by [byte Gender, byte Padding, uint TIDSID]. If you can find your Trainer ID at any offset (0x*00A), with data roughly matching the playtime, try changing the first 6 bytes (0x*000 - 0x*006) to be 0xFF. Do this for the backup save as well, so it'll need to be done at another offset with the same style. 3. Load in pkhex, should load as SAV3EU, export. Should be fixed.

SAV->Event Flags->find the Starter choice in one of the tabs.

PKHeX is assuming your save file is Japanese, and every character in the trainer name is probably 0x00. You can fix it with a hex editor after specifying a new OT name and then with the hex editor ensuring all 7 trainer name bytes are set (or 0xFF). OR just revert to a backup save file.

Channel Jirachi is not WISHMKR Jirachi.

You can export a box binary for each box you don't want to sort, then clear the box. After sorting, import each box binary. If you care about retaining the box names, you can always reorder boxes to have those boxes last.

I've updated my post with a link to pret's disassembly of emerald, which shows the structures for value & flag storage. In the disassembly, they remark how the Received Jirachi flag isn't accessible for Emerald, but if you hack the distribution disc to allow connecting to Emerald, it would still work the same. Might be iffy as a distribution disc might not know about a future game's overall structure (correct offset to interpret the struct at) but both structures are present for all mainline games apparently.

The Generation 3 mainline saves have an `ExternalEventData` region that is used by linked games like C/XD/Event Discs. PKHeX just implements them all as shared values because there's nothing known to be reusing the same offset within the struct that is version exclusive. https://github.com/pret/pokeemerald/blob/2304283c3ef2675be5999349673b02796db0827d/include/global.h#L932

How exactly are you importing your edited save into the emulator? Be sure the emulator imports your save correctly and that you aren't using save states to resume a prior snapshot. Close the emulator, overwrite the save file, open the emulator, start the ROM, then proceed past the title screen and continue game.