Zelda OOT is being beaten under 23 min as we speak

A new speed run glitch has been discovered and it's now possible to beat the game within 23 min.

Ocarina of Time any% speedrun in 23:29 - YouTube

It's actually 22:56 but not uploaded yet.
Zfg1 < he' trying to beat this to.

In under 23 minutes...? Wow.

I think the world record still stands at around 6 hours, but this is playing the game without any cheats/glitches.

Wow, that's interesting. Some people really are dedicated to this stuff.

Originally Posted by Eternal Legend

In under 23 minutes...? Wow.

I think the world record still stands at around 6 hours, but this is playing the game without any cheats/glitches.

With glitches/cheats, I think it's 2 hours.

I personally prefer the no glitches/cheats run of around six hours because of the endurance and more ability to make mistakes, but both are really cool, and I admire the dedication.

What.

I.

What.

But he was like.

Just killed Gohma but then.

Suddenly Ganon.

I.

What.

Can someone more familiar with this stuff let me in on a few things? Like why was he suddenly at Ganon? I know it had something to do with the pausing and dying while beating Gohma...but how did that affect it? And what were the bugs about?

This stuff is mighty confusing, but really cool none-the-less.

Originally Posted by TheGreatSea

Can someone more familiar with this stuff let me in on a few things? Like why was he suddenly at Ganon? I know it had something to do with the pausing and dying while beating Gohma...but how did that affect it? And what were the bugs about?

This stuff is mighty confusing, but really cool none-the-less.

It's some strange type of warping, a very recent discovery. I'm not sure how it works exactly, but here's a video of it:

Well by disabling the OOT warp, he managed to change the warp values.

what's the point?

Wow! That is something! What can I say but this game has so much that you can do to it!

Originally Posted by chrisshanahan87

what's the point?

To find out what is all technically possible without cheat devices.

Originally Posted by TheGreatSea

Can someone more familiar with this stuff let me in on a few things? Like why was he suddenly at Ganon? I know it had something to do with the pausing and dying while beating Gohma...but how did that affect it? And what were the bugs about?

This stuff is mighty confusing, but really cool none-the-less.

This glitch is without a doubt one the most complex glitch found in Ocarina of Time to date. Here's what I've discovered about it.

The glitch in which ZFG and others are using to get to Ganon is known as Wrong Warping. While warping to Ganon is fairly new, this type of warping to the wrong exit was first seen in "Beta Quest".

Internally, there are two variables that the game sets to determine what scene (major areas like a boss room) you spawn at, and what position within that scene. They are your last entrance index, and your stage (also known as scene setup) number.

The last entrance index variable stores a value that represents the entrance you came from. It's generally used to determine where to place Link when a scene reloads after falling OoB.

Stage number is used to determine which cutscene to play. The cutscene chosen depends on the scene that is loaded/will be loaded.

The combination of these two values makes up what I call the "True" entrance index. When a cutscene is set to play, your true entrance ends up being a few values higher than your last entrance index depending on the number of the cutscene to play.

Now here's where things come together. When you walk into a trigger to load a whole new area, your last entrance index variable and your stage number are update. Your "True" entrance index is then calculated, and the scene/entrance you end up at are determined by a table lookup.

Now to the mechanics of the trick. When ZFG backflips on the blue warp and takes out the ocarina, the blue warp is triggered and prepares the Kokiri Emerald cutscene. If you manage to open the door leaving gohma at the right frame, the stage value is set to cutscene 1 (in this case), but the last entrance index changed. This changes the "True" entrance index, and you potentially end up somewhere unexpected.

In this particular case, leaving the boss room sets the last entrance index to 0252. With cutscene 01 set to play, the "True" entrance index ends up being 0257, which falls into the Tower Collapse sequence.

There is one less obvious, but crucial factor though. When the stage value is set to a non 0000 value, the game forces a cutscene to play. However, the tower collapse area does not have a cutscene 01, causing the game to fail to update a pointer which points the cutscene data to play. This means that the last cutscene (or whatever's in the memory where the last cutscene sat) determines if the warp crashes the game. In this case, you must make sure the previous cutscene to play was the Deku Tree intro.

That's impressive. I don't like to hurry through the games, however. I like to enjoy them (even during replaying them).

Still, that's pretty cool.

Cosmo-OoT - Ocarina of Time any% in 22:09
22:09

Originally Posted by MKBreeg

I wonder how these people manage to discover all these glitches, it's wonderful!

Way too much free time on their hands I'm guessing.

There is probably countless other glitches hidden in the game many of which ma never be found. I wounder how the people came up with what to do the activate the glitch. were they like "I will die at the same time"than le out those bugs and catch one near the door than stand on the edge of the blue warp thing and play my ocarina and that equipment my sword a lot than go through the door. lol they probably tried a million and 1 things.

whats the fun of the glitch? i love the games cause i love exploring and expanding on the story

No thanks I will still take my usual 50+ hours to play OoT.

Originally Posted by OcarinaofKeith

whats the fun of the glitch? i love the games cause i love exploring and expanding on the story

Game is going on 14 years, I'm sure a lot of people finished a normal playthrough multiple times already.