In this run, MrWint uses a glitch involving the Coin Case to execute arbitrary code and finish the game 24 minutes faster than the previous version. As with his TAS of Blue Version, the entire input file was generated by a computer program that brute forced the game for optimal luck manipulation. The expansive testing done by the program is the reason for the astronomical rerecord count.

To see a run of a second generation Pokémon game that avoids corrupting the memory, click here.

This run is so glitchy that it's near impossible to follow what's going on without help; reading the author's notes is highly recommended.

To see a run of the first generation of Pokémon that doesn't take advantage of save data corruption, watch the movie of the Blue Version.

This movie improves upon its predecessor by never having to leave Ash's room to gain full control of execution flow. However, that movie has a very different kind of payload at the end, and is worth watching as well. Both movies apply the idea that TASing is programming input rather than playing the game. For a list of more runs that embody this idea, see this post.

As this run was submitted on March 14 - "Pi Day", it contains many, many references to π. See how many you can find!

This is an improvement of 9:00.78 over the previous run in this category, which used a similar glitch to the more heavily glitched categories. You might want to check out the run that avoids glitched warps for an example of quickly completing the game without corrupting the memory.

It is recommended that you read the author's comments to fully enjoy what's being done here.

This run improves the previous movie by 19.08 seconds, mostly by finishing the first level quicker by taking a shell and performing the pipe glitch death.

In this TAS of The Legend of Zelda: Ocarina of Time, the author aims to beat the game as quickly as possible. He achieves this by exploiting a large sequence break which involves "tricking" the game into warping Link directly from the Deku Tree (the first dungeon) to Ganon's Castle. Child Link then goes on conquering the whole castle without a single thought about becoming an adult beforehand.

Despite how quickly this game can be beaten these days, this run is almost two minutes faster than its predecessor thanks to new tricks at the Deku Tree and tower collapse sequence as well as many small improvements throughout the run.

This TAS was done using the Japanese version of the game. The reason for this is that the text is significantly faster than in the English version, which means that far less time is spent waiting for text boxes and cut scenes to end before getting back to the action.

The author's notes explain in great detail many of the things done in this TAS, which may be confusing to those who aren't familiar with Ocarina of Time speedrunning. Reading them is strongly advised.

Note: There are encodes of higher resolutions in the discussion thread.

In this game, the second most diabolical evil genius in the universe, The Dark Queen, has kidnapped Princess Angelica and Pimple - a battletoad. Rash and Zitz must save them by traveling through the most insane multilevel set of plans ever designed. This includes falling down huge shafts, racing through obstacle courses at breakneck speeds, riding on snakes through a massive maze of spikes, passing through a killer ventilation system, navigating through a missile defense system, climbing a never ending revolving tower, and much much more. Along the way, the Battletoads must also face off against an evil army of robots, genetically engineered rodents, and The Dark Queen herself.

In order to make the game a bit easier, its creators embedded some secret warp zones to skip a few early levels in their entirety. But that simply wasn't good enough for MESHUGGAH; he decided to travel directly to level 3, where he invents his own warp and skips right to the grand finale. He took a glitch found in this TAS and exploited it further, to the point the Dark Queen just gives up and returns Angelica and Pimple, going off to hatch an even more evil plan for next time.

This run conquers the predecessor movie by 0.18 seconds by exploiting the fact that green toad is processed before the yellow one.

Thanks to this new method of item glitching, this is almost exactly nine minutes faster than the previous version of the run.

The author wrote detailed comments explaining this glitch.

In this movie, the author, AmaizumiUni, abuses a bug that causes character inventory to overflow, corrupting the game's memory and triggering the credits early.

This movie saves over five minutes from its predecessor. This is because instead of playing multiple levels to reach a spot for the glitch, a new wall-clipping trick is used in the third room of the very first level.

This movie was also the result of an intense frame war that spawned over a dozen attempts and ultimately resulted in an improvement of over 3 seconds of the initial attempt.

This movie has two YouTube encodes. The primary version has deliberately glitched ending graphics, whereas the second one displays proper graphics. Both versions have identical input except for the last frame.

