I am a huge fan of weird categories, but generally they shine when they force you to demonstrate a variety of unusual kinds of gameplay. This does showcase an unusual kind of gameplay, but it's rather straightforward and basically the same over and over, so I don't think this is a category the site is likely to want to publish.
I hope you keep thinking up weird ways to play and trying them out, though!
A warb degombs the brangy. Your gitch zanks and leils the warb.
Optimizing for reducing engine computation time is a fascinating and underexplored facet of TASing, strong yes vote. Would be really cool to someday see an improvement (or work on a similar game) that relies on fully decompiling and analyzing the algorithm to take advantage of whatever pruning strategies it has.
A warb degombs the brangy. Your gitch zanks and leils the warb.
I have been vaguely intending to play this game for Literally Years but for no particular reason have failed to do so until today, when I was inspired to by seeing that this TAS existed. Fun game, great TAS, thanks!
A warb degombs the brangy. Your gitch zanks and leils the warb.
It's quite frustrating that the submission text is not counted as a post in workbench threads, so if you post and then click "Show previous posts" you can't see it.
It is traditional for forum software to allow you to compose on the same page as the thread itself, and this would eliminate the issue and also just be much nicer in general. Having to click twice instead of 0 times to be in the often-desired "composing with visible context" state is pretty annoying.
But if that's too much to ask for, at least including submission text in Previous Posts would be really helpful.
A warb degombs the brangy. Your gitch zanks and leils the warb.
Oh my god, I remember delightedly poring over this post two years ago. What a lovely surprise to log in for the first time in a while and see it on the bench. And how much more beautiful it is to see than I ever imagined! Thank you both for all your hard work.
A warb degombs the brangy. Your gitch zanks and leils the warb.
I would like to cast my vote for publishing the "shortest input" version of this run. That's always been more interesting to me than drawing a fairly arbitrary line about which point in time counts as reaching the ending. Watching an ending play out by itself also adds a unique and pleasant flavor, especially when the input endpoint is displayed in the encode.
A warb degombs the brangy. Your gitch zanks and leils the warb.
I thought the music was pretty good throughout!
Some of the bosses are very cool, the soccer/basketball one and the guiding-fire-along-platforms one in particular.
And the story of how this game was found is truly incredible, thanks for bringing it to us.
A warb degombs the brangy. Your gitch zanks and leils the warb.
Clearly there's a strong precedent here, so I don't see much chance of this obsoleting the current run, but I don't see why it can't be its own branch, assuming people like the video.
Acumenium's argument may not have included some extraneous incorrect details, but it's correct in its main thrust, which is that the debug features exist on the shipped cartridge and are accessed via normal controller inputs.
There's no principled way to distinguish "debug tools left in" from any other glitch or even normal behavior. It's fine to decide that we're mainly interested in runs that don't use them when we can identify them on a case-by-case basis, but there's no reason at all that a high-quality, entertaining run that does use them shouldn't be published on its own branch.
A warb degombs the brangy. Your gitch zanks and leils the warb.
So I was reading this neat article about someone who found a remote execution vulnerability in Morita Shogi 64, and it contains this intriguing paragraph:
For example, Super Mario 64 is fully decompiled so I took a quick look and was able to find a write to an out of bounds pointer if sSoundMode (offset 0x1d1, 1 byte) is too large, which can be triggered by pressing the sound option box on the file select screen. That can be used to NOP out some code in the title screen renderer, but I gave up trying to exploit that - maybe someone reading will be interested in the challenge... if you could do it, you could potentially make a payload that patches Mario's colour to green to 'unlock Luigi' on a real cartridge, a feat people have been attempting since its release in 1996!
I have no idea if this will actually turn out to be exploitable, but it seems like folks here ought to be made aware of it..
A warb degombs the brangy. Your gitch zanks and leils the warb.
It seems obvious to me that there's a real market for all three solo-character runs, and they each deserve an any% branch.
Beyond that I don't personally care what further branches are allowed, but it seems really silly to me to reject this run based on a hypothetical about a game with 100 characters. That's not what we have, we have an actual real game with 3 characters, a lively community, and a history of producing extremely high-quality & popular TASes.
A warb degombs the brangy. Your gitch zanks and leils the warb.
I don't really understand what makes this a joke submission. It seems like a legitimately optimized TAS that a lot of work went into, with a slightly unorthodox goal? Am I missing something?
A warb degombs the brangy. Your gitch zanks and leils the warb.
