Difference between revisions of "Template talk:ArmorList"
From SpiralKnights
m (line breaks) |
(decimal breaks) |
||
| Line 2: | Line 2: | ||
So far, the only defense (normal, elemental, piercing, shadow) bar values we see after quantifying via pixel counting are: | So far, the only defense (normal, elemental, piercing, shadow) bar values we see after quantifying via pixel counting are: | ||
| + | <br/> | ||
<br/> | <br/> | ||
00.05<br/> | 00.05<br/> | ||
00.07<br/> | 00.07<br/> | ||
00.10<br/> | 00.10<br/> | ||
| − | 00.12<br/> | + | 00.12<br/><br/> |
01.07<br/> | 01.07<br/> | ||
01.11<br/> | 01.11<br/> | ||
01.12<br/> | 01.12<br/> | ||
| − | 01.14<br/> | + | 01.14<br/><br/> |
02.00<br/> | 02.00<br/> | ||
| − | 02.02<br/> | + | 02.02<br/><br/> |
04.00<br/> | 04.00<br/> | ||
04.04<br/> | 04.04<br/> | ||
04.05<br/> | 04.05<br/> | ||
| − | 04.06<br/> | + | 04.06<br/><br/> |
05.01<br/> | 05.01<br/> | ||
05.05<br/> | 05.05<br/> | ||
05.07<br/> | 05.07<br/> | ||
| − | 05.08<br/> | + | 05.08<br/><br/> |
06.05<br/> | 06.05<br/> | ||
| − | 06.13<br/> | + | 06.13<br/><br/> |
| − | 07.11<br/> | + | 07.11<br/><br/> |
| − | 08.13<br/> | + | 08.13<br/><br/> |
| − | <br/> | + | 0 should never be entered and remain a blank space, though I have put in coding to take care of that, it's unneeded labor. Let's have 0 labor for 0. |
| − | 0 should never be entered and remain a blank space. | + | <br/><br/> |
| − | <br/> | + | |
9 is used as a noteholder about how the stats image might not be fully informative about the item's performance, if the bar is completely full. | 9 is used as a noteholder about how the stats image might not be fully informative about the item's performance, if the bar is completely full. | ||
| − | <br/> | + | <br/><br/> |
| − | + | ---- | |
I will leave the number range (the values these #are = in the relevant switch used to organize images instead of text in the table) as is, so editors can add in new values without disrupting an entire numerically ordered column. Sometimes we get new stat bar values, so this flexibility is needed. But having the flexibility actively taking up space in the template all the time is not. Hence: reducing number space. | I will leave the number range (the values these #are = in the relevant switch used to organize images instead of text in the table) as is, so editors can add in new values without disrupting an entire numerically ordered column. Sometimes we get new stat bar values, so this flexibility is needed. But having the flexibility actively taking up space in the template all the time is not. Hence: reducing number space. | ||
Revision as of 01:07, 10 December 2014
Going through and reducing number space.
So far, the only defense (normal, elemental, piercing, shadow) bar values we see after quantifying via pixel counting are:
00.05
00.07
00.10
00.12
01.07
01.11
01.12
01.14
02.00
02.02
04.00
04.04
04.05
04.06
05.01
05.05
05.07
05.08
06.05
06.13
07.11
08.13
0 should never be entered and remain a blank space, though I have put in coding to take care of that, it's unneeded labor. Let's have 0 labor for 0.
9 is used as a noteholder about how the stats image might not be fully informative about the item's performance, if the bar is completely full.
I will leave the number range (the values these #are = in the relevant switch used to organize images instead of text in the table) as is, so editors can add in new values without disrupting an entire numerically ordered column. Sometimes we get new stat bar values, so this flexibility is needed. But having the flexibility actively taking up space in the template all the time is not. Hence: reducing number space.
