Template talk:Item infobox/Archive 1

The following discussion is preserved as an archive. Please do not modify it.

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.
•  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. 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 - 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)

Milestones?

Could there be an option to put in a milestone entry? Such as:

|milestone = 1

or

|unlock= Milestone 1

GeminiViRiS Talk · Contribs 07:27, 31 March 2011 (UTC)

What does "Tradable" mean?

It means it can be traded. Really, I question the need to have tooltips explaining these stats - paintable means it can be painted, giftable means it can be gifted, nameable means it can be named. Isn't that kind of obvious? They already have links to their respective pages (i.e. Trading, Gift Wrap, Paint Can, Name Tag). So can these be removed? I think they make the infobox look a little messy. --Cooper Kid (Blether · Contreebs) 23:19, 15 June 2011 (UTC)

 Neutral As long as we keep the "Craftable" (which can confuse some people).  –  Epic Eric (T | C) 23:20, 15 June 2011 (UTC)

 Question I'm not entirely sure what you are asking here. I would love to help out but I kinda need to know whats going on here. 23:28, 15 June 2011 (UTC)

Yeah, sorry, it looks like I didn't explain myself properly. I was referring to the tooltips (the text bubbles that appear when you hover over certain pieces of text) like this which are on the bottom half of the stats (Price, Tradable, Giftable etc.) --Cooper Kid (Blether · Contreebs) 23:29, 15 June 2011 (UTC)

Gotcha... Neutral I can see how it may seem redundant but if its useful to one person, then it was useful to that person, end of story. 23:33, 15 June 2011 (UTC)

Can be Unusual/Vintage

