Knockback: Difference between revisions

17 bytes removed ,  8 years ago
mNo edit summary
Line 182: Line 182:


===In ''Melee''===
===In ''Melee''===
In ''Melee'', the method of knockback stacking used varies based on how many [[frame]]s separate the first and second hit in addition to the relative angle between the two knockback directions. When the two hits are separated by fewer than 10 frames, the second hit's knockback always replaces the first's. This prevents attacks that hit repeatedly from accelerating the character that they hit with each strike, which would be the case were they added. This can also lead to some interesting scenarios that allow strong hits to be canceled into weaker ones, although this is mostly prevalent in [[team battle]]s and with certain [[item]]s. If the two hits are separated by 10 or more frames, the knockback is either set to the stronger value or the two are merged. The relative angle between the two hits' launch angles comes into play here: if the angle is large enough (meaning the hits are in opposite directions), then the two hits are merged via vector addition. However, if the relative angle is small (meaning the hits are in the same direction) the stronger hit is used and entirely replaces the weaker one. Since merging occurs when the hits are in opposite directions, merged knockbacks will often be in a direction completely unrelated to either of the previous two. For example, if a character is struck up and right by a strong hit and then up and left by an equally strong hit more than ten frames later, the character will be sent straight up (as the horizontal values cancel out and the vertical ones stack). This often leads to there being residual knockback from a previous hit in a combo which must be taken into account when trying to follow up.
In ''Melee'', the method of knockback stacking used varies based on how many [[frame]]s separate the first and second hit in addition to the relative angle between the two knockback directions. When the two hits are separated by fewer than 10 frames, the second hit's knockback always replaces the first's. This prevents attacks that hit repeatedly from accelerating the character that they hit with each strike, which would be the case were they added. This can also lead to some interesting scenarios that allow strong hits to be canceled into weaker ones, although this is mostly prevalent in [[team battle]]s and with certain [[item]]s. If the two hits are separated by 10 or more frames, the knockback is either set to the stronger value or the two are merged. The relative angle between the two hits' launch angles comes into play here: if the angle is large enough (meaning the hits are in opposite directions), then the two hits are merged via vector addition. However, if the relative angle is small (meaning the hits are in the same direction) the stronger hit is used and entirely replaces the weaker one. Since merging occurs when the hits are in opposite directions, merged knockbacks may be in a direction distinct from either of the previous two. For example, if a character is struck up and right by a strong hit and then up and left by an equally strong hit more than ten frames later, the character will be sent straight up (as the horizontal values cancel out and the vertical ones stack). This often leads to there being residual knockback from a previous hit in a combo which must be taken into account when trying to follow up.


In addition, [[hitstun]] duration is always refreshed by the second hit regardless of the time and angle between them, and the amount of hitstun applied is the amount that would be applied if the opponent had not already been hit. For example, the additional knockback put on the opponent from any merging does not factor in to the equation used to calculate the amount of hitstun that should be put on the opponent.
In addition, [[hitstun]] duration is always refreshed by the second hit regardless of the time and angle between them, and the amount of hitstun applied is the amount that would be applied if the opponent had not already been hit. For example, the additional knockback put on the opponent from any merging does not factor in to the equation used to calculate the amount of hitstun that should be put on the opponent.
1,891

edits