TFSthegreat

It appears in Slot 1 while a swarm is active. This spread/Pokemon combo doesn't occur without a Pressure/etc lead; without a lead the same spread appears on the next frame, in a different encounter slot

Latest commit is also flagging spreads exclusive to Pressure/Hustle/Vital Spirit lead

Not sure if this is the right place to report this, but PkHeX's legality checker is currently flagging Gen 4 Fishing encounters with Cute Charm PIDs that aren't accurately predicted by PokeFinder. This isn't consistent and doesn't affect all spreads; below are two Remoraids generated from the same encounter method during the same play session (on unmodified retail obv): The first is a spread that PokeFinder is blind to, the second one isn't. A couple more examples of unpredictable fishing spreads being flagged: PkHeX also can't find an RNG frame for any Honey Tree encounter, seemingly regardless of PID type. Example: This is probably the fault of PokeFinder's limitations, but the false positives are worth bringing to attention regardless.

SID 0 is flagged as Fishy for Pokemon transferred from the Virtual Console; these Pokemon can only have an SID of 0 Cute Charm PIDs are flagged as Fishy on daily/rotating Great Marsh encounters. The Exeggcute (rotating) and Quagsire (standard) below have the same PID and method; both were obtained on original hardware with no modifications

In Gen 8, the Tower Master Ribbon currently isn't treated as illegal on Deoxys, Manaphy, Phione, Darkrai, Shaymin, or Arceus. The ribbon cannot be legitimately obtained on these Pokemon - they are absent from SWSH and not permitted in BDSP's Battle Tower - and as such should be flagged as illegal.

My apologies. Thanks for the clarification!

No, it has no met location in HOME, nor moves or Dynamax Level. This Ho-Oh was moved from SWSH to BDSP via HOME, traded to a sysbot to obtain the .pb8 file, and then the .pb8 file was injected and traded back to the same BDSP save via sysbot. No alterations were made to the Pokemon, nor was there a duplicate of it present in HOME, BDSP or any other service. It was then placed back in HOME, which failed to identify it as the same Ho-Oh. The Pokemon was ostensibly identical before and after being extracted and injected, and there were no competing Pokemon with the same HOME tracker anywhere. This seems like it would imply there are other tracking parameters on the actual Pokemon not supported by PKHeX - how else would HOME fail to identify it if nothing detectable by PKHeX was changed? Either that or I'm misunderstanding how HOME tracking works, which I don't think I am.

Have a bit of a question about the new HOME tracker mechanics. This Ho-Oh (attached for reference) was originally transferred from Pokemon Bank and has data in SWSH as well. Sending it to BDSP, trading it to a sysbot, and reinjecting via sysbot seems to have wiped its HOME tracker data, despite no visible changes being made to the .pb8 file in the latest version of PKHeX. My understanding is that, because the HOME tracker visible in PKHeX hasn't been changed (nor anything else visible in PKHeX), HOME would 'remember' the Pokemon server-side and be able to restore its moves/Dynamax Level/etc when returned to SWSH, as well as exempt it from the one-shiny-legendary-per-BDSP-save rule. Neither of these have been the case. Am I misunderstanding how the HOME tracker works, or are there other tracking parameters not currently supported by PKHeX? Ho-Oh BDSP.pb8