23 January 2016

Pokemon glitch and Built to Spill videos of the week: Foundational Importance

There are three types of people in the world. The first type are people who, by either generational difference or  general lack of interest, know nothing about Pokemon at all. The second are familiar with Pokemon. The third are "Pokemon people". Pokemon people are like above average drivers: there are many more claimants than actual members of the group. Unlike being an above average driver, being a Pokemon person is not, in truth, a really a desirable social status. You can recognize a Pokemon person when they enter a conversation wherein type two people are referencing Pokemon in some superficial or nostalgic way. A Pokemon person will derail the conversation with details of the glorious couple months when they were an operator in a Pokemon-related IRC channel. Pokemon people necessarily know the controversy surrounding Blizzard's freeze rate. The second type of people can probably parse the aforementioned sentence, but are baffled by the implications. The first type of people have skipped to the Built to Spill video or more likely stopped reading all together.

All this is relevant because the following glitch video touches on something so iconic that it's likely, in my mind, that a type two person would recognize it entirely.

Pokemon Blue - Missingno. and 255 Mewtwo! (video by TheCheatMaster) HORRIBLE TECHNO WARNING: MUTE RECOMMENDED
This is the item duplication/over level 100 Pokemon/MissingNo. glitch. I think it's sort of unusual for a game to have a well known glitch. Maybe I'm overstating the well knownedness, but this is the type of thing that I'd expect anyone who played classic Pokemon to be aware of.  It has a a Wikipedia page. This glitch is so well known that it's hard to find a good Youtube treatment of it. It's just that ordinary. There are more videos of people sitting near the backs of buses and recording the engine sound.*

I'm sort of fascinated by the epidemiology of this glitch. I remember being a young kid in my parents' basement watching my friends playing Pokemon. I was reluctant to play it; it seemed like a really popular fad and I avoided such things with pathological zeal. But on this day I was testing the waters a little bit and asked my friend what Pokemon he was using as he slew his opponent's Pokemon with what appeared to a garbled collection of pixels. He said it wasn't really a Pokemon, but a glitch.

This sorta blew my mind. How did this glitch exist so stably within the game?  What was it meant to be? Was this cheating? How'd he figure out how to get it? This was in the days where the internet was something used primarily by academics and accessed via modems. This thing spread kid to kid, the old fashioned way.

A couple months later I started playing Pokemon, deciding that it was actually quite a compelling game, and got pretty deep into it. I was reluctant to perform this glitch; I had decided that it was cheating and I would not do such things. Nonetheless, I was fascinated with it. There seemed be an aesthetic rightness to it, almost a sense of intentionality. Yeah, you were performing a set of seemingly arbitrary actions but there was a sense of balance to it. You might encounter MissingNo. and get a huge number of your sixth item, but you could also encounter some extremely high level Pokemon and get mauled by it. There was reward, but it was coupled with risk.

I theorized about this glitch. Based off of the experiences of my friends it seemed as though you would encounter either MissingNo., a nearly identical glitch in which the only decipherable characters were 'M, either an Electrode or Magnemite at some level over 100 depending on whether you had Pokemon red or blue, and an arbitrary Pokemon over level 100 that seemed locked to the specific cartridge. My friends didn't really share my interest in this speculation, but were more keen on duplicating Masterballs to catch Pokemon and Rare Candies to level them up.

My interest in Pokemon waned over time, but the changes in the times conspired to reverse that. When my parents upgraded from dialup to cable, I found myself exposed to an abundance of information about all facets of Pokemon and my interest in it was rekindled. I found my theories, as logical as they seemed, to be invalidated. Those over level 100 Pokemon, and MissingNo., and 'M were determined solely by the trainer name. Namely, the second and third, fourth and fifth, and sixth and seventh characters formed pairs that got interpreted as a level and Pokemon, respectively. My friends, named Brian, Jon, Allan, and Jason, all had Ns at one of those critical locations. Only Allan had the blue vesion, and coincidently happened to use lowercase characters to spell his name. Of course, the uppercase N corresponded to the identifier for Electrode and lowercase N corresponded to Magnemite. The other characters corresponded to the other Pokemon and MissingNo.s. The character signaling the end of the name created 'Ms.

That sated my curiosity, but only partially. Why one would encounter MissingNo. was no longer mysterious, but the nature of it continued to be strange. Why did just encountering it duplicate the 6th item? Why were its stats and moves so weird? Those mysteries were not resolved until much later. They're fairly interesting, but in the Pokemon glitch narrative, where each glitch builds upon an earlier glitch to enable future game manipulation, the whys of MissingNo are not actually not that important. It turns out the most important element of the glitch is the fact that MissingNo. increases the amount of the 6th item by 128. While my childhood friends had their Masterballs and Rare Candies, future glitches depend on its ability to create arbitrary amounts of any item. But why that's important is a topic for another week.

Built To Spill - The First Song - Philadelphia, PA - 11/2/2013 (video by noochnooch)
MissingNo. is well known, this song probably not so much. MissingNo. is the first of a series of Pokemon glitches, in a way, and this is the first song off the first Built to Spill album, and it's called The First Song. The connection is tenuous, but I absolutely love this song. I think I was looking for a decent quality full Built to Spill live show to have in the background while working and came across this show in Philadelphia. This was the first song of the set and I was utterly transfixed by the introduction. It took me awhile to place it, and I definitely listen to The First Song, and its containing album Ultimate Alternatives Waivers as a whole much more often now. All I can say is "Aw thanks".

Part of what I like about this performance is that the band takes a song that on the album seems like a bunch of guitar parts spliced together, sometimes rather roughly, and performs it lives with what seems like effortless coordination between the performers. I also like that the song is about difficulty about being able to express ideas through language, and by reading this, you are painfully aware of how strongly this resonates with me.

https://youtu.be/d2ZVDzq-iPw is a reasonable starting point

No comments:

Post a Comment