Cloud (SSB4)/Down aerial

Line 104:

==Trivia==

*Like Cloud's {{mvsub|Cloud|SSB4|up aerial}}, the immediate auto-canceling of this move is possibly a coding error caused by the wrong type of timing function being used. In the move's scripts, the hitboxes are deleted on frame 43, then a timer with a count of 37 is placed in the next line for the auto-cancel window. However, this is an ''asynchronous'' timer, which enables the auto-cancel ''on'' frame 37, rather than a ''synchronous'' timer, which would enable it 37 frames ''after'' the hitboxes are deleted (on frame 60). As a result, the auto-cancel is instead enabled on frame 43, as the line is still read after the timer for deleting the hitboxes.

*Like Cloud's {{mvsub|Cloud|SSB4|up aerial}}, the immediate auto-canceling of this move is possibly a coding error caused by the wrong type of timing function being used. In the move's scripts, the hitboxes are deleted on frame 43, then a timer with a count of 37 is placed in the next line for the auto-cancel window. However, this is an asynchronous timer, which enables the auto-cancel on frame 37, rather than a synchronous timer, which would enable it 37 frames after the hitboxes are deleted (on frame 60). As a result, the auto-cancel is instead enabled on frame 43, as the line is still read after the timer for deleting the hitboxes.

**A very similar error can be seen with {{SSB4|Sonic}}'s {{mvsub|Sonic|SSB4|up aerial}}.

**Since this error was not addressed in any updates, it remains unknown whether the move's instant auto-canceling property was intentional or not. However, like with Cloud's up aerial, it was [[Cloud (SSBU)/Down aerial|eventually fixed in ''Ultimate'']], where the move's auto-cancel properly uses an asynchronous timer on frame 46 (in addition to the hitboxes ending earlier, on frame 40).

Cloud (SSB4)/Down aerial: Difference between revisions

Navigation menu

Page actions

Page actions

Personal tools

Navigation

Search

Participate

Tools

@@ Line 104: / Line 104: @@
 ==Trivia==
-*Like Cloud's {{mvsub|Cloud|SSB4|up aerial}}, the immediate auto-canceling of this move is possibly a coding error caused by the wrong type of timing function being used. In the move's scripts, the hitboxes are deleted on frame 43, then a timer with a count of 37 is placed in the next line for the auto-cancel window. However, this is an ''asynchronous'' timer, which enables the auto-cancel ''on'' frame 37, rather than a ''synchronous'' timer, which would enable it 37 frames ''after'' the hitboxes are deleted (on frame 60). As a result, the auto-cancel is instead enabled on frame 43, as the line is still read after the timer for deleting the hitboxes.
+*Like Cloud's {{mvsub|Cloud|SSB4|up aerial}}, the immediate auto-canceling of this move is possibly a coding error caused by the wrong type of timing function being used. In the move's scripts, the hitboxes are deleted on frame 43, then a timer with a count of 37 is placed in the next line for the auto-cancel window. However, this is an asynchronous timer, which enables the auto-cancel on frame 37, rather than a synchronous timer, which would enable it 37 frames after the hitboxes are deleted (on frame 60). As a result, the auto-cancel is instead enabled on frame 43, as the line is still read after the timer for deleting the hitboxes.
 **A very similar error can be seen with {{SSB4|Sonic}}'s {{mvsub|Sonic|SSB4|up aerial}}.
 **Since this error was not addressed in any updates, it remains unknown whether the move's instant auto-canceling property was intentional or not. However, like with Cloud's up aerial, it was [[Cloud (SSBU)/Down aerial|eventually fixed in ''Ultimate'']], where the move's auto-cancel properly uses an asynchronous timer on frame 46 (in addition to the hitboxes ending earlier, on frame 40).