http://alexnisnevich.github.io/untrusted/
You are trapped with the exit unreachable. However, your computer gives you access to the game's code, some of it still in an editable state. Perhaps you can code yourself a pathway...
21 levels. Previous knowledge of coding not required - there is enough code visible on each level to deduce the syntax of Javascript without having to refer to outside websites. Level 13 is the most difficult level, so don't get discouraged - Do all the googling and reading you need to for it. After level 13 it's smooth sailing. Expect 2-10 hours to complete.
By the way, what does 'manipulating' the state mean? What actions make it go up or down? Is it like the OoT wrong warp?
This was so obvious to me I forgot to mention it in the submission text, manipulation is merely pressing action (z, space, v, up or down) to make the game state go up. I think this is left over from the old game, as some of the old dialog (that's not actually used in the game) uses the game state to progress.
Oo! Ok.
Can you add this to the submission text? Also, when you can manipulate and when you can't (do you have to do it during the main menu? Before the dialog starts? Can you do it in a category that never accesses the menu?)
I love how you're still falling out of the teleporter while the wall of credits dialogue is happening. Starting the game way outside your shop is a great WTF moment too. It's short enough to not get boring, and crazy enough to get a Yes.
This does bring the question: how possible is any of this in realtime?
The previous TAS route was done in real time. I presume this one can be too.
By the way, what does 'manipulating' the state mean? What actions make it go up or down? Is it like the OoT wrong warp?
Why wouldn't you obsolete if we can build it faster, better, stronger. Let's make this the Six Billion Dollar TAS... or something.
Because no one is going to do it :)
Masterjun is making 100% no death TAS which by its category definition maximizes gameplay and won't have any large skips.
After that Masterjun wanted to make the fastest possible any%... Well, here it is! Masterjun didn't even have to make it :D
I doubt Masterjun will after both of those have a desire to make something like any% no S+Q. Well, maybe. But in the mean time there won't be any point to 'any% no S+Q no telefling' style category, because it has less gameplay than 100% no death and less glitches than true any%.
For reasons stated by Garrison and Graviton I also voted no. But PLEASE try again, Doom 64 is a really entertaining game to watch.
I have bad feeling about the run... I'm a little depressed now! Why did you vote no? The movie isn't entertaining =)!?? If my inspiration comes back to me, I'll try again. Bring It On diffic. goes??
Keep in mind that Garrison and Graviton are REALLY eager to see an awesome Doom 64 TAS. In fact, we all are! So here's what you should do
1) Play with all the glitches and speedrunning tricks you haven't tried out yet
2) Make a WIP of the first level, make an unlisted youtube encode of it, post both on the Doom 64 thread on tasvideos
3) Garrison, Graviton, etc will let you know if you missed any optimizations, and then you can fix them and be satisfied with the knowledge that your run of that level has no known errors left (It's a great feeling :) ). Proceed to the next stage, etc.
How does that sound?
BTW, the TAS should either be on the hardest difficulty or easiest difficulty.
One question remains: to obsolete or not to obsolete? I'm leading towards no because I don't want to see such a great run disappear.
Obsolete for sure. The run on the site would have to ban S+Q and teleflings to be optimized for its category - it's simply outdated with all these new finds.
While I don't totally mind this getting rejected, I do mind the fact that the current movie's branch name wasn't changed.
As plenty have pointed out, "11 exits" is not a good branch name. It's the same reason why the first Pokemon Gold run had its branch name changed from "all gyms" to "no memory corruption". Of course, a simple name is more difficult to come up with here, as "no arbitrary code execution" still allows the previous YI3 credits glitch run through.
I'd recommend something along the lines of "no arbitrary execution, defeats Bowser" or something like that. Would that work?
So my bullshit detector is on the fritz, so I'm not sure how much of this thread is serious.
Either way, this version of "11 exits" with heavy glitch abuse is faster than the published "11 exits" with heavy glitch abuse, so go-go gadget publication.
The existence of this TAS as an april fools joke is to do with a bit of tasvideos history. Let me give you the summary:
How categories used to be named on TASvideos:
Arbitrary code execution, glitches to credits: 'glitched'
Forgoes arbitrary code execution, uses orb glitch and everything else, 11 exits: <nothing> or 'any%'
Then, a new ruling: "Let's not call categories 'glitched'. If it's the fastest category, we call it any%/<nothing>. Anything slower than that has to explain what goal or restriction makes it slower."
How the categories are named afterwards (I may have the steps out of order but it illustrates the problem):
Arbitrary code execution, glitches to credits: <nothing> or 'any%'
Forgoes arbitrary code execution, uses orb glitch and everything else, 11 exits: something like 'any% no arbitrary code execution'
Then it was pointed out by an SMW TASer: "Wait! What about the previous glitched TAS, that spat out a null sprite on a brown platform in Yoshi's Island 3 ('brown platform glitch' and jumped to credits early that way? If the categories are meant to be comprehensive about what the TAS must and must not do, then I could take the old obsoleted glitched TAS, submit it again and it would override 'any% no arbitrary code execution' even though it really shouldn't."
So it got renamed something like 'any% no stun sprite glitch, no brown platform glitch'
Then it was pointed out: "This is a really awful, verbose category name. It doesn't roll off the tongue, and people not familiar with the game's intricacies in its glitches won't have a clue what this category is actually about. More to the point - If you find another distinct game breaking glitch, then you have to update every other category and make the definition even longer. Eventually it won't even fit in one line."
So it got renamed something like 'any% no memory corruption'
Then it was pointed out: "Isn't the chuck eat/orb glitch memory corruption? It puts something invalid into a memory address via an invalid process."
So it got renamed something like '11 exits'
But we all know the problem with that - you're looking at the thread dedicated to it!
I suspect next it will be renamed something like 'any% no heavy memory corruption' (How do you define heavy vs light? An intuitive definition can work for a while, but only until a memory corruption glitch that isn't obviously heavy or light comes along.) or we will just give up and relinquish ourself to arbitrariness once more. (Also, what do we do with things like SMW 96 exit/SMW2:YI 100%, where lots of techniques that would make the run faster but more tedious/boring like L+Ring and chuck eating are banned? In an objective/comprehensive categories world it should become part of the category.)
(And if I'm missing any key points in this summary lemme know)
I would add that 'once you have arbitrary code execution, you have arbitrary goal execution'. With a sufficiently fast enough ACE (and this game's is very fast), any goal that does not ban ACE will use ACE to just barely satisfy the requirements of the goal without satisfying the spirit of what said goal requires (for instance, no one would be impressed by a super metroid ACE TAS that gets 100% by editing all the items in!)
And it does. It is the 'not glitched' counterpart to the 'glitched' run. Just that currently it is not well articulated how/why they are different/allowed to be different.
Nope, that doesn't work. The run uses glitches, therefore it's clearly not a "not glitched" run.
OK, let's try this. Let's say next year's April Fools, masterjun submits a "96 exit" TAS that uses arbitrary code execution to do all 96 exits by teleporting to the end. Is this a correct obsoletion of the existing 96 exit TAS? Why or why not?
My post above should explain what the problem is (hint: the problem is that it shouldn't have been called '11 exits' in a category-labels-are-comprehensive world)
Well, the point is that the existing run must have a non-arbitrary reason to exist as a separate branch
And it does. It is the 'not glitched' counterpart to the 'glitched' run. Just that currently it is not well articulated how/why they are different/allowed to be different.
Either way, this version of "11 exits" with heavy glitch abuse is faster than the published "11 exits" with heavy glitch abuse, so go-go gadget publication.
Yeah, this.
It's hardly the first case that a newer run is faster but shows less of the gameplay than an existing run. That generally results in obsoletion of the slower run; I fail to see why this is suddenly a problem here.
My post above should explain what the problem is (hint: the problem is that it shouldn't have been called '11 exits' in a category-labels-are-comprehensive world)
So my bullshit detector is on the fritz, so I'm not sure how much of this thread is serious.
Either way, this version of "11 exits" with heavy glitch abuse is faster than the published "11 exits" with heavy glitch abuse, so go-go gadget publication.
The existence of this TAS as an april fools joke is to do with a bit of tasvideos history. Let me give you the summary:
How categories used to be named on TASvideos:
Arbitrary code execution, glitches to credits: 'glitched'
Forgoes arbitrary code execution, uses orb glitch and everything else, 11 exits: <nothing> or 'any%'
Then, a new ruling: "Let's not call categories 'glitched'. If it's the fastest category, we call it any%/<nothing>. Anything slower than that has to explain what goal or restriction makes it slower."
How the categories are named afterwards (I may have the steps out of order but it illustrates the problem):
Arbitrary code execution, glitches to credits: <nothing> or 'any%'
Forgoes arbitrary code execution, uses orb glitch and everything else, 11 exits: something like 'any% no arbitrary code execution'
Then it was pointed out by an SMW TASer: "Wait! What about the previous glitched TAS, that spat out a null sprite on a brown platform in Yoshi's Island 3 ('brown platform glitch' and jumped to credits early that way? If the categories are meant to be comprehensive about what the TAS must and must not do, then I could take the old obsoleted glitched TAS, submit it again and it would override 'any% no arbitrary code execution' even though it really shouldn't."
So it got renamed something like 'any% no stun sprite glitch, no brown platform glitch'
Then it was pointed out: "This is a really awful, verbose category name. It doesn't roll off the tongue, and people not familiar with the game's intricacies in its glitches won't have a clue what this category is actually about. More to the point - If you find another distinct game breaking glitch, then you have to update every other category and make the definition even longer. Eventually it won't even fit in one line."
So it got renamed something like 'any% no memory corruption'
Then it was pointed out: "Isn't the chuck eat/orb glitch memory corruption? It puts something invalid into a memory address via an invalid process."
So it got renamed something like '11 exits'
But we all know the problem with that - you're looking at the thread dedicated to it!
I suspect next it will be renamed something like 'any% no heavy memory corruption' (How do you define heavy vs light? An intuitive definition can work for a while, but only until a memory corruption glitch that isn't obviously heavy or light comes along.) or we will just give up and relinquish ourself to arbitrariness once more. (Also, what do we do with things like SMW 96 exit/SMW2:YI 100%, where lots of techniques that would make the run faster but more tedious/boring like L+Ring and chuck eating are banned? In an objective/comprehensive categories world it should become part of the category.)
(And if I'm missing any key points in this summary lemme know)
http://tasvideos.org/forum/viewtopic.php?p=323689#323689
Spider-Waffle demands that all doubters, libelers, and close minded non-productive people to the community will cease ALL activity related to OoT speedruns and TASes for 10 years.
Swordless is faster :D
This is already shaping up to be my TAS of the year 2014. I couldn't stop laughing at the OoB glitches, Superman looks so derpy doing them XD
Keep it up please
