20 Mind-Blowing Things You Didn’t Know About Pokémon
2. Kangaskhan's Baby Was Going To Be Its Own Pokémon
Kangaskhan is an absolute goldmine for rumours - they've been spreading around since its introduction in the very first Pokémon games. One that keeps cropping up is that Kangaskhan was originally going to be Cubone's final evolution, but it was scrapped at the last minute and the unused code became MissingNo - but this rumour has been debunked.
What is clear, though, is that the two were very definitely related in the initial game concepts. From early designs, Kangaskhan babies were originally going to be a separate Pokémon to the mother. If the mother fainted a set number of times, she would die - and her baby would take her skull and evolve into a Cubone, rather than into a Kangaskhan.
The idea was removed just before the game's release - it was apparently too difficult to program - but rumours are still flying around.