theSLAYER

yeah, but without some kind of RAM watcher, you can only check the PID is after you catch it. And yes, can confirm the PID you roll will be different each time, and XOR<>0 is effectively shiny chance.

yeah, basically someone made a bot and did like a heck load of encounters, re-encountering the same mon in GO Park again and again. (PID changes per encounter, and PID was captured from RAM) Only a very small percent had non 0 xors.. It's not even Bank to HOME, it's just how SWSH displays the shiny. (The PID doesn't change). Additionally, the same effect is applied to GO shinies too. I agree. My best advice is to simply not take GO mons from others, and don't generate a GO origin mon. Then you'll never have to worry bout it XD I don't have info about that. In any case, I would think HOME is just checking the event flags. The event flags for those legendaries are already documented..

@AliceTheAlice thanks for the info! The team is presently (and has been) reviewing information regarding GO -> HOME legality. [they've been thinking about this for a while, even before the announcement] Let me just address a few factors: a) The stuff in pointer form you've mentioned were already being considered :3 b) The xor = 0 would probably match the LGPE shiny formula they used. There's a "shiny chance" of a PID being xor <> 0 in the GO transfers there. c) Gen 5 Shiny Genesect was available to Japan and Korea, not just Japan. Also, I'm unsure of how the PIDs in Gen 5 were generated, but they should have been sufficiently random. Regardless, since it has a fateful encounter, it can only appear as Square Shiny in SWSH.

delete the plugin and try again.

not a question page. will remove your post within 24 hours.

I don’t think that’s accurate. Using the Dream Radar Landorus as a basis, while the therian forme has the same ability, reverting it to incarnate shows HA. Thus, the HA status was carried from the therian forme. In this case, the reverse should also be true. It’s possible it’s not accounted for in PKHeX. FYI: something similar occurs with Flygon. The one you catch in Max Den is HA, but in game you can’t tell cause the ability is the same. You’ll only notice after you breed it. edit: The Incarnate/Therian HA issue is known, and will be fixed in the next stable release.

Yes PKHeX needs to be updated to add them to PKHeX's legality registers Trading has NOTHING to do with PKHeX. It's just that the server's whitelist hasn't been updated yet. Truth ^^

Each tracker is assigned per entry into HOME. So it doesn't matter whether the mon is cloned. So each mon who enters HOME gets a different tracker.

Judging by how Hydro Pump Drillbur is treated, it's likely they'll be treated as illegal. Also, the special moves from Pokémon GO aren't transferred; the moves are reset. What the mistake *is*, is that any mons that exist in LGPE that has a regional variant, incorrectly use the LGPE moveset. For example: Alolan Vulpix uses LGPE Kantonian Vulpix moveset. Galarian Ponyta uses LGPE Kantonian Ponyta moveset. The link you posted doesn't show error, just GO exclusive movesets.

Yup, any GO Pokémon not transferred from LGPE would appear illegal until PKHeX updates. Wait patiently.

I answered you on Discord.

To preface this: I think the video below is a great video, and it is pretty informative. However, people who do not know how to achieve ACE on Emerald may lose out. Anyhow, people would likely wonder/worry about how the event has not been known, or ask other questions about it. The point of this thread is to cover what is known regarding this Pichu event. (it's not about ACE) Video in question: Before I explain what this Pichu is, I need to do a brief explanation of WC3. Brief explanation of WC3 (for FRLG and E): Split WC3 sections: Wonder card data (wonder card text and checksum and other settings) and the wonder card script. [more detailed technical breakdown here] The wonder card script literally controls what the delivery person says, what flags get set, and what the delivery person gives. When the debugging versions of the games leaked, it was discovered that certain debugging wonder cards (such as Old Sea Map, Aurora Ticket, Altering Cave, a Pichu egg etc) were stored in the debugging game. It was also discovered that in the games, the wonder card script is stored separately from the wonder card header. (It was later discovered that the debugging games have a local distribution mode. The wonder cards can be found here) So what is this Pichu? 1) First angle of attack at the problem. Using the dialogue that the hipster-delivery person hybrid spoke, I was able to find the egg Pichu script. (just in case you wanna try it for yourself, be aware that Gen 3 text uses the character encoding) I compared the Pichu Egg script found in the final game, against the Pichu Egg script for debug wonder card (for Emerald). The image below is the comparison. Left data is script from the debugging wonder card, right data is the Pichu egg script taken from ENG Emerald game. Note: offset is 0x674D3D of Final game (ENG), 0x3E4 in size. Besides the offset pointers being different, the rest of the script are almost mostly the same. (If you're curious on how to identify offset pointers, it's B8 XX XX XX 08. For example, in the data of the right, it's B8 3D 4D 64 08. When you account for endianness, it points to 0x674D3D, as mentioned above) 2) Second angle of attack at the problem. The video linked to a pastebin with the relevant codes (useful if you wanna try it out). Comparing to the pastebin (https://pastebin.com/dFLaf2TB), if we ignore the 8 in that highlighted value below (could just be RAM address or something; I imagine ROM data is stored in RAM starting from 0x8000000) You can see that the highlighted value is the same value as the offset I found in (1) [this means the data I found is indeed the correct data] Conclusion/TL;DR: The Pichu Egg is merely a leftover script of a wonder card that was in the debugging versions of the game. There are other scripts that were leftover, such as changing the species in Altering Cave, getting Old Sea Map, getting Aurora Ticket, getting Mystic Ticket etc.

Which link? This one works.

it's definitely not related to day skipping. I do that, so that ain't it. Do you still have "competition locked" Pokemon in your boxes. I imagine it's related to restoring a save either after you "competition unlocked" them or "recieved the gift".

There's no tool to inject WR8 into the WR8 bin presently. If you can figure it out (and documentation here), and it's not difficult to figure it out, all you need is to insert the WR8 into the bin, then inject the bin into your save with PKHeX.

unrelated to day skipping. Check your VS battle stadium rewards, let your team be unlocked (be it online competition or ranked battle). Potentially could be related to you reverting to an older save too. Usually it's something like that.

And add Latest NotOT handler

There isn’t any need to. Any event mon can be traded... you cannot receive event mon in-game using injected wr8...

I'm unsure how the VC injected GBA Pokemon saves would be different from proper GBA saves, but I would think there's some offset differences, hence why people have issues with it. If we're just talking about Gen 3 saves in general, I think the relevant offsets have already been documented: https://bulbapedia.bulbagarden.net/wiki/Save_data_structure_in_Generation_III#Data

Sadly no, because I'm not interested in GBA Pokemon injected into VC.

I don't do it, so I don't really know. I assume you're gonna need to compile your own PKHeX, with one of the resources being the personal file that has the changes done in pk3DS. I don't know if PKHeX has any kind of special overlay mode and whatnot... I actually refrained from answering here simply because I don't have an answer.

Yes you are right: the flag doesn't force star shinies. The same byte appears in standard event raids, as well as Dynamax crystal raids (tho it has yet to be used as this point) For my example earlier, I was referring to event raids, tho I suspect a similar mechanism also exists for standard den raids (I need to check back on the shiny byte in pkNX). Besides the fact that I've tested the byte for event raids, there's also wild area events that proves the point: recall the forced Shiny Magikarp, Shiny Clefable, Shiny Gourgeist, there were all forced square shiny. It appears they don't have a byte to switch between Square and Star shiny. The forced shinies results in squares. (as seen under shiny status) Ultimately, without going into the argument of "which shiny is more special", because that is subjective (i.e. depends on the eye of the beholder), it is a fact that Dynamax Adventure shinies are locked to XOR=1. If you want square shinies, just import the mon from a previous gen. Pokemon from past/other games typically can be Square or Star, with the exception of Shinies from PGO; certain code in the game forces any shiny from PGO to appear Square, just like Fateful Encounters.

To be fair, SWSH has treated any shinies with fateful encounter to be Square (regardless of actual PID) long before the aforementioned events were released, so it isn't anything special. To add on, forced shinies from Raids were locked to Squares, so in some sense getting the locked species in Star Shiny were actually more special (on the basis of lower rates compared to forced shiny). Well, to each their own.

Square shiny can only be xor=0 Dynamax Adventures can only be xor=1. That should be enough information for you to derive the answer :3

Maybe PKHeX changed it's shiny code from batch editing. In any case, there's nothing wrong with PKHeX. Pokemon that were transferred can be one of either star or square. It probably was just RNG (in terms of batch editing making shinies). Carry on with what you're doing.