Submission #10080: lionofzion's NES Super Mario Bros. 3 "Warps, Glitchless" in 19:44.017

Nintendo Entertainment System
Super Mario Bros. 3
Warps, Glitchless
BizHawk 2.10.0
71158
60.0988138974405
2365
PowerOn
Super Mario Bros. 3 [NES]
USA v1.0r1
6bd518e85eb46a4252af07910f61036e84b020d1
Submitted by lionofzion on 12/11/2025 8:04 PM
Submission Comments

TAS Info:

TAS By lionofzion on December 11th, 2025.
This is a first TAS for me, so I'll probably make revisions of this TAS as time goes on.
Run Length: 19:44.017 (71158 frames)
This TAS is of the NES Game Super Mario Bros 3. using no glitches and uses warps.

Run Screenshots

The Run:

I simply wanted to create a run with no glitches and warps was my intent. Basic gameplay :)
I'll add a section for future improvements sometime in the future.

Extra Comments:

This run took roughly 8-11 hours time in total to make, so it is more of a rough draft rather than an actual hard-worked on TAS.

DrD2k9: Claiming for judging.
DrD2k9: Welcome to TASVideos.
We're always glad to have new members showing an interest in our hobby. Our site strives to show off the best of what Tool Assistance in gaming has to offer; typically (but not always) from a speed optimization standpoint. Even when there is an additional goal besides simply going for speed (i.e. Maximum Score), such runs are generally still expected to meet the stated goal as optimally as possible.
While not a bad first attempt at TASing, this run unfortunately has obvious sub-optimal actions like bonking into walls, losing momentum where otherwise avoidable, and taking unnecessary routes (i.e. it's not required to go into World 2 or 7 to ultimately warp to world 8 as a whistle can be used from the warp zone itself). Therefore, we cannot accept this run for publication.
You mentioned
 This run took roughly 8-11 hours time in total to make, so it is more of a rough draft rather than an actual hard-worked on TAS.
and
 This is a first TAS for me, so I'll probably make revisions of this TAS as time goes on.
Since we don't accept obviously sub-optimal runs; generally you shouldn't be submitting "rough drafts" for judgment. Instead use userfiles to store Work-In-Progress (WIP) runs until you've polished the run enough to where you think it is as optimized as possible. Then submit for judgement and possible publication.
It is not my intent to discourage you when it comes to TASing.
There are many in our community who would be wiling help give pointers and suggestions on how to improve your skills. This will allow you to create higher quality and more highly optimized TASes in the future. Please reach out to other members via the forums or via Discord for such help.
For starters, I can offer a few points for ways to improve your TASing:
  • First, fully read through and understand the movie rules, the movie making guidelines, and submission instructions.
  • Use as many available TASing tools that you can.
    • TAStudio: BizHawk contains this tool which is an input roll feature which allows you to specify what buttons are pressed on any specific frame of your run. This allows for very precise timing of button presses for the most optimal play.
  • End your movie on the last input necessary to get to the credits/endgame.
  • In conjunction with the previous point, don't have any empty frames of input at the end of your movie.
    • Due to the way our site parses input files, blank inputs at the end of a run will artficially increase the displayed time of the run.
I hope these suggestions encourage you to continue TASing in the future. You are also encouraged to use userfiles to store your runs that aren't being officially submitted for judgement. Once again, welcome! We look forward to see what TASes you can produce as your skills improve!
Last Edited by DrD2k9 on 12/16/2025 5:33 PM
Page History Latest diff List referrers Change Log