Template Request

5 replies [Last post]
Dracora-Speaking

Halp. If someone can, -make this work.

Thanks <3

This is what I would like to see:

look at Costumes (Recolors). Those are some rather nice, rather unconventional, tables that people seem to like. I'd like to have something like {{CostumeRecolors|Hunter}} and {{CostumeRecolors|Shadow}} to just stick on the page in each ToC section, so when new recolors come out, we can just be like BAM, {{CostumeRecolors|NEWSTYLE}} and just upload images. Something to worry about: if my very shoddy understanding of coding is correct, then if there's more types (like hunter doesn't have crescent/flak/round/draped), then there might have to be different templates for each collection that has a different # of recolors in it. Not sure.

So far:
1 = color style
2 = fur cap
3 = hood
4 = pith helm
5 = plate helm
6 = sallet
7 = scaled helm
8 = tailed helm
9 = winged helm
10 = fur coat
11 = cloak
12 = brigandine
13 = plate mail (recolor)
14 = cuirass
15 = scale mail
16 = culet
17 = raiment

This applies to hunter. All the rest of the recolors have 4 more items: idk what to do about crescent/flak/round/draped - a whole new template or is there a nifty trick? And what if there's more forms in the future?

I could manage this if the whole visual weren't so...interesting...it is "interesting," isn't it? XD...very unconventional...but people like...loooooved it...in that costume forum node discussion...

This isn't a big deal, it would just mean less "fixing every line that says "surge" from my copy-paste to "NEWSTYLE"

Mon, 08/04/2014 - 14:29 #1
Skepticraven
↓

It could easily be done in the form of:

{{CostumeRecolors|[Name of style]|[List of available types]}}

For example:

{{CostumeRecolors|Hunter|Fur Cap|Hood|Pith Helm|Plate Helm|Sallet|Scale Helm|Tailed Helm|Winged Helm|Fur Coat|Cloak|Brigandine|Plate Mail|Cuirass|Scale Mail|Cutlet|Raiment}}

Or even using a key and documenting the key in the template would work as well for something shorter like this:

{{CostumeRecolors|Hunter|2|3|4|5|6|7|8|9|10|11|12|13|14|15|16|17}}

Using the numbering system you made.

Some things to think about:
Plate Mail (Recolor)|Plate Mail part may have to be hard coded (to be interpreted as "Plate Mail" that will convert to "Plate Mail (Recolor)|Plate Mail") [With numbering system this can be ignored].
Should the table be reorganized? (Currently there is an equal number of helms+armors, with matching style helms on top of armors, with the armor links below the image).
This wont work well for the Jackobombhead, or other specialty small tables.
Organization might pose a problem if number of helms is not the same as number of armors.

Edit:
Come to think of it, it might be simplest to just make a 2 parameter template:
{{CostumeRecolors|[Name of style]|[Available Style Key]}}

Where "Available Style Key" would refer to the list of costumes that would be available (and wouldnt need to be updated if the new stuff matched a currently used list).

Edit2:
Just added my second idea in. Hopefully i changed the template page so people understand it.

Mon, 08/04/2014 - 14:24 #2
Dracora-Speaking
heh

yeah I realized a few minutes ago that each item doesn't need a number, my brain was derping with the "hunter" vs. "every other recolor" so far.

Mon, 08/04/2014 - 16:44 #4
Dracora-Speaking
@Skepticraven

yes ;n;

One more thing:
make images link to the same thing the text does (like all the "STYLE-pith helm" pics link to the pith helm costume page. It's repetitive...but it's desired). I find that users really like clicking images to go to relevant pages. I feel like I could do it but I don't want to break it...

Thaaaaaank you.

Mon, 08/04/2014 - 17:21 #5
Skepticraven
↓

Easy change. (Oddly enough the fur coat was already done for hunter and nothing else and only noticed it while adding it in only to find my copy-pasta did the work for that one already.)

It's just a "|link=Pith Helm" in the image File tag, for future reference.
Should get pushed out the next time the wiki decides to update the pages.

I decided to opt for a bit more documentation on the template so that people that miss this thread can still hopefully use it easily.