@paulunga said:
Coming into this with almost no knowledge of arbitrary code execution I'm wondering how much of the stuff in the SMB 3 TAS was already in there. Was the backdoor message from Shigeru in there already? The Color-a-Dinosaur segment? I'm guessing the shinespark and turtle shield were programmed in, at least.
Still, amazing to watch.
We know those things weren't in there already because the person who put them there basically said so. For instance, he said (emphasis mine):
I thought it'd be fun to pretend that SMB3's legendary lead developer, Shigeru Miyamoto, had left an intentional "back door" hidden in the game which we had only just now discovered. Presented as an 80's style shell interface, the back door pretends to allow commands (with options) to be entered to enable the otherwise impossible happenings that follow.
If for whatever reason someone doubts this claim, it would be possible to look at the stream of controller inputs used to make the video and figure out how it encodes the "backdoor message" etc. This is all out in the open. Of course, if all we had was a Youtube video, it'd be harder to tell. Which is one of the reasons why it's good that someone is able to dig so deeply, to find out what's really there as opposed to the result of a few minutes/hours of video editing, and that the tools to do so are available to everyone. Even if only a few people will ever have the skill required to do so!
@tysonwritesel said:
I don't agree, I think it interferes with the author's intention and that is not right. How would you like it if someone went back on GameSpot and changed your Zelda scores to 1.0 for OoT and 10.0 for TP?
I'm not @jeff, but we don't have to speculate. Here, go look at the GameSpot review for OoT, open up a Javascript console (eg. ctrl-shift-i in non-Mac Firefox or Chrome will open the developer tools; from there select the console tab; Mac versions likely have different keyboard shortcuts; the F12 developer tools in IE offers something similar but I can't be bothered to confirm the exact steps right now), and paste in
document.querySelector("[itemprop=ratingValue]").innerHTML = "1.0";
Edit: <PSA>In general, you should avoid pasting arbitrary Javascript into a developer console if you don't understand it, as Bad Things could potentially happen. There's a reason Firefox no longer allows pasting Javascript into the URL bar by default any more, and instead makes you jump through the hoop of opening the developer tools. Be careful!</PSA>
There, I "changed" the review score. But, somewhat similar to ROM hacks or these newer total-control tool-assisted videos, it's easy to find out what the original was and therefore what the author's intent was. Sure, it's possible to trick someone who doesn't know better (eg. apply the "change", bring someone over and try to claim Jeff gave OoT 1.0), but also really easy to call bullshit (eg. reload the page, the "change" goes away). It'd be lousy if I tried to pass this off as the original author's intent, but I'm not, just like Lord Tom on TASVideos isn't trying to claim that the additions to SMB3 were in the original game. (As per the above quote, he did "pretend" it was in the original, but also admitted to doing so, so it's all in good fun.)
But maybe I misinterpret you, and instead of determining what the author's intention was, you're more concerned about preventing changes to the author's intent. In which case we're going to have to agree to disagree, because I'd rather be able to stand on the shoulders of giants (properly attributed, ideally!) than be forever locked into whatever someone happened to come up with years ago. (Not that fudging a review score is in any way standing on the shoulders of giants, so my analogy isn't perfect, but whatever!)
Edit: upon rereading this, perhaps the previous paragraph had too harsh a tone. Your opinion is of course valid!
Log in to comment