I just read up on the glitch, watched the TAS, seth's run and his new VOD. (all attempts not just the WR breaker)
There's a couple of things confusing me about his attempts and whether or not the run is "dead" and if he continues or not.
First, the sprite slots, what affects whether or not despawning stuff messes up the glitch? I though all shells, coins and powerups count, However I see him collecting coins (dragon coin) or breaking red shells with spin jump without measuring whether it's pixel perfect (walking koopas, accidental smashes, or smashes that he doesn't do every run) yet the run isn't dead. he keeps going, and on the final one the glitch occurs.
Secondly, Whether or not he gets a small or big explosion. the explosions look the same to me, can someone post a screencap of a small and large explosion so i can compare please?
actually while writing this, I thought of one more question, He mentions that even if he does everything right, the glitch still may not occur because of many other factors. I didn't see anything in any of the documentation about these factors (maybe because the documentation I've read is mostly for TAS's and they can be controlled)
Hmm I found the thread here
http://tasvideos.org/forum/viewtopic.php?p=399575&highlight=#399575
before I found this one, but the direction of this thread is much more related to my question about the super mario ACE so I'll just copy and paste it here
Unessential wrote:
I just read up on the glitch, watched the TAS, seth's run and his new VOD. (all attempts not just the WR breaker)
There's a couple of things confusing me about his attempts and whether or not the run is "dead" and if he continues or not.
First, the sprite slots, what affects whether or not despawning stuff messes up the glitch? I though all shells, coins and powerups count, However I see him collecting coins (dragon coin) or breaking red shells with spin jump without measuring whether it's pixel perfect (walking koopas, accidental smashes, or smashes that he doesn't do every run) yet the run isn't dead. he keeps going, and on the final one the glitch occurs.
Secondly, Whether or not he gets a small or big explosion. the explosions look the same to me, can someone post a screencap of a small and large explosion so i can compare please?
actually while writing this, I thought of one more question, He mentions that even if he does everything right, the glitch still may not occur because of many other factors. I didn't see anything in any of the documentation about these factors (maybe because the documentation I've read is mostly for TAS's and they can be controlled)
All the information I found is very fragmented, no page has complete and comprehensive information, I found that i'm always jumping back and forth between pages and sources.
Is there a comprehensive link of resources for the mario ACE or a single post that gathers mostly everything? It would be much easier to swallow everything. I find myself switching between many tabs going back and forth trying to understand everything. Before I go back to tabbing once more, the next thing I'm looking for is the address that brings the game to the end credits with names, and the end credits that starts from the chuck (the one done by seth). If someone can just answer that now that would be great as well. Thanks.
Masterjun's submission notes (found here and here) contain most of the relevant information, or link towards other pages detailing the glitches used. But as far as tabbing between pages, distilling what's useful and combining tons of sources into something that makes sense: welcome to the wonderful world of ROM hacking*.
* I know ROM hacking is not the exact same thing as ACE, but it's very related and anything else would just make the sentence unnecessarily long.
EDIT: Oops, typo. Thanks for noticing, Anty-Lemon.
Masterjun's submission notes (found here and here) contain most of the relevant information, or link towards other pages detailing the glitches used. But as far as tabbing between pages, distilling what's useful and combining tons of sources into something that makes sense: welcome to the wonderful world of ROM hacking*.
* I know ROM hacking is not the exact same thing as ACE, but it's very related and anything else would just make the sentence unnecessarily long.
But as far as tabbing between pages, distilling what's useful and combining tons of sources into something that makes sense: welcome to the wonderful world of ROM hacking*.
My major experience with rom hacking is through arcade boards of street fighter 2. (because as a competitive player we theorize, hack tools, situations and dream scenarios into the game). It's the same thing with newly discovered glitches, or previously known glitches that people didn't know the mechanics of (WHY it happens, and once we figure it out we can find other situations in which it can occur which we sometimes don't know possible). Everything is well documented with images, colour codes, references and definitions.
In addition to forum posts people who do the hacking and create tools document very clearly in blog posts every change, how they're discovered, review past discoveries and even create comprehensive quick reference and cheat sheets.
It's disappointing and upsetting that apparently this isn't reflected in other rom hacking communities. It's really another hurdle that's not needed in a hobby that already has a relatively difficult barrier to entry.
Non-official games are allowed for submission. However, they go through more scrutiny than other games. This is because the game itself also becomes a subject to judgment, so it must be a high quality and notable hack or homebrew with a strong following. The TAS should be high quality on its own merit, and must also show something interesting compared to other game(s) made on the same game engine, if applicable.
We have Super Demo World which extends SMW in length and beauty.
And we have Super Kaizo World which increases the difficulty of SMW while still being playable by humans (a hack made just for TASes wouldn't be as interesting).
Warning: Might glitch to creditsI will finish this ACE soon as possible
(or will I?)
IMO) The hack must have the following properties:
1) It must be a bit famous: Super Demo World, Kaizo, The 2nd Reality Projects fits here.
2) It must not be aesthetically unpleasant: Kaizo doesn't go well here, but the following rule is important too.
3) The gameplay required to pass the level should be interesting. My main issue with a hack the imitates SMB or SMB3, is that the mechanics of SMW is way easier to control in these levels (without TASing) than in the original games, specially with the cape.
Joined: 11/13/2006
Posts: 2822
Location: Northern California
Someone should TAS Notte Luminosa, then claim they're going to die of leukemia in two weeks to get people to vote yes during the submission process.
TASvideos Admin and acting Senior Judge 💙 Currently unable to dedicate a lot of time to the site, taking care of family.
Now infrequently posting on BlueskywarmCabin wrote:
You shouldn't need a degree in computer science to get into this hobby.
1) It must be a bit famous: Super Demo World, Kaizo, The 2nd Reality Projects fits here.
I know that it's your opinion and all, but what does popularity have to do with a hack's eligibility to be TAS'd or submitted...? If memory serves, it has always been about a hack's quality overall and not about how famous & popular the hack is.
I know that it's your opinion and all, but what does popularity have to do with a hack's eligibility to be TAS'd or submitted...? If memory serves, it has always been about a hack's quality overall and not about how famous & popular the hack is.
Non-official games are allowed for submission. However, they go through more scrutiny than other games. This is because the game itself also becomes a subject to judgment, so it must be a high quality and notable hack or homebrew with a strong following. The TAS should be high quality on its own merit, and must also show something interesting compared to other game(s) made on the same game engine, if applicable.
In my opinion, the hack must have a rating of at least 4.5 in order to qualify. To be fair that is an arbitrary number but it is a good indicator of what seperates an exceptional hack from a great one. SMW has so many modifications with much variety so we must only choose those ones which are considered by the community to be the best. Then we need to narrow it down to those ones which have interesting strategies. Nobody wants to watch left-to-right levels for 30 minutes or so. In addition to this the TAS must be exceptionally made (particularly with regard to entertainment) in order to justify acceptance of the hack. Please note this is all just subjective and I'm not a judge or anything but it seems sane at least.
You can sort the hacks via rating using this link.
My recommendations:
Anything by Anikiti (Japanese hacker who makes modifications that are exceptionally difficult (not kaizo level), with clever level design and custom stuff)
Hack (gimmicky but short hack that could make for some interesting strats)
Shipwrecked (very open hack)
Return to Dinosaur Land (very good level design hack with some interesting strategies. I was working on this but I don't know if I will continue. The RTAers are running this currently so we can share strats)
The 7th Annual Vanilla Level Design Contest: Collaboration Hack (Hack comprised of lots of levels made by separate people. I think it could be interesting)
Bowser Rampages AgainSuper Mario OmegaSuper Mario Odyssey (it's a demo but SO well known)
Gregor's New Super Mario World
As well as TSRP and MIX series. In particular the MIX series has potential for craaaaazy strats, as shown by Mister, ISM and other's runs, which have inspired me in the past.
Hello! I am new here and I watched SetBling make a Tool-Assisted speedrun and thought that it was cool. Now I am here wanting to make one myself. If I could have some tips or pointers on where to start off. Like what programs to use and stuff. PS: I am on a Mac os x Mavericks 10.8.5. Thanks!
I watched SetBling make a Tool-Assisted speedrun and thought that it was cool.
Beware that the making of a tool-assisted speedrun usually takes MUCH more time. Sethbling spent a few hours doing it, it's not uncommon to take a few months here.
Kilmstr wrote:
If I could have some tips or pointers on where to start off. Like what programs to use and stuff. PS: I am on a Mac os x Mavericks 10.8.5. Thanks!