I was wondering why these two particular attributes are not noted in the item infobox. To find this information, one has to search for "unusual," then click on "unusual table" and then scan for the hat they want (and that table isn't that easy to read or completely accurate). How difficult would it be to add these two attributes to the infobox? It seems to be pretty valuable information. Balladofwindfishes 00:23, 16 June 2011 (UTC)

Ya, I think we should put that kind of information in the infoboxes. I'm not sure about Geniuine information, since we already have the Promotional area in the infobox, but we really should put Vintage and Unusual. GianAwesome 00:33, 16 June 2011 (UTC)

I agree with genuine. That information is easily found usually by reading the second paragraph of the article. Balladofwindfishes 00:38, 16 June 2011 (UTC)

 Support at the very least adding "Unusual" to the infobox. Mar 02:27, 18 June 2011 (UTC)

Action items and rename

It seems that all action items don't have a rename parameter accepted, or at least not displayed. On Meet the Medic (Taunt), you can clearly see "rename = yes" yet nothing appears on the main article because it is an action item, not a hat or weapon. To avoid causing confusing with other action items like Mann Co Keys and paints, having rename as no or not having a rename parameter at all shouldn't display it in the infobox on the article. I haven't enough experience with templates to do this on a whim and it's a frequently-used template, so it'd probably be best that whoever does change it knows what they're doing. -- Psychopath 21:16, 29 June 2011 (PDT)

Name vs. Description

Does the rename parameter include if the item's description can be modified? Or does every item that can have the Name Tag tool used on it also have the Description Tag tool used on it and vice versa? Rolandius 20:08, 8 August 2011 (PDT)

Strange quality?

Should there be an entry for if a weapon has a strange variant? —GeminiViRiS Talk · Contribs 12:22, 17 September 2011 (PDT)

Decal Trait

Some items can now have decals applied to them. Seems like this trait should have a field now? Software2 00:17, 14 October 2011 (PDT)

Hat craftability

Currently, it's difficult to figure out whether a hat that someone is trying to sell you is actually craftable with the Rebuild Headgear recipe. What do you think of adding an optional "craft hat" field to the template, and using the information at Craft#Hats_and_Misc._items? Pez 18:35, 20 October 2011 (PDT)

I'm trying to get this implemented on the Availability Template, the idea being to link to a page dedicated to craftable hats that I've made here. I haven't had much feedback yet but any support would be appreciated! » Cooper Kid (blether) • (contreebs) 13:17, 21 October 2011 (PDT)

Festive version

I think that is a good idea add a parameter of festive version on 3D view, like the RED/BLU buttón or styles. Dio ★ | talk 16:26, 19 December 2011 (PST)

Image Consistency, Part Dix-Sept

The Image Consistency Project is complete and all item infobox images for hats and miscs are now in the format [[File:<item name>.png]]. Can this be hard-wired into the template now, in a similar fashion to the backpack images? » Cooper Kid (blether) • (contreebs) 17:59, 17 April 2012 (PDT)

Why not do it yourself? It's not protected. rebmcr 18:01, 17 April 2012 (PDT)

It's a very high-use template so I thought it better if I made sure everyone was ok with it. It's also a horrendously complicated piece of code, and while I might be able to do it myself, I'm quite likely to break something XD » Cooper Kid (blether) • (contreebs) 18:11, 17 April 2012 (PDT)

OK, I've got as far as this line of code:

| {{#ifexist: File:{{BASEPAGENAME}}.png
  | [[File:{{BASEPAGENAME}}.png|{{{imagewidth|250px}}}|center]]
}}

Am I on the right track - and if so, where should it go? This level of coding is kind of beyond me :S » Cooper Kid (blether) • (contreebs) 16:06, 20 April 2012 (PDT)

My stab at it:

--- old.txt	Sat Apr 21 04:00:20 2012
+++ new.txt	Sat Apr 21 04:04:18 2012
@@ -46,8 +46,8 @@
  -->{{#if:{{{image|}}}{{{team-colors|{{{two-models|}}}}}}
  | <tr>
     <td colspan="2" style="padding:0em;"><!-- 
-     -->{{#ifeq: {{lc:{{{type|}}}}} | weapon
-       | {{#if:{{Not|{{{game|}}}}}
+    -->{{#switch: {{lc:{{{type|}}}}}
+	  | weapon = {{#if:{{Not|{{{game|}}}}}
         | {{#if:{{Not|{{{unused|}}}}}
           | {{#if:{{{team-colors|{{{two-models|}}}}}}
             | {{#if:{{{3d-team-alt|}}}
@@ -134,7 +134,11 @@
             }}
         | [[File:{{{image|Screenshot needed.png}}}|{{{imagewidth|250px}}}|center]]}}
           }}
-      | [[File:{{{image|Screenshot needed.png}}}|{{{imagewidth|250px}}}|center]]
+      | hat | misc = {{#ifexist: File:{{BASEPAGENAME}}.png
+        | [[File:{{{image|{{BASEPAGENAME}}.png}}}|{{{imagewidth|250px}}}|center]]
+        | [[File:{{{image|Screenshot needed.png}}}|{{{imagewidth|250px}}}|center]]
+        }}
+      | #default = [[File:{{{image|Screenshot needed.png}}}|{{{imagewidth|250px}}}|center]]
     }}
     </td>
    </tr>

I am not familiar enough with this to know if it will work, or even what it all does. Guesswork from what is already there, mostly. — C2Talon (c/t) 21:23, 20 April 2012 (PDT)

That looks pretty good, though I'm still reluctant to try changing the template until someone who's confidant in the code takes a good look at it. » Cooper Kid (blether) • (contreebs) 04:29, 11 May 2012 (PDT)

Template:Dictionary usage?

This template uses some strings (BLU, RED) which are available in the dictionary. Should we adapt the template (and dictionary, if necessary) to use {{common string|BLU}}? Darkid (Talk | contribs) 13:18, 25 May 2012 (PDT)

Marketable parameter?

Now that Steam has a Community Market, some of the TF2 items can be directly traded on it. Should the template be modified to add a "Marketable?" to the infobox? —WhosAsking 16:03, 30 March 2013 (PDT)

Limited Quantity Parameter?

Now that Limited Quantity items are a documented thing in-game, I feel it'd be a good idea to add a Limited parameter to the loadout section of the template. When set to "yes," this would add a colored "Limited" before the level; as is shown in-game on items like the Gentle Manne's Service Medal and other currently limited items. -MarioMaster2008 (talk) 02:04, 19 September 2014 (PDT)

 Support. Yeah, this sounds like a good idea to me. Don't have any real issue with someone implementing this. --Omolong (talk) 09:13, 19 September 2014 (PDT)

Singled colored items with difference between classes.

Hi, I've been trying to implement this but I just can't. What I want to do is making a class table showing the model differences between classes (if there's any) on single-colored items. The model image would appear on the center, and the class on the top, but not separated from RED and BLU. For example, showing the differences of the Deus Specs on Demoman (broken lenses), Pyro (big lenses), Engineer (small lenses) and Other classes (normal lenses). This would be used for models that has drastic changes, not changes in size or position.
This also could work together with the team-colors-class, such as the Team Captain. The Heavy team-colors-class2 could have that single-color attribute, so it would appear only one Black Team Captain on the center of both BLU and RED (right now, there is two black team captains with the name RED and BLU, which isn't needed). Thanks. ▪ - 20:27, 1 July 2015 (PDT)

Cosmetic item rarity?

In yesterday's patch, cosmetics were added which functioned like the Gun Mettle Campaign weapons, in that cosmetics had their own tiered rarities. This went as far as to display the rarity of the cosmetic item above the item's level, in the color of the rarity, as seen here. I feel as though we should add the capability to display these rarities to the infobox, in the same way we currently do for limited quantity items. We could have a "rarity" parameter, where we would fill in either "civilian," "freelance," "mercenary," "commando," "assassin" or "elite" and get a display of "____ Grade Cosmetic Item" in that rarity's color before the item's level, perhaps even linking to the Decorated quality page, as Limited items do to the Limited section of the items article. It'd be all right to just have it display for the cosmetic items, since Gun Mettle weapons don't seem to warrant their own articles. -MarioMaster2008 (talk) 04:32, 28 August 2015 (PDT)

Gas Passer / Thermal Thruster

So these two weapons are apparently the first non-damage dealing weapons with taunt kills. This causes issues displaying their kill icons. Currently hide-kill-icon is set to yes for both items. This hides their taunt kills. Removing this parameter causes redlink / broken kill icon to appear because the template expects kill-icon-1 to be filled. Moving the taunt kill icon from kill-icon-2 to kill-icon-1 doesn't work as there is no kill-tooltip-1 to specify it is a taunt kill. The simplest solution would seem to be to simply add a kill-tooltip-1 parameter, however I am not sure how to do that myself. Tasty Salamanders (talk) 06:26, 16 November 2017 (PST)

Craftable (craft) attribute confusion

Currently the craft tag (craftable) has the documentation of "If the item can be obtained through Crafting." however the tooltip says "If the item is usable in Crafting." These are conflicting ideas as items usable in crafting don't always mean they are obtained from crafting. This leads to a problem of which one to use? The current documentation lines up with the literal sense of the word "craftable" but the tooltip lines up with what most people think of; that being the uncraftable property store bought items have (and others). In addition, changing to the tooltip version would also require further clarification on when to use it as items from the store will be uncraft but from other means wouldn't. I'd assume it'd be based on the primary way of getting the item; ToD is primarily a store item so it's uncraft, hats are primarily dropped/craft so they would be craft. Or would it get a "(no if store purchase)" next to a "Yes" if it's possible to get the item in craftable version outside of the store? Jh34ghu43gu (talk) 15:45, 20 April 2021 (UTC)

Tooltip vs documentation: The tooltip should be the correct one.

"I'd assume it'd be based on the primary way of getting the item" Yes. — Tark lm(pt-br) 15:52, 20 April 2021 (UTC)

Expired availability

The tooltips for expired availabilites all say "Currently this item cannot be earned in any way". This seems to imply the item is not obtainable at all, when often times the item is still available, just not through a specific method (eg: Conga cannot drop anymore but can still be unboxed/purchased). This tooltip makes sense for items that only had one way of obtaining them, such as campaign tokens or tournament medals, but for those other items that are still obtainable it causes a bit of confusion.

I think either the string needs edited to say "Currently this item cannot be earned this way", or items that can still be obtained should no longer display old ways of obtaining them. The former seems leagues easier to update for and also provides more information to readers (some people have asked about if taunts used to drop which is easily seen looking at the availability section as opposed to scrolling to the update history). Possibly a third option to add a third string like only-drop-expired that has the "this way" text and use that for items that are still obtainable. Thoughts? Jh34ghu43gu (talk) 05:03, 21 December 2022 (UTC)

  To my understanding, that tooltip was made having promo items in mind, such as Earbuds and Tux. But I agree, it should be modified to accommodate regular items as well. I vote on removing the "expired" way of obtaining such items, since its already in their Update History that those items were removed from the item drop system. Yossef • Talk 07:02, 21 December 2022 (UTC)

I agree that the tooltips could be updated to something else, and removing the expired parameters is not a good idea, otherwise some items like the Chemistry Set/2009 items/etc.. would have their availability section empty if that was the case. Mgpt (talk) 17:12, 8 February 2023 (UTC)

If you are referring to the retired items they already have retired text (Soldier's Stash as an example). If an item is truly unobtainable then perhaps it should just say Expired or Currently Unobtainable, since, as mentioned by Yossef, the page usually lists the ways it was previously available already (Chemistry Set example). Jh34ghu43gu (talk) 12:23, 10 February 2023 (UTC)

Suggestion: changing the tooltip for -expired availabilities to simply "This item can no longer be obtained this way". - BrazilianNut (talk) 14:39, 10 February 2023 (UTC)

I changed the text: here, let me know what do you think. Thanks Mgpt (talk) 23:34, 14 February 2023 (UTC)

The preceding discussion is preserved as an archive. Please do not modify it.