Submission #9888: jpgtg19's GBA Metroid Fusion in 11:31.407

Game Boy Advance
(Submitted: Metroid Fusion (USA, Australia).gba USA, Australia)
VisualBoy Advancev-24m-svn-r440a
41296
59.7275005696058
77
! Savestate
TAS Timing
Submitted by jpgtg19 on 9/5/2025 9:54 PM
Submission Comments
was for fun tho

nymx: Claiming for judging.
nymx: Well, this has certainly been a testing of many rules. First off, we always like to welcome new members to the community. Obviously, you enjoy it enough to participate in submitting work that you consider fun. So, welcome and please enjoy your stay! Though I understand the excitement of participation, there are a number of things that must be addressed. Sadly, all negative.
First, you have provided a movie file that starts from a "Savestate" condition. In order to legitimately condition, you must provide a "verification movie" on how this was achieved. If I understand this situation correctly, this ROM seems to have been modified. As TakuikaNinja stated, it would have been much more valuable and entertaining to have achieved this via an in-game situation that opens up or overwrites memory to achieve this condition. So, since we don't have a verification movie...this point becomes null and void.
Starting from a savestate is only allowed in special circumstances, and also requires a form of verification.
Second, movies must start from "power-on". This submission is a strict violation of our rules and also voids this submission for further considerations.
Always record new movies from power-on or SaveRAM. Starting from an emulator savestate is normally not allowed.
Third, there is optimization to consider. Let's say all other rules were met...optimization would clearly be an issue as many spots were observed being slow or unresponsive when immediate action is needed. From the very start, menu was obviously an issue and should have quickly navigated through it. Even the dialog messages weren't particular considered. Here...this also voids any acceptance of this submission.
Lastly, a "Alternative" classification could have been another consideration. This is obviously a category, which we really don't know, would require feedback of a great and positive response. Again...this case fails, since you are currently sitting at a "No" vote count of 9, and not comments have been provided to support it either.
So, here are some thoughts on how to approach any submission in the future. I'm sorry that this is not turning out as you had hoped, but don't dispare...we have a community who would gladly help point you out in the right direction. Search out our site for publications and check out what others have done to achieve such a goal.
Rejecting primarily for un-provable "Savestate" condition, and secondly...optimization.
Last Edited by nymx on 9/9/2025 12:35 AM
Page History Latest diff List referrers Change Log