TASVideos

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

Submission #5411: ruadath's NES Robo Warrior in 01:21.58

Console: Nintendo Entertainment System
Game name: Robo Warrior
Game version: unknown
ROM filename: Robo Warrior.nes
Branch:
Emulator: Bizhawk 1.11.9
Movie length: 01:21.58
FrameCount: 4903
Re-record count: 1972
Author's real name:
Author's nickname: ruadath
Submitter: ruadath
Submitted at: 2017-03-07 01:29:16
Text last edited at: 2017-03-11 00:20:50
Text last edited by: Mothrayas
Download: Download (2775 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:
Robo Warrior, known in Japan as Bomber King, is an action spin-off of the Bomberman series. This run uses a glitch to access the game's debug menu, skip to the final level and kill the final boss.

(Link to video)

Game objectives

  • Emulator used: Bizhawk 1.11.9
  • Accesses debug menu to skip to final level
  • Heavy glitch abuse

Comments

I don't really have too much to say here. The run was inspired by a run of Bomber King on niconico, but the US version is shorter by 2 seconds due to being able to skip the title screen much quicker. It does have longer gameplay, however, due to a certain invinciblity glitch with the bombs no longer working. This doesn't matter however, since you have to wait for the background music to completed a full loop before the glitch can be triggered, so all you see is me waiting in the menu for less time. I think the final boss fight is done as fast as possible, so I don't think that this can be improved. I could be wrong, though.

Other Comments

The ROM Hash is incorrect because I started TASing on the (J) version, then switched over. Just ignore it (and fix if you want). Also, first new NES game for me! #TASMania


Mothrayas: Judging.

Mothrayas: As has been noted in the discussion topic, the disassembly of the debug menu access method points to it being a deliberate code, and not a glitch. As such, rejecting for using a debug code.


Similar submissions (by title and categories where applicable):