Video

Part of the point of the finale was to show just how thoroughly TASBot had control of the console the whole time. Arbitrary Code Execution really means we can execute whatever code we want on the system, so we kinda downplayed that up until the Triforce but then took at that to the extreme at the end. Yes, this was really an unmodified, original OoT cartridge, and a real N64, just TASBot manipulating the console's memory through glitch exploitation leading to Arbitrary Code Execution. Of course the data for the BotW models and Twitch chat was not on the cartridge, but neither was much of what we showed. The specific things we said were beta content really were beta content, and the specific things we said were left on the cartridge really were left on the cartridge. Anything we didn't say was beta content was created on the fly in the console's memory by TASBot.

😂

This is a panel recording, the DEFCON staff member was mixing the audio for the live room (if there even was someone running the mixer at all), they had no idea how it was sounding on the recording and they didn't have the equipment needed for a multichannel recording that we could mix later.

@@Sauraen I'm at least glad I saw another comment pointing out it and saying it got better, so I just dealt with it

@@horndude77 Balance is a bit off again after they unexpectedly warp to the Lullaby cut-scene in Hyrule field (w/Impa)

What we built is an ACE showcase, that is a bunch of data for TASBot to inject by pressing buttons. However, if you run our build tools, they also output a romhack version of the project. But be warned that while we released everything we made completely from scratch, we were not able to release Nintendo copyrighted data like the BotW models. So the romhack version is missing some content. It also will only work on real hardware or high-quality modern emulators, not legacy emulators like Project64.

czcams.com/video/i7jSYqi9knk/video.html they did that

@@erierierierierie ty ty

You figured it out early--a lot of people didn't catch on until the ending, and some people weren't even sure then! But keep in mind, though most of this was not made by Nintendo, it really is just insanely advanced glitch exploitation in vanilla OoT. The cartridge and ROM are completely unmodified, it's TASBot using Arbitrary Code Execution to manipulate the console's memory to create everything.

You're welcome! It was an honor to have had the opportunity to make this.

¡Fue un honor!

Come on over to discord.gg/TASBot and we'll give you a hand on the modeling - and help you not feel alone

Anything we said was beta content really was on the real cartridge - the description and pinned post have a full list of everything that was beta content as well as the elements sources for other elements such as the triforce room - if there's anything that's missing or unclear, please let us know and thanks! We can't change the video (nor would I want to) but we're always willing to update the description if anything is amiss

⁠​⁠​⁠​⁠​⁠@@dwangoACguess what I should’ve said is that I feel its purposely misleading that most of what is shown is from the beta. Like at 47:12 it should’ve been more clear that everything shown is just a recreation but the way it’s said makes it seem like it’s all assets from the beta.

@@Laloa. I feel Sauraen did a good job of explaining that we used a lot of glitches and a huge number of button presses after achieving arbitrary code execution to create what we showed. We further explored those aspects during the end credits and provided a thorough explanation video thanks to help from RGME that went live as soon as possible after we showed Triforce% live and we also provided extensive documentation via a press release and the official website. I speak from experience when I say finding the balance can be extremely hard; I botched it in the other direction during AGDQ 2015 for instance, and likewise I'd say the AGDQ 2017 TAS block definitely didn't explain enough. For this presentation that required such a careful balance I feel we did as good of a job as we possibly could have done for a live environment where you can't just do a do-over. Some things weren't perfect and there are things I would have done slightly differently both during preparations as well as during the presentation itself. Still, I'm extremely happy with how this turned out and I have no regrets, we tried our best. If there's something else you feel could be done "in post" outside what's in the description, pinned comment, and website, please let me know and I'll do my best to ensure your concerns are addressed.

@@Laloa. We intended that viewers would suspend their disbelief and not be aware of how much we were creating with ACE along the way. However, we also intended that people would "figure it out" towards the end, which is why we made more and more impossible things happen within the game. And I explicitly stated what we had done during the credits speech. As dwangoAC alluded to above, we were also really trying to make sure that people understood that this was really just insane glitch exploitation within vanilla OoT. We had people afterwards claiming that it was a romhack or that the ending was just a video that we switched the stream over to. The fact that this is all as "legitimate" in the game as any other glitches--obviously not intended by the developers, but still a part of what the game is to the community--was the whole point.

Have a look toward the end of the video; during the panel, a meme character was created with their own theme song. The panel was two hours long roughly but this highlights video shrinks that down to just a few minutes. There's definitely some content here though, I wouldn't call it pointless, heh