Difference between revisions of "Template talk:Item infobox"

From Team Fortress Wiki
Jump to: navigation, search
m (Kill Icon Link: (oops))
(Item Sets: new section)
Line 46: Line 46:
  
 
This template looks a bit too delicate for my barbaric template editing skills.  Could somebody add an "Expired" attribute underneath "Released", it should only show if unused=yes and it has a value. Thanks -<!--[[User:RJackson|<span class="modbg" style="margin-right:1px;text-shadow: #538237 1px 1px 0px;">RJ</span>]]<span class="modbg" style="margin-right:1px;text-shadow: #538237 1px 1px 0px;">s</span>-->[[File:User_RJackson_Signature_Colon_DDDDDDDDDDDDDDDDDDDD.png|link=User:RJackson|200px]] 15:35, 1 January 2011 (UTC)
 
This template looks a bit too delicate for my barbaric template editing skills.  Could somebody add an "Expired" attribute underneath "Released", it should only show if unused=yes and it has a value. Thanks -<!--[[User:RJackson|<span class="modbg" style="margin-right:1px;text-shadow: #538237 1px 1px 0px;">RJ</span>]]<span class="modbg" style="margin-right:1px;text-shadow: #538237 1px 1px 0px;">s</span>-->[[File:User_RJackson_Signature_Colon_DDDDDDDDDDDDDDDDDDDD.png|link=User:RJackson|200px]] 15:35, 1 January 2011 (UTC)
 +
 +
== Item Sets ==
 +
 +
I'd like to create individual, more detailed pages for the Item sets than the current stubs we have now. As such, I'd like a better template to use on the side than the little one currently used for sets. Would there be any objections to adding in the following setup?
 +
 +
* type = set
 +
 +
* ICON
 +
========
 +
* bundle-icon = Backpack_(Class)_Bundle.png
 +
 +
* BASIC INFORMATION
 +
========
 +
* used-by =
 +
* contributed-by =
 +
* released =
 +
* price =
 +
 +
* SLOTS
 +
========
 +
* primary = yes/no - item
 +
* secondary = yes/no - item
 +
* melee = yes/no - item
 +
* headgear = yes/no - item
 +
 +
[[User:GJ|GJ]] 16:32, 24 February 2011 (UTC)

Revision as of 16:32, 24 February 2011

Some thoughts

  • Ammo section needs to be hidden for melee weapon unless any of it's parameters are defined (the Sandman has 1 ammo for example).
  • No need to support name-override, NAME, name and title at all (i.e. pick just one). We should stamp that out so we don't have to do it all over again.
    • Also only need two different parameters that deal with the name, as you noted loadout-name that includes things like the, der, el, la etc. and name for cases where there page name != item name (e.g. all language pages)
  • Document what the trade/paint/craft/rename parameters do by default (I guess this will come with extended documentation)
  • How are we defining the tradability of stock weapons? Are they untradable because they aren't accessible by default? Or are they tradable because they can be renamed and then traded?
  • {{Class name}} in conjunction with used-by to solve the same issue that was solved with slot names.
  • Does backpack-image need support?

These aren't criticism, just immediate problems that need solving that I am sure you are aware of anyway. Your work is excellent and invaluable! -- Pilk (talk) 12:31, 8 November 2010 (UTC)

Only just noticed this, lol.
  • That's a good idea, I'll work that in.
  • I added them in case somebody tries to add a display title /after/ we parse the pages. I will still change all instances to 'name', however. But this is just a little backwards compatibility.
  • Pictogram tick.png Done.
  • This is an issue I'm leaving to others to decide, as I don't believe a solution within the template is the best idea when you consider user friendliness and technical workability with translation switching. There are so many variations that it's impossible to define within the infobox.
  • I'm not sure. I was planning on leaving 'used-by' as a simple text parameter as there wasn't any need to categorize or anything so no switch was required. It's certainly possible to have it as: "| used-by = scout" and then autotranslate through the class name template, but when you consider it, most users translate the link already (i.e. Разведчик).
  • I can't think of any circumstances where 'backpack-image' would need to be used, as all the backpack images have been uploaded to file names matching the page names. User pages, etc, can simply just use a file redirect. I'll be phasing it out anyway when I parse over pages.
Thanks heaps for these notes, though, Pilk :) seb26 [talk] 06:37, 9 November 2010 (UTC)

Description contributor

How to deal with description contributor (for hat) ? Add to contributed-by or it needs a new param to be created ? --Giraf 09:45, 19 November 2010 (UTC)

What do you mean description? That field is just for the name of the contributor, what information do you want to add? Moussekateer 09:54, 19 November 2010 (UTC)
Valve launched a contest to add descrption to hats. So now some hats have two contributors: one for the model and one for the description of the hat. For example, the Bloke's Bucket Hat: AAA_BATTERY is the contributor of the model and Reclaimer077 is the contributor of the description (ie Gone Snipin'.) --Giraf 10:08, 19 November 2010 (UTC)
I see what you mean. Well the person who contributed the description is already documented in the article but I suppose moving it to the infobox might make sense. Moussekateer 10:10, 19 November 2010 (UTC)
We already have a description info in the trivia for each hat. I don't think we should saturate the infobox. The person who wrote the description is not nearly as important as the person that made the model. Just sayin' – Smashman (talk) 11:02, 19 November 2010 (UTC)
Well I think there should be a more elegant way of displaying the description winners but yea I agree the infobox is getting cluttered. Moussekateer 11:09, 19 November 2010 (UTC)

Availability

I'm going to suggest that since this template already performs automatic categorization for Primary, Secondary and Melee weapons, that this be extended to automatically categorize weapons into [[Category:Stock Weapons]] and such too. I think it could easily be done using the Availability parameter. Infi^ 22:08, 4 December 2010 (UTC)

"Medieval" yes/no info?

I think it would make sense to add a tag indicating whether a weapon is usable in Medieval Mode. Thoughts? Zrephel 08:52, 18 December 2010 (UTC)

Makes sense to me. -- Pilk (talk) 08:55, 18 December 2010 (UTC)

Kill Icon Link

I've just finished creating the first pass of a nice descriptive kill icon list. Requesting thoughts on editing the info box to link the "Kill Icon" header in the infobox to this article. --Ten19 08:49, 19 December 2010 (UTC)

Bumping this, any objections to it being implemented? --Ten19 00:17, 4 February 2011 (UTC)

"Vintage" yes/no info?

I think it would be helpful having a tag indicating whether an item is available in "vintage" status or not. Thoughts? --Kmessen 08:36, 20 December 2010 (UTC)

Add "Expired" attribute

This template looks a bit too delicate for my barbaric template editing skills. Could somebody add an "Expired" attribute underneath "Released", it should only show if unused=yes and it has a value. Thanks -User RJackson Signature Colon DDDDDDDDDDDDDDDDDDDD.png 15:35, 1 January 2011 (UTC)

Item Sets

I'd like to create individual, more detailed pages for the Item sets than the current stubs we have now. As such, I'd like a better template to use on the side than the little one currently used for sets. Would there be any objections to adding in the following setup?

* type = set
* ICON
========
* bundle-icon = Backpack_(Class)_Bundle.png
* BASIC INFORMATION
========
* used-by = 
* contributed-by = 
* released = 
* price = 
* SLOTS
========
* primary = yes/no - item
* secondary = yes/no - item
* melee = yes/no - item
* headgear = yes/no - item

GJ 16:32, 24 February 2011 (UTC)