I've written a guide for probably the most important glitch in the run, the infinite dash glitch. Let me know what you think and if you have any questions. What would you like the next guide to be on?

Slapping the side of the bongo counts as a clap, have fun memeing.

Hello friends,

I was thinking of running this game but I have a few questions, firstly are there any particular glitches that are known? Secondly, I see that only the GBC version of this game is listed and not the GB version. From what I could find, the GB version contains at least one particularly impressive glitch not found in GBC, so why is it that only the GBC is on the list? Also, would it be sensible to separate them into separate categories?

FCEUX lagging is not good to hear as it is pretty much the only emulator I know of to support the bootleg's mapper.

I think if you make splits and just go to each place detailed on the particular split you'll get it eventually even if you do it slowly. My initial runs were just that. I stumbled around inside the dungeons forgetting my way a bunch on my first few but once I started learning routes it became second nature then I started optimizing my own play. You also don't have to do the 8x speed glitch straight away, normal speed while learning should be fine. Walk before you run. Once you feel comfortable then bust it out and crush your PB with it, ha.

Are you interested in running the game, PunchAnimation? You should be able to grasp the route from Acmlm and my runs, Acmlm doesn't do the underflow glitch which is less RNG dependent but slightly slower to a run that gets it. If you have any particular questions, I can answer them. I'll try my hardest to get some guides up soon.

There are big differences. Most importantly, any physical attack against Moldorm (boomerang, bow, cane of somaria, sword etc.) will crash the game, this, coupled with the lower amount of lag on the emulator makes these non-comparable. To even begin to make them comparable would require a completely cycle accurate emulator.

Yes, though there has not been a demand so I haven't set one up. I'll set them up now.

It's certainly on my to-do list.

This has further been superseded by Infinite Ultra dash glitch. Speed values can be further increased or decreased by using ladders, to increase speed move towards the top or bottom of the ladder, then sideways and out, this will increase your speed from 4x to 8x, to slow down, do the opposite. This glitch may be done repeatedly but any more than once will lose the ability to move a single tile and collision will break down. It's just not worth it (but it is hilarious). Thanks to Acmlm for working out Ultra.

This glitch has been superseded by infinite super dash glitch. All that is changed is when performing the glitch begin on a "slow" tile that halves your speed. Perform the dash into the dungeon and save reset as per normal, when resuming you should have 4x speed rather than 2x and the glitch will no longer be lost to slopes (though while on the slopes you will have 2x speed, aka dash speed). Thanks to GelsamelXV for getting me to dash on a slope.

Holy shit, I just worked it out. I worked it out from my own video. If you enter the dungeon while dashing your outside speed is set to 4 and stays there, but when you leave the dungeon it resets it to 2. However, if you save the game, it stores multiple values including your outside speed but not the flag to reset it. Resetting the game and exiting the dungeon gives the glitch.

I just tried it out about 10 times and got it every try. I'll try and make a video soon.

So, I haven't worked out the glitch as of yet but some tinkering with various memory addresses in FCEUX has led me to the speed index for link on the overworld, address 6178. It is set to 2 normally, 1 when you walk down stairs and 4 when you dash. Setting it to the dash speed and exiting Skull woods reproduces the exact same effect as demonstrated in the above video. Though I have no idea what caused the value. Link's speed inside a dungeon is controlled by address 640A. If you dash into a dungeon the outside speed is kept at 4 but it appears to reset when leaving. More investigation is required. Edit: Here is an extended cut so you can see what I was doing just before the glitch as well:

So is the 18-21s specifically on the route? I remember seeing PresJPolk talk in another thread about just modifying the times, but if they're context specific then that would be poopy.

So, the bugs have been fixed, and lag reduced. That's pretty interesting. I bought the FC version because I have an AV Famicom (my NES is PAL) but I had no idea. Are any glitches different?

Yeah I know 2Q is a meme, but I'm all up for memes. Though, that being said, I actually think it's a pretty legitimate category.

Hello friends,

I was looking into running this fine game but was perplexed as to why NES and FC were different categories, I could understand FDS but was curious.

Also, off topic but if any of you know where some guides for 1st and 2nd quest are, please let me know, I could only find 1st quest guides.

This is some really good analysis here Acmlm.

Wow, so you actually get the underflow straight away and the screen transition means nothing.

So if I've read this all correctly, the setup is actually far simpler than I had thought, as long as a heart pickup gets you a pixel on the bar (in a dungeon), then if you get your HP down to 0, the underflow will work. That's way easier to do in runs! No need to keep track of various counts and far less concerns for pickup RNG.

It appears there are several variables that affect this glitch but I have found a setup that consistently works. First go into a dungeon, lose some HP, pick up a single heart, get your HP down to zero visible then leave the dungeon, get hit by an enemy, while in the flashing state move across a screen transition and you should have the glitch.

Picking up hearts in dungeons afterwards does not break the glitch, picking up hearts in the overworld does.

So I seem to keep randomly finding these crazy glitches.

I caught this one on stream:

I really don't know what happened, I was doing a set up for health underflow and it just happened. I don't recall doing anything special, the only thing is that I was in a flashing state when I left, I only bring that up because flashing states has been linked to the health underflow glitch.

I will upload higher quality video from amarec when it finishes encoding.

I have uploaded an example on emulator in the resource section: https://www.speedrun.com/alttpnes/resources this will work on patched and unpatched ROMs, which will not be provided here but are not hard to find. Emulator used was FCEUX.

Hello friends,

last night while streaming I came across a very exciting glitch, health underflow. As many of you know, health is an integral part of the run and taking the time to heal costs precious seconds.

Well, last night I had extremely low HP, apparently zero, got hit by an enemy without dying and while in a flashing state performed a screen transition and poof! Health bar was gone. I checked by damaging myself more that this was indeed an underflow as after several hits it would return to the top.

My question now is how to replicate it. I was able to reproduce the outcome several times as demonstrated in the video attached but couldn't get it on all enemies, and by the end of the night I couldn't seem to get it again.

Here is the Twitch video:

Here is the amarec recording: