TASVideos

Tool-assisted game movies
When human skills are just not enough

Submission #1416: Inzult's NES "glitched" Legend of Zelda 2 in 06:13.38

Console: Nintendo Entertainment System
Game name: "glitched" Legend of Zelda 2
Game version: USA
ROM filename: Zelda 2 - The Adventure of Link (U) [b4].nes
Branch:
Emulator: (unknown)
Movie length: 06:13.38
FrameCount: 22403
Re-record count: 12290
Author's real name: Phil C. M.
Author's nickname: Inzult
Submitter: inzult
Submitted at: 2007-01-04 20:41:06
Text last edited at: 2007-04-14 20:07:33
Text last edited by: Bisqwit
Download: Download (6734 bytes)
Status: decision: cancelled
Submission instructions
Discuss this submission (also rating / voting)
List all submissions by this submitter
List pages on this site that refer to this submission
View submission text history
Back to the submission list
Author's comments and explanations:
Here's an improved version of the Zelda 2 'glitched' run. I would describe the process of making this movie as 'tedious'. I tried pretty much everything I could think of in pretty much every room to get Link's movement just right. Hopefully it's as good as possible.

First off, I started this run because I noticed a few small things in the published movie. I decided to take a closer look, and the small things kept adding up.

I didn't want to make Gigafrost's run plus small improvements, but all of my ideas for route changes didn't work out, so that's kind of how it is.

So yeah, big ups to Gigafrost for all of his work and advice. There is no way on earth I would have figured out how to get through the great palace on my own. By extension, ups to Blitzag & Genisto for their initial work.

I still do not fully understand the healer glitch. As soon as I think I get what it's doing, it does something completely unexpected somewhere else. This is primarily why none of my route ideas worked.

On to the improvements: From the start of the game through the end of the jump cave, 50 frames are saved over the published run. Most of that (I've lost my earliest notes) are from a better overworld getting the trophy, and using jump in the cave. 2 frames are gained from exiting the palace to the left, and one or two frames are gained in a few other places from better movement.

Because of the change in timing of the two runs, the overworld between the jump cave and palace 2 was a nightmare. It seems like I worked on this sequence forever. I wound up losing 13 frames against the published run and I happen to think that's pretty good considering how unfriendly it was.

I gain 30 frames in palace 2. 10 frames are from passing through the first door better. 20 frames are from using a key on the second door. A few frames are lost getting the key and a few frames are gained from better movement.

Nothing much happens until I use jump to get downstab. I get to the door 8 frames faster, make the teacher appear 10 frames faster, and gain a few frames here and there from better movement.

From the start of the hammer run to getting the hammer, 5 frames are saved from small optimizations in various caves. 35 frames are gained by dying faster. It is possible to get the hammer a bit quicker, but the axe isn't as convenient and the 35 frames are lost.

The great palace was a lot more complicated to make than it looked from the start. My notes are literally just a list of room numbers and frame counts for this level (made sense as I was playing, but useless now). 73 frames are saved overall from optimizations throughout the palace and 10 frames are saved on Shadow Link.

copypasta:

I'll be happy to answer any questions the best I can. Enjoy the run.


adelikat: Very nice. Accepting for publication as improvement to the existing run.

Bisqwit: Processing...

Inzult: Canceled at the last second! I tested an idea for one of the later rooms in the great palace, and it worked out. As such, there will be a ~15 frame improvement coming in the next few days. I might as well aso try to hex in a better-looking overworld (if possible).


Similar submissions (by title and categories where applicable):