xfr

Here is a list of restricted seeds that should lead to a shiny mew: In the Pokécheck database I have found the following restricted seeds on legal mystry mews: None of these appear in the shiny ones. If twig or Sabresite could have a look in their distribution saves to see if one of the shiny seeds appear on any mew, we could be able to confirm that this distribution (and probably similar others) cannot be shiny (either the program that made the mews into the save file skipped the shiny ones, or they were manually released after they were made)

Can you give a link to this pachirisu?

You can always try this code on linux

It seems contradictory but it's actually right - the trash byte message is about the \x0200\x0000 part, something expected on a pokémon hatched on HGSS but it doesn't matter if this part is from STARYU or STARMIE since the new name has the same or greater length.

I don't understand your problem - you get error 13266 when a pokémon is successfully recorded on Pokécheck, this does not indicate an error.

You get this warning when one of the encounter date is in the future or before B/W release, or when an egg was hatched before it was obtained from the daycare. Most of the time this warning is not a bad thing as it is typically found on RNG abused pokémon.

My mistake, you're right. Trading eggs works except to japanese and corean games, because I'm missing the character table used for nicknames in those versions. The problem will be fixed once I find screenshot of all the character tables in jp/kr versions of the game and add them.

Pokécheck is right again. Please only report pokémon which you know are legit and show up as hacked - if you know it's hacked then don't be surprised if pokécheck tells you it's hacked.

After discussing your problem with Bond697, we reached the conclusion that your PID must have been altered somehow. Did you catch those pokémon yourself or did you trade them? Were you using an action replay when catching them?

You're right abotu fossils, I broke their encounter check by accident but it should be fine now. I don't know about the PID problem for your white version, I need links to check them.

I was able to determine that there is an oddity in the pokétransfer character table. The － character (full width hyphen/minus) is used in previous gens to emulate ー, hence the translation table should have 00F1=ー and all pokémon containing － were incorrectly translated. On an unrelated note I am still looking for someone to pokétransfer the two above pokémon and upload the result.

Thanks for reporting the problem. I already know the "ー" is at fault but I'm waiting for confirmation by Guested to be sure your pokémon has the correct transfered name or if all poketransfer programs are wrong.

Thanks a lot, this unfortunately confirms my fears. If I can abuse your help one last time, can you send two more with 4 and 5 character long names? You can use pokécheck or pokesav, both work fine.

Thank you cuber, this is quite helpful. I'm having problems with D/P japanese trash bytes as they don't seem to be consistent. If you could send a different hatched pokémon (unnicknamed) that would be much apreaciated.

All generation 4 eggs hatch with trash bytes - even if you nickname the hatchling. However, there's a catch - like pal park trash bytes, they are different across languages and versions. The goal of this thread is to find the string of trash bytes for all versions and languages of generation 4 games. For instance, english games use the following: D/P: \0237\4008\C019\50C8\020D\3B28 Pt: \0238\4008\C019\B318\020C\3730 HGSS: \0000\1960\0211\0002\0000\4008 French D/P: \0000\0237\4008\C019\5124\020D\3B28 Pt: \4558\0238\4008\C019\B3BC\020C\3730 HGSS: \0000\0000\1980\0211\0002\0000\4008 German D/P: \0000\0237\4008\C019\5124\020D\3B28 Pt: \4558\0238\4008\C019\B3BC\020C\3730 HGSS: \0000\0000\1940\0211\0002\0000\4008 Italian D/P: \0000\0237\4008\C019\5124\020D\3B28 Pt: \4558\0238\4008\C019\B3BC\020C\3730 HGSS: \0000\1960\0211\0002\0000\4008 Spanish D/P: \0000\0237\4008\C019\5124\020D\3B28 Pt: \4558\0238\4008\C019\B3BC\020C\3730 HGSS: \0000\0000\19A0\0211\0002\0000\4008 Japanese D/P: Last 8 bytes not consistent (FF otherwise) Pt: Last bytes not consistent (FF otherwise) HGSS: \FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\FFFF\0000\???? Korean D/P: \0000\0000\C0D4*\0237\4008\C019\0E1C\020D\3730 Pt: \0000\0000\54F4\0238\4008\C019\BDE8\020C\3730 HGSS: \DE60\021D\0000\0000\2360\0211\0002\0000\4008 Note that for english only the last 6 bytes matter because all hatched pokémon have at least 4 characters in their name. For german and french, it's 7 and 8 for japanese. What I am looking for is .pkm files of french, german, italian, spanish, japanese pokémon with the shortest possible name length (e.g. Claffa in japanese and german, ekans in french, otherwise seel/abra/natu/onix/jynx) hatched on a generation 4 game (and preferably not transfered to gen 5 as it removes the last 2 bytes). If the pokémon was nicknamed when it hatched it doesn't really matter as long as the nickname is at most as long as the original name. You can also check the trash bytes yourself in Pokegen. Furthermore, gen 4 trash bytes are not considered to be important from a legality standpoint because they are unfortunately removed by the name rater. However, it seems even the name rater can leave some trash bytes of its own for short names. Hence, I am also interested in foreign pokémon that were given a 1 letter nickname by the name rater, in all versions and languages of gen 4 games as before. I thank in advance anyone willing to help.

Ironically giving a gen 5 pokémon a valid type 1 PID is the best way to make it appear hacked.

Those were probably obtained by action replay modifier. They are not recognized as hacked because there are no encounter (location+level) checks for generation 4, and since the catch location AND encounter level are deleted during transfer to gen 5 it is very difficult to check previous gen encounters without making many legitimate events or special cases illegal, like all the pokémon ranch stuff. In other news I fixed Giratina-O and Skymin (the stats, abilities and moves, not the sprites).

Alternate forms like Skymin or Giratina-O are not supported yet. The form exclusive moves/abilities/stats are not recognized.

The main problem is that you need to have 9300 pokémon on the same save just to get a 1% probability of two sharing the same pseudo random PID.

Thanks, this was fixed. To answer your question there is no limit on the number of pokémon you can have. On a completely unrealted note, I noticed you are reusing the same seeds for different RNG abuses. Although this is not surprising given there aren't many seeds that give the spread/nature/ability you want it's not a good practise since it leads to pokémon getting the same PID.

That's because of the privacy settings, it's explained in the FAQ. You can make the pokémon private to disallow anyone from seeing it, public to allow everyone to see all its stats/legality analysis/download/export and the default is what you experienced - can see stats except part of the PID but not do anything else.

The legality checker tells you the ability is hacked because although it has its dream world ability, it is missing the HasDWAbility flag, in other words it should have byte 0x42 set to 1. It really shows how pitiful the random wifi checks are to not detect this.

Flare Boost is in the list of abilities in version 3.0b24. It's not in 2.312 since the ability was introduced in gen5.

My mistake. TOGEPI (1).pkm TOGEPI.pkm

I repeat my answer, the linear congruential and block shuffle algorithms are the same in gen 5.