theSLAYER

Hi, I guess I was editing my post while you were typing this. Refresh the page and read the edit I made, thanks

The latest version of PKHeX already supports GO Shiny Dialga. Your GO Dialga must have the correct date. PKHeX verifies dates. The range is literally in the error message. Make sure dates and levels and other details match the encounter details. Also, rather than make things from scratch, import from the encounter database. Also ensure you're at the latest version. edit: I reread your post, and it appears the issue you have is with Sysbot, not PKHeX (as in NOT issues related to making a legal shiny Dialga on PKHeX), my bad. I'm keeping my old content up for context (maybe it'll help others) Anyway, we have no control over the various copies of Sysbot out there, after it was downloaded by server owners. The server owner has to update their own version of PKHeX.Core (and various DLLs) that Sys-botbase relies on, to get the updated legality checks. So your file is legal, and PKHeX is working fine. It is just that the server owners need to update their system that runs legality checks. Alternatively, find a server that turns off legality checks.

@flaming.brockoli Same junk. Are you perhaps launching the game through another app or something? If one were playing the game normally, it should not be this sized, and that's the only explanation I can come up with..

Based on what you said, and a look at the garbage data, I doubt you ripped the save out properly. Read:

I find it hard to imagine that the game would randomly edit that data into your block. Are you absolutely sure only you played the game? Maybe someone claimed it in your absence? Yeah if you could get PKHeX load the save, and dump the block, I could help with its removal.

No worries. I know how to do it. Dump the Mystery Gift Block, then hex edit it, to remove the entry. I then asked you why do you want to do it.

well what we said handles the file you uploaded specifically. for anything else it may need different solutions. Anyway for other stuff just import from Encounter Database, then mess with the stuff from there. Don't create stuff from scratch

that wasn't the file you uploaded don't know what you are trying to imply. What we referred to is the file you uploaded.

I don't know why you mentioned Encryption constant, when that's not the issue with this Ho-Oh. a) Mons obtained from Max Lair have a certain Dynamax level. Just max it out. b) Max Lair legendaries have a minimum of 4 Perfect IVs, so just max one IV out. You can choose it at random. c) For Max Lair Legendary, abiltiy is 1. Also as Kaphotics said, the PID/IVs/EC/HT/WT are correlated, however not checked by PKHeX at the moment. So it appears legal, but ain't legal. I don't think there's a tool that acts like RNGReporter and gives correlated stats for Max Lair mons yet.

@ghost. could you just upload the files that has issues? maybe like provide 3 different kinds obtained from different methods? not everything needs properly correlated ECs.

The only ways are a) make sure you truly own them (all their details match the save, origin game match the save etc) b) Progress far enough through the game. As I've said prior: Consider reading outsider Pokémon and obedience.

@ghost. To clarify, you can perform the act of creation in PKHeX, it's just that they are illegal, right? If so: looking at your screenshot, you're attempting to receive an egg at the train station, and hatch it by the nursery couple. That location data is completely wrong. Try reversing it. (See image I attached) PKHeX's error message of unable to met an encounter from origin game means there is no such encounter possible in the encounter game. It means the encounter is not known to exist. Which in this case, it means you hacked it wrongly. PKHeX is acting as intended. Image: Additionally, if you're trying to edit wild mons from Gen 8, keep in mind they have a known PIDIV correlation. What this means, is that you cannot haphazardly edit their PID, EC, Height, Weight. More reading relating to PID Mismatch: Overworld8 here. Edit: I've edited the title to reflect a somewhat more accurate representation of the issue. Your original title may give the wrong impression that the issue is with PKHeX. If so, that would not be true, as PKHeX is flagging due to incorrect details. Thus, it is working as intended.

@JovianGuard Bank and HOME has almost has no legality checks, so you're right about their checks being garbage. Bred Pokémon's egg moves follow a somewhat specific move order. You probably just haphazardly threw moves into the Egg Move section thinking that's enough. Let the PKHeX suggest moves, that should set it into the correct order. Alternatively upload the file here. Or just follow this image:

That's not an icon. Anyway, from what I can tell, there was no real reason for you to create another thread. If no one replied, just wait patiently alright? Since you're new, let me teach you about forum etiquette, don't go around posting multiple times asking about the same thing. Just wait for people to reply :3 Anyhow, I've merged your threads :3 Back to the question, yeah, you can edit your Mystery Gift Block, and remove the data via hex editing. The question is: why? There is no real need to do that. What is your purpose for wanting it deleted? Bringing this up just in case you had these thoughts: 1) You can receive another Poke Ball Mew, even if the record still shows in the gift album, as long as you buy another Poke Ball Plus. Explanation: This gift is set to be multi-receivable. For every ball you purchase, you can redeem another Mew from it. 2) Deleting the record won't allow you to receive another Poke Ball Mew from the same Poke Ball Plus you used to redeem this Mew. Explanation: think of the redemption as a one time serial code; the serial code was used when you redeemed it the first time round. Since it's a one time serial code, you cannot reuse it once it is used.

Icon? what icon?

If the Pokemon fully belong to you (OT name, OT gender, TID and SID same between mon and save), it would obey, regardless of progress. Make sure they fully belong to you. No. There isn't a byte that controls obedience. That's probably a leftover from when fateful encounter flag was called obedience flag in Gen 3. (To give context, back in those days, any Mew and Deoxys will never obey, even if you defeated E4)

your save is too big. it doesn't even look like a proper save, it just cuts of randomly. One other thing I would like you to try, is launch the game, go past the continue screen, then launch EdiZon (while the game is launched), then dump the save from there. What happens? Also, quick question, how are you transferring the save to your PC? Looking at your save in hex, The does seem to have a proper header (at least the copies I own have that same value infront). And while it's normal for SWSH saves to look like junk cause they're encrypted, I don't think the values BF BD is supposed to appear that frequently. It's like appearing, every other other byte.

I'm under the impression those mons you edited did not belong to the trainer of the save, and the progress of that save is not far enough. You want to edit "outsider's Pokémon" and have them obey? Increase your trainer progress. (Basically earn more badges/trial stamps) There's no other way..

If I’m not mistaken that roman characters in JPN/KOR games are full width, while standard Roman characters in International games are half width, so it’s fine.

It's not a secret, it's just not documented properly. If I recall correctly, for Gen 6, the Map ID needs to be copied to 2 specific spots. I'm unsure if Gen 7 has that "2 spots" requirements, as well as unusure if NPC/overworld data is required: Additionally, there may also be another value that checks/determine whether you're indoors or outdoors (includes caves and outdoor areas that are pretty much special routes, so fake outdoors), and swapping from an indoor to outdoor area may result in the black screen. I more or less don't recommend editing *only* the coordinates. Or at least try warping with similar enough areas.

someone need to properly document it. and then codify it.

PID type discovered for Gen 8. One can't willy nilly edit them.

@HollowMaster read this thread:

Just adding these cause I get asked a bit. These files use the CGB format. Can be imported via PKHeX > Cgear

well, trolls exist in every community, We try our best to vet cases based on proof and such, gather stuff from different sources whenever possible etc.