Editing Princess / Swordsman spike

From SmashWiki, the Super Smash Bros. wiki
Jump to navigationJump to search
Warning You aren't logged in. While it's not a requirement to create an account, doing so makes it a lot easier to keep track of your edits and a lot harder to confuse you with someone else. If you edit without being logged in, your IP address will be recorded in the page's edit history.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.

Latest revision Your text
Line 1: Line 1:
{{ArticleIcons|ssbm=y|unofficial=y}}
The Princess/Swordsman spike is a Peach, Roy, and Marth specific tech. It is done by using a counter to setup an invisible ceiling glitch, causing your next attack to knock your opponent at a different trajectory than usual. Specifically, if on stage it will send them straight slightly away and then straight down. If your attack knocks the opponent off-stage it will remove all vertical velocity of the knockback, but retain their horizontal knockback and hitstun. This turns strong attacks that have upwards knockback, into powerful spikes.
{{image|Image for Peach}}
{{merge|Ceiling glitch|Has a "Uses" section already, and this is a direct use-case for it.}}
[[File:Swordsman spike.gif|thumb|{{SSBM|Roy}} using the Swordsman spike]]
The '''Princess/Swordsman spike''' is a specific technique in ''[[Super Smash Bros. Melee]]'' which can only be performed by {{SSBM|Peach}}, {{SSBM|Roy}}, and {{SSBM|Marth}}, as well as {{SSBM|Kirby}} after inhaling Peach. It is done by activating the [[invisible ceiling glitch]] with their respective [[counterattack]]s, causing the opponent to be knocked back at a different trajectory than usual.  


==How to perform==
==How to perform==
[[File:Swordsman spike 2.gif|thumb|{{SSBM|Marth}} using the Swordsman spike on {{SSBM|Fox}}]]
To setup the ceiling glitch, you need to press L or R to shield (for the best effect your shield should be decently small), release shield by letting go of trigger or using jump, roll, or grab and counter a grounded attack.
To setup the invisible ceiling glitch, first [[shield]] with the [[L button]] or [[R button]], and then release shield (letting go of the L/R button, [[jump]]ing, [[roll]]ing, or [[grab]]bing all work). To activate the glitch, use a [[counterattack]] move against a grounded attacker.
Then you should hit your opponent while they are airborne.


If done correctly, the opponent will be knocked back but take only horizontal knockback and no vertical knockback while incurring the full [[hitstun]] of the move. It should be noted that the spike is more useful on the left side of the stage, as the invisible ceiling glitch is active until the opponent touches the ground, while the glitch is only active for a few frames on the right side. This turns any follow-up attacks on the left side into pseudo-spikes. A strong follow up move will deal full horizontal knockback and hitstun while the character falls due to [[gravity]].
==Video demonstration==
{{#widget:YouTube|id=VJAKp_ODeUY}}


==How it works==
==How it works==
The invisible ceiling glitch is notoriously easy to activate with these three attacks specifically. This is likely because Peach's Toad [[hitbox]] and Marth and Roy's counter hitbox are very similar to the hitbox of a shield and are color-coded as the same type of hitbox as shields in debug mode. A standard invisible ceiling glitch is triggered by going airborne while still sliding back after a grounded attack hits an opponents shield, which can happen by either getting hit out of their attack on shield or for certain characters by walking or dropping through a platform after hitting an opponents shield with a specific attack. In most other cases, a player's counterattack would normally not cause any of the shield push back required to trigger an invisible ceiling glitch. However, once the player has used their shield earlier on that stock when the player's opponent gets countered, they will receive the same push back as they would have if they attacked the shield the player were previously holding up. The player's counterattack will still be able to trigger the Princess/Swordsman spike until the player releases their shield when it is incredibly small or the next time the player dies. Also, moving around or using the counter does not undo the setup.
This likely works because Peach's Toad hitbox and Marth and Roy counter hitbox are very similar to the hitbox of a shield and are color-coded as the same type of hitbox as shields in debug mode. A standard invisible ceiling glitch is triggered by going airborne while still sliding back after a grounded attack hits an opponents shield, which can happen by either getting hit out of their attack on shield or for certain characters by walking or dropping through a platform after hitting an opponents shield with a specific attack. Normally if you hit a counter it won't cause any of the shield push back required to trigger an invisible ceiling glitch. However, once you have used your shield earlier on that stock when your opponents attacks your counter, they will receive the same push back as they would have if they attacked the shield you were previously holding up.


The player's shield effects how soon after the invisible ceiling glitch triggers, as it effects the amount of pushback the opponent receives. Firstly, if a shield is too light, the glitch activates later and may not trigger at all due to the opponent losing their vertical momentum too quickly. The strongest shield possible is recommended to use for the afformentioned reasons. However, the game may register the strong shield as a light shield if the player releases too slowly, so timing and reflexes are key if the player does not want to use an [[out of shield]] option. Also, if the player makes their shield too small, they may not have any backwards momentum when the counter hits, which means it will not trigger the invisible ceiling. As a final prerequisite, the stronger the move that hits the player counter is, the longer it takes for the player's counter to trigger the invisible ceiling and the lighter the player can hold their shield while still triggering the glitch.  
Your counter will still be able to trigger the Princess/Swordsman spike until you release a shield when it is incredibly light or the next time you die. Also, moving around or using the counter do not undo the glitched shield + counter hybrid.


===Video demonstration===
===How the shield affects the spike===
{{#widget:YouTube|id=VJAKp_ODeUY}}
How light or strong your shield is before you release it has an impact on how soon after your counter will trigger the invisible ceiling glitch and the opponent will lose their vertical knockback. This is because how light your shield is reduces the amount your opponent is pushed back when they hit your shield. So if you release a lighter shield that is used for your counter, they will lose their vertical momentum sooner. If you make your shield too light they may not have any sliding back momentum when your counter hits, which means it will not trigger the invisible ceiling. If you are too slow when you release a hard shield, the game may register the light shield during the time your spring pushed your shoulder button back to its resting position. In this case, release your trigger quickly or use an out of shield option to avoid the risk entirely. The stronger a move that hits your counter is, the longer it takes for your counter to trigger the invisible ceiling and the lighter you can hold your shield while still triggering the glitch.


[[Category:Super Smash Bros. Melee]]
[[Category:Super Smash Bros. Melee]]
[[Category:Advanced techniques]]
[[Category:Advanced techniques]]

Please note that all contributions to SmashWiki are considered to be released under the Attribution-ShareAlike 3.0 Unported license (see SmashWiki:Copyrights for details). Your changes will be visible immediately. Please enter a summary of your changes above.

Do not submit copyrighted work without permission!

Cancel Editing help (opens in new window)

This page is a member of 2 meta categories: