This movie attempts to complete Metroid as fast as possible without fighting either one of the minibosses. I use the door glitch twice and Up+A once. I collect the Maru Mari, 30 Missiles, and Ice Beam (no Bombs.)
It is about 3:15 faster than ziplock's test movie. I tied Zoizite's 865 timeunits in the final shaft (FCE Ultra's frame counter is essential for mastering the technique there.)
I will respond in the Workbench Forum to whatever.
DeHackEd: Very nicely done. The people have spoken.
I'll publish it in a few hours by obsoleting your old video.
I love the alternate method you used in Brinstar to get through the first area you need the Maru Mari without hiding behind that zoomer the whole way. At first I thought I had some weird desynch :)
And you sure beat the hell out of Tourian with some seriously limited resources - love the way you blazed through it. And congrats again for the speed. It's now the fastest Metroid movie available. I can't believe the any% run is going to be faster.
This movie has been published.
The posts before this message apply to the submission, and posts after this message apply to the published movie.
----
[278] NES Metroid by Arc in 11:45.42
Fair enough, but why wouldn't it obsolete AP's suitless run, since they both use a restart sequence and aim to demonstrate a novelty (in this case avoding the mini-bosses and acquiring only the ice beam) rather than to break the record for a time attack on this game? This run could probably even be hex edited to be a suitless run so that it still looks like a demonstration of a novelty.
TASing or playing back a DOS game? Make sure your files match the archive at RGB Classic Games.
Because zoizite's run is notable for getting only one item (namely, the Maru Mari). This run is "just" a general speedrun without any constraints; the fact that it doesn't kill either miniboss is mostly to save time. Being able to show an interesting novelty is just a nice side-effect.
Not exactly true - it's been speculated that Arc's recently obseleted any% run would be faster than this run using restarts. I understand he is working on remake of the previous run using restarts which will undoubtedly be faster than this. It was always understood that anyone could easily beat Arc's time using restarts, but the movies would be compared as "If Arc had used restarts, would it be slower than this recent submission?" Well, if Arc had used restarts in the recently obseleted movie, it would have been faster than this.
In a nutshell, I think a slower movie just obseleted a faster one simply by using restarts. The trek back from the five missile cluster alone, not to mention needing to use the door glitch again to get back down would take at least 2 minutes.
When Zoizite's 1% run came out, it was faster than Arc's any% run, but it didn't obselete it for 2 reasons:
1) It used restarts.
2) It added a new category.
This is the precisely the same. Therefore, if Zoizite's movie didn't obselete Arc's, I don't see why this one did (unless it's because it's the same author). We'll see what happens when the any% run using the original route and restarts is submitted. Until then, it doesn't really matter. It's already done.
I agree with -ziplock-. A slower run has obsoleted a faster one, and there is no longer an any% run that doesn't use a restart sequence. What happens if a faster no restart movie is submitted now? Surely we have to at least have separate categories for "uses restart" and "does not use restart". If you then want to have a third movie that shows off something special, such as the no-item suitless run, or this no-miniboss run, then let that one be the third.
TASing or playing back a DOS game? Make sure your files match the archive at RGB Classic Games.
The problem I see in widening the offering of available movies is that the number of seeders doesn't grow at the same speed, yet the seeders' number of seeded movies stays approximately the same. Which means, every time we add a new movie (not obsoleting some of the olders), the chances of a random download being seeded just gets a bit worse.
And also, listing more movies [of the same game / of different games] clutters the list and makes the really impressive movies harder to find.
I don't think that that is a valid argument. Stop accepting the not really impressive movies then. I'd rather have two good metroid runs than one good metroid run and a run for some other game that in only decent.
That's why I recommended no more than three for Metroid (which is what we have). It just seems strange to obsolete a brilliant any% run with a run that would be slower except that it used a restart sequence. I think Arc was trying to do the same thing AP was doing with the suitless run, which is demonstrate something challenging that you could technically do, but wouldn't if your goal was to produce the lowest possible completion time. We're not going to allow 3+, or even necessarily 2 movies for every single game. As Bob said, reject the boring ones and make the occasional exception, to a reasonable maximum of 2 or 3, for movies that are particularly good, just as we always have.
TASing or playing back a DOS game? Make sure your files match the archive at RGB Classic Games.
I am sorry about posting it here, but I'm not sure where else it should go. I am trying to download the AVI file, but am getting "rejected by tracker" messages with both BitTorrent and BitTornado.
Try downloading the files again. There was a problem with the naming of the files, so Bisqwit went and renamed them. If it doesn't work now, wait a bit and then try again.