Editing Stale-move negation

{{ArticleIcons|series=y|featured=y}}

'''Stale-move negation''' ({{ja|ワンパターン相殺|Wanpatān sōsai}}, ''One-pattern offsetting''), known as '''Repetition Effect''' in ''[[Super Smash Bros. 4]]'' and '''Stale Moves''' in ''[[Ultimate]]'', is a mechanic and a gameplay element in all games in the ''{{b|Super Smash Bros.|series}}'' series. It refers to how moves cause less [[damage]] and [[knockback]] as they are used multiple times in a row. The strength of a move increases back to its regular power as other moves are used. Starting in ''Melee'', being [[KO]]'d resets the staleness of all of that player's moves. Moves not yet affected by stale-move negation are referred to as '''fresh'''.

Moves are only affected by stale-move negation if they connect with an opponent or other object that can take damage, such as a [[crate]]. They also do not stale if they hit a [[shield]], except in ''[[Super Smash Bros. Ultimate]]''.

The purpose of stale-move negation is to discourage players from using the same attack repeatedly or over-frequently, and encourage the utilization of a character's entire moveset. However, each game in the ''Super Smash Bros.'' series handles stale-move negation differently, albeit significantly more so from the original game to ''Melee''.

Stale-move negation is applied to the whole attack rather than individual hitboxes. As such, landing the [[sourspot|weak hitbox]] will weaken all hitboxes in the attack just as landing the [[sweetspot|strongest hitbox]] would. Similarly, any variation of the same [[special move]] counts as the same move; for example, [[Giant Punch]] shares the same staleness regardless of its charge level, or whether it is used on the ground or in the air. Moves that are counter-attacks or absorbers do not take the stale-move negation of the incoming attack into consideration. Prior to ''SSB4'', [[item]]s are also affected by stale-move negation, even if the player drops the item they're holding and picks up a different one of the same.

 

As ''Smash 64'' stores damage as integers and rounds up decimal damage done by attacks, moves that deal less damage are less affected by stale-move negation, to the point where attacks that deal 3% damage or less are essentially immune. Weaker moves will also essentially reach full power in fewer stages; any attack that deals 24% damage or less will (after rounding up) be dealing full damage one stage before they are considered perfectly fresh.

Using a single move as 35% or more of one's attacks during a match awards the Cheap Shot [[List of bonuses|bonus]], worth -99 points. The bonus is not actually connected to stale-move negation; in fact, it is possible (though unlikely) to earn it even by using two other moves in between the repeated move.

 

 

In addition to this, starting in ''Brawl'', a move that does not appear in the queue at all gains a '''freshness bonus''', dealing a slight bit of extra damage. As a result, attacks effectively never deal exactly their base damage - they will either be fresh and gain a bonus, or stale and take a penalty. However, the bonus for using a fresh move is usually negligible in gameplay, with the exception of special circumstances such as a fresh move being countered by a fresh counter.

The following table lists how much a move becomes weakened for each position it appears in the queue.

!Queue position /<br>Reduction factor!!1!!2!!3!!4!!5!!6!!7!!8!!9!! !!Fresh!!All slots<br>in total

|''Brawl''||0.1||0.09||0.08||0.07||0.06||0.05||0.04||0.03||0.02|| ||1.05||0.54

|''SSB4''||0.08||0.07594||0.06782||0.06028||0.05274||0.04462||0.03766||0.02954||0.022|| ||1.05||0.4706

|''Ultimate''||0.09||0.08545||0.07635||0.0679||0.05945||0.05035||0.04255||0.03345||0.025|| ||1.05||0.5305

As an example, if a move is in positions 1, 2, and 6 in the queue - it has been used two times in a row, and another time as the sixth-most recent move. This corresponds to adding the reductors of each position together for a total reduction. Therefore, if the move is used once more (and hits) without anything changing, it will deal a damage reduced by the amount shown below:

 

''Melee:'' 0.09 + 0.08 + 0.04 = 0.21, the total damage is 79% of the base amount.<br>

 

The calculation of knockback in ''Melee'' partly ignores a move's staleness for non-projectiles. Since the knockback formula bases the knockback a player suffers on the post-damage of an attack, there is still a decrease in knockback as a move is staled, though it is extremely minimal. Typically a move will require around the same post-damage to KO regardless of its staleness value, so the additional damage needed to KO with a stale move will be around the damage dealt lost to stale-move negation (for example, a fully-staled [[Fox (SSBM)/Up smash|Fox up smash]] will deal 9.9% damage, so it will require about 8.1% more damage than a fresh up smash to KO).  

