Talk:Movelist

Discussion page of Movelist

Ballerina Spin

A) It does have an effect on the gameplay, it wall splates on hit B) It already is used in frame data all the time on this site, it has to be explained

Wherever it's currently used it should be removed. If a move wall splats, that should be indicated in the notes regardless. RogerDodger (talk) 15:47, 23 January 2021 (UTC)
Then I would advice also removing all the +43a (+26a), as they cause more confusion than explanation
The purpose of that notation is already explained elsewhere, but to be blunt: it's frame data, bro. RogerDodger (talk) 16:10, 23 January 2021 (UTC)

Crush

In fighting games, that is called reversal mechanics, not only because under that category we also have actual parries, but also because that's what they are, reversal mechanics, things that make throwing moves in a disadvantage viable. Same reason Reversal as a fighting game term was going to be a page at some point

“Reversal” is already a term with a specific meaning in Tekken. This applies to “crush” as well, but it's shorter so preferred here. RogerDodger (talk) 15:50, 23 January 2021 (UTC)
And that meaning is a terrible meaning, as Reversals as parries, Parries, and Sabakis are essentially the same, and don't need any distinction other than disambiguation. People coming from other games are more likely to refer to Crushes as Reversals. And in Tekken we tend just to not have a common term for all the reversal options

General Approach to editing

Don't just delete articles, there is a reason why things get added. I added that information to the lettered add-ons because they just don't give full explanation, and since they don't have links to fuller pages, this is the place they are explained the most fully.

I'll try my best to explain why I delete anything in particular, but just because someone adds something doesn't mean it stays. There are also plenty of reasons to remove things: to ensure the writing is important, coherent, not redundant, etc. The primary concern of the wiki is to provide value to readers. It's of no relevance if something is true if it doesn't matter in a particular context. Most of what I've edited by you has been of this nature. RogerDodger (talk) 16:05, 23 January 2021 (UTC)

g -- Opponent can guard during recovery -- that explanation raises questions on what in the world does that mean, I know because it's a very common thing to need further explanation

Opponents can never move during any recovery. You confuse and waste readers' time telling them things they already know. RogerDodger (talk) 16:05, 23 January 2021 (UTC)

0 doesn't need an operator - important thing to note, people would sometimes write +0 as advantage, especially on automated things

0 does need an operator, which is explicitly mentioned in Template:MoveData, and implied to be necessary by the text: "Any number with a + or - in front it indicates frame advantage ...". If your zero has no plus, then it is not a "number with a + or - in front of it". RogerDodger (talk) 16:05, 23 January 2021 (UTC)

Startup

The frames where the move can hit, also known as the active frames.

Factually wrong, categoriacally, directly contradicts the Frames page. And it's okay to explain things more than once, no one is expecting a person to read up every page on a wiki to get a hold of a particular subject
Not sure what part of "This—on top of the 1 frame for input processing—is simplified to saying that the move has a 10 frame startup and 17 frame recovery." you think contradicts this, other than that you also want to make that incoherent too. RogerDodger (talk) 16:08, 23 January 2021 (UTC)