Template talk:Skin infobox

Kick-off

I thought that I'd get this kicked off.

Current thoughts:

• Color - I don't think that it should be the same color as items, armor nor weapons - I thought pink was alright for this.
• Property naming scheme - I've used "Property:Has skin supertype" for armor/weapon/back item, and "Property:Has skin type" for the usual suspects.

I don't think that I've missed anything yet. -Chieftain Alex 11:39, 23 April 2014 (UTC)

Skin type names for allowable property values needs sorting. -Chieftain Alex 11:52, 23 April 2014 (UTC)

Pink works for me. poke | talk 12:12, 23 April 2014 (UTC)

Added a couple extra variables for usage in item variant rows for loot items. —Dr Ishmael 12:45, 23 April 2014 (UTC)

you mentioned delinking Property:Has skin type from weapon+item infoboxes on my talk page. If NAME OF SKIN = NAME OF WEAPON/ARMOR, will we add skin details + keep the type annotated on those pages? -Chieftain Alex 14:16, 23 April 2014 (UTC)

Pink added to css as .skin (could have called it .dulfy colors I guess >.> <,<). GW2W:COLORS updated + Chat link format/0x0B codes created using poke's sandbox1. -Chieftain Alex 16:17, 24 April 2014 (UTC)

Category names

Currently this generates some pretty irksome category names for armor (luckily we don't have many pages using it yet... 1), i.e.

• Light helm skins
• Light aquatic helm skins
• Light shoulders skins
• Light coat skins
• Light gloves skins
• Light leggings skins
• Light boots skins

Possible options:

Option 1. (Dropping the "s")	Option 2. (What we use for the icons)
Light helm skins Light aquatic helm skins Light shoulder skins Light coat skins Light glove skins Light legging skins Light boot skins	Light headwear skins Light aquatic headwear skins Light shoulderwear skins Light chestwear skins Light handwear skins Light legwear skins Light footwear skins

Option 1 imo. thoughts/suggestions? -Chieftain Alex 23:42, 29 April 2014 (UTC)

Shut our brains off and use the wardrobe names for these categories:

• Light/Medium/Heavy Headgear Skins
• Light/Medium/Heavy Shoulders Skins
• Light/Medium/Heavy Chest Skins
• Light/Medium/Heavy Gloves Skins
• Light/Medium/Heavy Leggings Skins
• Light/Medium/Heavy Boots Skins
• Light/Medium/Heavy Aquatic Headgear Skins
• Back Skins

A couple of them sound a bit strange, but by all regards we should use it. Its canon. Psycho Robot (talk) 23:53, 29 April 2014 (UTC)

Jeez, the wardrobe really has such clunkers? :/ -Chieftain Alex 23:58, 29 April 2014 (UTC)

If you remove "skins" then you have all the category names in the wardrobe. For example, there's a category called Light Headgear, Medium Headgear, Heavy Headgear. The skins would be something we'd be adding... so theoretically we could change that bit. Psycho Robot (talk) 23:59, 29 April 2014 (UTC)

(Edit conflict) I've never been a fan of the "-wear" names, as they don't correlate to any of the in-game terms at all (cf. table), but I never felt it was worth my time to complain about some silly old file categories.

However, I'm not sure about trimming the "-s" on the pseudo-plural terms, either, at least not on all of them. For one, "legging" sounds really strange - even though it is a dictionary word, it is hardly ever used in the singular. Just because the combination sounds weird doesn't mean it's wrong - would "light boots icons" be as objectionable, without the "-s s-" construct? (I know there's a phonetic/etymological name for that.) —Dr Ishmael 00:07, 30 April 2014 (UTC)

@Psycho: the terms used in the wardrobe match the "Slot tooltip" column in the table I linked. Most internal things on the wiki, however, are following the API. —Dr Ishmael 00:09, 30 April 2014 (UTC)

I thought the type would have the Property:Has armor type and had Property:Has armor weight class if it has its own infobox... It should match armor infobox on categories too. --Relyk ~ talk < 00:40, 30 April 2014 (UTC)

Perhaps because we now have a very visible in-game source - the wardrobe categories - we can take this as an opportunity for change? I previously pushed for the API because no in-game source was obviously better than any other, and I'd be fine sticking with that, but I'd also be fine switching to the wardrobe terms. We already deviate from the API on four weapon types: LongBow -> Longbow, ShortBow -> Short bow, Speargun -> Harpoon gun, Harpoon -> Spear. —Dr Ishmael 01:01, 30 April 2014 (UTC)

