Template talk:CharacterPhysics
So here's the deal with this:
Last night on Discord I brought up the idea of making a template like this, which would be used for per-game character pages like Mario (SSB4) and Donkey Kong (SSB4) and such. While the attributes sections of these pages describe the character's general physics (mobility and weight and traction and such), it always bothered me that you need to hit up a ton of different pages to get the exact values for those.
It bothers me so much that I said I'd be willing to make the template and fill it out for every single character page myself, and I still stand by that... Except for the "make the template" part. I was woefully underprepared to make a template in Wikitext that works in this "fill-in-the-blanks" way, and even after basically two entire nights and an afternoon, I've not really been able to figure out how to code a template like this.
This template is incomplete and almost certainly nonfunctional. What you see on the page is an approximation of how I think it should look, and beneath it is the code that I want to be used to fill it out. I'm posting it regardless though, because at the rate things are going (and given my level of coding knowledge), I doubt I'll be able to do it myself.
Also, I realize it's kind of strange to post something like this, which is essentially a proposition, outside of the forum. I was given the OK to go ahead and make it by Toomai though. He says that anybody who cares will see this and be open to discuss it. And we will need to discuss this, because it's possible I left out some things, or put some unnecessary things in. Please use this talk page to discuss potential changes to be made to this table, or whether you want to use it at all, because we'll need to come to a consensus on what we want this to look like.
Sorry about how messy this all is top to bottom, but it's here now. Please share your thoughts. Someone who's more knowledgeable with Wikitext can finish the template if they want, but like I said before, I'll still take it upon myself to actually put the thing on relevant pages. Nymbare and his talk 21:46, 2 July 2017 (EDT)
Support
I see no problems. I would fully support this as standard on character pages.
--- Monsieur Crow, Author Extraordinaire, 21:50, 2 July 2017 (EDT)
I'd be down for this Poultry(talk) the God-Slayer 11:24, 4 July 2017 (EDT)
Support This would tie pages together with information that is more easily comparable in one table. RobSir zx 20:25, 4 July 2017 (EDT)
Support. I've wished we had something like this in the past. Nyargleblargle (Contribs) 21:25, 4 July 2017 (EDT)
Neutral
I agree that it would be nice to have these values in an easy format, but I am unsure this is the way to do it. Serpent King 22:08, 2 July 2017 (EDT)
- If not something like this, what other ways do you think we could present the values? Nymbare and his talk 20:17, 4 July 2017 (EDT)
Oppose
...
Discuss potential changes here
One thing I should note is that I deliberately left out landing lag, of which some characters have unique values (for Hard Landings exclusively, as far as I'm aware). Should we include that, or no? We may also need to do a per-game split to account for various system changes. Nymbare and his talk 21:46, 2 July 2017 (EDT)
- What if we made the table vertical then floated it to the right of the moveset table? Serpent King 04:29, 4 July 2017 (EDT)
- That could work quite nicely, actually. Now that I think about it, it may "clash", in a way, for this to be a horizontal template where the overwhelming majority of templates like this are vertical. I would be alright with this change. Nymbare and his talk 20:17, 4 July 2017 (EDT)
We might want to make only more basic stats like jump count and weight visible at first glance but include a separate, initially hidden table with the ranks and other stats. Nyargleblargle (Contribs) 21:25, 4 July 2017 (EDT)
Okay here's my quick opinions:
- Don't put three numbers in one cell for aerial maneuverability.
- Some things could be reordered; put traction and jumpsquat before aerial movement for example. Weight should be last.
- Don't float one table next to another. That's just ugly2.
- I think weight and number of jumps could be important enough to put in the infobox instead of this. Not 100% sure though.
Toomai Glittershine The Brazen 21:34, 4 July 2017 (EDT)
- I also oppose putting a theoretical table next to the moveset table; it'd make pages look far too "busy" and "messy.". I'd prefer putting this table either as part of the Character infobox, or in the attributes section.