(Notepad so pasting might be chunky. Will fix as necessary.)

So I was doing the ship thing for the umpteenth time since my hand has decided it doesn't like to play the game anymore, so I decided to mess around at the start to see if I could find a faster way to kill the ship.

I found one way that might have been faster but I wasn't sure, so I recorded myself doing the way, and compared that to the normal way we are doing now, more or less the perfect execution of it.

Link to the video comparing the two ways: https://www.youtube.com/watch?edit=vd&v=nTH6lmCk8E0

Before I go into any of that, we need to do a little math first. Now my recording equipment is rather low-end, so every frame had some jumpiness to it. Here's a recording of fourteen frames, or the amount of frames it takes for the player ship to go from the first moment of being able to move till when the text box pops up stopping its movement.

(These numbers were taken based off my more or less perfect execution of how to kill our ship now). 3 16 08 (Everything is 3 16 so will drop those for the remainder) 13 16 21 24 27 32 37 41 46 51 54 58 62

Now the 58 and the 62 frame didn't actually have any recorded movement in them, so we are given a range of two numbers to work from: 3.1-3.5 ms a frame.

Now how far do we move then per frame?

Here's the distance, in units given by A Ruler For Windows, which supposedly tracks pixels on screen. For these purposes, they will be refered to as units, but they most likely pertain to pixels. Each distance pertains to the frames mentioned above.

0 20 50 70 105 120 160 175 205 225 255 275 310 310

Also note that these numbers are also approximations within 1-2 units of their actual values. If we average those out, we get approximately 27-29 units. Dividing those numbers by the approximations of ms per frame above, we get a range about 8.3-8.7 units/ms, so approx 8.5 units/ms. NOTE, this number could be slightly off as I had another measurement earlier at 6.9-7.1 having approx 7 units/ms being another number, however in this instance the semantics are not truly necessary since the end points should not be any different. A comparrison shall be given using both results.

That being said, lets look at some values then.

First the normal way, the way we currently do it.

3 16 08 First Frame avail

3 16 62 Text Pop Up ~~ Roughly .54 seconds Actually going in and measuring movement stopped exactly at .5 seconds, which means half a minute to move. This can be proven in the code if we have access to that.

Textbox frames then

3 18 46 - 3 18 50 Regain Movement ~~ 1.84 seconds until regained movement, this is given that rough estimate due to recording issues.

3 20 46 Death Screen

.54 seconds 2 seconds more or less to get to death 2.54 seconds

Now, the .04 seconds given there relates to the values above, from the 58 frame to the 62 frame. No movement is captured there, so the true value lies from 2.5-2.54. On the low end, 2.5 seconds RTA to kill yourself using this way.

Now, lets look at the math done my new way.

2 43 54 First Control (First frame available)

2 44 04 Text Pops Up

2 45 92 Regain Control of Movement ~~1.88 seconds to regain control so .04 seconds variation

2 47 54 Death

.50 seconds ~~.04 variation as seen in the last numbers. 1.62 seconds to kill self 2.12 seconds total movement ~~ Roughly since screen grab ain't too fast

So just over 2.1 seconds to kill yourself this way. One thing that had to be accounted for was variation in how long it took to exit screens and such, so theres about a .04-.05 delay that needs to be taken into account.

Other information to note: I showed in another video which is linked here: that if you move up and down during the starting phase, it does NOT affect your x movement. The most you can move during the starting half a second was calculated at 397.5 units, which is basically 400 units.

So as shown above and as can be seen in the video, it is approximately .4 seconds faster to kill yourself this way. Note, this is not perfect and can be potentially done faster, and the way I did it was not quite perfect either. However, it is at least .2 seconds faster to do this.

In honor of how little time you'll save executing a maneuver that I find difficult to do, I call this move the Kappakaze.