• Aims for fastest completion
  • Heavy glitch abuse
  • Manipulates luck
  • Doesn't corrupt save data
Emulator: VBA-rr v20, it doesn't sync on any other version
Well, I was bored and decided to improve the published movie by 10 frames.
The rival battle could've been faster. In fact, when I started the run, I improved it, but getting to Viridian in less frames got me terrible randomness. I need to encounter a Lv2 Pidgey to do the glitch optimally and the way the RNG works, I couldn't get it without a massive loss of frames in that occasion. So, I left the battle untouched and improved the movie after it.
For those who are not familiar, Doko Kashira Door is one of the many Select button bugs that occur in the first japanese versions released, and is the fastest known way to complete the game apart from save data corruption.
I had to use v20 because it's the only version that emulates the glitch. This is unfortunate, because it doesn't have Lua scripting implemented, which could be used to shave more frames by manipulating a faster rival battle that generated good randomness for the wild pokemon encounter.

The glitch

Doko Kashira (where am I?) is a game-breaking bug on the japanese versions of Pokémon. It occurs because the programmers forgot to disable the flag for switching items or pokemon when the menu is exited in battle. This was fixed later in the (J) v1.1 release and subsequent (U) releases.
Because of this bug, it's possible to force a lot of garbage data into the game's RAM, making it go nuts. The trick abused here is to switch the 2nd item in your inventory with the first pokemon. That somehow destroys the end marker for your party and the game starts overwriting data in other portions of memory. The useful fact is that it decreases the map ID of the destination of certain doors everytime you walk four steps, this is used to get from the rival's house to Celadon and from there to the Hall of Fame.
This isn't everything about the glitch though, it may occasionally change the coordinates of a warp, change the graphics of a block of four tiles and remove their wall status, and sometimes the game may simply crash or KO your entire party.
In the run, the fight menu is clicked because it's necessary to avoid the game killing you. It's necessary to encounter a L2 Pidgey when doing the glitch. All other pokemon that appear there, except L2 Rattata, make the game crash when you take the shortest path back. Rattata's cry is longer than Pidgey's though, encountering it would make the run longer.

GabCM: Added YouTube module.
Flygon: Added point-based YouTube module, Mister Epic, you deserve that name, because you're friggin' epic! *hugs the epic Epic tightly* :3!
Flygon: Just some formatting related business regarding the modules, should look cleaner now.
Also, added download link for point encode, I encourage GabCM to upload my point upload to his Archive collection, as well as his HQ encode.

Nach: Accepting as improvement to existing run.
sgrunt: Since nobody else has apparently done a standard encode of this, I'll do so. Apparently I missed GabCM's encode. Either way, this will be published as soon as I grab a screenshot. Can't use GabCM's encode - it has a bad aspect ratio flag. I'll encode this myself as previously stated.

Spikestuff
They/Them
Editor, Publisher, Expert player (2305)
Joined: 10/12/2011
Posts: 6341
Location: The land down under.
Nice job on linking where the freaking post came from you silly goose. Post #386429 and Post #386494 And it should be noted again that this is: 1) Different Game Entirely 2) Different Glitch 3) Needs to be Jap version Accepted.
WebNations/Sabih wrote:
+fsvgm777 never censoring anything.
Disables Comments and Ratings for the YouTube account. Something better for yourself and also others.
Skilled player (1707)
Joined: 9/17/2009
Posts: 4952
Location: ̶C̶a̶n̶a̶d̶a̶ "Kanatah"
Spikestuff wrote:
Nice job on linking where the freaking post came from you silly goose. Post #386429 and Post #386494 And it should be noted again that this is: 1) Different Game Entirely 2) Different Glitch 3) Needs to be Jap version Accepted.
I got one question. What exactly is the vault even for if it's not the fastest time? People including me are already making jokes that its a dumping ground, and TAS'es like this that don't exactly belong to vault doesn't make it better. Can this move to moons at least? Edit: In case I get shot down again, I'm complaining it's placement on VAULT. I'm not complaining that this TAS exists.
Site Admin, Skilled player (1236)
Joined: 4/17/2010
Posts: 11274
Location: RU
It was put to Vault when the latter was just created, and no clear rules existed for it, only entertainment cutoff. Then, as the rules were worked out, a lot of auto-vaulted runs were mooned just because of incompatible goals. This one was not noticed, because it doesn't contain unvaultable movie classes that were used to find unvaultable games that were auto-vaulted. Another question is, was it known when this run was made, that the game can be beaten faster? Was the timesaver deliberately avoided? Because if not, it's pretty vaultable run then.
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
Editor
Joined: 11/3/2013
Posts: 506
feos wrote:
Another question is, was it known when this run was made, that the game can be beaten faster? Was the timesaver deliberately avoided? Because if not, it's pretty vaultable run then.
Well in that case it should be an obsolete movie, no? And AFAIK changing a movie's tier is far less controversial than retroactively obsoleting it.
Site Admin, Skilled player (1236)
Joined: 4/17/2010
Posts: 11274
Location: RU
thatguy wrote:
Well in that case it should be an obsolete movie, no? And AFAIK changing a movie's tier is far less controversial than retroactively obsoleting it.
I mean, if it was known to be the fastest when it was accepted, it can perfectly reside in Vault, even while being potentially obsolete (and as soon as there's a run with the save glitch - actually obsolete too).
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
Site Admin, Skilled player (1236)
Joined: 4/17/2010
Posts: 11274
Location: RU
To explain what happened to the movie.
Mothrayas (2018-04-06 23:03:39) wrote:
back when the first SRAM glitch run was published, it didn't obsolete the JPN door glitch run because it was considered "different enough to warrant a new category" (so not to obsolete the Green run), establishing that the Green run is no longer published as any%. The same SRAM glitch could be done on the Japanese versions - it's not exclusive to the newer releases. Actually, considering its rating and our present-day publication structure, it probably should be retroactively obsoleted now.
From movie maintenance log:
  • Mothrayas 2018-05-09 18:33:29 Changed tier from Moons to Vault
  • Mothrayas 2018-05-09 18:33:52 Changed obsoleting movie to #1958 from #-1 (wrong movie ID accidentally)
  • Mothrayas 2018-05-09 18:34:16 Changed obsoleting movie to #1123 from #1958 (proper movie ID)
If movies of both games used that save glitch they would look identical. So it's inevitable for Green and Yellow any% to get merged. The only step what was skipped was having Green "save glitch" obsolete Green "warp glitch" by pure speed. It wasn't a routing decision or a movie goal to avoid this glitch. And judging by Green's current rating, even if we view it as being deliberately avoided, Green "warp glitch" isn't entertaining enough to exist on its own.
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.