Template talk:Simple icon

it'll trim the borders on trait icons.--Relyk ~ talk < 18:54, 25 June 2013 (UTC)

traits

the icon this makes looks really bad for me I am wondering why for traits it dost use the same icon format that {{Trait icon}} uses?- Zesbeer 05:19, 17 April 2014 (UTC)

Template uses {{borderless}} strip the black box around skill icons.--Relyk ~ talk < 05:37, 17 April 2014 (UTC)

ok, but regardless of that but this:  Deployable Turrets looks 100000% better then this:   Deployable Turrets. - Zesbeer 06:08, 17 April 2014 (UTC)

@Relyk: unless you can make switch logic to not use borderless for trait icons, then this shouldn't be used for trait icons. I know the point of this was to reduce the query/template load on game update pages, but since the trait icon template doesn't use borderless, that's a lot less template code to be parsed, even though it introduces a semantic query. —Dr Ishmael 12:33, 17 April 2014 (UTC)

Filenames that differ from pagename

Game updates/2015-06-23 has a bunch of missing skill icons because the skill pagename is different to the skill icon name (e.g. Detonate Supply Crate Turrets and File:Detonate Net Turret.png). Recent file deletions imply that "Redundant images" are not wanted. This template provides an override for display text but not icons.
Is it recommended to:

1. do parameter override? — anywhere this template is used the parameter has to be specified to avoid broken file links, and multiple edits are required to change the destination link
2. do file redirects? — anytime the icon for a skill needs to be updated, only one change to the redirect destination is required to propagate the change
3. ignore those red links? — blah redlinks are not harmful blah pretty pictures not needed blah
4. do something else...? — I don't know

Also, I'm curious as to what the current policy/guideline for duplicate (skill, item, etc) icon is. --BryghtShadow (talk) 10:12, 27 August 2015 (UTC)

Well the images themselves are exact dupes of other files, and certainly in most situations, stuff fixes itself because we use SMW to annotate the specific file. The whole point of this template is to stop smw breaking things on long pages. I'm loathe to use redirects since I recall the file redirect function is (/was?) usually added by poke each time a MW update turned up, and I don't know if it'll be around forever. For now at least I'll add an "icon" parameter to circumvent the problem for now. (My real problem is that I trust people to check what links to things before tagging stuff with delete >.<) -Chieftain Alex 13:08, 27 August 2015 (UTC)

traits v2

Revisiting old discussion (#traits) Trait icons look terrible when {{borderless}} is applied to them. This template supports the common trait icons (I~XIII) via {{{3}}}, so how about using {{{3}}} as a way to say "this is a trait, don't apply borderless"? See example. --BryghtShadow (talk) 12:09, 18 February 2016 (UTC)

So the changes suggested remove borderless if trait=y or if a numeral trait=i is specified. Sounds good. I'd probably still link to the skill in the default case from borderless. Feel free to update this template. -Chieftain Alex 13:05, 18 February 2016 (UTC)

Alrighty, I'll apply the changes to this. (Also, woops. added linking for borderless in suggested changes.) --BryghtShadow (talk) 13:54, 18 February 2016 (UTC)

I've seen usage for other icons besides skills and traits, so maybe {{{border}}} or {{{borderless}}} would be a more descriptive parameter if usage becomes more widespread and necessary. --BryghtShadow (talk) 14:32, 18 February 2016 (UTC)

The template is for avoiding SMW calls. It should be replaced with {{icon}} in any other place.--Relyk ~ talk < 15:15, 18 February 2016 (UTC)