theSLAYER

Use at your own risk

The game or the pk file or the editor exe ?

If you’re trying to use the ticket normally in-game, I think you’ll need to have the National Dex and access to the ferry. Requirements to access Birth island as per Bulbapedia And to keep legal, depends on what origin game: Emerald -> ENG FRE GER ITA SPA FRLG -> ENG FRE GER ITA SPA JPN I advise you to read this page: https://bulbapedia.bulbagarden.net/wiki/AuroraTicket

You can ignore it for those particular events.

You brought a more than dead thread back to life (necroposting, search it up) Anyhow, if you’ve read what was said in the entire thread, any traded pokemon need to have Not OT Trainer details. This is true even if it went back to the original trainer. Look at the screenshots. Format of PKHeX changed but it should still be relevant.

Very detailed findings, great work as usual! I’ll look into the saves from the second hand Japanese cartridges I’ve bought, to see if I could find anything

It’s about the RNG generation. At any time for raids (I believe SV is included for this?) RNG seed generates calculable PID - IV - Mark - Shininess (fake trainer ID). Thus tempering with shiny/mark generation within the ROM *could* result in invalid values being generated. Since I’ve not tried the scenario for SV, I cannot be sure. You could try and see if (a) it causes illegal correlations or (b) if the correlation the ROM generates is still legal or (c) raid SV data is sufficiently random

Probably could use pkNX (ROM editing). The resulting pokemon would likely be illegal.

You should be able to fix checksums in the tool or in PKHeX. Then export/save that fixed save. Then try again. also make sure the wonder card you’re trying to use matches your game version + game language.

Just add the item using PKHeX, add it directly to your bag.

Event distribution has since ended

You can't extract saves out of ROMs. But if you managed to extract your own demo games and what not, and played it on an emulator, you can extract the save from the RAM. I'm not sure if there's any specific guides online, but you'll need to identify the area of the RAM to extract and it'll *almost* function as a save (If I'm not mistaken, there's one more edit to achieve but I don't remember where to change) In any case, if you were just interested in the Pokemon, can use this:

What could have happened: you’ve had an English pokemon in your viewer, then tried to change the language to Korean. As a result, the existing English name became trash bytes. hold down the control button on your keyboard, then click on the nickname. A window should pop-up, where you can delete trash bytes.

For the most part, same as generating BACD algo, but restricted to certain seeds. You’re gonna need to know what those seeds are. And know how to sacrifice 3 RNG calls to the ravenous RNG beast Also, I would NOT recommend attempting to generate Gen 3 event mons. They might have other RNG corrections outside of the standard PID correlations, that could affect stuff like version/origin game or OT gender, which PKHeX may not check for or maybe not properly documented.

Any chance you were using state saving instead of regular saving? Or the saves were grabbed from the correct location? Also games and emulators can crash, so that part isn’t the mystery. More curious about why no data was written into your save.

AFAIK as long as you inject in an unmodified pokemon with a valid tracker, even if it’s an event pokemon, it’ll be accepted. Also the trackers can be clones; it just copies the data and assigns a new tracker. you can try to send performing a trade with the discord, using a Mon that supposedly the tracker. This confirms if the server really retains the tracker.

Try this. Ensure you keep safe backups.

yeah HOME doesn't overwrite it. If it shows up in HOME First Met, then the data is likely there and PKSM simply isn't reading it. (I've previously heard about PKSM messing up transfer locations; as in the data is there but read it wrong, so I can only speculate that maybe they've stopped trying to read it altogether.) no worries have a good one!

Continued from Discord. You've since received many, many explanations. However I figured I could provide screenshots (since I'm the one that shared this Zeraora upload), as that may be the only way to convince you. HOME app: Mobile HOME app: Switch Specimen A) Copy that I left untouched in HOME (and do not intend to move it out): Specimen B) Copy that I shared here, moved into HOME (deposited using included tracker): Do you notice any differences? Also for the record: The Origin Game for all of the HOME's Zeraora is Sword, instead of HOME.

I cannot talk about the efficacy of transferring up using PKSM, however you can see the following details to judge for yourself: The hex data remains unchanged, so you gonna need to read the data and compare to Gen 5 offsets. For simplicity, use PKHeX to view the data. If viewing from PKSM, well, I've heard instances that transfers aren't shown correctly. AFAIK HOME does not modify Met Location. If you use the HOME mobile app, you can even see the actual old met location. (HOME specifically built a function around it, to reference old met locations, cause the data in the met location portion of the pkx format remain unchanged since Gen 5) In this example, this is a Spinda transferred up from Gen 3. The First Met says Poké Shifter, the transliterated Japanese name of Poké Transfer FYI, this tidbit can be seen on Poke Transporter's page on bulbapedia and HOME's page on bulbapedia However, I understand how it can be missed, as those pages are filled with many many words. Those pages would cover other modifications as well. Also, PKHeX covers conversion fine, so you could convert up your pk3 to pk6 with no issues.

I’ll get to your other post later. In the mean time, what do you mean they don’t work. As in you tried putting into HOME and got an error? Are you using Sysbot to transfer the Mon into your game? Some Sysbot wipes the HOME tracker when injecting it into the game to trade to you. You’ll need to find a Sysbot server that maintains the HOME tracker.