FranceImo we should just go by IGT to the second, even if it leads to ties or whatnot. Honestly it's not like ILs matter a lot so it's overkill to framecount them (and also most maps are long enough that IGT to the second would be ok)
It's frame based RNG, so basically you delay beating stages by one more frame until you get the desired outcome. If you have SMB3 TAS concerns, I would suggest contacting Tompa as he's been TASing this game for as long as time.
I think he's looking for a tutorial for harder WW setups. I don't think there's any but if you know how to do easy setups, you can probably replicate harder ones because you'll understand what matters for the shells and all. You can also ask questions (i recommend asking in discord) so we can help directly with what you don't understand.
Just giving a small outsider opinion (because I think the discussion is interesting): allowing the runs that used Mouser Skip in the past to remain in the LB -if you decide to ban it- wouldn't hurt imo, partially because the top runs already don't use it (so it's not like keeping runs with Mouser Skip would make it harder for the records to fall). Seems like a reasonable alternative to not be unfair to people who used it when it was allowed, while trying to maintain the "spirit" of the category (beating all the stages).
Alright I went through the entire LB. And holyshit it was a mess.
Half of the runs were actually already timed on last frag, including the record. Some runs start the timer poorly (during the first loading) so I roughly estimated the time difference (i'm not gonna framecount some run at the mid of the LB to determine for sure which second it is). A few videos are missing (4th, 9th and 18th), probably due to Twitch URL changes. I don't think it does any harm if the runs stay in the LB. 20th run was off by more than a minute because the guy added all the ingame timers together to determine his time instead of real time. 22nd run didn't reset the game as far as i can tell (and also started the timer when gaining control of the char in dm0 so it was quite off). The run is 2 years old though and the guy prolly not around anymore so it would feel overkill to remove it. I'll just roll with it (even with extra cutscene loads, it wouldn't affect his ranking). 26th run actually paused the game & timer in q3tourney4 so I added the duration of the pause to his time (roughly 19s).
All in all, the LB should be pretty consistent and accurate atm. A few old runs with missing videos and such, I can live with that.
Well I'm the one who messed up initially and also brought that up so I don't mind going through the list myself. As you said it's really minor but yeah, still better to keep it consistent. I'll have a look later today.
It's not so much that it's necessary more than it's really easier to time that way. I've been timing my runs that way so far (and verifying runs with that too) without realising it said something else in the rules tbh. Also in general i spam at the end of the run and instantly skip the last cutscene.
Hey, instead of cutscene trigger at the end, can't we just end the time on the final frag against xaero? Way easier to pinpoint (and i've been verifying thinking it stopped there until now honestly) and makes the most sense as it's the last thing you do in the run.
Just to be clear about Bizhawk, it has multiple cores. One of them is pretty much perfect and the best emu you can use for NES, but one of the cores (and i don't know the specifics because i'm not anywhere near knowledgeable about all that) allowed for different setups to work in the same way as VC did (although i don't remember if "normal" setups would also work, i don't think they would though). Which is why Bizhawk was banned despite being such a good emulator otherwise.
About the mini, i wouldn't be surprised if the WW wasn't working on it with the setup(s) that are normally used but still haven't tested it (because i don't have the means to test it). If anybody wanna put in the work so we know more about it, it's more than welcome.
It's a good question Pamagea, that console hasn't really been tested so far for any%. The problem with VC (and one of the cores of Bizhawk) is some setups are possible that are not possible on an original NES. And we have no idea if those impossible setups are also possible on a mini NES at the moment.
We'll probably have to wait for more informations before having that console in the any% LB.
As long as you beat them before the game over, it's fine to skip them if you can.
The physics, glitches (except wrong warps) and almost every stage are identical. The (almost) only difference that matters for speedrunning is in loading times, so we thought it was better to keep everything in the same LB and treat it as different versions (you can filter by platform and all if you want). Like typically, you wouldn't have a LB for each language version of a game. I think smb1 and smb2 have relatively big gameplay differences in all-stars that led to the creation of a different LB.
Not sure if this is the appropriate place to request this but would it be possible to give an option in the LB settings to mark milliseconds as optional (not saying it should always say optional next to milliseconds for any LB, but that the option is there for some LBs if mods want it).
Basically my problem is this: I added the possibility to add milliseconds to the times submitted for SMB3 because it can prove important for short categories. Obviously, it should only be used if the run was actually framecounted, and whole seconds are perfectly fine otherwise, particularly for long categories. But since I added it, there's been many submissions with milliseconds that are completely wrong because people just entered whatever livesplit was saying at the end of the run. Just trying to think of a way for people to stop doing this (if they didn't framecount).
If not an "optional" message, maybe hide the milliseconds by default in the submission page and show it only if the runner clicks something, i don't know.
Fernando51, there's been some new developments regarding your run, and it's been removed from the LB for the time being, waiting for you to hopefully provide more informations about the various points raised.
The issues are multiple:
It's been confirmed with 100% certainty that some of your previous runs (both on sr.com and in your youtube channel) were cheated with the help of a turbo button. Beyond turbo, many elements in these runs are also incredibly unnatural for human beings and are most certainly TAS'd. The fact that you actually partake in TASing (and have uploaded such videos on your youtube account) does solidify the suspicions.
There's a wild inconsistency in your execution. You fail to recognise some basic optimizations that even players of a way lower caliber than #2 place would notice, and yet you go for some overly complicated and difficult strats, that sometimes are even slower. An example of that is your 1-3, which is both harder, slower and less consistent.
In 7-1, not only do you include in your strats some really obvious flaws that make no sense, but you also perform at time some movements that make no sense for a human, and only make sense if you're trying to adjust subpixels (which is not something you can know when to do in a RTA setting) or if you accidentally slipped off the controller.
All in all, when we combine these elements with the fact that you've never streamed or shown any session of attempts anywhere, and also the fact that another mario community (SMW) has rejected one of your runs for similar reasons, it's fair to say that your run should be removed until we hear from you on all these topics (and possibly more, this isn't an exhaustive list of all the suspicions). If you want to discuss directly with some of us, come to the SMB3 Discord channel. I can provide an invitation if needed.
OK so your speedrun.com account (0100100001101001) being brand new, can you tell us who you are, if this is your first speedrun etc.
Additionally, where did you learn that setup? Most of what you do is known by some players but hasn't been showcased in any public run yet (because of the difficulty to pull it off). Please detail everything you do in 7-1 as much as possible.
Also, we're gonna have to ask you to give us some videos of attempts. You don't seem to be streaming, your Youtube account only has this video, so the only thing we can rely on is your offline sessions. You say on your Youtube videos you grinded for weeks, so please show something for it.
Thanks in advance for helping with the verif!
In any% (and only in that category), the time now ends on the 1st frame Mario is visible inside the chamber (and not on the 1st frame the chamber itself is visible). The entire LB has been retimed (by me) and edited. You can see all the changes here:
If you think I made a mistake, don't hesitate to contact me or another mod and we'll look into it. As far as I can tell, the only "problematic" run is Fernando's because it's so borderline it should be framecounted from the source (but even then I think the new time should be accurate).
If you're wondering why we decided to change that (there was discussions about it on Discord), I put in that pastebin the message I initially posted on Discord about all that:
Among the people who expressed their opinion on the subject, there was an overwhelming support for 1st Mario frame, a couple of people in favor of last input, and nobody wanted to keep the old system (it was shit so that's no surprise). If you want to see the full discussion, I should be able to pastebin it (also if you're not in Discord and want an invite, just ask, most runners are there already).
Additionally, I now added the possibility to add milliseconds to the times in the LB. PLEASE ONLY USE THAT IF YOU FRAMECOUNTED YOUR RUN. Don't just write down what livesplit says if you manually started and stopped the timer. Rounding down to a full second isn't a problem right now but it could be one in the future for short categories in particular. If you don't want to bother framecounting your run (and honestly, don't bother unless you're going for WR in one of the two short categories), you don't have to worry about it, times in whole seconds are perfectly fine.
Edit: oh and one thing, we kept the "If the game crashes the run is invalid" line in the rules, but one of the purposes of stopping the timer on Mario is you only see him if the game didn't crash, so we basically stop the timer when the run is confirmed to be valid.
