Because the franchise is fresh on everyone's mind with Pokémon Go
And more importantly, why they happen
I think this is a really good case study about a complex piece of software that tries its best to work on very limited hardware. We take a lot of features on modern hardware for granted.
While not directly applicable to what we do here, some exploits do share similar vulnerabilities to known exploits in PHP, like so:
http://phpsecurity.readthedocs.io/en/latest/Insufficient-Entropy-For-Random-Values.html
Probably the most popularly known glitch, lots of people know it exists but probably not why it happens
The tens-digit is trying to represent a number in base-16 but is just trying to use the sprite data a few blocks after '9' instead of the letter 'F'
In short: the game reads memory it shouldn't and interprets it as valid data anyhow.
A: Golduck
B: Hypno
C: Golbat
D: Mewtwo
E: Snorlax
F: Magikarp
G: Missingno.
H: Missingno.
I: Muk
J: Missingno.
K: Kingler
L: Cloyster
M: Missingno.
N: Electrode
O: Clefable
P: Weezing
Q: Persian
R: Marowak
S: Missingno.
T: Haunter
U: Abra
V: Alakazam
W: Pidgeotto
X: Pidgeot
Y: Starmie
Z: Bulbasaur
a: Missingno.
b: Missingno.
c: Missingno.
d: Ponyta
e: Rapidash
f: Rattata
g: Raticate
h: Nidorino
i: Nidorina
j: Geodude
k: Porygon
l: Aerodactyl
m: Missingno.
n: Magnemite
o: Missingno.
p: Missingno.
q: Charmander
r: Squirtle
s: Charmeleon
t: Wartortle
u: Charizard
v: Missingno.
w: Missingno. (KABUTOPS FOSSIL)
x: Missingno. (AERODACTYL FOSSIL)
y: Missingno. (GHOST)
z: Oddish
#define NOT_SEEN = 0;
#define SEEN = 128;
#define CAUGHT = 255;
byte pokedex_table[151];
byte item_list[41];
byte missingno_pokedex_index = //some byte that's definitely greater than 151
pokedex_table[missingno_pokedex_index] = SEEN or CAUGHT;
No Gameshark, no external devices, nothing except natural in-game input
Not just for Mew, and not intended by the developers
http://bulbapedia.bulbagarden.net/wiki/List_of_glitch_Pok%C3%A9mon