Difference between revisions of "Template:ArmorList/doc"
From SpiralKnights
m (save point) |
m (save point) |
||
| Line 4: | Line 4: | ||
{| align="left" border="1" cellpadding="4" cellspacing="0" style="border:\#c9c9c9 1px solid; margin: 1em 1em 1em 0; border-collapse: collapse;" | {| align="left" border="1" cellpadding="4" cellspacing="0" style="border:\#c9c9c9 1px solid; margin: 1em 1em 1em 0; border-collapse: collapse;" | ||
| − | |||
| align="center" style="background:#FF9999;"|'''ability type''' | | align="center" style="background:#FF9999;"|'''ability type''' | ||
| + | | align="center" style="background:#99CCFF;"|'''Combination''' | ||
| align="center" style="background:#FFFFFF;"|'''.''' | | align="center" style="background:#FFFFFF;"|'''.''' | ||
| align="center" style="background:#B2B2B2;"|'''Ability Subtype B''' | | align="center" style="background:#B2B2B2;"|'''Ability Subtype B''' | ||
| Line 11: | Line 11: | ||
| align="center" style="background:#99FFCC;"|'''Intensity''' | | align="center" style="background:#99FFCC;"|'''Intensity''' | ||
|- | |- | ||
| − | |1 = | + | |1 = Uniform||1 = just one||.||1 = Damage||1 = Beast||0 = Maximum! |
|- | |- | ||
| − | | | + | |2 = Item Bonus||2 = two abilities of the same type (example: [[Ancient Plate Mail]])||.||2 = Charge Time||2 = Construct||1 = Ultra |
|- | |- | ||
| − | + | |3 = Monster Bonus||3 = three abilities of the same type (example: [[Sacred Falcon Pathfinder Helm]])||.||3 = Attack Speed||3 = Fiend||2 = Very High | |
|- | |- | ||
| − | + | |4 = Penalty|| ||.||4 = Movement Speed||4 = Gremlin||3 = High | |
|- | |- | ||
| − | | || ||.|| || | + | | || ||.|| ||5 = Slime||4 = Medium |
|- | |- | ||
| − | | || ||.|| || | + | | || ||.|| ||6 = Undead||5 = Low |
|- | |- | ||
|} | |} | ||
| Line 27: | Line 27: | ||
These interrelated columns might seem redundant when it comes to certain placeholder values, but in a world where templates are dynamic, we want to keep the possibility of merging columns and templates together as time goes on. This number sorting system permits some flexibility for these changes - meaning that the data entries can stay the same while editors change the display. | These interrelated columns might seem redundant when it comes to certain placeholder values, but in a world where templates are dynamic, we want to keep the possibility of merging columns and templates together as time goes on. This number sorting system permits some flexibility for these changes - meaning that the data entries can stay the same while editors change the display. | ||
| − | + | There's plenty of room if different kinds of penalties are put into the game later. Oh, yeah we don't really see Ultra. If we ever do, it has a placeholder - so things can be updated easily. You see? Oh well in case you don't, here's a few examples in action: | |
Example: | Example: | ||
Revision as of 16:13, 20 December 2014
To permit flexibility in a changing game, the template is designed to sort via numbers while showing icons. These numbers seem to be "huge" numbers...do they signify damage or resistance values in-game? Nay! They are a system of placeholder values so that new values (which could show up with a game update, and have before many times) can be added without disrupting an entire numerically sorted column. This also saves a small amount of space in the templates that use them.
For the number placeholder "##.####" each column in the table below corresponds to a digit in this "big number," left to right:
| ability type | Combination | . | Ability Subtype B | Ability Subtype A | Intensity |
| 1 = Uniform | 1 = just one | . | 1 = Damage | 1 = Beast | 0 = Maximum! |
| 2 = Item Bonus | 2 = two abilities of the same type (example: Ancient Plate Mail) | . | 2 = Charge Time | 2 = Construct | 1 = Ultra |
| 3 = Monster Bonus | 3 = three abilities of the same type (example: Sacred Falcon Pathfinder Helm) | . | 3 = Attack Speed | 3 = Fiend | 2 = Very High |
| 4 = Penalty | . | 4 = Movement Speed | 4 = Gremlin | 3 = High | |
| . | 5 = Slime | 4 = Medium | |||
| . | 6 = Undead | 5 = Low |
These interrelated columns might seem redundant when it comes to certain placeholder values, but in a world where templates are dynamic, we want to keep the possibility of merging columns and templates together as time goes on. This number sorting system permits some flexibility for these changes - meaning that the data entries can stay the same while editors change the display.
There's plenty of room if different kinds of penalties are put into the game later. Oh, yeah we don't really see Ultra. If we ever do, it has a placeholder - so things can be updated easily. You see? Oh well in case you don't, here's a few examples in action:
Example:
