TASVideos

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

Submission #3277: agwawaf's SNES Mega Man X & Mega Man X2 & Mega Man X3 "Multi task 300%" in 43:51.02

Console: Super NES
Game name: Mega Man X & Mega Man X2 & Mega Man X3
Game version: USA
ROM filename: Mega Man X (U) (V1.1) [!].smc & Mega Man X2 (U).smc & Mega Man X3 (U).smc
Branch: Multi task 300%
Emulator: (unknown)
Movie length: 43:51.02
FrameCount: 157861
Re-record count: 84515
Author's real name: TO
Author's nickname: agwawaf
Submitter: agwawaf
Submitted at: 2011-09-04 08:46:18
Text last edited at: 2011-12-07 14:06:22
Text last edited by: Ilari
Download: Download (45409 bytes)
Status: published
Click to view the actual publication
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:
Hello, This is my second multi-task: "multi-task 300%". And I tried making "INPUT-ANIMATION". By the way, this is SNES 1,43 movie.


(Link to video)

HISTORY RELATED TO THIS TAS

2005-07-16 DeHackEd submitted FIRST MULTI-TASK: DUAL RUN with MMX and MMX2

2007-03-02 FractalFusion and Graveworm submitted currently published FASTEST MMX2 RUN.

2007-03-19 JXQ performed AWESOME INPUT ANIMATION in his Super Metroid 100% run.

2009-02-27 dezbeast submitted currently published MMX 100% run.

2011-05-08 Mothrayas submitted currently published MMX3 100% GOOD ENDING run.

Finally, 2011 May 8th, Mothrayas submitted his MMX3 100% run. This submission stimulated me to do this. And I watched JXQ's INPUT ANIMATION in his Super Metroid 100% run. This stimulated me to do INPUT ANIMATION.

WHOLE OBJECTIVE

  • aims for fastest time
  • 3 games in one movie
  • defeats sigmas's last form at the almost same time
  • 300% item completion
  • does NOT aim for best ending
  • does input animation
  • uses death as shortcut

DEFERENCE BETWEEN THIS AND EACH PUBLISHED RUN

MMX2

  • collects all Z-Parts

MMX3

  • does NOT kill bit and byte
  • does NOT aim for best ending
  • gets Z-Saber

improvement lists

I write improvement or loss in MMX3's 8 robot masters. For example, this my run is 35frames faster than currently published MMX3 100% run in intro stage although I did 3 games at the same time. + means save, - means loss. Loss is....this is just multiple playing.
save or loss total comment
Intro Stage +35 35
Tunnel Rhino +56 91
Blizzard Buffalo +112 203
Neon Tiger -28 175 I saved 35 frames in Stage run, but I lost 63 frames in Boss fight. Also, Except Bit fight because of defference of the rule.
Gravity Beetle +6 181
Toxic Seahorse +51 232
Blast Hornet -225 7 This loss is multiple-thing. Also, Except Byte fight.
Volt Catfish +164 171 Except Byte fight.
Crush Crawfish +33 204
Revisiting 1 +52 256
Revisiting 2 +7 263

Special Thanks To

  • Authors of each run, Especially JXQ for his INPUT ANIMATION , Mothrayas for his MMX3 100% good ending run.
ENJOY =)


Mukki: Judging...

Mukki: The response to this run was overwhelmingly positive. After watching it myself I cannot help but agree that this is an incredibly impressive piece of work.

One outstanding issue is whether this should obsolete the current dual run of MMX and MMX2. This is a difficult call as we have no precedent regarding the ways in which a multi-game run may be obsoleted. Common sense would dictate that a faster run of the same games would triumph, this goes without saying, but this is not the case here. The judge guidelines clearly state that the number of branches of a particular game should be kept to a minimum, consistency dictates that this should also apply to having multi-game runs of the same series For example, we could have the NES Mega Man quad-run, plus a run of MM4 + MM5, then perhaps a run of MM6 + MM3, then perhaps a run of MM3,4 and 6. This is, of course, an exaggeration, the point is that these runs are a demonstration of a concept, there is no point in publishing numerous multi-game runs within a series when they are merely variations of the same concept. Instead the multi-game run that best demonstrates this concept should be published.

The common concept between these runs is that they both demonstrate that multiple games from the Mega Man X series can be completed by a single sequence of input. I find that this run is superior in demonstrating this concept for a number of reasons. Firstly, a multi-game run must be impressive in the sense that it creates a clear divide between that which is possible for a human and that which requires tool-assistance. These runs mock the game by being able to play several games concurrently. As the difficulty increases with the more games one adds it can be said that the submission that beats three games is more impressive. Of course, this must be balanced with entertainment as the product becomes less impressive the more difficult it is to follow. Personally I find that quad-runs can get rather cluttered, three games seems to be just right. I found this run more entertaining and no more difficult to follow (probably because there was often some downtime in one of the games and so only two were being watched). Furthermore, the fact that this run also includes input animation adds to how impressive it is; the hypothetical player is not content with beating three games 100% at once, but also generates patterns with the controllers scattered around him/her.

Secondly, I find the goals in this submission to make for a more satisfying movie. Both runs collected all items in MMX2, but DeHackEd expressed regret that 100% could not also be achieved in MMX1 which this run now achieves in conjuction with 100% in MMX3. This persuades me that this run is a fitting continuation of what DeHackEd hoped to achieve with this concept.

I am therefore accepting this run as an obsoletion of the currently published Mega Man X series multi-game run.

Velitha: This'll be my next big project. The author has kindly sent me the stats screen video to add to the encode. I have a few nifty ideas on how to incorporate this into a nice encode, but this may take a while to produce. Processing...


Similar submissions (by title and categories where applicable):