Hey, I've got a little quiz for all of you, Ready? Here it is: Which game was the glitch missingno in? I will reveal the answer when someone gets it

General
,
41

Did someone say Heavy Ball? :arrow_down:

2 Likes
42

Here is one I think is easy but I will ask in a cryptic way.

  1. I am a Pokémon.
  2. My original concept was to be the evolution of another Pokémon. I was made standalone.
  3. In subsequent games, mechanics were introduced that made my concept nonsensical.
  4. A reference to my original design intention is present in Pokémon Sun & Moon.

Which Pokémon am I?

Bonus Clue: My typing changed when I was made standalone, evidence for which is still present in my debut game.

43

baby kangaskhan

1 Like
44

Go on…

1 Like
45

Well im guessing it’s cubone but wouldn’t have got there without pfm lol

1 Like
46

cry

1 Like
47

@pfm @trainerjack You’re both right up on, so I will reveal. The answer I am looking for is actually Kangaskhan!

image

  1. Kangaskhan was originally an evolution of Marowak and carried a baby Cubone in its pouch.
  2. It was meant to be the thematic conclusion of Cubone’s weeping for its deceased mothers - which in this case referenced Kangaskhan. The skull it wears belongs to this lost evolutionary concept.
  3. Kangaskhan was originally ground type, which is why Giovanni uses a Kangaskhan on his team - the only non-ground type on his team.
  4. Kangaskhan come to “aid” when Cubone call for help in Pokémon Sun & Moon.
  5. This long posited theory was confirmed in the gigaleak development files, in which the back sprite for the lost Marowak evolution was included. The front sprite has never been seen.
  6. The Lavender Town “Cubone’s Mother” plotline may have been designed around this lost concept as well before being replaced with Marowak. But this is conjecture.

Obviously with actual baby Pokémon and breeding was introduced in Generation II, the Kangaskhan concept got pretty confusing and weird.

8 Likes
48

Phew!

Paraphrasing from Bulbapedia here:

In Crystal, a glitch corrupts the weights of Kadabra, Tauros, and Sunflora when they’re read for the catch rate calculation, and so these Pokemon incorrectly receive the maximum bonus of +40 to their catch rate. The reason it’s these specific Pokemon is because they have an index number divisible by 64. (Don’t ask me why that causes this glitch because I do not know.)

In Heartgold and Soulsilver, if a Pokemon weighs less than 204.8 kg, the game is then supposed to check if it weighs less than 102.4 kg to determine if the Heavy Ball will have a 0 or -20 added to the Pokemon’s catch rate. However the game instead checks if a Pokemon has a catch rate of less than 1024. Because no Pokemon has a catch rate that high, it means that every Pokemon that weighs between 204.8-102.4kg will incorrectly have a -20 catch rate modifier with the Heavy Ball instead of the 0 catch rate modifier they should have.

In every game, if a Pokemon’s catch rate is calculated to be below 0 when a Heavy Ball is used, it sets the catch rate to 1 so that there’s always a tiny chance that it will still work. However, in Sun and Moon only this was accidentally set to 0 instead. Beldum and the Tapus are the only Pokemon in the game who are light enough and have a low enough base catch rate that their final catch rate with the Heavy Ball is a negative number. This means it is impossible to ever catch these Pokemon in a Heavy Ball in these games.

4 Likes
49

This is awesome. I didn’t know kang was origanlly a ground type, but it makes a lot of sense. Thank you for the info!

1 Like
50

Thank you for the detailed response!

1 Like