Kaphotics

That space is currently used for legality triangles

Purchase the DLC legitimately.

Thanks, fixed on latest commit: Enhance H/W/S invalid messages, flag !255 alphas · kwsch/PKHeX@3a8bc58 Thanks, it's actually a GUI bug the invalid Ball you picked is actually being forced back to Poke, but it displayed whatever you selected instead. If you set it to a slot then re-view it, you can confirm the "fixing" of the GUI indication as it really is legal. I've added some logic to display the actual sanitized value (not the selection, if it was impossible), as well as added some logic to check for a specific case where the batch editor/external code managed to set an invalid BallHGSS value. Add Gen4 HG/SS ball check · kwsch/PKHeX@6e48294

PKHeX is telling you that there is no RNG frame that can hit the seed, because it checked every single frame against that 37%. It's an impossible-to-hit frame, aka illegal.

If you're running a Cute Charm lead, how do you trigger the encounter? There are no species that have the ability Cute Charm, that can also learn Sweet Scent. Without Sweet Scent, you must "randomly" encounter it. That is why PKHeX flags it; you cannot trigger an encounter to land on that PID/IV -- RNG Reporter does not check if a lead can exist for it. The "random" chance of triggering the encounter is 25% (boosting to ~37% via White Flute). See below snippets of PKHeX's code where it verifies the feasibility of "random" encounters. private static bool IsAbleToSweetScent(this LeadRequired lead) => lead is None // Pretty much anything grass. or IntimidateKeenEyeFail // Masquerain & Mawile or PressureHustleSpirit or PressureHustleSpiritFail // Vespiquen // Synchronize: None // Cute Charm: None // Static/Magnet Pull: None ; // BCC only allows one Pokémon to be in the party. // Specific lead abilities can learn Sweet Scent, while others cannot. // The only entry into this method requires an ability that has no species available with Sweet Scent. // Therefore, without Sweet Scent, we need to trigger via turning/walking. // With an area rate of 25, this arrangement will succeed 37% of the time. // The game checks 2 random calls to trigger the encounter: movement -> rate -> generate. // HG/SS has an underflow error (via radio) which can pass the first rand call for movement. // Only need to check the second call for rate. // Rate can be improved by 50% if the White Flute is used. // Other abilities can also affect the rate, but we can't use them with our current lead.

Not a valid dump; I don't think there's any save data in whatever you ripped.

Multiple missing sectors in your savefile, based on the save file structure. Sector 2 @ 02000 invalid. Sector 4 @ 04000 invalid. Sector 6 @ 06000 invalid. Sector 12 @ 0C000 invalid. HoF first sector invalid. e-Reader data invalid. Using the Gen3 Save Recovery tool: GitHub - projectpokemon/RecoverSaveGen3: Try and recover a Gen3 save file via console app! Pokemon - Leaf Green Version (Rev 1).sav.fixed

Read the first post of this thread. This thread is not for help when you've made edits to a Pokemon with the program, it is for legitimate things being flagged incorrectly. Z-A has RNG correlations and you cannot modify IVs without invalidating the PID IV+ correlation.

Meltan: fixed shortly after the previous release: Update EncounterStatic9a.cs · kwsch/PKHeX@61a13fd Hoopa: fixed just now, thanks for the reminder: Misc tweaks for Hoopa-1 plus flags · kwsch/PKHeX@85abb48

Crossposting OP's resolution for closure:

You overwrite the save file you opened, which is main.

The program gave you every hint possible. Look at your SD card and check the write protection switch. If you aren't able to figure it out, it should be an easy Google search.

NuGet Gallery | PKHeX.Core 25.12.21 You can write your own C# scripts and run them with LINQPad; you can aggregate all the donuts as you see fit with a dozen or so lines of code: const string path = @"D:\main"; var data = File.ReadAllBytes(path); var sav = new SAV9ZA(data); var donuts = sav.Donuts; for (int i = 0; i < DonutPocket9a.MaxCount; i++) { var donut = donuts.GetDonut(i); // interact with the Donut9a object }

The expected size is 0x309FA6, not 0x309F9E. Your save file is 8 bytes too small. Based on save file structure, 8 bytes different is assumedly "wrong" in that it can't be a missing block (a block is 4 bytes identifier, 1 byte type, then however many bytes needed for data -- 3 is not representative of anything, and not a 2-byte boolean array missing). If you transferred the same truncated save file back to the console, then the original (correct) size file is probably lost. Try backing it up again? Try saving again in-game, and transfer that file? If that still doesn't work, you can try private messaging me the file so I can see what is actually missing (truncation, or cheat codes corrupting the save data).