theSLAYER

I can’t be sure, but seems reasonable. Remove the caught/seen in Pokédex, then load that save, and send a Spinda out in battle. Win the battle, check the Pokédex, then check if it only shows the one you sent out to battle.

I guess the question is if that is intended behaviour for the Pokédex. You’ve got a save that hasn’t been hacked before?

Pre Gen 6, it’s appearance is based on PID. Gen 6 and above, it’s appearance is based on EC. It’ll only “change every time” if you changed those every time.

Well, if you're not playing on your Emunand, restoring to your Sysnand is enough. Glad it all worked out.

Well in the context of Pokemon, I recommend not doing anything that the server may notice. They log saves from time to time, so don't change anything that is not meant to be mutable. Like your OT, or your SID, or your trainer model/skin, that kind of things. This also extends beyond the context of Pokemon. Don't pirate games, don't install impossible themes, stuff like that.

From my experience, yes. I'm purely CFW on Sysnand. I go online and do some online competitions and stuff. Just don't do super illegal stuff in more ways than one. Still, my experience may differ from others. It is all at your own risk.

Atmosphere FSS0 SYS refers to launching CFW (Atmosphere) in Sysnand (SYS)

Is something like this not there?

Have a new current backup before reformatting the SD card before copying the current Sysnand into a new Emunand. Both the contents and the existing Emunand. You wouldn't want to lose anything.

You won't have to recreate Sysnand. You just need to recreate Emunand based on current Sysnand. I'll advise backing up the SD first. As for launching CFW in Sysnand, I *think* Hekate has the option in the boot menu. If it doesn't, another way is to completely remove Emunand. A rather nuclear options in my opinion.

Well, normally if you use CFW in Emunand, you only make changes to Emunand. I'm guessing you were used to making changes in Emunand and seeing them actually change stuff in Sysnand. That observation is a bug, not a feature. The way I described in the past is something like 'think of your Emunand and Sysnand as separate profiles. They were meant to be separate. However, both your Emunand and Sysnand profiles were sync'd, so the changes carried over. Somehow or rather, maybe a game update or FW update, caused the Emunand and Sysnand profile to now desync, hence the changes no longer carrying over'. So either launch CFW in Sysnand, or recreate your Emunand based on current Sysnand. All at your own risk, of course :3

If I were to take a guess, you're trying to restore the save into your Sysnand, using Emunand CFW, is that correct? If so, can you launch the game in Emunand CFW and check if the changes are there?

Do you happen to use Emunand on your Switch?

Let us focus on one specific thing to help narrow things down I see this here: Is this not appearing in-game?

Upload the save here. Mention what you’ve changed.

Upload the save here. Not the ROM, only the save.

did you check the various folder in appdata? There's should be no where else it'll remain I don't think

While I'm still holding onto some that can be received via a request in my DMs, I'm letting these last 30 (from the spreadsheet) go into the wild. 170 Celebi : U120GJ6U673JMH34 & Zarude : U121G09B94N7R3QU 171 Celebi : U12078QY4KXFV0KH & Zarude : U121C7A6WGTMEG71 172 Celebi : U120B1FBQQUUGSQS & Zarude : U121D5DH370EJSWE 173 Celebi : U120GJ4TF2J0VKX9 & Zarude : U121G07K8X4G6BY0 174 Celebi : U120GJ6BKKCN6F93 & Zarude : U121G08YKDSKAWRF 175 Celebi : U120H66DQWS6AKSW & Zarude : U121AKX3QNPC6GQH 176 Celebi : U120GJ4XM10FTE2N & Zarude : U121G07T7NJB40BW 177 Celebi : U120GJ4XL708MJU2 & Zarude : U121G07SWG0BVCAX 178 Celebi : U120B1QVD4NP00H8 & Zarude : U121C9LTGSQFU3EW 179 Celebi : U120B1JBAUDY3NX5 & Zarude : U121C9EE9U86ULDU 180 Celebi : U120H65W8KSQ7JXP & Zarude : U121AKWJ2VWCA86D 181 Celebi : U120B1J1YAYAYNEN & Zarude : U121C9DXE7W7WBHL 182 Celebi : U120H67YYURGVAB2 & Zarude : U121AKYMST2BKQDJ 183 Celebi : U120GJ6GR7EGATYW & Zarude : U121G0937DBNKATY 184 Celebi : U120GJ540N2YR6VD & Zarude : U121G07Y40GUQCE5 185 Celebi : U120H680M28L3NX7 & Zarude : U121AKYNHLX05VPL 186 Celebi : U120AHYCW5NUVYCM & Zarude : U121C7JH91WKCQW5 187 Celebi : U120B1JAC3S5FS32 & Zarude : U121C9ED3RVN8N1T 188 Celebi : U120GJ4U6GQ88P87 & Zarude : U121G07LGQBPTDNY 189 Celebi : U120GJ6DTURWKHBE & Zarude : U121G09015QK8YUL 190 Celebi : U120GJ6E87FW2L2U & Zarude : U121G0904WGTYD15 191 Celebi : U120GJ51RAQJX01G & Zarude : U121G07V39U8XUF8 192 Celebi : U120H66236YB16QE & Zarude : U121AKWN5T47EX5L 193 Celebi : U120GJ52SAETM4UR & Zarude : U121G07VHGBJUSN9 194 Celebi : U120GJ52Y2LD58KD & Zarude : U121G07W72CDKWJ9 195 Celebi : U120GJ6GMHFP3G4R & Zarude : U121G092EA77HGFB 196 Celebi : U120AHXAQ7ESLSL7 & Zarude : U121C7HCUXQPFYYT 197 Celebi : U120AR3SY96WKRC7 & Zarude : U121C7PH470UY1KM 198 Celebi : U120B1E6V3NUYXJ1 & Zarude : U121D5C6RUURWAGK 199 Celebi : U120B1EHX6SMMNK1 & Zarude : U121D5CHTAABVT1L 200 Celebi : U120AR3J7VX387AH & Zarude : U121C7P5VJJY3PKK Happy new year everyone. :3

Check your %appdata% folder.

Check if the modded cro is saved to somewhere else, that is what pk3DS looks at.

I think modifying statics/starters require an exeFS edit? It's been quite a while since I've looked at ORAS files. To be sure, it doesn't stick when you checked via decompile/recompile or via loading the ROM?

Oh, was your save at the very beginning of the game? Yeah there's a few fixed encounters sprinkled here and there, and the Wurmple is one of them. If I recall correctly, it is shiny locked, so that your first encounter won't be an impossible shiny (one that you couldn't catch). Well hopefully it is all good for ya now :3

I don't think Citra would secretly store a copy of the unedited ROM and read from it. There could be more than one encounter table for the Route. There could be a table for standard encounters, and another for DexNav. Maybe there's one for before the legendary event. It's hard to say, I'm no expert in encounter table editing, but all those seem like possibilities to me, hence why I suggested performing a different change. Or perhaps, go the randomization route, this way all tables are changed.

then I got no clue. Maybe try making a different edit. Maybe your edit isn't as unique/noticeable as you think. Perhaps start with performing an edit on a mon. Do a personalinfo edit and change Bulbasaur's type or something. Or maybe change the model of a species.

For future reference: 1. Don't make a Pokémon from scratch. Use one from the Encounter Database. 2. When you get PID Mismatch, follow the guides: Anyhow, here's a fixed version: 641-01 ★ - Tornadus - A3116F6598D0.pk8