theSLAYER

HOME is not known for rigorous checks, nor is it known for banning accounts with blatant hacks (for example, I’ve seen Shiny Victini remain undetected). For the most part it appears like it’ll be fine However, anything else in your setup or process could get your Switch profile or HOME account banned. I can’t give guarantees, and can only advise you that you’ll be doing it at your own risk. (keep in mind that they can take action retroactively if they so choose, and they pretty much log everything)

Sorry, no.

This code can be bypassed, but you’ll need a encrypted OTP from another device. https://gbatemp.net/threads/release-luma3ds-mod-to-unban-a-console-with-022-2812.565173/ For now, try unlinking the NNID step, and see if you’re get past it via making a new one (without OTP swap) edit: this seems to be more current: https://gbatemp.net/threads/release-luma3ds-mod-to-unban-a-console-with-022-2812.565173/page-4#post-10371677

What is the full code? Anyway in the meantime, being able to access eShop is probably good news. Go to your System Settings and try to set up a new NNID (I assume there isn't one) You also may need to update to latest firmware, make sure you update the CFW files first

Have you tried connecting to eShop recently? Or booting Bank? Checking just to check whether the ban is still enforced on your unit.

Your limiting factor would be an authentic HOME tracker on each mon. Only way to obtain it (for those mons) would be to legitimately go through bank and into HOME. Try to find ways to unban your 3DS (use an unblocked Local Friend Seed for connectivity) and pray that is enough to connect to Bank [provided you have connected before] (they appeared to be lax with some old ban criteria and some units can be unbanned this way). if your modded Switch and Switch 2 share the same Nintendo Account profile, you can transfer mons easily consoles easily, as both will connect to the same HOME account.

While detectable by HOME (if they specifically look for the info) right now if you insert something with a cloned tracker, it just assigns a new tracker. They could do anything retroactively but right now it doesn’t penalise the player. All at your own risk (and the risk of the accounts)

Yeah, champions being in 2026, you’re not pushed for time. It is considered slow, but I only replayed scarlet over the past week (I think 2 hours per night) and I’ve cleared the true ending (excluding DLC), in order to fight 5 star raids (for Shiny Wo chien) Having the DLC helps, and also a having a second Switch with a completed save helps. Even before the first gym, locally invited my new scarlet save to do some 5 star raids so that I have some level 75 (not that they’ll obey outside raids, but good to have), as well as obtain some EXP candy. Then went to the DLC maps to try to catch some stuff (also for EXP). At Blueberry academy, you’ll have the ball vending machine, which pretty much unlocks balls that would have been stuck due to story progression. Went to Medali to get Amulet Coin. After all that, attach the Amulet Coin to your starter, EXP candy it till level 60-70, then breeze through the game.

Certain ribbons restrict mons from being Wonder Traded away. An example would be the Classic ribbon, found on most event Pokemon (beyond Gen 3). This note is taken from Bulbapedia. At a glance, other ribbons include Premier ribbon and Birthday ribbon.

PKHeX doesn’t need a plugin to show height and weight. Just right click and view and go through the tabs of the pokemon.

Don’t modify any immutables, and these files + their tracker will work: (modifying the immutables will break the tracker)

Accordingly to this, scale was locked besides the ones stated otherwise (Pikachu being an example; it wasn’t locked, but is forced to generate a one 140 and above)

I’m assuming you’re referring to a few titled “hex extracted” in the event gallery. It was found that the wondercards within owned distributor carts had a small bit of extra detail that the game ignores when receiving the beacon (due to the set on the wondercard) or overwrites. I cant recall what specifically, but I think the one example is date recorded. In any case, hex extracted is for archival purposes only. You could use the regular ones in Event Gallery, or the ones already preprogrammed into PKHeX

Keep in mind that you are using a ROM hack, the game could have restarted due to the fact that the modified save isn't compatible. Try using this method with a vanilla unmodded game first. That should help reduce any noise that could cause issues with the modification process.

@Dyctinna PKHeX can directly edit dsv save files, just make sure the emulator is closed. And don't rename the file or change the extension. PKHeX can export back to dsv, just overwrite the original dsv file. And if it remains a dsv, won't have to try to import back into Desmume, the next load will automatically load the dsv (provided it is in the right spot) Also don't use state saves. Use the in-game menu to save the game, and when you load the save, just mash through the title screen sequence. ____ For future reference, if you are trying to modify a save and trying to import into Desmume (in this case, I believe the size is actually for dsv but you've renamed it to sav, so Desmume got confused), used the AUTO (from imported save data).

was the Latias caught on console or emulator?

I'm able to replicate; spin trades led to Link Trade (NPC) Gen V Also, Gen IV is correct

Are you using FTP to transfer the save to your computer? The data is truncated to a weird degree. When I shifted your data, it partly showed up correctly, but became truncated again down the line. This can be explained by the FTP setting being incorrect.

Could be, but I don't use that emulator, won't know for sure. What you could do is export the save file, and see if PKHeX can read it. (Note, PKHeX isn't meant to work with ROM hacks, but if all you've done is randomization, then it should work)

I can think of another place: form arguments. Usage may slightly vary and the info isn't useful for the game once evolved, but relevant to hack checking. Like it keeps track of how much damage was done to Galarian Yamask. How many time the Hisuian Basculin used the recoil move to evolve. Technically speaking, the HOME tracker is trash bytes within the respective games, as they don't use it nor reference it, and it was written from an external program. But we know it is important as it is used and tracked by HOME. Pal parking causes trash bytes too, and I don't remember where those trash are written to. In any case, PKHeX allows you to go through each extra byte, which may or may not hold undocumented data. PKHeX should have everything documented but it is more future proofing, in case the location becomes used in the future I don't recall if it happens in newer games, but absolutely happens in older games during evolution. In Gen 5, I traded a English captured unevolved mon to be evolved in a Korean game. IIRC that resulted in Korean species names and English trash bytes. A scenario I vaguely remember but never actually tried was hatching an egg (from a trainer with a long OT) into a different save (using a trainer with a short OT), and that resulted in trash bytes in OT. Not sure which generation this applied to, tho. I'm not sure. I think "captured unevolved Pokemon within it's own game" are fine, but anything evolved may bear a potential for trash bytes, and everything else is probably a case by case basis. I think some transfer up clear trash bytes anyway so maybe look into that first (not transfers between Switch and HOME games). You probably should clear Trash bytes in OT/Nickname first, then worry about how they may get applied. Or better yet, just gen something that would have had it's trash byte cleared upon transfer (but in that scenario you'll likely be missing a legit HOME tracker) Not sure. If it's clearing, then unlikely?

It should be fine. But keep in mind when you go online, the injected one will get replaced by the current one