Wierd glitch from cloned Pokemon in X/Y?

Alright, so basically my sister and I were trying to clone my Groudon in Y in the wayBulbapedia says you can do it. But when we finally cloned Groudon, everything seemed fine, but when I tested it on a wild Flabebe on Route 7 (Groudon is level 86 by the way), instead of saying Groudon it said Skarmory and not only that, but Earthquake was super effective AND didn’t even KO the level 13 Flabebe.

I saved the game and turned it off, but later when I turned it back on, the Groudon was no longer in my Party. I searched all of the PC boxes but it wasn’t there, and my original Groudon also disappeared.

Well this was obviously a glitch, but I was hoping that someone could tell me why this happened?

Pleaselog inorregisterto add a comment.

There really isn’t a understandable and specific reason for this happening. All of your answers lie in the code of the game and with the data that was affected when you stopped the trade.

The most likely reason for the buggy Groudon is that it was cloned improperly; you didn’t perform the glitch correctly. I can’t really go into specifics since I’m not a programmer, but the timing must be very precise for things to run smoothly as the game sends the Pokemon’s data to the recipient, as Bulbapedia mentioned:

Most Pokémon will clone at aboutthree seconds, although it has been observed that some held items impact the time taken to clone.

Since the game received what was essentially glitched Groudon, strange occurrences like these shouldn’t come as a surprise. This is probably why Groudon appeared as Skarmory and explains why the real Groudon disappeared. The level 13 Flabebe surviving the Earthquake is most likely a bug with Groudon’s Attack stat (again, because it is glitched), or a bug with the game that caused it to calculate the damage improperly, which would also explain why it was super effective. Of course, it could have been a bug with the Flabebe, but I find it easier to believe that the problem was with the Groudon.

Again, it is impossible to give you a specific and definite reason, but what we do know is:

Try going back to your game and checking that it still runs normally. If it runs normally, it was probably just the Groudon or a temporary bug. If it is still glitchy, then clearly the Groudon or your attempt to clone it has damaged something in the game.

Cloning in itself is a glitch, so weird glitches like that are bound to happen.

Only someone who looked at the code of the game can tell youwhythis happened, just try cloning Groudon again and see if it works. if it doesnt, your Groudon is “uncloneable” for some reason.