It's this little pink thing again.

Game objectives

  • Emulator used: FCEUX 2.2.3

Comments

It's an one frame improvement over the published run. The slope clip is improved. Everything else is unchanged. I (TASeditor) tried to improve other things as well by delaying and interupting certaing actions, but it didn't work out due to lag sadly. Here's is an userfile with these tests in second room, just in case.
For non glitched graphics change inputs from TLR to TDLR on last frame.
Now it is 9 frames faster than the current published run, thanks to better lag reduction due to interrupting movement.

First room

Don't interrupting by extending jump height at frame 603, 2 lag frames and 134 subpixel inproved at frame 888 when swallowing. At frame 1069 being 6:224 pixels ahead, due to delaying the running start and interupting movement in mid-air. 12:199 pixels ahead at frame 1229. 6 frames faster in this room.

Second room

Interrupting before sliding in order to go over the hill efficiently, this section is very laggy. ~2 pixels needed to be sacrificied at frame 1584 to not bumb into the Waddle Doo. At frame 1620 being 21:8 pixels ahead, thanks to better lag reduction on the hill. 3 frames faster in this room.

Last room

Not improved, due to the lag behaviour of the game.

Masterjun: Judg... no wait I'm an author dang it!

Nach: I'm not an author, judging.

TASeditor: Please update the submission with this file!

Nach: Replaced movie file.

Nach: It's now larger than a 1 frame improvement, and a nice one at that. Accepting.
Spikestuff: Publishing.

Alyosha
He/Him
Editor, Expert player (3520)
Joined: 11/30/2014
Posts: 2725
Location: US
Nach wrote:
What's going on with this run? Is there a particular file it should be replaced with? Are you guys still working on an improvement? Do you want to cancel this for now and come back in a couple of weeks when you figure it out?
I'm not actively working on it, other things need to be sorted out first. A correctly emulated run that works on console is not on the horizon. I think TASEditor wanted to use this file:
Please update the submission with this 8 frame faster run: User movie #36341054517440931
Post subject: Movie published
TASVideoAgent
They/Them
Moderator
Joined: 8/3/2004
Posts: 14856
Location: 127.0.0.1
This movie has been published. The posts before this message apply to the submission, and posts after this message apply to the published movie. ---- [3318] NES Kirby's Adventure "game end glitch" by TASeditor, MESHUGGAH, CoolKirby, Masterjun, MUGG & illayaya in 00:35.76
Fortranm
He/Him
Editor, Experienced player (775)
Joined: 10/19/2013
Posts: 1114
Sorry if this has been discussed before, but does the credit warp really count as beating the game in this case? Apparently, there is no save file generated from this run because the credit sequence itself does not change game progression. The memory address 0x7917 (and 0x793D) seems to be the progression counter that gets incremented by 1 every time a level is complete or a big button is pressed. The counter progression for the final stage happens around the time the full moon gets turned into a crescent after the final boss fight with the save file being updated at the same time. The player can reset at this point without losing progress, and if all big buttons have been pressed by then, the Extra Game mode would be unlocked as well. So... yeah. This movie basically ends with triggering a sequence that doesn't change the game progression whatsoever. Given the precedents of movies triggering the credits in a similar fashion not being accepted as beating the game (#3903: Masterjun & FractalFusion's GBC Pokémon: Red/Green/Blue/Yellow Version "glitched" in 01:10.47 and probably more), should this movie (and the other ones in this obsoletion chain so far) really be considered to have achieved game completion?
Site Admin, Skilled player (1236)
Joined: 4/17/2010
Posts: 11264
Location: RU
Fortranm wrote:
Sorry if this has been discussed before, but does the credit warp really count as beating the game in this case? Apparently, there is no save file generated from this run because the credit sequence itself does not change game progression. The memory address 0x7917 (and 0x793D) seems to be the progression counter that gets incremented by 1 every time a level is complete or a big button is pressed. The counter progression for the final stage happens around the time the full moon gets turned into a crescent after the final boss fight with the save file being updated at the same time. The player can reset at this point without losing progress, and if all big buttons have been pressed by then, the Extra Game mode would be unlocked as well. So... yeah. This movie basically ends with triggering a sequence that doesn't change the game progression whatsoever. Given the precedents of movies triggering the credits in a similar fashion not being accepted as beating the game (#3903: Masterjun & FractalFusion's GBC Pokémon: Red/Green/Blue/Yellow Version "glitched" in 01:10.47 and probably more), should this movie (and the other ones in this obsoletion chain so far) really be considered to have achieved game completion?
We've had this discussion with MM1 GEG. The main idea is that those are 2 separate things, and the sequence you're describing is a part of another level's gameplay. We can't jump to that level, so we can't do the things it does. To check more precisely, somebody needs to see game code probably. Checks didn't happen in due time because reasons. One of the submissions was accepted by me, but I was busy dealing with other aspects of this branch (framewars, encodes).
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.