Myth about cubone.

T

The King of Nidos

Owner of a shiny Nidoking
Joined
Dec 29, 2008
Messages
1,090
Reaction score
0
I was on the internet minding my own business when all of the sudden I stumbled across a myth about Cubone being Kangaskhan's child and that it actually wears Kanghaskans skull. It then goes on to say that Marowak was actually going to evolve into Kanghaskan but that they took it out of the game.

Here is the link Cubone Myth

Please give me some feedback on this subject. Thank you.
 
I always thought the sprite was a funny thing to use as evidence. It's recolored and the head is entirely made from scratch.

I remember there being a logical explanation about the relationship between Missingno and Kangaskhan but I can't remember what it was, unfortunately.
 
The "Cubone myth" is just... something, not too different from a fanfic, of an apparently unknown origin but popularized by that /b/ thread.

It's nonsense. First, it assumes pokémon look similar to be related, in a generation with like five pokémon with the same face, pokémon that switched places, pokémon that evolve into things that look nothing like the original ones, etc.
Second, even then, Kangaskhan and Cubone/Marowak aren't even that similar.
Third... They actually do share the concept of parenting. Except, that's just in that Cubone is an orphan, and Kangaskhan have children-- Marowak doesn't have that parenting deal at all. By that rule, you could say it evolved from Chansey.
(Actually, saying that Kangaskhan evolved from Chansey makes even more sense. Egg -> Baby, the chances are none but there is at least a relation)


They are two distinct lines with different concepts. And certainly they didn't make any pokémon relating them when Kangaskhan is already very defined.

And if at some random point, in the distant past, ever they considered the idea of linking both lines somehow, the idea was thrown away almost immediately when they considered the implications that would have in gameplay and continued to design each line individually, setting them apart in case they weren't, and further redesigning them.

As for Missingno, while they did have ideas for 30 more pokémon, I'm sure either none of these ever made it into the games, or in the extremelly off-hand case one DID it was overwritten by other existing pokémon or random things eventually (they did run out of space, after all). MissningNo. isn't a real pokémon in the sense that it isn't "leftover data" nor anything. It is an error message for the game loading a random thing.


As for what the picture itself says... well, it just doesn't work that way. Saying a "Last minute change" involved redesigning two lines, reprograming them, etc, and that the deleted pokémon became Missingno, is like saying "The programmers screwed up and you can get Yoshi!!!11"


tl;dr It has many flaws, and the Missingno implications are just ridiculous.
 
Last edited:
If I remember correctly, there was going to be a baby Kangaskhan. They took it out, and the leftover data became one of the lesser-known glitch Pokémon (rather than Missingno.) I think it's called 'M.
 
Infinity Mk-II said:
The "Cubone myth" is just... something, not too different from a fanfic, of an apparently unknown origin but popularized by that /b/ thread.

It's nonsense. First, it assumes pokémon look similar to be related, in a generation with like five pokémon with the same face, pokémon that switched places, pokémon that evolve into things that look nothing like the original ones, etc.
Second, even then, Kangaskhan and Cubone/Marowak aren't even that similar.
Third... They actually do share the concept of parenting. Except, that's just in that Cubone is an orphan, and Kangaskhan have children-- Marowak doesn't have that parenting deal at all. By that rule, you could say it evolved from Chansey.
(Actually, saying that Kangaskhan evolved from Chansey makes even more sense. Egg -> Baby, the chances are none but there is at least a relation)


They are two distinct lines with different concepts. And certainly they didn't make any pokémon relating them when Kangaskhan is already very defined.

And if at some random point, in the distant past, ever they considered the idea of linking both lines somehow, the idea was thrown away almost immediately when they considered the implications that would have in gameplay and continued to design each line individually, setting them apart in case they weren't, and further redesigning them.

As for Missingno, while they did have ideas for 30 more pokémon, I'm sure either none of these ever made it into the games, or in the extremelly off-hand case one DID it was overwritten by other existing pokémon or random things eventually (they did run out of space, after all). MissningNo. isn't a real pokémon in the sense that it isn't "leftover data" nor anything. It is an error message for the game loading a random thing.


As for what the picture itself says... well, it just doesn't work that way. Saying a "Last minute change" involved redesigning two lines, reprograming them, etc, and that the deleted pokémon became Missingno, is like saying "The programmers screwed up and you can get Yoshi!!!11"


tl;dr It has many flaws, and the Missingno implications are just ridiculous.
Click to expand...

Ah I see. That makes much more sense. I guess it is true that you should never trust anything you read on /b/.
 