When "perfection" is defined as "as fast as possible", it requires some sacrifices. Indeed, this movie sacrifices a lot in the playability of the game. Full of tricks to pass through walls, tricks to avoid mandatory battles, tricks to pass through enemies relatively unharmed, tricks to acquire weapon refills in little time — there is very little in this movie left that resembles normal playing. Even death is used as a viable playing strategy that saves time. All of the tricks are still performed by the means of mere controller input, even though significant portions of the input were calculated by a computer program.

This movie is a considerable improvement of 3:04.39 to the previous movie; this is mainly due to a new technique which tricks the game into calling an 'end of level' object.

Of course, upon watching this movie, one does have to question something... is it Mega Man saving the world? Or Dr. Wily trying to save it from absolute destruction?

ForgoneMoose and sockfolder, by corrupting the save data, manage to corrupt the memory and go straight to the ending, totally skipping Richter and the whole second castle.

A 100% run covering the whole castle is also available here. If you prefer the main character to have muscular bare arms and to pray to the rain gods to defeat bosses, you may enjoy the Richter version. If you want to see a run on Replay mode that can skip many cutscenes, see this run. A run with clear save without memory corruption is also available here.

This run, a ten frame improvement over the previous version, abuses a glitch that was fixed in later releases of Pocket Monsters (Pokémon) that allows a player to warp freely through the world. Victory is achieved in a matter of minutes with this route. Normally, the game takes well over an hour at the fastest to finish.

To see a more substantial run of the first generation of Pokémon, watch this movie. For a less substantial run (which also demonstrates that they didn't fix all the glitches in later versions), watch this one.

And now, for something completely different. In this run, the authors, p4wn3r and Mukki, catch all 151 Pokémon and complete the game while only using what they call "light glitches", showing off much more of the game than seen in the other runs while still using many glitches to complete this goal much faster than the programmers could have imagined. For more details about the techniques used in this run, and for their definition of what constitutes a light glitch, as always, please read the authors' notes.

Spoiler: Hover over the screenshot.

In this TAS, pirohiko blazes through the game in under two hours using a host of tricks, glitches, and battle strategies. We recommend reading the author's comments for more information on the route used.

This is a completely new type of Super Mario World TAS. It beats the game by jumping to the credits from one of the two levels available from the start, Yoshi's Island 2. This happens because a glitch involving stunning a flying question block allows manipulating the code being executed by changing the position of sprites.

This run is 56.50 seconds faster than Masterjun's previous movie. For those who love to read the technical specifics of such runs, there are detailed author's comments about the new method used here. Suffice to say, 8 controllers are required to get this to work.

If you want to see more movies like this, let this post be your guide.

A technical explanation is available on the submission page.

This movie was famously played back on a real SNES during the speedrun marathon AGDQ (Awesome Games Done Quick) 2014:

• Ars Technica
• ExtremeTech

Here, the author, Masterjun, abuses a glitch that results in corruption of the egg list. This confuses the game and causes it to jump to the SNES CPU registers and start executing arbitrary code, which triggers the credits.

There is also a run without game-breaking glitches and a 100% run.

Exploiting this glitch instead of just using a warp glitch to get to 6-8 quickly saved over 3.5 minutes over the previous movie.

In this movie, amaurea, cpadolf and total travel to the Lower Norfair region much sooner than you would normally be able to in order to use a hidden debug code to obtain beams and weapon ammo. After this, they use a glitch to trigger the ending credits around seven minutes faster than the previous fastest completion of Super Metroid. For more details, see the run's comments and discussion thread.

We have many movies of Super Metroid on this site. Among them are runs that complete the game using the X-Ray glitch, using no heavy glitches, aiming for the lowest legitimate ingame time, backwards, and while collecting 100% of the items.

However, due to an inventory corruption glitch, the author decides to take the quick route and skip over almost the entire game. See the author's comments for more information.

The primary encode for this run has subtitles from the author as well. If you want even more information available when the run is playing, see the author's own encode with subtitles, memory watch and map on YouTube.

For more Wizardry runs, see the first game, the second game, and the third game.