I like the wardrobe categories over the Trading Post because we have a category every single slot and this makes it close to de facto for players. The only addendum being that we wouldn't use "back" over "back item". The official articles use "back-slot item", "back item", or "back piece" and most people will favor "back item slot" over "back slot" at this point. This is an argument that our item types are page properties and should link to the actual page instead of something like having "Back" as the value and redirecting to back item. It follows that the category names match the page names and use the same semantics.--Relyk ~ talk < 09:06, 30 April 2014 (UTC)

Psycho's Wardrobe Skin Categories	Relyk's addendum	Alex doesn't give two fucks and thinks it should be singular item with plural "skins"
Light/Medium/Heavy Headgear Skins Light/Medium/Heavy Shoulders Skins Light/Medium/Heavy Chest Skins Light/Medium/Heavy Gloves Skins Light/Medium/Heavy Leggings Skins Light/Medium/Heavy Boots Skins Light/Medium/Heavy Aquatic Headgear Skins Back Skin Skins	Light/Medium/Heavy headgear skins Light/Medium/Heavy shoulders skins Light/Medium/Heavy chest skins Light/Medium/Heavy gloves skins Light/Medium/Heavy leggings skins Light/Medium/Heavy boots skins Light/Medium/Heavy aquatic headgear skins Back item skins	Light/Medium/Heavy headgear skins Light/Medium/Heavy shoulder skins Light/Medium/Heavy chest skins Light/Medium/Heavy glove skins Light/Medium/Heavy legging skins Light/Medium/Heavy boot skins Light/Medium/Heavy aquatic headgear skins Back item skins

Alright. Last orders for category names. Happy with these or not? -Chieftain Alex 00:53, 8 May 2014 (UTC)

I am fine with all of them. I'm not sure if its relevant anymore but when I transcribed the skin category names from the wardrobe, I made a mistake. It's not Back Skin Skins, as you may have guessed. Its simply Back Skins. The category name in the wardrobe is just "back". Psycho Robot (talk) 00:57, 8 May 2014 (UTC)

(Added my favourites back in to the table.) -Chieftain Alex 00:59, 8 May 2014 (UTC)

It would be most logical for everything to match - parameter values, property values, display text, and category names. We've had a disconnect for a long time due to using the API values for parameter/property values but translating e.g. coat to chestwear for the category. I admit, that's mostly my fault for insisting on following the API (and I deeply regret not fighting for the categories), but as I said above, I'm going to relent and let the wardrobe trump the API. So my vote's for the (current, untl Alex adds something else) second column. —Dr Ishmael 02:04, 8 May 2014 (UTC)

possible idea: "Category:Skins for Heavy Boots" / "Category:Skins for Gloves" etc -Chieftain Alex 02:24, 8 May 2014 (UTC)

If it could be organised so that we end up with a category:Skin/Heads, that would be super. — snograt 08:40, 8 May 2014 (UTC)

00:40, 30 April 2014 (UTC)

2017

Wardrobe + Trading post	(Aquatic) Headgear / Shoulders / Chest / Gloves / Leggings / Boots
API	Helm(Aquatic) / Shoulders / Coat / Gloves / Leggings / Boots
Current icon categories	Headwear / Shoulderwear / Chestwear / Handwear / Legwear / Footwear

So it's been three years since I last asked about this topic. I propose we use the ingame nomenclature for the categories too, i.e. <Weight uppercase first> <type name as reads ingame lowercase> icons.png -Chieftain Alex 14:15, 1 October 2017 (UTC)

But, I was just getting back in the habit of re-writing "headgear" and "chest" on all those skin pages... Seriously, though, if you could unify these things, I'd be very grateful! G R E E N E R 14:21, 1 October 2017 (UTC)

Old

New

Category:Light headwear icons Category:Light shoulderwear icons Category:Light chestwear icons Category:Light handwear icons Category:Light legwear icons Category:Light footwear icons Category:Medium headwear icons Category:Medium shoulderwear icons Category:Medium chestwear icons Category:Medium handwear icons Category:Medium legwear icons Category:Medium footwear icons Category:Heavy headwear icons Category:Heavy shoulderwear icons Category:Heavy chestwear icons Category:Heavy handwear icons Category:Heavy legwear icons Category:Heavy footwear icons

