Ruby Genseki

Which ones do you have left? If there are any that you're unable to correct yourself, as theSLAYER said, upload the files. And, as a tip, if you're making some other Mon look hatched, make sure the "Egg received" date is not more recent than the hatched/transferred date. A mismatch like that doesn't necessarily make'em illegal, but still looks fishy and I've seen many people overlooking it.

Due to the PID type, the easiest way to solve your issue seems to be making it look hatched: Though, if you wanna make it a wild encounter in order to keep the Great Ball (as a gen 4 hatched Pokémon can only be in a regular Ball), you can use RNGReporter and generate a new PID. IIRC, the gen 4 wild PID method is the default one (Method 1). Anyway, here's the corrected file: 429 - Mismagius - D40F8ABCECCA.pk7

I've been looking for the same thing every now and then, but haven't had any luck so far. The game's coding seems to be too tightly encrypted, so not many hackers are interested on it.

The latest version is the 17/10 one, right? That's the one I'm using.

This is something I found out just now. When a shadow Pokémon has been already purified, and it is then edited in PKHeX, it reverts back to being shadow in-game again, even if the heart gauge is set as 0 and the "Shadow" flag is unchecked. Of course, since the heart gauge is still 0, all it takes is going to Agate Village and re-purify it in there, but since I was too lazy to do that (and I'm in the middle of the story so it'd be kinda anti climatic) I tried solving it via HxD. Succeeded, so, if it's of any use, here's what I got: This is how the affected Pokémon looked when re-shadowed: *The heart gauge status is determined by these 4 bytes. As you probably know, hese values vary depending on the in-game heart gauge. These are the values of a shadow Pokémon that's ready to be purified. Here's the file, if needed: 156 - Fuji - 4DEBB64B197C.ck3 And this is the exact same Pokémon when purified: *These "purified" values seem to be the same, regardless of the species. The Pokémon used on this example is a Quilava. File: 156 - Fuji - 6FFCB64B197C.ck3 Pokémon XD seems to have some trouble as well, as any edit on this matter will have no effect in-game and trying to do it seems to cause a bug on the snagged/purified count. Haven't found out anything about it.

Even if the location matches, the origin game would make them illegal anyway. They're just a nice thing to have on a collection, this kind of stuff is somewhat valuable to me

Oh ._. derp Never saw that thread (even though I had been lurking for quite some time before actually creating an account), so didn't know about that

Didn't even remember that version existed ._. well, that solves everything, I guess (Still wanna dump the actual Totem Pokémon tho)

Ok, managed to totem-size a Raticate of my own. This is what I have to point out about this: The changed offset is 1D. This offset is actually the one determining the gender and forms of any Pokémon. Shininess is excluded since that's determined by the PID (that's why I was able to keep it shiny). The value changes I made were: -10/11: Turns it into an Alolan Totem-sized Raticate (M) -12/13: Turns it into an Alolan Totem-sized Raticate (F) -14/15: Turns it into an Alolan Totem-sized Raticate (Genderless) These changes occur regardless of the Raticate's original size, form and gender. Each totem Pokémon seems to have different values for this. As a result, when trying to use Raticate's values to resize other totem-compatible species, they became somewhat buggy in PKHeX and didn't have any visible changes in-game. As you might be able to tell from my previous point, in the game's coding, these are not just automatically resized models, but completely different forms, and thus, no other species besides the 8 totem Pokémon can be resized like this. ...But I think we ended up getting far too off topic.

Oh, I was gonna try the same thing right now xD

Well...I wanted to see if I was able to dump a totem Pokémon and keep it big-sized, so I started a new game, warped myself to Totem Raticate/Gumshoos's Den and inserted a Pokémon to my game as soon as I was able to save, started the battle and dumped the thing via HxD. Have the file if you want it: 020-02 - Raticate - 6593A77D77A0.pk7 You can insert it into your game via PKHeX. However, I do not recommend editing it since doing so will turn it into a regular Raticate.

They are! And, indeed, as you might tell, their boosted stats depend solely on their totem aura. This is the Totem Raticate (dumped from the totem battle) compared to a "common" alolan Raticate. Same level, nature and IVs:

The legendaries are something I've been hoping for since the game was announced, so I'm now really hyped about it. That, and Team Rainbow Rocket. Loved the concept (even though I don't like the name that much). Yesterday's trailer got me all fired up! The new photo feature seems like something I could enjoy, too. Specially with Pokémon that are totally unfit for such a "kawaii" feature, namely, Giratina. On the other hand, there's stuff I'm mostly indifferent to, such as the Totem-sized Pokémon (dobut they'll have any stat enchancement), the Ultra Wormhole minigame, or Mantine Surf (gee, they should at least let us wear some decent clothing while doing so, the riding gear is why I avoided using ride Pokémon as much as I could) Also... The Mirage Spots legends in ORAS weren't shiny locked, so I dobut these Ultra Wormhole ones will be.

Yes, noticed after sending my reply xD as I said, forgot about these "fake item" Foongus/Amoongus, it's been so long since I last played gen 5. Seems to be an error indeed since there doesn't seem to be anything wrong with it but the "Unable to match encounter" thing. So, @Kaphotics?

I have a question. Did you perhaps catch that thing on a hackROM? Say, for example, Blaze Black/Volt White 2? If you read the Bulbapedia link you attached yourself, you'll notice Amoongus in that route are supposed to be at Lv. 39, so, just change the met level to 39 in and it should be all right. [EDIT] Oh, nevermind, my bad. Forgot about the "fake item" things.

Thinking about it...doesn't that mean RNGReporter'd have to be updated in order to match this "unique" PID type?

Oh, well...I even considered the possibility of some bug in the game and since the illegal flag kinda bothered me I just restarted it in order to get a new pair! ^^U These new two are all right

-Not sure if posted on the right forum. Please move if necessary- So, I started a Colosseum game and as soon as I was able to save, I opened the file via PKHeX, only to find out both my Umbreon and Espeon are flagged as illegal when I couldn't possibly have edited them. About Umbreon, the program stated the typical "PID-Encounter mismatch". About Espeon, it's "Encounter conditions-RNG Frame mismatch". If needed, here are the unedited files: 196 - ESPEON - C245B6B1134E.ck3 197 - UMBREON - 0D43FC6BC225.ck3

Don't know if any of you guys already got it, but since jojo asked me some time ago I've been looking for that Battle Royal pre-patch Stockpile Shuckle, and today, I've finally encountered the damned thing. I wanted to post a screenshot of it using the move, but even though I kinda held back in order to give it the chance to do it, the thing just kept spamming Rock Tomb against me xD Anyway here's the file: 213 - Shuckle - FA8F6C74B3D6.pk7

Well, here's the thing as a .pk6 file 670-05 - Floette - 1C97EE6B2801.pk6 You can drag it to a slot on your team or in a PC box like this, and that's it. (It's no different from simply using the .wc6full, actually)

Not sure if you want it as a .pk4, but... you can convert this one to later gens anyway: 492 ★ - Shaymin - 0E9EB96B19DF.pk4 It's timid, and its IVs spread is 13/0/28/31/28/31

It's not legitimately obtainable at all. You can simply gen it and that's it, but it will be obviously illegal, and thus, you'd risk a ban if you were to use it online.

Well, my memory's never been that trusty, haha! Mine's a bit tricky I guess. I changed it recently, when I changed my in-game outfit, but the only visible difference is the top's color (which is barely visible due to the small portion that's shown and the purple on the newer pic being almost black anyway)