I like the decision on this movie, though I don't think "low%" is going to tell anything about the main goal of this run, and how it was achieved: about a game-breaking glitch. In other words, that label doesn't address how the intended route is dealt with. If one looks at Super Metroids, one might think this run avoids game-breaking glitches, since low% runs of SM avoid them.
Voting for giving this run the most telling and already traditional name, "game end glitch".
Especially since this is arbitrary code execution, it's possible to add some input the check all the flags for each stage. :P
So what does this mean for SMW TASing? Is chuck eat now banned in non-ACE categories? Or is it OK as long as you don't get an 'executes data as code' kind of sprite in your powerup box?
Wasn't there a similar case regarding some death glitch in Battle Toads?
(this is the reason why I don't like this, Open Bus is almost not manipulatable, if you have luck, everything works out).
Wait, I thought you said that was "Cheap" or something:
I consider these kind of runs "cheap" because they rely on the game crashing (really executing BRK instructions) and then running over controller registers by accident
How is this any different from manipulating the game to not crash and instead conveniently reach the control registers?
Then again, executing ram as CPU instructions rather than just corrupting memory is a definable difference. Just one that isn't very "laymen", and requires a detailed study of a TAS to determine. In fact it is quite possible that a run could be ACE without an author realizing it, they just knew they corrupted somethings, and then teh game went crazy.
I think a precedent gets set here one way or the other.
Well that doesn't discourage a TAS surely, considering that clearly proves that these movies are in fact being made. Notice how he didn't say "This glitch would take 11 hours to set up, so no way in hell am I gonna TAS that".
If you look at his channel, you see we have a lot of body parts. So all we need now is a Frankenstein to sew them all together. Granted it would be long, but hopefully any encode would simply skip all the boring sections such that that video has done, giving us a vid which is only 2-3 hours long.
1. That would most likely cause people who are watching the encode (and not the input file) to vote "Yes" despite I'm pretty sure they only found 1/10th of the movie entertaining.
2. Cutting out boring parts and only looking at the fun parts seems rather unfair for judging a TAS.
There's a vault tier, so might as well try and save as much time as possible. It's not like this game can be made more entertaining given how bad it is.
This game is terrible. It bores you with the ring stages and makes you want to see something different, but then when something different DOES occur it lags like hell to the point of annoyance; making you want to go back to the ring stages to kill off more brain cells.
No vote, sorry.
I'd probably be interested in a no-DSS-glitch run in the future, but in the meantime, I think this is good. I'm not as worried about the use of newgame+ as I thought I would be. I recommend that this obsolete the current any% run because it has a better route.
It just seems odd to me that someone can effectively "hijack" a game completion by submitting it and then cancelling it
1. Make a highly optimized run
2. Submit it
3. Cancel it
4. Have fun improving it.
On another related note, has Masterjun commented this on irc or the like? :o
Does the pokemon that you obtain with this glitch count in the pokedex?
Also, to help with this TAS:
This theoretically means that if you scrolled for a while just right, would it be possible to switch your current location to the Hall of Fame and cause a glitch warp as in the RBY movies?
1. How does this make it exactly "cheap"? That makes it sound like it's something anyone can do, despite this glitch initially discovered in 2012 and noone managed to do this.
2. What's with the sudden anti-glitch stance? I know there's always video game "purists" who want to ban glitches (even if they can't exactly agree what to ban at times) but what made you spontaneously think these runs are not worth it?
Wait, is it possible to use this to somehow trigger all stages as "Complete" before showing the credits? That should make it more "legit" to the viewers.
Well, the alternative is to allow a TAS that aims for fastest time (which the published tas most certainly does not) to go into the vault. Would you rather have a clock stopping glitch run, or a run that shows less skill that is faster? (For instance, doing a KO on Piston II which is trivial vs doing a very difficult TKO in less clock time)
Well, if this get's accepted to moons, It's alright I guess, but if it set's a precedent for ingame time runs for vault, all I'm thinking of is this. :P
This can be a problem though. I wonder can they be hex editted away?
I think even for the vault, we could allow the sacrifice of 20 frames per fight in order to allow them to at least be seen. Watchability has to matter some.
And this isn't breaking vault rules. In this case, in-game time is the yardstick for the record. Realtime is secondary. It still represents the fastest completion time within the context of this game.
Wouldn't this allow the clock stopping glitch TAS for the original game to be able to publish to vault though?
However, going through the menus as fast as possible means the fight times can only be seen by slowing down playback. To keep them visible at full speed, I sacrifice 20 frames at the end of each fight.
This can be a problem though. I wonder can they be hex editted away?
Is this supposed to happen?