Why is it that my theory always get's mixed with Missingno.? It has nothing to do with missingno. and any one who knows anything about Pokemon glitches could tell you that.

Gezz.....

And why is it that nobody knows I created it? I mean, I talked about it on forums for over two years and I made a video about it. And yet everybody is more familar with the /b/ thing. *sigh*.
 
Last edited:
coolcatkim22 said:
Why is it that my theory always get's mixed with Missingno.? It has nothing to do with missingno. and any one who knows anything about Pokemon glitches could tell you that.

Gezz.....

And why is it that nobody knows I created it? I mean, I talked about it on forums for over two years and I made a video about it. And yet everybody is more familar with the /b/ thing. *sigh*.
Click to expand...

The games are over a decade old. I read that theory back when I was a kid, so there's no way you were the first person to ever put it out there. Not implying you copied it off of someone else, you could have easily just come up with the same idea on your own, but it certainly was around long before you did. :/
 
Pomegranate said:
The games are over a decade old. I read that theory back when I was a kid, so there's no way you were the first person to ever put it out there. Not implying you copied it off of someone else, you could have easily just come up with the same idea on your own, but it certainly was around long before you did. :/
Click to expand...
Yeah, but it just so happen to become pretty popular only a month after I posted my video. Why is it that it only became popular then?
 
coolcatkim22 said:
Yeah, but it just so happen to become pretty popular only a month after I posted my video. Why is it that it only became popular then?
Click to expand...

I have never met anyone ever that didn't know that theory and played the first generation of Pokemon, tbh. I've never even heard of your video, or seen anything linking to your video, or seen anyone talk about your video, or even know what's on it, lol. This theory has been popular as far back as I can remember, it's like "find Mew under the truck after beating the Elite Four 99 times", it's just a part of the fabric of Pokemon lore.
 
It doesn't matter who came up with that, chances are more than two people did.

Actually, it's two theories: One about Cubone being related to Kangaskhan (As the /b/ threads calls common knowledge on it). The second is the one that the thread comes up with about Missngno and all that.

The first one that relates Cubone to Kangaskhan is pretty flawed. They are quite distant in concept and not enough points to link them nor at the right places. Though it works in fanon, it isn't a real thing.

The /b/ one that implies the existence of another pokémon, that was deleted and became Missingno, is just your usual MISSINGNO PROSSES YOUR GAME'S RIB.
 
But wasn't Missingno. the result of storing data in the wrong place?
 
The fact that the mother died is just recalling Lavender Town.
That Marowak was the mother of all Cubones.
___
I I
-
 
maybe cubone was supposed to be kangashan's baby but early in the game they wanted something with team rocket and there wasnt enough connection
 
Unlikely as it may seem, the connection between MissingNo. and Kangaskhan makes sense, and is somewhat based on fact. You see, MissingNo.'s evil twin brother 'M, who is often mistaken for MissingNo., evolves into a Kangaskhan at Level 0. But in that case, they should still credit it to 'M, not MissingNo. They are different entities.
 
i just can't believe this... just doesn't seem reasonable enough to me i guess. but then again, the world may never know!
 
I thought about this too. It's interesting if: Karakara -> Garagara -> Garoora is true. I noticed the names; they're similar. Also, these Pokemon are found at the same place in the game, are they not? The problem is that Garoora/Kangaskan is not ground-type, it's normal-type. But in Red/Green/Blue boss Sakaki (encountered 3 times) has only ground Pokemon + Garoora. If the myth is true, they must have changed the Type (and Pokemon no.) before release.
 
Although the Cubone->Kangaskhan myth is fake, I've always wished it was true.
It would just make sense IMO if it was true, cause I to this day feel confused every time I see a Kangaskhan hatch from an egg with a baby in it's pouch.
Let's face it, Cubone and Marrowak have a very close looking sprite design as well as color scheme to Kangaskhan, and let's face it the lore about Kangaskhan protecting it's baby so carefully and then Cubone missing it's mother so much that it wears it's mothers skull, just seem to fit so well together.
Even if it wasn't the original intention of Game Freak, I admit that it would be better if Game Freak did make it that way.
I to this day say that Cubone should have an Alternate evolution into Kangaskhan.
 
Nah I don't think this myth is true.
Though I wonder how baby kangaskhan gets bigger. If it's through evolution, then the little one should also have some name.
 
Please note: The thread is from 14 years ago.
Please take the age of this thread into consideration in writing your reply. Depending on what exactly you wanted to say, you may want to consider if it would be better to post a new thread instead.
Back
Top Bottom