Tool-assisted game movies
When human skills are just not enough

Submission #6290: airwe's NES Kaiketsu Yanchamaru 2: Karakuri Land "game end glitch" in 00:12.18

Console: Nintendo Entertainment System
Game name: Kaiketsu Yanchamaru 2: Karakuri Land
Game version: JPN
ROM filename: Kaiketsu Yancha Maru 2 - Karakuri Land (J) [!].nes
Branch: game end glitch
Emulator: FCEUX 2.2.3
Movie length: 00:12.18
FrameCount: 732
Re-record count: 12
Author's real name: airwe
Author's nickname: airwe
Submitter: Airwe
Submitted at: 2019-03-07 05:25:10
Text last edited at: 2019-04-17 21:42:54
Text last edited by: ThunderAxe31
Download: Download (475 bytes)
Status: decision: rejected
Submission instructions
Discuss this submission (also rating / voting)
List all submissions by this submitter
List pages on this site that refer to this submission
View submission text history
Back to the submission list
Author's comments and explanations:
There's a glitch with this game. In the MUSIC TEST mode, from the 15th tune, subsequent tunes have glitches. Opening the game, enter the MUSIC TEST mode, choose the 26th tune in a particular frame (in fact, other tunes can be, but No.26 is the front), wait for the screen to pass, press ST button and go straight to the end. I found this glitch in process of MMC3 hacking and don't know why this is so. What's the meaning of this movie? This is a very low-level work. This is probably not in conformity with the norm, sorry...

Game objectives

  • Emulator used: <FCEUX 2.2.3>
  • <Guess not.>


Stage by stage comments

Other comments

<Explain here things the audience would probably like to see> <Explain also things that could be improved in your movie> <You may also suggest screenshots.>

Masterjun: Judging.

Masterjun: Resetting to new.

ThunderAxe31: Judging.

ThunderAxe31: This is a little movie, yet it features some interesting aspects that need to be properly addressed. airwe, please don't feel bad about it, because we actually appreciate this kind of submissions, as they help for setting new precedents and discovering new possible situations to figure out.

First off, there have been brought doubts about the legitimacy of the glitch itself, in the submission thread. It's indeed very suspicious how multiple people were unable to reproduce this game end glitch on more accurate emulators than FCEUX. However, that doesn't necessarily prove that the glitch itself is the result of inaccurate emulation, since there are potentially infinite variants for causing the glitch itself. But that also means that there are no guarantees that an actual proof will ever be found, and since we can't keep a submission potentially forever stuck in the queue, it makes more sense to just reject it now and keep the idea that it could be potentially un-rejected in case a proof is found later... Except that for this specific submission it's never going to happen, as there are two more reasons why it should be kept rejected.

The second issue is about the usage of the music test mode. We don't allow cheats and debug functionalities, because these are found outside of intended gameplay. I found no evidence suggesting that the method for accessing this sound test is mentioned in-game or in the official game manual, which would make it allowed. Instead, I noted how the sound test allows to input invalid music track values, which highly suggests that this music test mode is a debug leftover, and not supposed to be accessed under normal gameplay.

Lastly, there is the biggest issue for this submission: triviality. As I also noted in the thread, by looking at the movie inputs and performing tests I could learn that this game end glitch can be triggered by meeting just two frame-perfect inputs, which would make it easily matched by human attempts. We can't accept movies that don't feature superhuman gameplay, as it's the main purpose of the site.

Rejecting for emulation issues, usage of debug feature, and triviality.

Similar submissions (by title and categories where applicable):