Template:CostumeTable/Recolors/doc

From SpiralKnights

Revision as of 05:04, 24 December 2015 by Novaster (Talk | contribs)

Jump to: navigation, search

Usage

Used to update several costume recolor pages rapidly. Simply add the color style to the code of this template, instead of one at a time in every page. This reduces copy/paste spacing errors and allows editors to simply force-refresh the pages, upload desired images, and be done.

Parameters

On Published Pages

See what links here for examples of this template in action.

1
The costume name. We have hunter scale mail, vile scale mail...use Scale Mail.
2
A number deciding which list of recolors the template will display on the page:
1 = Recolors
2 = Recolors not including hunter
3 = Recolors including hunter and serene (serene=ancient)

This Template's Code

Edit this template to add or fix data in the display within the sibling templates. Simply copypaste a previous entry and fix it up with the new data. If there is a significant pattern change in the future (such as hunter, or if not all of these items were released in a new color), fix this template accordingly with a switch, and/or discuss it with editors on the talk page. See sibling template: Template:CostumeTable/doc for more parameter details.

Notes

Due to the pattern of releases, this template has not been merged with Template:AccessoryTable/Recolors. Not all costumes have been released in all "recolor" color patterns - this is the case with polar, for example. They could be merged with some chunky switches, if editors wish to do so in the future, but aside from template compression, there isn't a huge need to do so - it would require more specified inputs on individual pages, too.

It is generally a good idea to keep display templates for different item types separate - we don't have a uniform accessory and costume template table, even though the fields are currently so similar. This is because the game might update one item type, requiring a slightly different display, or editors may wish to include information such as slots or description in the table, which would not apply to accessories, and would require chunky switches in a uniform template and yet more specified inputs on individual pages. This is a different issue than within-template consistency data, which applies to templates such as DoRSource.

Personal tools