Oklahoma, USAAlthough NESNinja and other online ways to play the game are not allowed to submit as a speedrun for this game.
You can use one of the four approved emulators ( FCEUX, Nestopia, Bizhawk, OpenEMU ) or one of the other approved ways to play to submit runs: (See rules below)
Legally, roms cannot be discussed on these forums. You can also go to a used game store, and the old NES consoles typically run for about 70 USD, then mario costs another 15 USD or so. You can also play on an emulator, or virtual console through Wii, Switch, WiiU or 3DS
Although, to your question... most runners use either the Mario / Duck Hunt combo cart, or the Super Mario Bros. / Duck Hunt / World Class Track Meet cart... with the majority using the Duck Hunt / Mario cart. There is also a single cart with only mario, and a rarer Super Mario Bros. / Tetris / Nintendo World Cup that i've never seen anyone use. Any of them are perfectly acceptable to play, since the mario piece is the same in them all.
Approved hardware/software (please specify in the run comment):
- Original NES, Famicom or FDS
- Original NES or Famicom with Everdrive or Powerpak
- Wii, Wii U, Switch and 3DS Virtual Console
- FCEUX, Nestopia, Bizhawk, OpenEMU
- NES Classic Edition
- Analogue NT Mini
As per the rules on the leaderboard (posted below) online emulators are not allowed. The game is timed to the millisecond, and so any discrepancy in timing, lag emulation, or any other type of deviation from console is a big deal. You'll have to use one of the four approved emulators (FCEUX, Nestopia, Bizhawk, OpenEMU)
RULES (any%)
Beat the game as fast as possible by any means necessary.
Timing is done using the SDA standard: Start - The frame "400" appears in the top right corner after selecting 1 player. End - The frame all sprites are invisible after touching the axe in 8-4.
Approved hardware/software (please specify in the run comment):
- Original NES, Famicom or FDS
- Original NES or Famicom with Everdrive or Powerpak
- Wii, Wii U, Switch and 3DS Virtual Console
- FCEUX, Nestopia, Bizhawk, OpenEMU
- NES Classic Edition
- Analogue NT Mini
Important rules (please read before submitting):
- All times require a video.
- Turbo/Autofire and left+right/up+down are banned.
- Times below 5:00.00 are treated with suspicion. It is highly recommended that you stream all of your attempts and provide split files to have your run accepted.
- Times below 5:00.00 require an input file if you are playing on an emulator that can record input files.
- Using savestates to the title screen is prohibited. You must use the reset function on your emulator or console and the reset must be shown in the video.
I think 500,000 usd is a very conservative estimate
Yeah just deleted my post after rereading it, lol - d10 no idea
https://www.speedrun.com/smb1/thread/dg86r - Pellsson's practice file has "scenarios" which start you on the optimal subpixel right after leaving the pipe before the stairs... and it tells you what exact inputs you need, and what you pressed instead of what you were supposed to...
Even better than a savestate =)
Although, if you're literally looking for a savestate for some reason, there is one under the resources tab in the "saves" category
More power to you to do this, go for it... However
It was before my time with smb1 NES - but apparently IL leaderboards used to be on the speedrun.com page and they took it off
You'll end up with a huge amount of tied-for-first runs, like @zdoroviy_antony said, unless people do fast accel and fpg, which is really the only two ways to speed up individual levels, and isn't THAT hard to do with savestates. It's going to be a NIGHTMARE to time if people actually submit runs. You're going to have to use software to check the number of frames, you're going to have cheaters, and if people submit multiple levels
There's a reason the current submissions get back-logged even with 14 mods (although only half or so of them time runs)... because they take timing seriously and are very standardized and precise... and check for cheating
If you actually have this catch on, you're going to have several people submitting 20 runs at a time, which you're going to have to check frame-by-frame keeping in mind the possibility of spliced runs and other forms of cheating. Then if you get ANYTHING wrong you're going to have people complaining to you.
Again, more power to you, but I think this is going to be more complicated and less rewarding than you think :)
Every bowser, as well as any object or enemy that has rng, is determined by what exact frame you're on, as well as some other objects or enemies you've interacted with in the level. In all other castle levels this means you CAN manipulate exactly what bowser will do, because you'll enter the castle on a knowable framerule, and you can manipulate his behavior by doing something standardized like entering the level on a buffer jump vs not buffering a jump.
8-4 bowser is the exception to this. Because he's on his own individually loaded part of 8-4, you can enter it on any FRAME rather than any FRAMERULE. If you were consistent enough to know what exact FRAME you enter the last section of 8-4 on, then you would be able to know exactly what bowser will do. The fastest runners usually know what they expect bowser's behavior will be in a small range of frames that they can enter that section on. But even they can't be consistent enough to know EXACTLY what frame they will enter that stage on. And a normal player will have no idea what frame they will be on, and even if they knew the range of frames, there would be no way of knowing what exact frame they would be on.
So theoretically it's possible to know and manipulate bowser's behavior... but (1) manipulating it in that stage would require some variant of a slowdown, which you don't want to do in 8-4, since every frame matters... (2) Even if you did know the range of frames and what bowser would do in each one, it's practically impossible to know what exact frame you're on, since frames are... really fast
However, this IS possible on every OTHER castle level with bowser - and it's been mapped. For instance, if i'm 2 framerules behind my pb on 1-4, I know to do a buffer jump against the ceiling to guarantee that bowser will jump backwards, which is faster for completing the level with the small fire glitch.
TL;DR It's theoretically possible, but practically impossible to (1) predict and (2) manipulate bowser's behavior in 8-4, and even if you could, you probably wouldn't want to
https://www.speedrun.com/smbce#Both_Quests_Warpless I know artism already posted a link to the ce page in general but here's a link to the exact category you're referring to. It works perfectly as a category extension... That's what the ce page is for
You can also use any previous version of the Pellsson rom as your original rom file
(1) I'm not sure 9 days qualifies as a necro - especially as inactive as the forums have been lately - it's possible you haven't even checked the forums at all in 9 days, in which case the posts you would be replying to would be "necro"
(2) What good does posting "necro alert" do? You're working against your own cause of decluttering the forums - unless you're trying to shame people out of cluttering I guess? But <3 Aldyn
(3) I haven't seen this method, but if it's possible to do consistently, it looks pretty cool, would be tempting to try :)
It's better to create a new post rather than commenting on an old post unrelated to your topic.
That being said, no you don't have to use an NES controller - you can see the official rules on the "Rules" button on the leaderboard, but I copy/pasted it below...
To summarize the rules, you need to do (1) video record your run starting with the reset and (2) Use the actual console or one of the listed approved emulators
However, you can use a third party controller... it's probably a bad idea, since all third party controllers I'm aware of are worse than the originals, but go for it. Also if you're playing on emulator you can, of course, use a keyboard.
RULES LISTED BELOW
Beat the game as fast as possible by any means necessary.
Timing is done using the SDA standard: Start - The frame "400" appears in the top right corner after selecting 1 player. End - The frame all sprites are invisible after touching the axe in 8-4.
Approved hardware/software (please specify in the run comment):
- Original NES, Famicom or FDS
- Original NES or Famicom with Everdrive or Powerpak
- Wii, Wii U, Switch and 3DS Virtual Console
- FCEUX, Nestopia, Bizhawk, OpenEMU
- NES Classic Edition
- Analogue NT Mini
Important rules (please read before submitting):
- All times require a video.
- Turbo/Autofire and left+right/up+down are banned.
- Times below 5:00.00 are treated with suspicion. It is highly recommended that you stream all of your attempts and provide split files to have your run accepted.
- Times below 5:00.00 require an input file if you are playing on an emulator that can record input files.
- Using savestates to the title screen is prohibited. You must use the reset function on your emulator or console and the reset must be shown in the video.
@zsjetu9 I can't replicate what you did - maybe it IS because of the failed fast accel? Most of the time when I fall off the back lip of the second pipejump pipe (like you did) I fall in the magical death pixel between the second and third goomba... but when I do manage to kill the third goomba, I never despawn the goomba necessary to clear the pillar. IDK - must be the slowdown at the start?
Here's my split file for my high 4:58 run - It has no "tricks" like FPG or BBG - the only "tricks" it has is the wrong warp in 4-2 and the wall jump in 8-4
1-1 29 seconds 1-2 33 seconds 4-1 34 seconds 4-2 31 seconds 8-1 48 seconds 8-2 36 seconds 8-3 35 seconds 8-4 47 seconds
Those are all times with the tenth place cut off - not rounded
That should give you a general idea of what time to shoot for - I split at the BLACK screen at the end of a level.
I have a tutorial on all of the "tricks" for the game - https://www.speedrun.com/smb1/thread/uz8f3 - also a video showing 100% safe strategies for a run that ends in a time of 5:18
GL
Don't let that be an excuse not to submit a run - get one up on the board, then you can start improving from it.
@Skitaculour - you can submit it without a timer, and the mods will time it, just make sure to get it from reset to axe... and get the whole screen on the recording (obviously)... then you'll get yourself up on the ol' leaderboard
That's what @tavenwebb2002 does - and he's currently 4th place.
1-1 Flagpole Glitch (DISCLAIMER: This is not practical to add to a run until trying for roughly a low 4:57) See for full tutorial
You must land on the 3rd block from the top on the first pixel while not holding "B" - on the first frame with mario in the "running" animation (as opposed to the jump/falling animation), you hold only right (not "A" or "B"), then for exactly the next 2 frames, hold "B", then do a full jump on the 3rd frame (as shown). Hold all inputs until the jump is completed. By the time you reach the flagpole block, you will need to release "A" and "B", and hold "left" for exactly 3 frames (as shown), then jump on the 4th frame. If you do the first "jump" half of the trick correctly, you will clip into the block assuming you do a full jump, even if you mess up the "second" part. If you do not clip into the block, it means you messed up the jump.
Frame counter will obviously be different depending on your pace - as long as you hit the first pixel on the block, it doesn't matter if you do a full or partial jump. In order to "save" the framerule, you will need to be 4 frames from perfect on the coin pipe section, which means that some "380"s will not be fast enough to save the rule. Credit to runner "Sockfolder" for finding out exact inputs for an RTA run.
25% with slowdowns
50% no slowdown
It's like dangerous said... You do the same inputs... But later. Fpg is really hard. It sounds like you have a misconception of how hard it is. Talking on a Google call with someone isn't going to help you. Get pellssons rom with the practice mode. It literally tells you what inputs you pressed and what you SHOULD have pressed for fpg - - - also if your emulator has a slowdown feature, try slowing the inputs down to 12% or even 6%... (or slower) So you can make the correct inputs to show you conceptually how it is done then gradually speed it up
