839
edits
Omega Tyrant (talk | contribs) mNo edit summary |
Unnamed anon (talk | contribs) No edit summary |
||
Line 39: | Line 39: | ||
::I'll also reiterate it ain't just about their hypothetical playability, you still fight these characters, which makes their moveset data still completely relevant information. Readers should be able to know the frame data of Giga Bowser's moves, or how early Duon's moves will kill you, or how to most effectively DI Dracula's moves, or how big the hitbox of Male Wireframe's u-tilt is, and so on, to be able to most effectively fight these characters. It's not like any other respected wiki will neglect data for NPC characters just because they aren't playable, like imagine going to a wiki to find the data of some boss giving you grief and the wiki doesn't have it. Also, while a recurring NPC's moveset may not gain many new moves across games, their data still very much changes and should be documented (much like how that it is for playable characters, who gain few if any new moves but get significant balance adjustments that still makes it necessary to document their movesets on a per-game basis). <span style="font-family:Edwardian Script ITC; font-size:12pt">[[User:Omega Tyrant|<span style="color:forestgreen">Omega</span>]] [[User talk:Omega Tyrant|<span style="color:forestgreen">Tyrant</span>]]</span> [[File: TyranitarMS.png ]] 01:08, April 19, 2023 (EDT) | ::I'll also reiterate it ain't just about their hypothetical playability, you still fight these characters, which makes their moveset data still completely relevant information. Readers should be able to know the frame data of Giga Bowser's moves, or how early Duon's moves will kill you, or how to most effectively DI Dracula's moves, or how big the hitbox of Male Wireframe's u-tilt is, and so on, to be able to most effectively fight these characters. It's not like any other respected wiki will neglect data for NPC characters just because they aren't playable, like imagine going to a wiki to find the data of some boss giving you grief and the wiki doesn't have it. Also, while a recurring NPC's moveset may not gain many new moves across games, their data still very much changes and should be documented (much like how that it is for playable characters, who gain few if any new moves but get significant balance adjustments that still makes it necessary to document their movesets on a per-game basis). <span style="font-family:Edwardian Script ITC; font-size:12pt">[[User:Omega Tyrant|<span style="color:forestgreen">Omega</span>]] [[User talk:Omega Tyrant|<span style="color:forestgreen">Tyrant</span>]]</span> [[File: TyranitarMS.png ]] 01:08, April 19, 2023 (EDT) | ||
:::I absolutely agree to giving them more detailed moveset tables, maybe even separate hitbox data pages like the ones that exist for fighters, but with a few exceptions, not extra pages for the NPC's appearance in the specific game. A big problem can be seen for smash-original bosses, as all of their origin/gallery/trivia sections would be entirely relegated to one page the origin page while the other one is purely moveset data that can easily be on the same page, and doesn't waste time having the same infobox on two pages. I still stand by that stage hazards, including so-called stage bosses (which only have around three attacks aside from Ridley), are not notable enough to have dedicated specific game pages. If Galleom's two moveset tables causes his page to load too slowly, I can see it can be split, but single-game bosses absolutely can just get the moveset table on their main page. Also, Plague is specifically mentioning Rayquaza a lot, does he have a lot of data that can let you control him compared to other bosses like Porky and Meta Ridley? Again, though, more detailed moveset tables are a very good idea. [[User:Unnamed anon|Unnamed anon]] ([[User talk:Unnamed anon|talk]]) 01:25, April 19, 2023 (EDT) |
edits