Kirby (SSB)/Up aerial

Overview
Kirby spins around repeatedly in midair, dealing 10%-6% damage depending on when it hits and somewhat high set knockback. This move is officially referred to as Twinkle Star, and would later become his neutral aerial from Melee onwards. The move comes out on frame 10 and has an FAF of 80, making it Kirby's slowest aerial and the slowest up aerial in the game by a significant margin. In addition to this since the move has set knockback, it is completely incapable of KOing, only leading to KOes if it is used as an edgeguarding option (although it can lead into early edgeguards at low percents due to its set knockback). On the positive side, the hitbox, while small, has a very long duration; lasting the entire animation once it activates, somewhat counteracting the move's relative sluggishness. The move has limited combo potential. If Kirby lands with the move, it can combo into a or a  against most characters. Against floatier characters, the move can combo into a although this is the easiest to perform against  and. The move can also lead into an against Samus although this is difficult to land. Against, Kirby can land a although this requires good spacing to land.

If Kirby lands during the move without Z-cancelling it, there will be an extra landing hitbox. However, due to its somewhat high landing lag, it is still recommended to Z-cancel the move.

Overall, up aerial is considered to be Kirby's least useful aerial due to its extremely poor speed and low utility, being incapable of KOing and having limited combo potential. As a result, Kirby is almost always better off using one of his other aerials, making up aerial rare to be seen in competitive play, though it occasionally sees use on platforms for shield pressure. The Kirby main Alpha(CL) from Chile was well known for his use with this move.

In the Japanese version, the move is slightly better due to its clean hit dealing 12% damage and its mid hit dealing 9% damage although since the move has set knockback, this does not have a significant impact, besides making the move safer on shield. The move also had a bigger hitbox, making it harder to intercept.

NTSC-J

 * }

NTSC-U/PAL

 * }

Landing lag

 * Normal
 * L-cancelled
 * L-cancelled

Trivia

 * Due to what is presumably a programming error, the 10% hitbox is listed to start on frame 8 even though the hitboxes do not activate until frame 10. Because of this, the script immediately skips to the 10% hitbox and so the early 12% hit never occurs. It's likely that the early hit was meant to be active from frames 10-17 but due to a timing error (with a frame timer being used instead of a wait timer), it never comes out. Even stranger, the same error exists for the move in Melee where it became his neutral aerial, suggesting the code was copied and the error was never caught despite the altered hitbox properties/durations.
 * Additionally, the move's hitboxes remain active for the move's entire animation (after they activate) because there is no flag to remove the hitboxes. The hitboxes were most likely supposed to only be active until frame 46 but due to this error, they remain active until the animation ends (on frame 80). The same error can be found with in Melee.