25,140
edits
(→Wanted gifs: new section) |
|||
Line 28: | Line 28: | ||
:I don't know, in my opinion, the table looks really confusing and hard to read with all the moves in separate rows. It'll look even worse when each of the moves start having paragraphs for descriptions. I think for the sake of readability that we group them together, with the obvious note that the grouping is not official. Additionally, most of the moveset tables have always really only comprised the standard moves or moves that can be grouped into those standard moves, other moves and mechanics are usually put in separate tables below. A paragraph about those non-standard moves / mechanics above a designated table makes it easier for people who are unfamiliar with the character and their moves/mechanics to understand them, so I don't think it makes it look messy. If column width is a problem, it can always be changed in the editor. If the template can be redone entirely to comprise standard and non-standard movesets while also keeping it consistent and readable and understandable, I'm for it, the moveset template has also been a bit messy especially when it comes to characters like this. I am also of the opinion that we should wait until we get all the technical information to make any kind of accurate grouping, if there are any.--[[User:MontztheMan|MontztheMan]] ([[User talk:MontztheMan|talk]]) 20:34, June 29, 2021 (EDT) | :I don't know, in my opinion, the table looks really confusing and hard to read with all the moves in separate rows. It'll look even worse when each of the moves start having paragraphs for descriptions. I think for the sake of readability that we group them together, with the obvious note that the grouping is not official. Additionally, most of the moveset tables have always really only comprised the standard moves or moves that can be grouped into those standard moves, other moves and mechanics are usually put in separate tables below. A paragraph about those non-standard moves / mechanics above a designated table makes it easier for people who are unfamiliar with the character and their moves/mechanics to understand them, so I don't think it makes it look messy. If column width is a problem, it can always be changed in the editor. If the template can be redone entirely to comprise standard and non-standard movesets while also keeping it consistent and readable and understandable, I'm for it, the moveset template has also been a bit messy especially when it comes to characters like this. I am also of the opinion that we should wait until we get all the technical information to make any kind of accurate grouping, if there are any.--[[User:MontztheMan|MontztheMan]] ([[User talk:MontztheMan|talk]]) 20:34, June 29, 2021 (EDT) | ||
Now that we have the data, I think it is safe to say that the current grouping and naming is about as correct as it's going to get. The extra moves do not have any more or less importance than the typical moves, and testing gives evidence that nothing shares staleness and thus should not be squeezed into sharing rows. The general moveset table template is planned to be updated to reflect this within a couple days. [[User:Toomai|Toomai]] [[User talk:Toomai|Glittershine]] [[File:Toomai.png|20px|link=User:Toomai/Bin|???]] The Loony 17:24, June 30, 2021 (EDT) | |||
== Why can’t we edit == | == Why can’t we edit == |