Leaderboard

@suloku I found our culprit! Actually it's 0x7F00C, the value which is used as the new encryption key for the next transfer. I'm not sure if it's a proper way to just set 0x7F00C to zero but the DR actually seems to get the key anyway even if it's not there. Probably the key is actually derived somehow from the 0x25E00/0x7F004 value? But since setting 0x7F00C to zero works I guess knowing the origin of the value is not so important anymore. I assume 0x7F00C is not the new encryption key but rather the legendary flags which are encrypted by the new key (where ever it comes from)! I'm thinking so because 1 XOR 0xD4C5D9CE (the new encryption key from 0x7F090 in sav 4) is actually 0xD4C5D9CF (the value at 0x7F00C in sav 2)! I've attached my save so you can see yourself. POKEMON B2.0.sav - clean save before DR transfer POKEMON B2.1.sav - after DR transfer with Tornadus POKEMON B2.2.sav - after receiving 3DS Link POKEMON B2.3.sav - 0x7F00C set to zero! POKEMON B2.4.sav - Tornadus transfered again! B2 Saves.zip

Basically, it seems that clearing the flags needs an extra step since they seem to be encrypted in some unique per savegame way. I've just thought a tedious way of locating where the secret value migth be, albeit time consuming: 1) Create two blank savefiles (A and B) (blank so less data is in them, the 3DS link feature is accessible anyways). 2) Put the value at 0x25E00 from B in A, then check if any of the lengendaries can't be transfered anymore (we want at least one to be flagged as already transfered) 3) Start inserting blocks from savegame B into savegame A. After each insertion, check if the game allows to transfer the legendary again. 4) Repeat 3 until we can transfer the lengedary. Those steps would allow us to locate the block where the value used with 0x25E00 is stored, from there locating the actual value should be easier...at least in theory. Another option would be to reverse engineer how the value at 0x25E00 is generated on a new game, but that's something I can't do. This reminds me of the mirage island in ORAS, I hope this uses a simple operation with a value somewhere in the save, and not a complicated algorythm like that one (which someone actually went and kindly reversed). EDIT: I've been using desmune and I've noticed that each time you receive 3DS link data, the value at 0x25E00 is different, so as I feared this seems to have some RNG involved...

hopefully I don't regret this, feels hacky https://github.com/kwsch/PKHeX/commit/eb8b9602b2d00b4cbab57528727bb1cce5ebddb3

PKHeX decrypts the data and doesn't modify it. Dumping box data is safe.

The time frame between colosseum and FRLG is roughly 2 months, while Emerald came out 9 months after FRLG, so it makes sense that support would be lacking.

Hope you'll create this distrib ROM. I've found this today, which confirms @suloku theory. In case of it can be usefull, mostly for other event distrib (Jirachi, Celebi ...). Source: TCRF

It certainly fits the 40000th thread... And LOL about that 40000 year old Pokémon look...

Hey, back once again after being absorbed into Zelda for the past week. After seeing a huge chunk of the stat labels filled out in the latest release the people who did that deserve a huge thanks! I still managed to find out a few stats. 051: Times twirled 057: Pelago Wild Visitors tapped 120: Best Super Singles Streak 121: Best Super Doubles Streak 122: Best Super Multi Streak PS Some are most definitely unused but a couple are still in need of being identified so keep it up, researchers!