theSLAYER

What Windows version are you using, XP?

something in the post probably tripped the word filter IB uses. I'm gonna try setting something for your account that prevents that. Should be live in 5 mins edit: should be live, give it a try

How did it end up locked. I'm guessing you did an edit, and it tripped up InvisionBoard's word filter or something. We don't get approval notifications for those, so do let us know next time if such a thing happens again :3 (Tho best would be to find which word is tripping the filter, then omit it in the future)

Oh, I thought it popped up after you loaded the save. Please check this page:

You can directly upload files and images to our site. Can you please upload the save?

That's because that option doesn't exist in Gen 1. The Magikarp were probably received from trade. There's nothing real special about it, I say let it go.

Based on what you want, the catch rate on your "invalid" file is wrong. Weedle and Kakuna have different catch rates. As I said with my earlier example, specific to Gen 1 mons, PKHeX can determine (or guess) the encounter based on catch rate. In your case, specific to this example, with these values applying to untraded to Gen 2 mons: Catch rate 255 -> Caught as Weedle Catch rate 120 -> Caught as Kakuna. No way a Beedrill would have Weedle's moves if it is caught as a Kakuna. So while the game doesn't store met location, it does store the catch rate, which could be used to determine what the mon was when it was caught. Catch rate stored on the mon doesn't change unless you trade it to Gen 2.

The Japanese release is legal. As for newer events, read this: Anyway, no need to push/rush for a release. It'll be out when it is out.

mind attaching said beedrill?

And to add on, specifically for Gen 1 <-> Gen 2 trading, the Catch Rate may need to change. When trading from Gen 1 -> Gen 2, the Catch Rate data slot is usurped and used for Held Items. That is how some mons caught in Gen 1 come with Held Items. The game just converts the value in that datapoint to an held item. However, it is important to note some values in that slot don't correspond to a working item, so that game takes that into account and changes the value in that slot. So if such a mon was then traded back from Gen 2 -> Gen 1, the modified value is kept. TL;DR: For certain Gen 1 mons, if their catch rate is unchanged, it implies it was never traded to Gen 2. Read more here: https://bulbapedia.bulbagarden.net/wiki/List_of_Pokémon_by_wild_held_item_(Generation_II)#Generation_I_held_items

In this case, they need to be thoroughly zeroed out.

To clarify, the datapoint HT/WT doesn't exist in USUM. And HOME doesn't add data to it when you transfer up.

Yeah the OT name was missing. I'm wondering if it is a remnant from you trying to change the OT name or something.

Was the egg's OT name originally blank? Did you make this egg from scratch or received it in-game? Writing an OT to the egg in current stable PKHeX doesn't stick. I had to modify the pk3 with Hex editor for the egg to show up legal. I wrote the line into PK3 via hex editor

Just a reminder to readers: this applies to Gen 3. The encoding/characters format changes in other generations. I didn't apply your workaround. My egg is an egg I received in-game on an ENG save, free from modifications. Relating to your "Asian encoding" statement, what you see is just a quirk with the Gen 3 encoding, or maybe I should say it is a quirk with eggs for how PKHeX chooses to display them. The encoding table for Roman characters between both International and Japanese games are the same. It is just that PKHeX parses them differently based on the language selected on the Pokemon file. They are not actually encoded as "Asian" characters by themselves. The way they appear changes based on language byte. (remember, Eggs in Gen 3 games come with JPN set as the language byte) My Egg examples: In-game caught Pokemon: Notice how despite they appear different, the bytes are actually the same? The issue here is with your OT name. Why does it start with a terminator? There's data after the terminator, implying there other characters. (Characters U, T and R) So let me ask again. Was the OT removed? What was the OT of the save that received the egg? :3 I'm curious. Did you delete the name? Maybe it bore other characters and PKHeX yeeted them? Maybe the other OT characters don't go into an egg before it hatches? Need to know what is your OT name, and whether this egg was modified before extraction. Perhaps provide your save so I can take a look.

not every mon can have random IVs. You probably edited mons that bears PIDIVs relationships. Depends on what mon you edited, but those need to be fixed one by one (or just revert to the old IVs)

So I just did a test on some random's game: The original OT still exists. Oddly your file doesn't have an OT. Was the OT removed? What was the OT of the save that received the egg?

mind uploading the file for me to take a look?

Yeah, if you had an account you could request for one then check the expiry (it'll probably be mentioned in the mailer). Welps.

Do you have an account? It doesn't indicate when the code expires

@SkyLink98 thanks for compiling the dates and the links. There seems to be a little error with France, Netherlands and Ireland; as far as I can tell, they end on the same date as UK. Also, it appears Spain site bans non-European IPs. In the mean time, I've updated my table, and added them to webarchive

If a mon was never traded to Gen 2, it cannot have a move removed. There is no move deleter in Gen 1 How PKHeX can recognize "was it traded before", is by checking the Catch Rate. Certain Catch rates change value when traded to Gen 2 and back, due to how some values don't match up held items in Gen 2, so Gen 2 changes them to proper held items upon receiving them. Try dragging your Venusaur between 2 PKHeX windows, one for Gen 1, and one for Gen 2, you can observe in real time.