User Files from Samsara

Emulator: FCEUX 2.2.2 (with TASeditor)

Had a lovely July 4th and didn't really have much else to do so I, uh, spent the last 8 hours working through the rest of the game.

It's decently optimized, though there's still a lot of work left to do: The prize world code could very well end up different in the final run, fadeout lag needs to be optimized further, I still have to do some testing with some of the tricks I found, and some of the playaround sections could be more entertaining. Thankfully, the game behaves nicely and it shouldn't take more than a day or two to finish up. I'm expecting a final time of around 20:15 after full optimization unless I find something big.

This run gets up through Stage 3 976 frames (00:00:16.27) faster than micro500's WIP, and finishes the game 29,712 frames (08:15.20) faster than CeSaR74's rejected submission. The prize world code entry is all micro500's input since I started working off of his WIP, so if it remains intact by the time I submit the finished run (which is highly likely), then he will be listed as co-author.

203 frames ahead. Most of the time saved is from skipping the boots, but there are small movement optimizations all throughout. The invincibility glitch is activated near the end of the stage.

This is probably the most boring item skip.

The boots apparently aren't necessary to beat the game, so it seems, and in a TAS using the invincibility glitch it ends up being around 80 frames faster to skip them. However, it could be possible to save more with a different damage route and more optimization (this was only a quick test), and the enemy/platform patterns later on in the stage could be better or worse.

TAS ADHD is a serious disease. Serious cases can lead to never finishing a run, letting people down, and claiming that everything in Super Mario World is memory corruption. Made in FCEUX 2.2.2 using TAS Editor.

I used the passcode entry from micro500's last posted WIP, which is why the rerecord count is that high. I only used about 723 rerecords from the looks of it. Stage 1 of that WIP syncs in FCEUX 2.2.2 but desyncs in Stage 2. Like everything I've been doing lately, if this run were finished it would not be submitted.

Compared to that WIP, I save 5 frames (I climb the rope 2 frames faster, kick one time less, and something around getting the controller gives me the other two frames), but I lose 3-4 of them (1 frame of lag and a couple frames delaying before that bastard caterpillar). I'm trying to find a way to manipulate that thing into shooting twice like it does in the other WIP. There's a way to manipulate it to shoot later and a way to manipulate it to not shoot at all, but I still have yet to figure out shooting twice.

Either way, I don't have enough health for later, so when I come back to this after the several other projects I have going, I'll start from the beginning.

Through Stage 4. 153 frames faster than my test run so far.

Optimized will definitely be sub-6.

http://tasvideos.org/forum/viewtopic.php?t=15339

Merely a test, not optimized.

I did say I had a few frames left to save in the stage itself... 89 frames is a few, right? New strategies, tighter movement optimization and pixel positioning, and reducing 41 lag frames (meaning less charged buster shots and less damage taken).

Stops right before the Star Man fight.

343 frames faster than HTWT's rejected submission, 148 frames saved in the stage itself and the rest on the Star Man fight. The Star Man fight is actually 16 frames faster than Mothrayas' when timed from the first hit to the last hit. However, the faster Star Man fight actually wastes far more frames, likely due to Star Man's lower positioning and the fact that it seems to take far longer for the boss explosion to despawn, so I'll need to redo the entire fight and manipulate him better. There are probably some frames to be saved in the stage itself, too, so I might just redo the entire thing.

Okay, bye.

Completes the first five levels and goes up to the first boss(es) of the 6th. 162 frames ahead of the currently published run, again due to reducing lag and optimizing movement as much as possible. I'm estimating a total of 200-220 frames saved by the end of the run. Made entirely with TASEditor in FCEUX 2.2.0