Template talk:MovesetTable
Something really weird happened with those last two changes. Look at Link's. The {{{neutralname}}} and {{neutraldesc}}} I understand, but the ftilt block moved up oddly. Ryxis (talk) 23:49, 30 March 2014 (EDT)
- Fixed. Someone put that Link has 4 neutral attacks, which is wrong (should be 3 plus infinite), and the template didn't know what to do with it. Toomai Glittershine The Ghostbuster 00:06, 31 March 2014 (EDT)
Grab
On every page, the template displays the Grab name as {{{grabname}}} and the description as {{{grabdesc}}}. Can this be removed? Awesome Cardinal 2000 16:31, 22 June 2014 (EDT)
- Fill them in, that'll get rid of them. Toomai Glittershine The Emissary 16:59, 22 June 2014 (EDT)
A bit of a problem
I was busy fixing the [[Thunder]]
links to {{b|Thunder|Pokémon}}
, and when I reached "Pikachu (SSB)", I tried changing the "dsname" to Thunder (Pokémon)|Thunder
to emulate the same thing, but it didn't work. When we add moveset tables for Link (SSBB), Young Link (SSBM), etc. etc., the same thing will happen. How can I fix this?Qwerty da beast 01:22, 19 July 2014 (EDT)
- You can fix that for now by using {{!}} instead of |, but yes there's probably a better way. I'll look for one. Toomai Glittershine The Cloronic 08:54, 19 July 2014 (EDT)
- Okay it's now possible to (for example) specify
|dsname=Thunder|dspage=Thunder (Pokémon)
. Toomai Glittershine The Jiggy 09:13, 19 July 2014 (EDT)
- Okay it's now possible to (for example) specify
Names
Can we please have this edited to make the name section optional, and blank if none is entered, for all moves? Miles (talk) 23:05, 1 December 2014 (EST)
No customs for downloadable characters
If someone is willing to wrestle with the wikicode, I think it would be nice to make the rows for custom specials not appear if a SSB4 characters lacks them (like all downloadable characters). --Menshay (talk) 18:23, 1 July 2015 (EDT)
- Alternatively, we could just make a clone of this template for them that removes those rows. Miles (talk) 18:48, 1 July 2015 (EDT)
- I think I can figure something out, but that first requires the decision: will the controlling parameter be called "hascustoms" or "nocustoms"? Toomai Glittershine The Rainbow 18:52, 1 July 2015 (EDT)
- maybe "customs"? We could have boolean values. Nyargleblargle (Talk) 19:18, 1 July 2015 (EDT)
- More to my point, we need to pick whether "yes" or "no" is the default. And because it should be "no" for most games but "yes" for the one where it matters, I don't know what it should be in the end. Toomai Glittershine The Riotous 19:23, 1 July 2015 (EDT)
- Probably no, then. Changing 51 tables is easier than changing 80. Nyargleblargle (Talk) 19:31, 1 July 2015 (EDT)
- More to my point, we need to pick whether "yes" or "no" is the default. And because it should be "no" for most games but "yes" for the one where it matters, I don't know what it should be in the end. Toomai Glittershine The Riotous 19:23, 1 July 2015 (EDT)
- maybe "customs"? We could have boolean values. Nyargleblargle (Talk) 19:18, 1 July 2015 (EDT)
Move-type links fail on character pages
Because the links to move-types (e.g. Neutral aerial, Up Smash) are relative to the page in which the MovesetTable is set, they link to nonexistent pages. To remedy this, I attempted going through each subtable of the MovesetTable (e.g. Template:MovesetTable/Tilts) and fixing the links by removing the initial forwardslash which causes them to mis-link. However, these changes (which did fix problem I have described) were reverted. I am posting here in hopes to see why, and if there is another issue that the solution I have proposed might give rise to, discuss how both issues might be resolved. Verxix (talk) 00:07, 14 August 2015 (EDT)
- The pages being linked to are supposed to exist (eventually), going to pages like this. Toomai Glittershine The Quiet 00:09, 14 August 2015 (EDT)
Proposal on the Addition of Columns
Start-Up, Hitbox Active, First-Actionable-Frame, Angle, Base Knockback, Knockback Growth should be columns added to the moveset table, if I'll be honest. I'll even go out of my way to put in most of, if not all, of these things in their individual columns, if added. I think it would be a nice addition so people can get more of a glimpse of how powerful or weak attacks may be, how fast they are, etc. Any thoughts?
75.66.17.17 17:59, 24 October 2017 (EDT)
- Part of the point of this table is to be minimal in technical data. All the in-depth numbers are for the moveset subpages. Toomai Glittershine The Yellow 19:58, 24 October 2017 (EDT)
- Yeah I am going to have to agree with Toomai here. This would take up way too much space on the table and would be confusing for the entry level players whom these tables are intended for. The only thing we possibly could do is add columns for bkb and kbg (or fixed kb as the case may be) as knockback is more important than damage output anyway...but the problem with that is the fact that each hit of each move typically has more than one hitbox with more than one different knockback value(s) and angles. This is a problem already for listing damage output, but this would be many times worse. It would get far too dynamic far too fast. Serpent King 20:59, 24 October 2017 (EDT)
- Link's Melee Spin Attack is a perfect example of what I mean here. The move has 2 forms, a grounded form and an aerial form. The grounded form has 3 hitboxes, each with different knockback and angle values, and they decay (I think with each spin (6 spins)), so that's 18 (x3 for bkb, kbs, angle) values already. Then the aerial form has 4 hitboxes per hit, and there are 5 hits, meaning take another 20 (x3 again) values right there. So in the end that one move would end up having 38 values just for knockback, which is just unrealistic. Even if you ignored the decay on the grounded one, that's still 3 for the grounded and 20 for the aerial...and 23 values is still unrealistic and overly complex. Serpent King 21:19, 24 October 2017 (EDT)
Ladder attacks
Which subtemplate should we include the new ladder attacks in? Nyargleblargle (Contribs) 22:14, 8 December 2018 (EST)