(Nico Nico movies has Japanese description in greater detail.)
Emulator used: Dolphin 3.0-378 (more-save-fixes)
Game objectives
Scenario "A New Journey" ending.
Takes no damage
Only uses necessary parts.
Runs away from all battles when possible.
Emulator details
- Dual core off
- Idle skipping off
- Progressive scan on
- DSP LLE recompiler
Comments
I aim for the "A New Journey" ending.
In battle, I try various things to defeat the enemy.
Obtaining parts takes long, and the tempo is bad, so it is only done once.
Explanation of parts
- GUN
The first basic gun has so-so firepower. But I change for the vertical gun obtained much later, since it is better. Its firepower falls behind that of the basic gun, but its homing and DOWN (decrease enemy's endurance meter) power is higher, so the number of times firing is less.
- BODY
RAY01 has better attack in general, and has very efficient strength. In the "A New Journey" scenario, other BODY parts cannot be used.
- BOMB
Standard Bomb has high power. It is suitable for doing lots of damage. I could not think of any other suitable parts.
- POD
Standard Pod is similar to the bomb, easy to use.
- LEGS
Standard Leg was a little inefficient. When able to, it is better to switch to Phaser Leg.
General Tricks and Glitches
Countdown control: The cube's number can be manipulated to an extent. By mashing A or B, or possibly holding them, the counting speed can be manipulated. To decide the first number, by pressing start button in battle setup, it is decided when the battle starts.
Boss transition: When start is pressed in battle, by the timing of the cancel, the enemy's behavior is transformed in a big way.
Double hit bug: In some cases, at least 2 kinds of attack can hit at the same time. It is possible, while avoiding decrease of damage (depending on combo), the value at which the endurance meter decreases is unusual. Originally, it is possible to avoid the endurance meter becoming 0.
Bomb attack: By using the double hit bug, which is easy to do, the technique does lots of damage. In RAY01's body type, after firing bombs, if the attack is timed well, they can hit at the same time.
No-damage hit: If hit at the time it says "KO", even though damage is 0 a hit is indicated. This is often seen in this run. If damage occurs, it is not counted.
FractalFusion: Replaced the movie file with one that hopefully fixes the savestate bug. However, it is not known if it syncs yet, or what changes.
Nahoc: Judging!
FractalFusion: Some information about ISO version from Guga in this post. It is unclear what the last line means.
Name: wrg-crob.iso CRC-32: 4df76b35 MD4: ee00f93406dfda6bd5e7e86acac04073 MD5: 6c74f607554a4d991e0a783b14d8b232 SHA-1: 5bc6196df3cee9410f07777d6bbc7593f5ad1948 The movie only syncs in the version listed in the submission text.
Nahoc: This is a tough call for me.
On one hand, I am thinking this:
"Despite the amount of efforts you put into this and votes in favor of publishing this movie, I feel the need to reject it. Being labeled as a "playaround", this TAS fails to entertain for its lenght. It is repetitive and doesn't feel like a superplay in many levels. It seems like you first went for an any%, but decided to switch your goals halfway in. You could've switched parts, used more various attacks, wandered around in a funny way while controlling the human character, played around in the credits, etc.
Don't get me wrong though; I think that this game might be a good candidate for a "playaround". Just not this particular TAS. Maybe, as mentionned in the thread, other game modes could suit a tool-assisted superplay better."
On the other hand, I am thinking this:
"People who've played the game have pointed out how godly you manipulated the AI and that you made this game look easy (but it's supposedly not!). This TAS also received a great feedback on niconico. This would also be our first GC movie to be published on the site. The 4-player battles are action-packed and mind-blowing. Gladly accepting!!"
In the end, I finally decided to reject this. It's just not enough to be a playaround. Hopefully, I can still expect an update (v2) from you, asutoro. Thanks for submitting.