Category:Light headgear icons Category:Light shoulders icons Category:Light chest icons Category:Light gloves icons Category:Light leggings icons Category:Light boots icons Category:Medium headgear icons Category:Medium shoulders icons Category:Medium chest icons Category:Medium gloves icons Category:Medium leggings icons Category:Medium boots icons Category:Heavy headgear icons Category:Heavy shoulders icons Category:Heavy chest icons Category:Heavy gloves icons Category:Heavy leggings icons Category:Heavy boots icons Category:Headgear icons Category:Shoulders icons Category:Chest icons Category:Gloves icons Category:Leggings icons Category:Boots icons

Not sure about this anymore. -Chieftain Alex 18:29, 5 October 2017 (UTC)

Done anyway. -Chieftain Alex 15:16, 6 August 2022 (UTC)

2022

Giving this a kick (spurred on by the to do list prompt). The double plurals on some of the categories above irk me a bit. e.g. "heavy/medium/light boots/gloves/leggings/shoulders icons". -Chieftain Alex 18:05, 5 August 2022 (UTC)

could reverse it and do "boots/gloves/leggings/shoulders heavy/medium/light icons" -Chieftain Alex 18:09, 5 August 2022 (UTC)

Wardrobe + Trading post + Current icon categories Wiki: Template:Armor infobox / Template:Skin infobox	(Aquatic) Headgear / Shoulders / Chest / Gloves / Leggings / Boots
Recipes Wiki: Template:Recipe	Helms (includes aquatic ones) / Shoulders / Coats / Gloves / Leggings / Boots
API	Helm(Aquatic) / Shoulders / Coat / Gloves / Leggings / Boots
Item Tooltips	Head Armor / Shoulder Armor / Chest Armor / Hand Armor / Leg Armor / Foot Armor

We planning on make new pages for every skin in the wardrobe?

so, just wondering if this is something we need/want? Because I would love to waste my time creating them xD Dustix (talk) 14:40, 14 June 2014 (UTC)

I think there is a complete list on someone's page? I think it was Relyk or someone else, can't remember; feel free to correct me if I'm wrong, though. --Ventriloquist (talk) 14:55, 14 June 2014 (UTC)

http://wiki.guildwars2.com/wiki/Chat_link_format/0x0B_codes -149.254.250.98 22:24, 21 June 2014 (UTC)

Hidden skins

I was wondering if we should add a variable to track which skins are hidden until unlocked. I know one of the users has a list with a lot of them marked, but it hasn't been updated in a long time. SarielV 18:01, 13 November 2015 (UTC)

So, about {{Default item parameter}}...

{{Default item parameter}} sets [[Has context::Item]]. That seems a bit inappropriate for skins. It also doesn't set [[Has game id]] for the "skin id" parameter, so skins now have two game contexts but no game IDs. -- Dagger (talk) 00:46, 16 December 2015 (UTC)

"set" parameter

currently since it is using the logic from the weapon infobox, it ends up sticking " weapons" on the end of the given parameter. This clearly isn't appropriate if the set is called "Bloodstone weapon skins". Note to self to fix. The current workaround is to create a redirect from the malformed weapon set pagename to the actual set name. -Chieftain Alex 06:35, 25 August 2016 (UTC)

Moving towards using the skin infobox to set the default appearance and icons for items

^ I've been moving loads of files around today with the objective of having the filenames match, or be very similar to, the canonical skin name. Eventually I'd like to be able to just specify the skin on a weapon infobox, and let it fill out the gallery and icon from the skin page. -Chieftain Alex 14:14, 20 November 2016 (UTC)

There may be a few oddballs out there where that doesn't match (only one that comes to mind off the top of my head is one of the windcatcher skins), so you'll need to leave a way to override it. SarielV 14:45, 30 November 2016 (UTC)

Default rarity

The rarity variable is very rarely filled out, which is understandable. Most skins are Basic, and the exceptions are few enough to not grab anyone's attention. Can someone update the infobox to show the default as Basic? Or would it be better to go through each skin and specify them individually? SarielV 14:48, 30 November 2016 (UTC)

API link

Since this is being tested on the skin infobox, I figured I could start this here. I for one am for the addition of the API link in the infoboxes, and would like to see it in all other relevant places. It's not really intrusive since we pretty much already have links to 3rd party websites anyway (for item infoboxes)-Darqam 16:04, 10 December 2016 (UTC)

I thought I'd start with an infobox that doesn't need {{default item parameter}}. I'm evidently for including an API link too. Is the display name fine? (currently "API", could be "Official API", "GW2 API" etc) -Chieftain Alex 17:19, 10 December 2016 (UTC)