Hitting non-character targets, such as Shy Guys on [[Yoshi's Story]], doesn't affect staleness.

If a move is [[interrupt]]ed with itself, all but the first instance of the move will not deal the correct amount of reduced damage. This is because the character never enters a different action, so the game sees the sequence of linked moves as instead being one long move with multiple hits. As a result, the move will only stale once, and all hits after the first will be that one level more stale. Several moves (such as most [[down tilt]]s and several neutral attacks) are specifically guarded against this bug, so they do stale as expected when interrupted with themselves.

 

If a move shoots multiple projectiles, such as [[Blaster (Fox)|Fox's Blaster]], each projectile fired will have its staleness set to the move's staleness at the time it is fired. If one projectile deals damage, the move will be added to the queue, but the rest of the projectiles that exist at the time will only "re-update" their staleness if their hitbox changes. For example, if the first Blaster shot connects, the second Blaster shot will still deal fresh damage - until it changes from the clean hitbox to the late hitbox, which updates its staleness to the new value. In addition, if a move shoots multiple projectiles, only one projectile produced per animation can count in the queue. For example, Fox's Blaster will count every shot because he shoots one laser every time the animation loops, while Bowser shoots multiple chunks of [[Fire Breath]] per loop, so only a portion of them contribute to the queue.

 

 

{{SSBM|Zelda}} and {{SSBM|Sheik}} also share one staleness queue. The queue is not reset on [[Transform]], so for example Zelda's up air is always as equally stale as Sheik's.

 

[[Reflect]]ed projectiles (whether by moves that reflect or by [[powershield]]ing) contribute to the staleness queue, applying to the defender's queue based on the projectile's move type (e.g. reflecting a Charge Shot will stale the defender's neutral special if it hits).

 

Staleness is ignored when playing on debug level 3 or greater. Using the Reset option in training mode does not reset the queue.

 

 

 

Also unlike ''Melee'', ''Brawl'' protects later hitboxes of multi-hit moves from being staled while the move is in progress, fixing the bug that weakened the non-initial hits of multi-hit moves. It did not fix the bug where attacks interrupted with themselves do not reduce in damage during the chain, while also breaking the band-aid of certain attacks being guarded against it. Combined with the multi-hit fix and freshness bonus, multiple quick hits of {{SSBB|Meta Knight}} or {{SSBB|Marth}}'s down tilt will all deal maximum damage if initiated during the cooldown of the previous one, making the bug much more prominent.

 

In ''Brawl'', the staleness of a projectile is now attached to its existence as an object rather than to each hitbox, so simply changing from a clean hit to a late hit does not re-update it if an earlier shot connects. On the other hand, should a projectile self-delete and replace itself with something else (for example, when [[Thunder Jolt]] hits the ground the aerial ball is deleted and replaced with the grounded wave), its staleness value is re-updated.

The {{SSBB|Ice Climbers}} still share one staleness queue between them, but now only Popo has any effect on the queue, so Nana landing moves or being KO'd no longer interferes. It is currently unclear how exactly this interacts with the staleness protection above, other than Nana's move being guaranteed to have the same staleness level as Popo's under regular non-desynched conditions.

Transforming between {{SSBB|Zelda}} and {{SSBB|Sheik}}, {{SSBB|Samus}} and {{SSBB|Zero Suit Samus}}, or {{SSBB|Squirtle}}, {{SSBB|Ivysaur}} and {{SSBB|Charizard}} now resets the related queue. As transformations don't exist in ''SSB4'', while ''Melee'' and ''Ultimate'' do not reset the queue after transforming, this marks the only installment where transformations reset stale moves.

===Specifics in ''SSB4''===

The freshness bonus from ''Brawl'' is retained, and damage calculation is altered to the point where a fully staled move will deal 0.5294x of its original damage, being higher than in ''Brawl'' but lower than in ''Melee''. In addition, the knockback formula reduces the sum of reduction factors and freshness bonus to 0.3x of its calculated value when taking in the damage dealt, meaning that staleness is 70% less of a factor on knockback dealt. As a result, the damage dealt by KO moves will easily override the knockback loss to staleness outside of extreme cases, especially when taking the [[rage]] effect into consideration, and like in ''Melee'', players do not need to actively concern themselves with preserving the usage of KO moves. This change also prevents the exploitation of staleness to chain a single low-knockback move well beyond normal.

In addition, staling one item will not affect another of the same item, and only the item that was actually used. This includes character-produced items such as Link's [[Bomb (Link)|Bombs]] and Mega Man's [[Metal Blade]], and as such single use items are essentially immune to staling, and since the usage of them will still enter the queue if they hit, characters that can produce items can effectively refresh their queue without having to stale other moves, when they hit another character or damageable stage element with their item.

Like in ''Brawl'', both the stale-move negation and the freshness bonus do not apply in any single-player mode outside of the [[Home-Run Contest]].

===Specifics in ''Ultimate''===

In ''Ultimate'', a major change to stale-move negation is that it applies when hitting a shield, which in previous games had no effect on the staleness queue. However, moves that stale on shield have the reductor in their queue position reduced to 0.85×, including if perfect shielded, meaning that hitting shields is 15% less punishing on a move's final damage reduction for that spot in the queue.<ref>https://twitter.com/Meshima_/status/1078340842169950208</ref>

In addition, the {{SSBU|Ice Climbers}} behave differently in that Nana now affects the shared queue. Popo updates the queue when the [[freeze frame]]s from his attack expire, while Nana reads the queue when her attack hits. As a result, if Nana hits during Popo's freeze frames, she will share the same staleness level; if she hits after the freeze frames are over, her move will be one level more stale. Oddly, Nana does not read the queue at all if Popo hits before she acts, which means her first neutral attack will always deal base damage unless she hits alone. This oddity does not occur for item swings.

Transformations no longer reset the queue, as in ''Melee''. As such, the staleness queue is now fully shared between {{SSBU|Pokémon Trainer}}'s three Pokémon, unlike in ''Brawl''. {{SSBU|Pyra}} and {{SSBU|Mythra}} also fully share their staleness queue as well, similarly to Zelda and Sheik in ''Melee''.

Items went under another adjustment in ''Ultimate''. Items no longer enter the stale-move negation queue, making items unable to stale their damage or refresh other moves. The exception to this rule is attacking with battering items like [[Beam Sword]] or [[Home-Run Bat]], which do still count as "attacks" that are added to the stale queue as their own unique action. However, throwing a battering item does not affect the queue like any other item.

Otherwise, the staleness system is generally unchanged from ''SSB4'', but slightly stronger reductors have increased maximum staleness to 0.4695x. In addition, there is now an option in [[Training Mode]] to toggle stale moves (as well as [[rage]]) on and off, as opposed to previous games, where no such option was present. Moves will enter the queue even if the option is disabled, but will still deal their base damage in this case.

While the damage reduction caused by stale-move negation is nearly the same in ''Brawl'' as in ''Melee'', the calculation of knockback in ''Melee'' ignores it (for non-projectiles), while ''Brawl'' does not. As the damage of a hitbox is a main component in the knockback formula, this results in a much more severe drop in the knockback of a stale attack.

The much more severe stale-move negation in ''Brawl'' has had a mixed reception among the competitive fanbase. Those who support the severe stale-move negation argue that it adds more strategy and depth to the game, giving importance to "saving finishers" until the opponent is in the KO range, while rewarding those who plan the use of their attacks appropriately, and punishing those who rely on their KO attacks to rack up damage. Detractors argue that it allows some attacks to [[combo]] into themselves much more effectively than they should, resulting in them being [[broken|overly powerful]] damage rackers at low percents. This has been the primary cause of some [[counter (matchup)|hard counter matchups]], with the most notorious examples of such attacks being {{SSBB|Pikachu}}'s [[down throw]] and {{SSBB|Sheik}}'s [[forward tilt]]. Furthermore, the severe stale-move negation is sometimes argued to unfairly punish characters with fewer reliable KO options, such as {{SSBB|Samus}} and {{SSBB|R.O.B.}}, as their most powerful moves will generally be used too often to allow them to use them as KO options.

Some [[mod]]s of ''Brawl'' alter stale-move negation, with the developers often having similar sentiments as opponents of ''Brawl's'' native stale-move negation. Some reduce its powers to varying degrees, while others remove it altogether.

As covered prior, ''Smash 4'' drastically lessens the impact staleness has on knockback; it is now generally  considered a non-factor and is thus no longer a centre of controversy.

*[[Grab aerial]]s prior to ''Smash 4'', including the [[Hookshot]], Clawshot and [[Grapple Beam]].

*[[Taunt]]s excluding [[Kazuya]]’s side taunt, Demon’s Wrath.

In addition, certain hitboxes appear to be immune to the stale moves system due to being attached to an object, which is attached to another object, which is attached to a character. It is believed the "signal" to alter the damage of such hitboxes is not properly propagated along such object chains. An example of this behaviour is {{SSBB|Zero Suit Samus}}'s [[neutral air]] in ''Brawl''.

In ''Brawl'' onward, stale-move negation does not apply to any single-player mode outside of the [[Home-Run Contest]] (except ''Ultimate''{{'}}s [[Training Mode]], if Stale Moves is turned on). It additionally does not apply in the [[Online Practice Stage]], and the testing mode in [[customization]]. In the single-player and practice area cases, the freshness bonus is also ignored, so attacks always do their base damage.