Cloud (SSB4)/Up aerial: Difference between revisions

Cloud (SSB4)/Up aerial (edit)

2 bytes removed , 2 years ago

m

6,286

edits

@@ Line 162: / Line 162: @@
 *The immediate auto-canceling of this move is a coding error caused by the wrong type of timing function being used. In the move's scripts, the hitboxes are deleted on frame 26, then a timer with a count of 18 is placed in the next line for the auto-cancel window. However, this is an ''asynchronous'' timer, which enables the auto-cancel ''on'' frame 18, rather than a ''synchronous'' timer, which would enable it 18 frames ''after'' the hitboxes are deleted (on frame 44). As a result, the auto-cancel is instead enabled on frame 26, as the line is still read after the timer for deleting the hitboxes.
 **A very similar error can be seen with Cloud's {{mvsub|Cloud|SSB4|down aerial}}, as well as {{SSB4|Sonic}}'s {{mvsub|Sonic|SSB4|up aerial}}.
-**As this error was not addressed in any updates, it remains unknown whether the move's instant auto-canceling property was intentional or not. However, it was [[Cloud (SSBU)/Down aerial|eventually fixed in ''Ultimate'']], where the move's auto-cancel properly uses an asynchronous timer on frame 32.
+**As this error was not addressed in any updates, it remains unknown whether the move's instant auto-canceling property was intentional or not. However, it was [[Cloud (SSBU)/Up aerial|eventually fixed in ''Ultimate'']], where the move's auto-cancel properly uses an asynchronous timer on frame 32.
 {{MvSubNavCloud|g=SSB4}}
 [[Category:Cloud (SSB4)]]
 [[Category:Up aerials (SSB4)]]