Difference between revisions of "Template:Colorstyle"
From SpiralKnights
m (Figured out I had the two backwards, but realized the height is a better value to change (derp). Next is to add the variables in (somehow)) |
m (added in variables for a test) |
||
Line 7: | Line 7: | ||
{{SKWindow/NewRow}} | {{SKWindow/NewRow}} | ||
− | {{SKWindow/EmptyCell| |center|top|1|1|*|40px| | + | {{SKWindow/EmptyCell| |center|top|1|1|*|40px|{{{primary}}}}} |
{{SKWindow/NewRow}} | {{SKWindow/NewRow}} | ||
− | {{SKWindow/EmptyCell| |center|center|1|1|*|40px| | + | {{SKWindow/EmptyCell| |center|center|1|1|*|40px|{{{secondary}}}}} |
{{SKWindow/NewRow}} | {{SKWindow/NewRow}} | ||
− | {{SKWindow/EmptyCell| |center|bottom|1|1|*|40px| | + | {{SKWindow/EmptyCell| |center|bottom|1|1|*|40px|{{{tertiary}}}}} |
}} | }} |
Revision as of 06:15, 13 May 2014
| |||
|
Image showing what I want over there in the module. I do NOT want that to be an image, but rather a block that can change color based on the colorIDcode you plug and chug into it. This example is for Hallow. I also do not want primary/secondary/tertiary labels, as not all items of that style have the same P/S/T orientation.
Image showing a possible end result.- please note: this isn't isolated to event styles. We could do this for toasty, dusky, even prismatic.
- Purpose: information module on style pages
From template: accessorystyle (delete this section later)
{{{1}}} |