theSLAYER

Note: while it doesn't specify PLA, pkNX works for PLA. Make sure the ROM files are dumped properly from your Switch. Using ROM files downloaded from elsewhere is piracy, and we legally won't be able to assist you.

I'm locking this thread. The OP (if they decide to come back) can DM you to reply you. Alternatively, the OP can DM me to unlock the thread. Consider dropping an issue on their github page. Consider checking if there are any forks from their git too, testing the most active repository, then dropping the issue there if it exists there too. Best of luck.

Save the game properly. Extract the save properly. If playing on emulator, make sure they aren't state saves. Also make sure the save size is correct (check your settings)

Try turning flags 1508 and 0005 on, then inject the item into your bag, see if that works.

Probably search the net. To my understanding there's a ROM hack that removed it (Theta EX or something), so the info is out there.

Sounds like you need ROM editing. Or some kind of cheat code.

Yeah, that's all the save: That's literally all there is. That's not a save.

Start with a small ROM hack tool. Maybe perform something simple, like change a starter or an encounter or something. Then proceed from there.

The save seems odd. PKHeX actually loads it despite throwing the error. All mons on the save is illegal. Is your save from a randomizer or something?

So you're effectively still performing a region change + CTR transfer on Citra, but sounds less risky than doing it on a 3DS (tho you should be using EmuNAND for that anyway). In any case, glad to hear it works

sounds good to me. Maybe try again with a different region, for posterity sake.

I believe Citra also doesn't emulate the secret coords correctly, unless you do a proper dump from your own 3DS. Which would require different region'd 3DSes. Which goes back to the CTRtransfer shtick. But this is still worth a shot. Also, I think Citra can install CIAs. Since the user already dumped a CIA, could just try installing that and see if that works.

only if they both have the same user profile (also a Nintendo Switch feature to share user profiles locally), both at the latest firmware, both has access to the internet and can use Nintendo server features (no DNS blocking of any kind)

So far all the poke_trade I’ve seen are rather small, hence can’t store enough enough data to be significant. (I’m assuming it doesn’t grow). I’ve read about it storing trade info too, but I don’t know the particulars. All the ones I’ve seen so far have been the same. If they are indeed different, perhaps they store data like what mon you’ve most recently put up for link trade or surprise trade or something. That’s just a guess. In any case, it should be safe to move on with whatever you’ve been doing. Edit: So my 2022 poke_trade is exactly the same as my 2020 poke_trade, and I definitely made some trades. Until definitely proven otherwise, I'm just gonna make a calculated guess and say that the 'it stores trade data' is something people assumed based on the name on the file, with no real backing behind it.

I can’t recall if CIAs specifically has that check (I think they do) but it won’t matter if you’re running the CIA in CFW. CFW by default bypasses that check.

To be specific, those carts do run a check to see if the region of the 3DS matches the printed (manufactured in) region on the cart, yes. But that’s pretty much before the game properly runs. Initial phase, much like giving the prompt to older consoles to update their firmware. Once the game runs, the save uses the 3DS’ region and stores it, NOT using the cart’s manufactured region. Hope that clears it up. In other words, you can’t use a different region’d cart to try to bypass the Vivillon locality issue. Like I said earlier, it’s based on the coordinates saved into the 3DS’ profile, the cart has no influence over it.

The region info is stored on the 3DS, not the cart. A proper Pokémon CIA should run on any 3DS region’d device. Anyhow, when it comes to spoofing Vivillon forms (ignoring save editing to change the form) there’s no way around it: you gotta CTRtransfer to properly have the 3DS be in another region.

It’s based on how the 3DS works, and how the Pokémon game piggybacks off that function. When one selects the sub-region and country on a 3DS device the normal way [country settings], the device actually stores a set of coordinates (based on the location) in the 3DS profile. It appears to be normally not used nor seen, however the Pokémon area of the save reserved for Vivillon actually grabs and uses that area the moment you start a new game. The game determines which Vivillon encounter you should have based on those coordinates. People couldn’t tell there’s a difference (hidden cords, not region settings), because when you set the country settings in the device, it changes the coords to reflect that. Everyone wasn’t using CFW so there would never be a coord-country mismatch like you’re experiencing now. The Luma region spoofing correctly sets the region and country settings, but doesn’t touch that pair of secret coordinates. That pair only correctly shows up if you use the in-device menu to set the country settings. Thus, if you really really want to spoof Vivillon, consider doing a CTRtransfer for region spoofing. The 3DS CFW guide should have the CTRtransfer files there, and GBAtemp should have an old guide on using that to region spoof. I recommend doing that on a copy of your Emunand. All at your own risk tho. PKHeX doesn’t create a database of OT/TID/SID and cross check if all the region data to see if they’re consistent. The legality checks are more “this Pokémon is isolated in a bubble away from real world details” kind of thing. Anyone from the real world who took a look would know something is amiss. Anyhow, the form is set the moment you encountered the Scatterbug/Spewpa/Vivillon. The game doesn’t set the form upon evolution; it’s already there. It’s just that you only see it in game at the final evolution. In an isolated bubble world sense, probably fine.

Where are your game saves at. Try searching the Desmume app folder for .dsv files