Leaderboard

Switch Gift Data Manager aims to make past Mystery Gift events back again in all the Pokémon games for Nintendo Switch. Since those games won't allow wondercards injection in the SAV file, this tool allow users to create a forged BCAT package, injectable with homebrews like JKSV. This allows wondercards to be redeemed through the In-Game Mystery Gift Menu. What's New: Download | FAQ | Guide and Support Thread View full article

That’s the problem. Stuff caught in dens have correlated stats, so you can’t just reroll the PID without accurately changing the other stats to match. so you’re best off: 1) not changing any of the stats, or 2) catching one for yourself

Read FAQ point 3. No, this isn't a save file injection. It's BCAT injection. Save file wondercard injection isn't possible in Switch games.

Over the past year I have spent time on and off working with the IR signals for the Gen II Mystery Gift (specifically in regards to the Pokemon Pikachu 2), and there are two clarifications to bayleef's data that I was able to gleam, for whatever that's worth. I will note that I wouldn't have gotten to where I am if it hadn't been for bayleef's trove of information and trailblazing on this topic. I discovered that, of the 67 bytes the receiving Pikachu sends, the first two bytes are--for some reason--the number of Watts that was most recently given to Pikachu on that Pokemon Pikachu 2. When a player goes to "Present," then "Give," the Watt amount given will show up as a binary-coded decimal in the Pikachu's payload, followed by 65 0x00 bytes (ie If the receiver was recently given 987 Watts, its payload will be 0x09, 0x87, 0x00, 0x00...; you can even "reset" this to 0 by giving Pikachu 0 Watts). To quote bayleef, don't ask me why! (Note: This was discovered by reading from a Japanese Pocket Pikachu Color, but I'm confident it applies to the international version as well) I was noticing that there was considerable variety among my Pokemon games' status byte here when there was an item waiting at the center. It took an embarrassingly-long amount of testing and troubleshooting for me to discover how it actually works. If there is no item waiting at the Center, the status byte will of course be 0x00. However, if an item is waiting at the Center, the status byte will actually be the ID of the item waiting at the center. However, it is not the Mystery Gift ID of the item. That is a separate and unique ID list. It goes off of the item's internal GSC ID number. In bayleef's case, it happened to be 0xAD--the Berry item that otherwise has a Mystery Gift ID of 0x00. I will note that upon this revelation that at least once, the Mystery Gift's payload used GSC ID numbers, I was excited at the possibility of using Mystery Gift to inject items like the GS Ball. However, the rest of the process uses the unique Mystery Gift IDs, so I unfortunately don't believe that is possible. Would love for someone to prove me wrong though!