Kaphotics

You're importing things wrong. This is not an issue with PKHeX.

Check the date in the top left corner of the program and compare it to the latest release date.

Reboot the console and turn off any cheats before launching the game (hold L when booting the game). This isn't the place for plugin-specific help; seek help where you obtained them from.

ty fixed https://github.com/kwsch/PKHeX/commit/afeb06d3ae69cb070bc0c9aa03179659bfb383c8

Related: https://github.com/kwsch/PKHeX/issues/2697

You can have any seed, and they advance in a predictable fashion. You'll be fine with any seed you inject, even randomly entered ones.

Depends how you're inserting the seed; the "four parts". PKHeX displays it as one number; you'd have to check how 3DSRNGTool is presenting the 128bit value and ensure you're importing it correctly.

Depends which game. For games with seeds that are advanced, then you can just replace the seed, like you are describing.

Shift already sets the relearn flags for the current moves. There's no need to have more than the current moves. If you want to give ALL, you have to open the form and hit the associated button.

The batch editor edits PKM files contained in the boxes / folder. There is no way to modify a game's overall progress, as there is no documentation on how every single flag/toggle/value would need to be modified to be at a given point in the storyline. Take a donor save file at the desired progress point, import the PKM from your folder, then make your cosmetic changes.

Read the shortcut list, it's shift ;).

Use PKHaX.

PID gender would have been encountered as a Male Combee, which can't evolve to Vespiquen. PKHeX is working as intended, flagging this as hacked is correct.

https://github.com/kwsch/PKHeX/commit/9e16df49702852426bb0cbcb9bf40773206bbf00

@theSLAYER

5d ago https://github.com/kwsch/PKHeX/commit/5e65df675803995206e66877270327b438649904

There aren't any entered-character sanity checks, so cross-language incompatibility isn't checked.

https://github.com/kwsch/PKHeX/commit/15121c294594bd0e5d53a3e6e7f308406b41cb36

Ignore it if you aren't editing a SWSH save file / pk8 files. It should be hidden for prior format editing, but we missed it before pushing the last release.

Having duplicate/wrong tracker values wouldn't raise flags either? HOME auto-deletes cloned tracker value Pokémon when they're stored on your account at the same time. HOME auto-assigns a new tracker value if left empty. It's better stewardship to let HOME manage things rather than fail to trick it. Edit: As of time of edit, HOME tracker assigns a fresh tracker to any entries entering HOME, that bear a duplicate tracker when compared to an entry already in HOME.

Introduced in the middle of February, Pokémon HOME allows for transferring from Bank and Let's Go Pikachu / Eevee as a central storage site with connectivity to Sword & Shield. When a Pokémon is transferred from Bank or Let's Go Pikachu / Eevee or their games of origin into HOME, it is assigned a unique 64 bit number to differentiate it from other uploads. Pokémon that have not yet visited HOME do not yet have a HOME tracker. Pokémon that are traded in-game (online/local trades) do not get assigned a tracker. Pokémon that must travel thru HOME to reach the game it resides on must have a HOME tracker (origin->current). Pokémon that are uploaded in the same batch are not guaranteed to have a similar tracker (usually incremental). Trackers are only a concern in PK8+ formats. Pokémon that aren't yet in the PK8+ (2019) do not have a field for this data. What exactly is this value be used for? Storing data for each game visited outside of HOME (ex. SW/SH, PLA, BD/SP, S/V...) Tracking how Pokémon are traded between users. Detecting if a Pokémon has been modified/cloned from the original upload. Detecting if a Pokémon is newly entered into the HOME system (having a value of zero). HOME trackers will be changed each upload, so a tracker value is not a permanent value. Only HOME can determine if a tracker value is valid. Best practice is to let the server assign you a tracker, rather than assigning a blatantly wrong tracker. For local/online gameplay, GameFreak does not obsess over this metadata, so having arbitrary/lacking tracker values does not matter. Validating a HOME tracker requires API access to HOME, and is not something the hacking community will ever have access to; currently, GameFreak does not validate HOME trackers for online play. Due to the described behavior, here are our recommendations: When creating new Pokémon that are from generations prior to Sword & Shield, transfer into HOME via Bank first. When creating new Pokémon that reside in their game of origin, leave the tracker blank. When creating new Pokémon that reside in a game different from their origin set, generate them in their game of origin then transfer. When modifying any (that have already visited HOME) immutable values (PID, IVs, etc), zero out the tracker then transfer starting from their origin games. Why not create a random tracker value? Again, only HOME can determine if a tracker value is valid. HOME will check tracker values to see if the details match the original upload (modified data). HOME will check tracker values to see if the details are on another user's account (cloned data). HOME will disallow uploads if the tracker doesn't match the data on their server (error code 10015). Uploading to HOME without a tracker value will automatically assign a new one (note: only when entering from the correct game). You can receive Pokémon that lack a tracker value from other players via trade (in addition to a game's natives). PKHeX's default settings are to ignore missing tracker values (should be on every non-Gen8 origin Pokémon that is residing in Gen8+, etc), but has a toggle setting to opt-in for strict checking. This is to allow users to create the most-legal data without forging an INVALID tracker value, for in-game play.

Leave it blank on anything you create, and clear it for any clones.

Online Rulesets are different than raw legality checks.