Does this work on Kirby, Peach, ROB, or Zamus? Mr. Anon (talk) 15:40, 17 August 2011 (EDT)
- To my knowledge, no. Omega Tyrant
00:56, 18 August 2011 (EDT)
- The glitch happens because of the programming that says "You enter your regular falling state, but you can't use your up special again". Those four characters don't apply perfectly: Kirby and Peach don't enter their regular falling state, and R.O.B. and ZSS can use their up specials more than once (though R.O.B. needs to have the fuel to do so). Toomai Glittershine
The Frivolous 23:20, 25 August 2011 (EDT)
- The glitch happens because of the programming that says "You enter your regular falling state, but you can't use your up special again". Those four characters don't apply perfectly: Kirby and Peach don't enter their regular falling state, and R.O.B. and ZSS can use their up specials more than once (though R.O.B. needs to have the fuel to do so). Toomai Glittershine
Move ProposalEdit
Since this hasn't had any discussion yet, I'd propose moving this to Grab release, under the "Air release" section. This "glitch" is a side effect of how air releases work, as transitioning to a grounded state is what gives you some Up Bs back. You could maybe add a subsection like "edgeguarding" and place this content there. Thoughts? --
Plague von Karma 09:25, June 6, 2021 (EDT)
I don't like the claim in the move suggestion that there is "no evidence" of this being a glitch. For this to not be a glitch, it must be by design and intentional that some characters are affected and others are not, and I find it extremely difficult to believe that "grab at edge and allow escape without pummeling" is a purposeful way to automatically KO some characters but not others. It is far more likely that it is a per-character glitch with enough common elements between characters to appear more universal. Toomai Glittershine The Zesty 09:50, June 6, 2021 (EDT)
Honestly, I don't think this is a glitch (purely unintended mechanics) so much as it is an exploit (using intended mechanics in an unintended way), as the characters it works on don't go into helpless, and only gain the move back if they are hit (with some exceptions, like Pit in Brawl), which grab releasing with pummeling isn't a hit. Awesomelink234, the Super Cool Gamer (talk) 13:49, June 6, 2021 (EDT)
Oppose for the same reasons as Toomai. I highly doubt that grab releasing certain characters for an automatic easy KO is an intentional design choice. Compare this to the landing lag glitch which only effects certain characters, but not all, yet that was clearly unintentional. I am of the opinion the same applies here. 
Omega Toαd, the Toad Warrior. (I'm the best!) 19:22, June 6, 2021 (EDT)
Ok, it seems some people have completely missed the problem here. All of the affected moves are moves which don't cause helplessness, and therefore are not refreshed simply by escaping helplessness. They are programmed to be refreshed if either hitstun is inflicted on the character, or if they touch the ground. Neither of these 2 things is happening in this case, and so they do not get their special move back. At what point has anything resembling a glitch occurred? You can call it a dumb mechanic if you want to, but that does not make it a glitch. There is no justification for calling this a glitch. Every factor is behaving in the way they are designed to behave. Grab releases are not designed to restore special moves that require restoration, and so they don't. Alex the Weeb 20:20, January 19, 2022 (EST)
Bumping this with agreement with what AtW put out. It really doesn't feel like a glitch to me - again, a side effect of how it works. A glitch isn't strictly something unintentional, and I think that line of thinking stretches the definition by quite a lot. A glitch usually describes a program acting out of its intended function due to faulty programming that causes erratic results. There are many intended mechanics that have uses outside of what was intended, which we call exploits for this reason. This doesn't seem to be either of these: It is a program going through the exact motions that were written out, with mixed results. There is a name for this in glitch hunter communities: an Oversight: A case that was not considered by the developers that is thus working in a state of ignorance. For example, the Old man "glitch" in Pokemon Red and Blue was a fully intended function, storing wild data in an area that seemingly didn't have grass tiles, but it did, and they just forgot, causing the erratic behaviour; that's an oversight. "Glitch" is a pretty strong word that should be considered carefully, as in many cases where something is called a "glitch", it's often for merely strange behaviour that may have been intended (eg. Wavedashing was found during development and kept, so you could absolutely make the argument that it was intended). To me, something like Mewtwo's glitchy custom moves in Smash 4 would be glitches, where the game ends up calling garbage data, for example, or the many, many giant model bugs we have. This, by comparison, fully feels like an oversight to me, rather than a glitch. -- Plague von Karma 19:24, July 26, 2023 (EDT)