FWIW I've been using this JS:

    /* Add a numeric ID after every chat link field,
     * linking to the corresponding API endpoint. */
     $("span.gamelink").each(function() {
      var id = this.getAttribute("data-id");
      var type = this.getAttribute("data-type");
      var url = "https://api.guildwars2.com/v2/" + type + "s/" + id;
      $("<span/>").append(" (").append($("<a/>", { text: id, href: url })).append(")").insertAfter(this);
    });

which produces something like this:

   Item link    [&AgFFlgAA] (38469)
   Skin link    [&CsAUAAA=] (5312)

which has the advantage of not taking any extra lines in the infobox. -- Dagger (talk) 17:51, 10 December 2016 (UTC)

"External link" makes it sound like an unofficial source to me and the API is still in the "guildwars2.com" domain. I like "Official API" followed by the number. J.Tesla (talk) 18:55, 10 December 2016 (UTC)

Dye slots and channels

Thought I'd document something here on the talkpage for the future. Following a discussion on User talk:Akashanephthys, it was suggested to insert the number of slots into the infobox. I originally also thought it would be neat to add the default dyes in too.

However although the number of slots stated within API:2/colors is stable, the default dyes returned by the API associated with each skin randomly change and is NOT at all stable. On the basis of not trusting the information for dye colours in the API I've chosen not to add this in the end. -Chieftain Alex 11:02, 19 June 2021 (UTC)

Nice, thanks! The suffix (default) feels a little bit redundant when there are no other race/gender depending dye channels. What about deactivating it on default? --Tolkyria (talk) 21:11, 20 June 2021 (UTC)

Agree, suffix is not needed if there is only one number. —Kvothe (talk) 16:13, 22 August 2021 (UTC)

Collection icon

Can someone add the collection icon to this template too? See this edit on default item parameter. I came up with the following code but that is just based on deduction and not real understanding of the code. —Kvothe (talk) 09:30, 4 August 2021 (UTC)

{{#if: {{{collection|}}} | 
;[[Collections|Collection]]
:{{#arraymap: {{{collection}}}|;|@@@|<!--
-->{{#if: {{#pos:@@@|#achievement}}
    | [[{{#show: @@@|?Has game icon|link=none}}|20px|link=@@@]] [[@@@|{{#show: @@@|?Has canonical name}}]]
    | [[{{#ask: [[Has achievement page::@@@]]|?Has game icon|headers=hide|link=none|mainlabel=-|limit=1|searchlabel=|default=File:Skill.png}}|20px|link=@@@]] <!--
   -->[[@@@|{{#ask: [[Has achievement page::@@@]]|?Has canonical name|headers=hide|link=none|mainlabel=-|limit=1|searchlabel=|default=@@@}}]]
   }}|<br>}}
}}

The code is kinda complicated because it also supports achievement subobjects, i.e. <achievement page>#achievement<id> for collection pages that don't have any individual achievement page. Not sure if we actually need this? I can't find any page where we actually use it.

Thus, if we would remove it (also from the default item parameter template) it would simplify to:

{{#if: {{{collection|}}} | 
;[[Collections|Collection]]
:{{#arraymap: {{{collection}}}|;|@@@|{{#set:Is part of collection=@@@}}<!--
-->[[{{#ask: [[Has achievement page::@@@]]|?Has game icon|headers=hide|link=none|mainlabel=-|limit=1|searchlabel=|default=File:Skill.png}}|20px|link=@@@]] <!--
-->[[@@@|{{#ask: [[Has achievement page::@@@]]|?Has canonical name|headers=hide|link=none|mainlabel=-|limit=1|searchlabel=|default=@@@}}]]|<br>}}
}}

--Tolkyria (talk) 09:52, 4 August 2021 (UTC)

Collections always get their own page, so it should not be an issue. —Kvothe (talk) 10:11, 4 August 2021 (UTC)

Added to the skin infobox.

We had one case once, that's why I introduced it in the default item parameter template. I removed it, see this Default item parameter edit. --Tolkyria (talk) 10:48, 4 August 2021 (UTC)

Thank you. —Kvothe (talk) 11:27, 4 August 2021 (UTC)

Back item/skin category

Currently we have Category:Back item skins which consists of both consumable skin items and skins. Does it make sense to split the category and have "Category: Back skin"? —Kvothe (talk) 16:16, 22 August 2021 (UTC)

Or rather we have Category:Back items too, so I want to suggest a rename and consistent use of item/item skin/skin. —Kvothe (talk) 16:18, 22 August 2021 (UTC)