theSLAYER

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.

and did you use .PID=$shiny0 as a command?

but were their PIDs hacked by you, before transfer?

and that's enough info. The PID doesn't change from UM -> SWSH. The PID doesn't change with transfer process, not by PKHeX, not by HOME. Nothing changed in HOME or SWSH. The one thing I gotta to ask is: are the square shinies events? As I said, fateful encounter shinies are displayed as Square. Unless, these PIDs were made shiny by PKHeX (before and after the supposed update)? Tho I don't think they changed the shiny formula...

are you using PKHeX to transfer VC games to gen 8, or just any random games. As said, PKHeX doesn't change the PID (if the PID already exists. Slight exception: if the mon wasn't shiny in Gen 3/4/5, but it bears a PID that would allow it to morph into a shiny beyond Gen 5. Then again, that "PID change" uses the official game method of flipping a bit). All in all, PKHeX emulates the transfer as per the games. So it's probably a coincidence that you're noticing these. What games were you "transferring" the from?

erm.. what determines square or star is based on PID, so the PID doesn't change upon transfer, so I don't see what that has to do with PKHeX. (Note: Stuff from GO and fateful encounters are displayed as square in SWSH, also nothing to do with PKHeX) Some mons can be star, and some can be square. nothing to do with PKHeX..

try Read and follow the instructions fully and properly.

lol.

your save probably has extra flags that will cause it not to be recognized as a save file. Happens a lot with saves from ROM hacks.

Make sure shiny is xor=1. Use the latest PKHeX, and follow what Kaphotics said

TL;DR: There hasn’t been any tested and known way. Also, to answer your question, and homebrew event injection that works off saves would likely not work, due to your save is being stored in the ROM sector. The long version:

Yup, OT and TID variable to some extent. Are you sure you've been reading the right posts, or the right information? VC Celebi is only legal on VC. PCNY Celebi is only legal on retail carts. You cannot officially cross a mon from the realm of VC save into retail cart saves, and vice versa.

Just uncheck and recheck the nickname box. Issue known to be from PKHeX

Controls and resets the Zacian or Zamazenta encounter on top of the Energy Plant. If you only set ookami (wolf) flags, game crashes. Put these NPCs back on the roof: 161E0C4A z_d0602_LEADER_AKU Bool1 76355375 z_d0602_ASSISTANT_HAKASE Bool1 7C5D52A3 z_d0602_SWORD_MAN Bool1 279B69B5 z_d0602_SHIELD_MAN Bool1 DAD72DAC z_d0602_NURSE Bool1 Sword: FB18D095 z_d0602_PM_888_OOKAMIK Bool1 Shield: 31B0958B z_d0602_PM_889_OOKAMIT Bool1 Will change your current story progression: BB7B57FB WK_SCENE_MAIN_MASTER 3180 Changes the message on Rotom Map to match: C4F35C2E SYS_WORK_ROTOM_TUUTI 3180 If your elevator is closed: 9F73F31F z_c0201_g0201_ELEVAOR_SWITCH_01 Bool1 9F73F4D2 z_c0201_g0201_ELEVAOR_SWITCH_02 Bool2 Box32 Unlocked 32A339E9 FSYS_SECRET_BOX Bool2 71825204 (probably will be named KBoxesUnlocked) Byte set to 32 Battle Eternatus This will act as tho you lost your first battle to it, and it just wait at the roof for you. BB7B57FB WK_SCENE_MAIN_MASTER 1990