Personally, I think it would be more TAS-like if you shot exactly enough times to survive the attack of the smiley heads, but that's just me.
I think that would be cool, too, but not as feasible in Hourglass as many other emulators, and also I'm far too impatient. So I demonstrated shooting every other frame instead (for parts of it).
and this run was literally submitted to prove a point.
What point was that, and to whom were you making it?
1. That this game can be TASed, and could possibly be mildly interesting if someone with more patience than me were to TAS it
2. The world (No-one in particular)
I run this game RTA, and helped define the categories. So, you know...
That's a nice Appeal from Authority you've got there. Category names are one of those things with some close to universal rules, and Spikestuff is correct here. Just because you originally helped name them doesn't mean that it was done right- I've renamed and adjusted categories based on community feedback before, as it turned out I overlooked something. I've also been the one pointing out overlooked things.
But I digress- this TAS just looks bad. The game choice is fairly poor as there's really nothing interesting to TAS, and the movement speed is very slow. Were there even any other options for route- did Mario have to touch the fuzzy? Voting no, as I was most definitely not entertained.
1. Yeah, sorry about that 2. No there are no route options - it's basically an autoscrolls, without the auto scrolling.
In the barest terms possible: This site would be worse off if this run were accepted.
To be honest, I don't particularly care if this is accepted, I only really submitted it for the purposes of having submitted it. If it gets rejected, I'm not going to hide in a corner and cry.
There are literally thousans Super Mario fangames, and with the current availability of tools and graphic sets any halfway-competent coder could make a new one in just a single afternoon.
So what's so special or notable about this one?
Nothing in particular, just I run it and it doesn't require the mouse. For example, SM63 requires the mouse, so I can't TAS it.
There are two categories for this game - Any/100% means beating the game, Softlock% means softlock. Softlock% is by far the least interesting of the two, and this run was literally submitted to prove a point.
Actually to correct you.
It's "Beat the Game" or "Softlock%" cause giving it a category such as "any/100%" makes no sense when you're beating a game with no other value it could give you.
I run this game RTA, and helped define the categories. So, you know...
Windows Normal Super Mario Bros. ""Any/100%"" in 02:18.78
What does that even mean when the game has only 1 stage with seemingly nothing to collect? Also what's "PoC"?
PoC - Proof of Concept
There are two categories for this game - Any/100% means beating the game, Softlock% means softlock. Softlock% is by far the least interesting of the two, and this run was literally submitted to prove a point.
I guess this is your encode ?:
Link to video
the times are differents, that's why I doubt
Yeah. I didn't link that as the encode because 1. The timer I used shows realtime not input frames and 2. That video doesn't have the logo thingy at the start.
Please can someone compile the DeSmuME Libretro core that doesn't crash for me? I hate savestates+frame advance TASing, and BizHawk has TAStudio. I don't care how fast it runs, as long as I can use TAStudio. Whenever I try to compile, it either doesn't compile at all, or BizHawk doesn't like the compiled core.