periwinkle | (1'41"5) Cave Story+ "Nemesis Challenge" speedrun @periwinkle. | Uploaded April 2020 | Updated October 2024, 4 hours ago.
Personal best from 2020/04/20 to 2020/09/29 (beaten on PC) and 2020/10/01 (beaten again on Switch).
I'm on a quest to get all of my Cave Story+ time attack challenge PBs on video. (Here's the play.list of all of the challenges that I've already completed: youtube.com/playlist?list=PLeKYCW86fVk2dI8dIZcXTp9VySj56eZAj)
That means that for each of the challenges that I don't have recorded PBs of, I'll just have to set a new PB!
This is the Nemesis Challenge. Call it extremely difficult, call it unfair, call it poorly-designed, call it whatever...this challenge is certainly most people's least favorite out of all of the time attack challenges.
This run isn't great, but it's so hard to finish *any* run at all that I'll take what I can get. I'll certainly go for 1'3X" some day, but for now, I'm moving on to Wind Fortress.
Personal best from 2020/04/20 to 2020/09/29 (beaten on PC) and 2020/10/01 (beaten again on Switch).
I'm on a quest to get all of my Cave Story+ time attack challenge PBs on video. (Here's the play.list of all of the challenges that I've already completed: youtube.com/playlist?list=PLeKYCW86fVk2dI8dIZcXTp9VySj56eZAj)
That means that for each of the challenges that I don't have recorded PBs of, I'll just have to set a new PB!
This is the Nemesis Challenge. Call it extremely difficult, call it unfair, call it poorly-designed, call it whatever...this challenge is certainly most people's least favorite out of all of the time attack challenges.
This run isn't great, but it's so hard to finish *any* run at all that I'll take what I can get. I'll certainly go for 1'3X" some day, but for now, I'm moving on to Wind Fortress.
![[TAS] Super Mario Bros. glitchless in 5:05.763 (5:02.485 RTA timing)](https://i.ytimg.com/vi/ZGBATWVR4d0/hqdefault.jpg "[TAS] Super Mario Bros. glitchless in 5:05.763 (5:02.485 RTA timing)
Apparently Kriller37 found a frame save in room 2 of 8-4, so heres an updated TAS. It also includes 2 frames of time saves in 4-2 found since the last glitchless TAS update: 1 frame by Gaster and samm_1703 in the underground, and 1 frame by me in the warp zone. (Its still far from saving a framerule, though.)
Individual level notes:
1-2: Still 2 frames away from saving a framerule. Its so close, yet so far...
4-1: I finish the level with 8 frames to spare in the framerule, but its possible to finish with 9 frames remaining by delaying 1 frame to grab the flag on the first frame of 340 instead of 341. This would save a frame overall because youd lose 1 frame slowing down to grab the flag later, but then gain that frame back by the timer being 1 less, and then gain another frame from not getting fireworks. (Yes, 1 firework does technically lose 1 frame.)
I opted to get the firework anyways for entertainment purposes, though.
4-2: A better subspeed on the movement up to the vine allows for getting speed on the vine platform earlier. That means something something and then you can grab the vine a pixel higher, saving a frame on the climb. I also saved a frame in the warp zone by being a better TASer than I was 3 years ago. :)
In terms of pellsson/Sockfolder ROM scores, this level would be 4-9 to 8-D (11 frames to spare).
8-2: The bullet shot I get at the end is fast enough for the TAS 8-2 framerule. Too bad its a glitchless TAS...
8-3: I kick a koopa shell and it goes straight through a hammer bro without killing it. Nice glitch in a glitchless TAS :D
Also, apparently I hadnt manipulated the judges properly in my last glitchless TAS, so this TAS now finishes with 1 extra frame to spare in this level (8 frames compared to 7 in the last TAS).
8-4: B 9 C 1+2 (45.458s). The frame save in room 2 comes from faceplanting harder into the block, which makes you get pushed out of the block to the left much more than you otherwise would, giving you more room to accelerate and get up to speed quicker. You do land a frame later from that jump than the previous strat (which is why I didnt consider that possibility; shoutouts to Kriller37 for having a bigger brain than me), but I guess the extra wiggle room combined with doing the running speed jump strat (which didnt previously save time) more than makes up for it.
Total rerecords: 8888 (nice)
FM2 movie download: http://dehacked.2y.net/microstorage.php/info/726294582/glitchless_v6.fm2")
![[TAS] Cave Story+ (PC) Spike% in 13.164s (10.973s RTA timing)](https://i.ytimg.com/vi/_lZR8B5oWXE/hqdefault.jpg "[TAS] Cave Story+ (PC) Spike% in 13.164s (10.973s RTA timing)
Randomly felt like updating this due to a number of developments since my old 2019 TAS (https://youtu.be/Qj8uJzaR9qU), mainly:
• The framerate of the game on PC was discovered to not actually be 60 FPS. Its more precisely 1/0.0166 ≈ 60.24 FPS, which means the old TAS which was done at 60 FPS skipped a few frames and the final time wasnt calculated precisely.
• The old TAS missed a couple of instances where holding Z/X sped up the cutscene.
• I used a brute-forcer to optimize the Start Point movement, so Im much more confident now that there are no more improvements to that room.
• This video is now uploaded at a higher resolution, which means YouTube should give you the option to play it at 60 FPS whereas the old video is limited to 30 FPS because I didnt realize at the time that videos needed to be at least 720p to have a 60 FPS option. Also, I did away with the holiday graphics, because yeah.
The TAS timing of 13.164s in the title is calculated from opening the game to the last input (pressing jump towards the spike), so its pretty meaningless (IMO) but I included it anyways because thats how TASes are typically timed, as well as for consistency with my Mario TASes which also always include the TAS timing in the title. This movie also assumes the existence of a blank save file with the language set to Japanese; I considered starting from a clean slate which would include the time spent changing the language setting, but TASVideos guidelines permit either way so I went with the faster option. (Not that Im planning on submitting this to TASVideos anyways.)
The RTA timing of 10.973s follows the speedrun.com category rules which begin timing from the first textbox frame and end on the frame that the player explodes when touching the spike.")
