Difference between revisions of "Team Fortress Wiki:Discussion"

From Team Fortress Wiki
Jump to: navigation, search
(Strange Weapons: new section)
m (Image Policy)
 
Line 1: Line 1:
 
__NEWSECTIONLINK__
 
__NEWSECTIONLINK__
<div class="plainlinks" style="margin:1em -0.56em; background:#ededed; padding:0.65em 1em; font-size:175%; border:1px solid #aaa; border-left:0px; border-right:0px; text-align:center;">[{{fullurl:Team_Fortress_Wiki:Discussion|action=edit&section=new}} '''create a new section''']</div>
+
<div class="plainlinks" style="margin:1em -0.56em; background:#ededed; padding:0.65em 1em; font-size:175%; border:1px solid #aaa; border-left:0px; border-right:0px; text-align:center;">[{{fullurl:Team_Fortress_Wiki:Discussion|action=edit&section=new}} '''Create a new section''']</div>
 
<div style="margin-bottom:1em;">{{CentralDiscussion}}
 
<div style="margin-bottom:1em;">{{CentralDiscussion}}
 
</div>{{TFWiki navbar}}
 
</div>{{TFWiki navbar}}
{{Discussion archives/2011}}
 
{{Discussion archives/2010}}
 
<!-- Uncomment this when the tabbed boxes discussion has been archived: {{TOC float|right}} -->
 
 
[[Category:Team Fortress Wiki]]
 
[[Category:Team Fortress Wiki]]
[[Category:Team Fortress Wiki discussion| ]]
+
[[Category:Team Fortress Wiki discussion]]
 +
{| width="100%"
 +
|__TOC__
 +
|{{Discussion archives}}
 +
|}
 +
{{clr}}
 +
 
 +
 
 +
== Dark Mode ==
 +
 
 +
I don't think I even need to explain this. Wikipedia itself has it, so do other wikis. I do have a browser extension for dark mode, and optimally a dark theme for TFwiki should still keep muted earthy orangish tones and such, but at this point with my eye strain I'd take anything. It would encourage more dedicated editing streaks, perhaps, since many of us are night owls too.--[[File:Leaderboard class allclass.png|15px|link=]] [[User:Akolyth|<span style="font-size: 14px; font-family: Trebuchet MS">'''Akolyth'''</span>]] ([[User_talk:Akolyth|talk]]) 03:23, 16 October 2023 (UTC)
 +
 
 +
:Easier said than done, it's being worked on but we can't promise anything.<br>[[File:BLU Wiki Cap.png|20px|link=List of Wiki Cap owners]] | [[Help:Group rights|<span style="color:green;font-family:TF2 Build;">s</span>]] | [[User:GrampaSwood|<font color="DB9C1F">GrampaSwood</font>]] [[File:PraisetheSun.png|20px|alt=Praise the Sun!]] ([[User talk:GrampaSwood|<font color="DB9C1F">talk</font>]]) ([[Special:Contributions/GrampaSwood|<font color="DB9C1F">contribs</font>]]) 11:13, 16 October 2023 (UTC)
 +
 
 +
== Valve Store ==
 +
 
 +
The official Store has been closed down for months now by Valve, and there's no reasonable smidgeon of proof to believe it's coming back any time soon. The Wiki, in many articles, links directly to the Store still, or mentions it, but even tooltips for certain hats will just say they're "not available". This is kind of awkward, and makes the average user waste a click (the horror, I know). And even I get a false hope sometimes that it changed, but it's Valve after all. Should something be done about this, and how? Can there be an automatic disclaimer the Store is gone? Should links be removed? Just let the dead ends sit forever?--[[File:Leaderboard class allclass.png|15px|link=]] [[User:Akolyth|<span style="font-size: 14px; font-family: Trebuchet MS">'''Akolyth'''</span>]] ([[User_talk:Akolyth|talk]]) 02:44, 18 October 2023 (UTC)
 +
 
 +
:Try to find an archive.org version of it, otherwise just add a tooltip saying it's not available anymore due to store shutdown.<br>[[File:BLU Wiki Cap.png|20px|link=List of Wiki Cap owners]] | [[Help:Group rights|<span style="color:green;font-family:TF2 Build;">s</span>]] | [[User:GrampaSwood|<font color="DB9C1F">GrampaSwood</font>]] [[File:PraisetheSun.png|20px|alt=Praise the Sun!]] ([[User talk:GrampaSwood|<font color="DB9C1F">talk</font>]]) ([[Special:Contributions/GrampaSwood|<font color="DB9C1F">contribs</font>]]) 11:12, 18 October 2023 (UTC)
 +
 
 +
== Painted variants with both Styles and separate Classes images, a design proposal ==
 +
 
 +
Hi. So, I have several mockups of things to suggest which I'll be writing it up eventually. For now, I was making changes to the [[Robot Chicken Hat]] page, and was thinking about adding class variants to the paint gallery, as each class changes the hat's design a little (taller combs, different beak designs, etc.). However, if I were to make those paint variants per class, the current way we put styles and classes to the table looks... off, to say the least. At the moment, if I were to make it consistent with the rest of the Wiki, it would look like this: [https://i.imgur.com/gfdAUBL https://i.imgur.com/gfdAUBL]. But, instead, I thought about this mock-up: [https://i.imgur.com/QmQCLsK https://i.imgur.com/QmQCLsK]. Not only this looks more visually appealing, but it also takes a lot less space. The only problem that it may be confusing for cosmetics that separate styles by a group of classes ([[Cotton Head]], [[Brotherhood of Arms]], etc.). So... I thought about just making the class buttons that aren't active a little darker (same thing with the Style name): [https://i.imgur.com/Fiw1zRT https://i.imgur.com/Fiw1zRT]. Here's another example with the Cotton Head: [https://i.imgur.com/ZhkQwGG https://i.imgur.com/ZhkQwGG]. Mouse-hovering the class icons could also show their class names ("Pyro, Medic, Spy" and "Other classes" in the case of Cotton Head) Thoughts? [[File:User Gabrielwoj Signature Icon.png|15px|Headphones style when?|link=User:Gabrielwoj]] - [[File:User Gabrielwoj Signature 1.png|link=User:Gabrielwoj]] ▪ [[File:User Gabrielwoj Signature 2.png|link=Special:Contribs/Gabrielwoj]] - [[File:User Gabrielwoj Signature 3.png|link=User talk:Gabrielwoj]] 13:11, 18 October 2023 (UTC)
 +
 
 +
:I like this proposal, although I think it's not necessary for every page. Only for the ones where the tabs become too much.<br>[[File:BLU Wiki Cap.png|20px|link=List of Wiki Cap owners]] | [[Help:Group rights|<span style="color:green;font-family:TF2 Build;">s</span>]] | [[User:GrampaSwood|<font color="DB9C1F">GrampaSwood</font>]] [[File:PraisetheSun.png|20px|alt=Praise the Sun!]] ([[User talk:GrampaSwood|<font color="DB9C1F">talk</font>]]) ([[Special:Contributions/GrampaSwood|<font color="DB9C1F">contribs</font>]]) 13:15, 18 October 2023 (UTC)
 +
 
 +
== Inconsistency regarding items with one team color, but shows team-colored parts of a player model ==
 +
 
 +
Hello. So, when I started adding tabs to the paint variants, and just browsing the Wiki as a whole, I noticed that a couple pages are inconsistent in regards to the unpainted variants. In almost every case of cosmetics that use part of the player model, but only has 1 skin (not team-colored), the team-colors syntax isn't added to the tab, and we only have the UNPAINTED version on the paint variants table (example includes the [[Soldier's Stash]], [[Horrible Horns]] on Spy, and much more), but some other pages still shows the BLU variant of a player model despite the item only having one skin ([[Texas Half-Pants]], [[Millennial Mercenary]]'s Streaming 2Fort style, [[Exquisite Rack]], [[Battle Bob]]'s With Helmet style, [[Bacteria Blocker]]'s Headphones style, etc).
 +
 
 +
Some other pages also includes two identical RED and BLU images for the infobox, just because the item has two materials per team, but still uses the same exact texture and values (basically two identical .vmt files). I don't remember what pages has it now, but there are some pages that has that. I did that on [[Decorated Veteran]] since I've heard about doing that in the past before: "even if they look identical, put in two separate uploads". There's also no current way to just show one skin on the infobox (however that's something I'm looking to suggest soon enough on my mega infobox improvements topic).
 +
 
 +
Because we use the infobox, as well the RED and BLU parts of the paint variants table to show the different Skin Colors of the ITEM, I would say to actually cleaning it up these inconsistencies. So, for instance, on Texas Half-Pants, there wouldn't RED and BLU images for each style, because they look identical on either team, and, there's only two skins on the model (one for the Tan style, the other for the Midnight style [older cosmetics used a different way in handling styles, as opposed to separate models, many old cosmetics would use different skins for styles, and the Item Schema would redirect what skins to use depending on the style chosen]). The colors change on the images right now, because it's the colors of Engi's default pants, but not the actual item model changing colors. Meaning that, the RED / BLU on the infobox would be removed, the BLU_... images would be deleted, and the RED_ images would be moved to the _UNPAINTED.png suffix instead.
 +
 
 +
Some may argue that, since the team-colored paint can image previews also change the pants colors, that these should stay in, but, I don't agree. These are to show the item's team-colors being affected (both the UNPAINTED versions and the team-colored paint cans), not the player model's team-colors, but let me know what do you think.
 +
 
 +
Items that have 0 changes on team-colors despite having them (same exact .vmt values), I'd also say to get rid of it, as they provide no real information for the reader other than perhaps modders, so they don't need to go all the way of decompiling models to add team-color support, for instance. Some require close inspection however. The [[Mann-Bird of Aberdeen]] looks like to be the case, but the green area is just slightly brighter on BLU. I'd still keep the same colors for Styles and classes (like [[Team Captain]] for Heavy), until a more fully-fledged infobox edit comes along the way that adds support to just 1 skin on the infobox (like this: [https://i.imgur.com/GQP1ou0 https://i.imgur.com/GQP1ou0]). I will still point out many of these on my eventual discussion of infobox changes in another topic. [[File:User Gabrielwoj Signature Icon.png|15px|Headphones style when?|link=User:Gabrielwoj]] - [[File:User Gabrielwoj Signature 1.png|link=User:Gabrielwoj]] ▪ [[File:User Gabrielwoj Signature 2.png|link=Special:Contribs/Gabrielwoj]] - [[File:User Gabrielwoj Signature 3.png|link=User talk:Gabrielwoj]] 13:43, 18 October 2023 (UTC)
 +
 
 +
:I would support every page having both team colours.<br>[[File:BLU Wiki Cap.png|20px|link=List of Wiki Cap owners]] | [[Help:Group rights|<span style="color:green;font-family:TF2 Build;">s</span>]] | [[User:GrampaSwood|<font color="DB9C1F">GrampaSwood</font>]] [[File:PraisetheSun.png|20px|alt=Praise the Sun!]] ([[User talk:GrampaSwood|<font color="DB9C1F">talk</font>]]) ([[Special:Contributions/GrampaSwood|<font color="DB9C1F">contribs</font>]]) 13:57, 18 October 2023 (UTC)
 +
 
 +
== Articles for individual environmental hazards ==
 +
 
 +
Some of the older environmental hazards have their own articles. Specifically, they are: [[Ghost]], [[Pumpkin bomb]], [[Saw blade]], and [[Train]].
 +
 
 +
These are some fairly simple hazards: ghost goes "boo", pumpkin bomb goes "boom", blade goes "bzzt", and train goes "''[Train horn noises]''". They all have fairly short articles, and are also covered in the [[Environmental death]] article.
 +
 
 +
I propose we change these four into redirects to the Environmental death article, similar to [[Pitfall]].
 +
 
 +
As for their Update histories, I have three ideas:
 +
* Add the section to the Environmental death article and carry them over.
 +
* Create a separate page for that (similar to the [[Item timeline]] pages).
 +
* Ignore them (essentially already the case for all the hazards that don't have their own articles).
 +
 
 +
I am ok with [[Skeletons]] and the Halloween bosses having their own articles, however, as they are more elaborate (which is noticeable by simply comparing article sizes).
 +
 
 +
Opinions? - [[User:BrazilianNut|BrazilianNut]] ([[User talk:BrazilianNut|talk]]) 16:36, 19 October 2023 (UTC)
  
== Supporting charities ==
+
:I think some of these pages can add value, such as the specifics in the hazard infobox. I'd push for more articles rather than less, similar to [[List of game modes]], where each hazard has its own page as well as a short description on the overall page. I would prefer this because it would cut down on the clutter on the Environmental death page, for example the pumpkin bomb section is 5 identical hazards that are just reskinned. It would be better to have this in a gallery on its own page, rather than several entries on that page.<br>[[File:BLU Wiki Cap.png|20px|link=List of Wiki Cap owners]] | [[Help:Group rights|<span style="color:green;font-family:TF2 Build;">s</span>]] | [[User:GrampaSwood|<font color="DB9C1F">GrampaSwood</font>]] [[File:PraisetheSun.png|20px|alt=Praise the Sun!]] ([[User talk:GrampaSwood|<font color="DB9C1F">talk</font>]]) ([[Special:Contributions/GrampaSwood|<font color="DB9C1F">contribs</font>]]) 16:40, 22 October 2023 (UTC)
  
How about the TF Wiki starts supporting charities? And with that I mean put up the HTML widget for the Humble Bundle?
+
:: I believe it is better to keep the pages separate, as putting them all together in one could generate a lot of visual clutter, in addition to having a lot of information for the reader to consume at once. Furthermore, it would be complicated to gather all the update histories on the articles. Essentially, we would be taking separate articles and combining them into one big article, where each section (divided by {{code|<nowiki>== Section title ==</nowiki>}}) would be a "complete" article.<br/>[[User:Tiagoquix|<font color="#1e90ff">Tiagoquix</font>]] ([[User talk:Tiagoquix|<font color="#19c819">talk</font>]]) 18:45, 22 October 2023 (UTC)
http://www.humblebundle.com/
 
  
I think it'd help them a lot, and it wouldn't hurt the Wiki in anyway. I have yet to see confirmation of that we're allowed to use the actual widget they provide, but I don't think Wolfire would mind it all that much.
+
== A request ==
  
Actual code is here, I'm e-mailing him as I type this.  
+
In Polish language we don't capitalise most words like in English language and the way quality items have their quality displayed looks like this: Rocket launcher (vintage). The problem is that in [[Template:Mann-Conomy Nav]] Vintage quality in Polish and Russian is not capitalised and looks weird in the template where everything is capitalised except this one word. Is it possible to add a new entry in the dictionary for this template only, where 'Vintage' is capitalised for these languages? In Polish it's even more confusing, because [[Classic]] and Vintage share the same translation, so it could be shown in the tempalte as 'Vintage quality' (Jakość klasyczna in Polish). [[File:User Denied signature.jpg|50px|link=User:Denied]] [[User:Denied|Denied]] [[User talk:Denied|(Talk)]] 10:28, 24 October 2023 (UTC)
<iframe style="margin:0 auto; border:none;" src="http://www.humblebundle.com/_widget/html" width="410" height="150"></iframe> (source: http://blog.wolfire.com/2011/07/Introducing-Humble-Indie-Bundle-3)
 
  
Thoughts? --[[User:Mave|Mave]] 12:40, 31 July 2011 (PDT)
+
:If it's the very first letter that needs to be capitalised, you can use <nowiki>{{ucfirst:<string>}}</nowiki> to turn the first letter into a capital. For example, <nowiki>{{ucfirst:hello world}}</nowiki> generates {{ucfirst:hello world}}.<br>[[File:BLU Wiki Cap.png|20px|link=List of Wiki Cap owners]] | [[Help:Group rights|<span style="color:green;font-family:TF2 Build;">s</span>]] | [[User:GrampaSwood|<font color="DB9C1F">GrampaSwood</font>]] [[File:PraisetheSun.png|20px|alt=Praise the Sun!]] ([[User talk:GrampaSwood|<font color="DB9C1F">talk</font>]]) ([[Special:Contributions/GrampaSwood|<font color="DB9C1F">contribs</font>]]) 11:15, 10 November 2023 (UTC)
:Great idea but it'll need Wiki Staff approval first. '''» [[User:Cooper Kid|<span style="color:red">Coo</span><span style ="color:gray">per</span><span style ="color:blue"> Kid</span>]]''' <small>([[User_talk:Cooper Kid|Blether]] '''·''' [[Special:Contributions/Cooper Kid|Contreebs]])</small> 16:53, 31 July 2011 (PDT)
 
::Without a doubt, of course. Any chance you could get the word out to them? I have no idea who to contact, hehe. --[[User:Mave|Mave]] 03:32, 1 August 2011 (PDT)
 
:::Almost everyone watches this page (editors & mods) so you'll probably get some more comments soon. I would first say that this doesn't seem that feasible on this site. IFrames are pretty dodgy, and they are also disabled by the software so that would not work out. If people agree to this, maybe we could link to humblebundle.com somewhere? [[user:seb26|<small style="background:#f9f9f9;border:1px solid #0070FF;padding:0em 0.5em;color:#000;-webkit-box-shadow:2px 1px 1px #8BBEFF;">'''seb26'''</small>]] 03:51, 1 August 2011 (PDT)
 
  
== All-Class emblem in navs ==
+
::Could you help me with this? I've changed it in [[Template:Mann-Conomy Nav]] but doesn't seem to capitalise the first letter. [[File:User Denied signature.jpg|50px|link=User:Denied]] [[User:Denied|Denied]] [[User talk:Denied|(Talk)]] 10:54, 17 December 2023 (UTC)
  
It would appear we don't really have a concrete idea of what to do here. For awhile we were using a question mark, but that looked just odd. Now we have a TF2 logo, but it still looks odd. Further, the icon is being removed from some templates and left on others, and it's being placed on some items but not others. Overall it's confusing and I think we need a direction so our navs don't have different styles going on between them. Personally, I think we should organize everything into class. Instead of having all the weapons organized by class in rows, and then all the hats scattered about, we should just throw the hats into the place we put the weapons, or create a second part of the nav for rows of class hats. No matter what we need a good idea of what all the navs need to look like, so we don't have various navs with different styles. [[User:Balladofwindfishes|Balladofwindfishes]] 09:44, 2 August 2011 (PDT)
+
:::Hmmm, yeah seems like the automatic translation templates automatically uncapitalise it. If you really wanted to implement this you'd have to use the {{tl|lang}} template instead.<br>[[File:BLU Wiki Cap.png|20px|link=List of Wiki Cap owners]] | [[Help:Group rights|<span style="color:green;font-family:TF2 Build;">s</span>]] | [[User:GrampaSwood|<font color="DB9C1F">GrampaSwood</font>]] [[File:PraisetheSun.png|20px|alt=Praise the Sun!]] ([[User talk:GrampaSwood|<font color="DB9C1F">talk</font>]]) ([[Special:Contributions/GrampaSwood|<font color="DB9C1F">contribs</font>]]) 13:49, 17 December 2023 (UTC)
:{{c|comment}} I personally think that there should be neither question mark icon, nor tf2 logo, simply leave all class or multiple class items with no emblem. I also don't like the idea of splitting the navs into different rows, the navs are already massive enough as it is. <span style="font-family:TF2 Build;font-size:17px;color:#70B031">[[User:MogDog66|MogDog66]][[File:User MogDog66 Service Metal No WhiteSpace.png|24px|link=User_talk:MogDog66]]</span> 00:52, 4 August 2011 (PDT)
 
:{{c|comment}} In the recent [http://www.teamfortress.com/deus-ex/ Deus Ex Update], Valve has actually used the TF2 emblem as an all class icon, near the bottom. The Machina, Diamondback, Purity Fist, Widowmaker, Short Circuit and Nanobalaclava all use the icon of their TF2 class, while the Company Man and Dues Specs, both all class items, use the TF2 emblem. -- <span style="font-family:TF2 Build;font-size:90%;">[[File:Killicon train.png|40px|link=User:Hefaistus]] [[User:Hefaistus|<font color="#FF9933">Hefaistus</font>]]</span> - [[User talk:Hefaistus|<span style="color:black;font-size:82%;">talk</span>]] 00:56, 20 August 2011 (PDT)
 
  
== "Basic strategy" template ==
+
::::[https://wiki.teamfortress.com/w/index.php?title=Template:Mann-Conomy_Nav&diff=3408072&oldid=3388990 I already did it once and...] [[File:User Denied signature.jpg|50px|link=User:Denied]] [[User:Denied|Denied]] [[User talk:Denied|(Talk)]] 14:19, 18 December 2023 (UTC)
  
There was a nice template used on each class page to list the official basic tips (those shown during the map's loading), especially helpful to prevent people writing their own "tips".
+
:::::Perhaps leave a hidden comment and use {{tl|lang incomplete}}?<br>[[File:BLU Wiki Cap.png|20px|link=List of Wiki Cap owners]] | [[Help:Group rights|<span style="color:green;font-family:TF2 Build;">s</span>]] | [[User:GrampaSwood|<font color="DB9C1F">GrampaSwood</font>]] [[File:PraisetheSun.png|20px|alt=Praise the Sun!]] ([[User talk:GrampaSwood|<font color="DB9C1F">talk</font>]]) ([[Special:Contributions/GrampaSwood|<font color="DB9C1F">contribs</font>]]) 14:27, 18 December 2023 (UTC)
  
While unfortunately it didn't prevent the manual addition of tips (as Seb26 stated [[Template_talk:Basic_strategy#Useless|here]]) nonetheless it was useful to quickly clean up the section. "''Pyros are good allies. They can help remove Sappers from Buildings using the Homewrecker or the Maul.''" on the Engie's page is a good example.
+
::::::I've coppied how it looked oryginally but now it shows as red link 'VintageVintage'. Could you look what's wrong with [https://wiki.teamfortress.com/w/index.php?title=Template:Mann-Conomy_Nav&diff=3584139&oldid=3583139 this edit]? Except equals sign. I've fixed it later. [[File:User Denied signature.jpg|50px|link=User:Denied]] [[User:Denied|Denied]] [[User talk:Denied|(Talk)]] 13:21, 19 December 2023 (UTC)
  
Keeping that section clean will be a nightmare, just like the Trivia. Should we have it back? --[[User:Kid Of The Century|Kid Of The Century]] 08:03, 3 August 2011 (PDT)
+
{{Outdent|6}}Looks like you forgot to add a vertical bar, which made the link <nowiki>[[VintageVintage]]</nowiki>.<br>[[File:BLU Wiki Cap.png|20px|link=List of Wiki Cap owners]] | [[Help:Group rights|<span style="color:green;font-family:TF2 Build;">s</span>]] | [[User:GrampaSwood|<font color="DB9C1F">GrampaSwood</font>]] [[File:PraisetheSun.png|20px|alt=Praise the Sun!]] ([[User talk:GrampaSwood|<font color="DB9C1F">talk</font>]]) ([[Special:Contributions/GrampaSwood|<font color="DB9C1F">contribs</font>]]) 13:31, 19 December 2023 (UTC)
  
'''''EDIT:''''' [[User:Kid_Of_The_Century/Sandbox#Basic_strategy_template|Concept time.]] Feedback's welcome. --[[User:Kid Of The Century|Kid Of The Century]] 01:39, 4 August 2011 (PDT)
+
== Mann Manor/Mountain Lab's history ==
  
'''''EDIT 2:''''' Seb26 suggested a way that could please everyone, and personally I approve that. Take a look below.--[[User:Kid Of The Century|Kid Of The Century]] 01:37, 7 August 2011 (PDT)
+
I feel maps that we know more detailed information on the history of we should actually have written down so it isn't forgotten, such as for example, Mann Manor/Mountain Lab being an art contest was not the original plan in fact the maps used to have textures before but, that's just what I think. [[User:The American Boot|The American Boot]] ([[User talk:The American Boot|talk]]) 04:34, 10 November 2023 (UTC)
:{{c|Yes}}. How about adding all official tips (for every language) and then protect it? When new tips are added, just unprotect it, add them, and protect it again. [[File:User_SackZement_signature.gif|link=User:SackZement]][[User:SackZement|<span style="font-size:14px;font-family: Tf2 Build"><font color="orange">SackZement]]</font></span> [[User_talk:SackZement|(Talk)]] 08:12, 3 August 2011 (PDT)
 
:{{c|Comment}} Any way it could be made into a table, and then just protect the table from editing? [[User:Balladofwindfishes|Balladofwindfishes]] 08:15, 3 August 2011 (PDT)
 
::Well, I guess so. We should come up with a proper layout though, just using the usual table model for a list might look bad.--[[User:Kid Of The Century|Kid Of The Century]] 01:20, 4 August 2011 (PDT)
 
:{{c|Oppose}} You said it yourself: "Keeping that section clean will be a nightmare". The instant you put up tips, ever Tom, Dick and Harry thinks to themselves "I HAVE THE BEST TIP" and they go to add it. It's annoying to keep clean and you can't really blame them for adding their stuff. Even then, the tips don't really add anything to the page. Their only distinction is that they're in the game. Anything worth saying about any given weapon has very likely been said in its respective Community Strategy page. -- [[Image:User Alex2539 Sig.png|47px|link=User:Alex2539|Alex2539]] - {{mod}} <sub>([[User_talk:Alex2539|talk]] | [[Special:Contributions/Alex2539|contribs]])</sub> -- 01:50, 4 August 2011 (PDT)
 
::I'm not really sure what you're talking about: are you suggesting we should just scrap the section altogether? I personally wouldn't, but it'd be better than keep that mess. --[[User:Kid Of The Century|Kid Of The Century]] 02:47, 4 August 2011 (PDT)
 
::As i said, it will not be a nightmare if we protect the template. [[File:User_SackZement_signature.gif|link=User:SackZement]][[User:SackZement|<span style="font-size:14px;font-family: Tf2 Build"><font color="orange">SackZement]]</font></span> [[User_talk:SackZement|(Talk)]] 03:51, 4 August 2011 (PDT)
 
:{{c|Neutral}} &ndash; I think the basic strategy tips should probably be copied to the dictionary (to prevent duplication of certain lines, for example the "Press E for Medic" line which appears on each page), but it is not a good idea to simply protect the page to stop people from adding things. {{tl|Basic strategy}} was made like this last time and for months there were translations being made on the talk page because the page was protected. Protection doesn't work as well as it sounds and it will stop valid edits from translators (and not just people wanting to add their own tips). A better solution would to simply have each line in the dictionary, each set of lines in the dictionary (to avoid a #switch with Scout, Soldier, etc) and then on each page add {{tl|Basic strategy}} again. [[user:seb26|<small style="background:#f9f9f9;border:1px solid #0070FF;padding:0em 0.5em;color:#000;-webkit-box-shadow:2px 1px 1px #8BBEFF;">'''seb26'''</small>]] 00:14, 5 August 2011 (PDT)
 
::{{c|Comment}}. I support this dictionary idea. Let's see if people find their way through to add custom tips. [[File:User_SackZement_signature.gif|link=User:SackZement]][[User:SackZement|<span style="font-size:14px;font-family: Tf2 Build"><font color="orange">SackZement]]</font></span> [[User_talk:SackZement|(Talk)]] 00:30, 5 August 2011 (PDT)
 
::{{c|Agree}} I don't know how this dictionary thing actually works, but probably this is the best suggestion to please everyone. While at it, I'd suggest also to rename the section from "'''Basic Strategy'''" to "'''In-game tips'''" to better specify that the section is for official tips only.--[[User:Kid Of The Century|Kid Of The Century]] 01:35, 7 August 2011 (PDT)
 
  
==New Section Suggestion==
+
:If you think this fact is worth and most player don't know, you can try adding it to Trivia section. Here is a more detailed [[Help:Style_guide/Trivia|Trivia guild]].[[User:Profiteer|Profiteer(奸商)the tryhard]] ([[User talk:Profiteer|talk]]) 05:07, 10 November 2023 (UTC)
I think that we should add a new section to the wiki front page, it would be small and would show "This month 1 year ago" "This month 2 years ago" and would show a small summary of important things that happened in Team Fortress 2 at that time.  
 
Such as "This month 2 year ago... The classless update was released. The Classless Update was the first non-class specific major update. The content focus of the update differed from previous updates; instead of introducing new weapons or achievements, the Classless Update added new hats, game modes and maps, while also delivering a large number of bug fixes and minor tweaks to existing gameplay."
 
  
I am  open to suggestion and I hope that people like my idea. [[User:Chef Tony|Chef Tony]] 04:14, 5 August 2011 (PDT)
+
:I'm not sure where this Trivia came from or if there is any source for. The [[Art Pass Contest]] page states that Robin Walker said they had a map that hadn't been worked on for a while and they didn't have time to do an art pass on it (which means the map just had dev textures).<br>[[File:BLU Wiki Cap.png|20px|link=List of Wiki Cap owners]] | [[Help:Group rights|<span style="color:green;font-family:TF2 Build;">s</span>]] | [[User:GrampaSwood|<font color="DB9C1F">GrampaSwood</font>]] [[File:PraisetheSun.png|20px|alt=Praise the Sun!]] ([[User talk:GrampaSwood|<font color="DB9C1F">talk</font>]]) ([[Special:Contributions/GrampaSwood|<font color="DB9C1F">contribs</font>]]) 21:34, 10 November 2023 (UTC)
:Quite like this idea, but id want to see it in either side panels or boxouts rather than in main text. --<span style="font-size:83%;border: 1px solid #FF0000;background:#FFFFFF">[[User:Swarfega|<font style="background: #FF0000" face="Arial" color="#FFFFFF">'''&nbsp;Swarfega&nbsp;'''</font>]][[User talk:Swarfega|<font style="background:#FFFFFF" face="Arial" color="#FF0000">'''&nbsp;T'''</font>]] [[Special:Contributions/Swarfega|<font style="background:#FFFFFF" face="Arial" color="#FF0000">'''&nbsp;C&nbsp;'''</font>]]</span> 10:14, 5 August 2011 (PDT)
 
:Might be tough to maintain manually, but a little database and a bot might handle it okay.  Certainly worth considering. -[[User:RJackson|<span class="modbg" style="margin-right:1px;text-shadow: #538237 1px 1px 0px;">RJ</span>]] 10:18, 5 August 2011 (PDT)
 
:: I personally don't think it would be that high maintenance as you think. I was able to get information on 1 and 2 years in about 5 minutes. [[User:Chef Tony|Chef Tony]] 10:27, 5 August 2011 (PDT)
 
::: I agree, if it only changes monthly it shouldn't be too hard to add some interesting information manually. [[User:Balladofwindfishes|Balladofwindfishes]] 15:35, 6 August 2011 (PDT)
 
  
== Availability for stock weapons ==
+
== Weapon articles mentioning taunts that aren't kill taunts ==
  
As suggested by [[User:Balladofwindfishes]] on the IRC channel, should we start putting "Uncrate" on the stock weapons infoboxes? {{n}}[[File:User_Heffebaycay_stslogo.png|link=]] [[User:Ohyeahcrucz|<span style="font-weight:bold;font-family: Segoe UI"><font color="black">Ohyeahcrucz]]</font></span>  <span style="font-size:10px;font-weight:bold;font-family: helvetica"><font color="black"><nowiki>[</nowiki>[[User_talk:Ohyeahcrucz|T]]<nowiki>][</nowiki>[[Special:Contributions/Ohyeahcrucz|C]]<nowiki>]</nowiki></font></span> 16:55, 6 August 2011 (PDT)
+
I've noticed a few articles for weapons mentioning that those weapons have a unique taunt that is not a kill taunt, or a variation of the default weapon for that slot (which is still not a kill taunt). These are the [[Lollichop]], which mentions it has a unique taunt based on a scene from Meet the Pyro, and the [[Third Degree]] and [[Neon Annihilator]], which mention the added guitar sounds, respectively. In comparison, the [[Cow Mangler 5000]], [[Scottish Resistance]], and [[Ullapool Caber]], which also have unique taunts, do not mention them since they're not kill taunts, and the [[Vita-Saw]], which has has a variation of the default taunt, does not mention said variation.
: Technically a Shotgun and Pistol are uncrateable. Personally, I think "uncrate" and then a tooltip about it being a strange weapon might be worth considering. [[User:Balladofwindfishes|Balladofwindfishes]] 16:55, 6 August 2011 (PDT)
 
: I am in favor of "Uncrate: Yes (tooltip this is uncratable in strange form) et cetera --[[User:SilverHammer|SilverHammer]] 17:45, 6 August 2011 (PDT)
 
  
== Quakecon nav box ==
+
I think we should remove these notes from the Lollichop, Third Degree, and Neon Annihilator, as they are already all noted in the Pyro taunts page.
  
Other promotional's such as grordbort victory pack have nav boxes. So why can't this promotion have a nav box? should it? '''<span style="font-family:aharoni; font-size:110%; font-style:italic;">[[File:RED Überneedle.png|42px|link=User:Lexar]] - <span style="text-decoration:underline">[[User:Lexar|Lexar]]</span> - <span style="text-decoration:underline">[[User talk:Lexar|talk]]</span></span>''' 17:44, 8 August 2011 (PDT)
+
Speaking of the [[Pyro taunts]] page, I think we can move the "as in Meet the Pyro" comment from the Lollichop's description to a new Trivia section and add that Execution is also based in a Meet the Pyro scene (which is not mentioned). - [[User:BrazilianNut|BrazilianNut]] ([[User talk:BrazilianNut|talk]]) 16:45, 7 December 2023 (UTC)
  
Well, with the QuakeCon update, we aren't getting a multitude of items, like with Dr.Grordbort's Victory Pack, we are only getting [[The Original]].  So, that's why there is not navigation box. [[File:Killicon_splendid_screen.png|60px]][[User:TheTimesAndQueriesOfMyAss|<span style="color:#B8383B;font-size:14px;font-family: 'Trebuchet MS';text-shadow:#e3e3e3 2px 2px 0px;"><b>TheTimesAndQueriesOfMyAss</b></span>]] 17:46, 8 August 2011 (PDT)
+
:I think variants on an existing taunt should be mentioned, such as different sounds (such as the Third Degree/Neon Annihilator adding guitar sounds and the Vita-Saw having different melodies being played), but the non-kill taunt shouldn't be mentioned (no note about the Lollichop taunt. Although seeing as it's unique to that weapon, I think the Trivia can stay).<br>[[File:BLU Wiki Cap.png|20px|link=List of Wiki Cap owners]] | [[Help:Group rights|<span style="color:green;font-family:TF2 Build;">s</span>]] | [[User:GrampaSwood|<font color="DB9C1F">GrampaSwood</font>]] [[File:PraisetheSun.png|20px|alt=Praise the Sun!]] ([[User talk:GrampaSwood|<font color="DB9C1F">talk</font>]]) ([[Special:Contributions/GrampaSwood|<font color="DB9C1F">contribs</font>]]) 17:14, 7 December 2023 (UTC)
:Plus the [[Pip-Boy]], [[Tamrielic Relic]], [[Wingstick]], [[Anger]]. {{n}}[[File:User_Heffebaycay_stslogo.png|link=]] [[User:Cructo|<span style="font-weight:bold;font-family: Segoe UI"><font color="black">Cructo]]</font></span>  <span style="font-size:10px;font-weight:bold;font-family: helvetica"><font color="black"><nowiki>[</nowiki>[[User_talk:Cructo|T]]<nowiki>][</nowiki>[[Special:Contributions/Cructo|C]]<nowiki>]</nowiki></font></span> 17:49, 8 August 2011 (PDT)
 
:: The update wasn't much different than the Summer Sale, which has a nav. I fully agree the update should have a nav, it added a bunch of content related to a specific event (QuakeCon) which is basically similar to the Summer Sale with slightly less items and a shorter sale. [[User:Balladofwindfishes|Balladofwindfishes]] 17:51, 8 August 2011 (PDT)
 
:::Here is what it would look like (excuse the title its not in the dictionary because it hasn't got a page of its own).
 
{{Navbox
 
| name  = QuakeCon Sale
 
| state = {{{state|uncollapsed}}}
 
| liststyle = padding: 0.25em;
 
| title = [[QuakeCon Sale{{if lang}}|{{weapon name|QuakeCon Sale}}]]
 
| group1 = [[Weapons{{if lang}}|{{weapon name|weapons}}]]
 
| list1  = {{Navbox | child
 
| group1 = {{class link|Soldier|size=16px}}
 
| list1  = [[Original{{if lang}}|{{weapon name|Original}}]]
 
}}
 
  
| group2 = [[Hats{{if lang}}|{{hat name|hats}}]]
+
== Main menu Smissmas 2023 header localization ==
| list2  = {{icon class|Sniper|size=16px}} [[Anger{{if lang}}|'''{{weapon name|Anger}}''']]<!--
 
-->{{md}} {{icon class|Heavy|size=16px}} [[Tamrielic Relic{{if lang}}|'''{{weapon name|Tamrielic Relic}}''']]
 
  
| group3 = [[Miscellaneous items{{if lang}}|{{hat name|misc}}]]
+
'Smissmas 2023' is localized but 'December 7 - January 7' is not. Is it possible to localize it too? [[File:User Denied signature.jpg|50px|link=User:Denied]] [[User:Denied|Denied]] [[User talk:Denied|(Talk)]] 10:29, 17 December 2023 (UTC)
| list3  = {{icon class|Engineer|size=16px}}[[Wingstick{{if lang}}|'''{{weapon name|Wingstick}}''']]<!--
 
  -->{{md}} {{icon class|Engineer|size=16px}} [[Pip-Boy{{if lang}}|{{weapon name|Pip-Boy}}]]
 
  
}}
+
:See [[Template:Dictionary/common_strings#.5BMain_Page.5D_Smissmas_2023|Dictionary common strings]].<br>[[File:BLU Wiki Cap.png|20px|link=List of Wiki Cap owners]] | [[Help:Group rights|<span style="color:green;font-family:TF2 Build;">s</span>]] | [[User:GrampaSwood|<font color="DB9C1F">GrampaSwood</font>]] [[File:PraisetheSun.png|20px|alt=Praise the Sun!]] ([[User talk:GrampaSwood|<font color="DB9C1F">talk</font>]]) ([[Special:Contributions/GrampaSwood|<font color="DB9C1F">contribs</font>]]) 13:37, 17 December 2023 (UTC)
I may have forgotten a few thing in it. The main idea is that we can get a nav box. change the colors all you like, this is just a basic layout. '''<span style="font-family:aharoni; font-size:110%; font-style:italic;">[[File:RED Überneedle.png|42px|link=User:Lexar]] - <span style="text-decoration:underline">[[User:Lexar|Lexar]]</span> - <span style="text-decoration:underline">[[User talk:Lexar|talk]]</span></span>''' 18:14, 8 August 2011 (PDT)
 
: Something about that seems scattered and unorganized, which is kind of funny since it's organized just like any other nav. [[User:Balladofwindfishes|Balladofwindfishes]] 18:35, 8 August 2011 (PDT)
 
::I don't think a nav box is necessary or warranted; the Dr. Grordbort nav box makes sense since it was content that was created specifically for TF2 that is independent of anything else and was its own update, while some of the promo items from the most recent sale are from games that weren't even part of the QuakeCon package (they just happened to be on sale) at the same time).  Given that, the Original is really the only real promo item, and that does not warrant a nav box of its own.  [[User:ButteredToast|ButteredToast]] 11:28, 9 August 2011 (PDT)
 
::: All items included were part of the QuakeCon event. The promo wasn't just for the package. On the wiki, we shouldn't make the call on what is a "real" promo or not. The fact remains the items are all promo items that all fit under a very specific theme. Such a criteria is also why we have the Summer Camp Nav and Shogun Nav [[User:Balladofwindfishes|Balladofwindfishes]] 11:30, 9 August 2011 (PDT)
 
::::I have to agree with TheTimesAndQueriesOfMyAss; the other games that happened to be on sale (such as Brink and From Dust) weren't necessarily part of the package, and just happened to be on sale at the same time as the QuakeCon package (and had promotional items).  Steam has sales on software all the time, but not every sale warrants a nav box.  [[User:ButteredToast|ButteredToast]] 12:14, 9 August 2011 (PDT)
 
::::: Nobody was talking about putting the From Dust promo into a nav. Brink was a major part of the QuakeCon sale and had an entire day dedicated to it, plus free DLC launched just for it. Brink was also made by Bethesda, who had the majority of the promos items and ad space during the event. And for the record, we do have navs for every major sale (as this was) tied to promo items. Both the Steam treasure hunt and Summer Sale have navs including their items. We don't need navs for midweek madness or daily deals, but the Quakecon sale was a massive sale that spanned 5 days and was directly related to a special event. All the promos added last friday were released for the purposes of that event. [[User:Balladofwindfishes|Balladofwindfishes]] 12:18, 9 August 2011 (PDT)
 
::::::The point I was making with the From Dust reference is the fact that there can be sales of other things (that include promo items) that go on at the same time that aren't necessarily included in a sale or set; you even acknowledged this yourself after I made the point, but won't hold the other games or promo items to the same standard despite the fact that they weren't all part of the same package.  That aside, just because something was "done before" does not necessarily mean that it is correct or should be continued; a lot of things that are done on a Wiki are typically done because someone else did it or some variation of it before, but it does not always serve as an ample justification or precedent.  [[User:ButteredToast|ButteredToast]] 13:32, 9 August 2011 (PDT)
 
  
== Wikifier ==
+
:: Thanks. [[File:User Denied signature.jpg|50px|link=User:Denied]] [[User:Denied|Denied]] [[User talk:Denied|(Talk)]] 14:19, 18 December 2023 (UTC)
  
Hello everyone!
+
== Link of the wiki team fortress energie drink don't work ==
For more than 1 month, the wikifier script has helped the Russian Team to write articles. It a button that appears on the edit page, that calls a script when clicked. When you click the button, the Wikifier script fixes common mistakes in the article (the button only shows in the wiki editor, and you can preview what it does). For example, it puts the correct russian quotes («...» and “...” inside them), the right spaces after and before punctuation symbols (It will replace “Здравствуй ,  сударь ! ” by “Здравствуй, сударь!”), and fix wiki and HTML marking, etc. It is like WindBOT working in your browser. Wind and I want to make this script global. To do this, I need to know what do you, localization teams, want it to do? Can you tell me some your language-specific punctuation and typographic rules? Common mistakes that editors in your language do? --[[File:Login_Soldier.png|link=User:Daniil]][[User:Daniil|Daniil]] 23:58, 14 August 2011 (PDT)
 
:{{c|Support}} [[Media:Heavy specialweapon09.wav|I like dis new weapon]] :3 — [[User:WindPower|<span style="font-weight:bold;">Wind</span>]] 00:02, 15 August 2011 (PDT)
 
:{{c|Support}} This is good applicable to the german language. [[File:User_SackZement_signature.gif|link=User:SackZement]][[User:SackZement|<span style="font-size:14px;font-family: Tf2 Build"><font color="orange">SackZement]]</font></span> [[User_talk:SackZement|(Talk)]] 01:15, 15 August 2011 (PDT)
 
:{{c|Support}} Very good idea. The Spanish team would certainly see benefit to the Wikifier.  [[user:BiBi|<small style="background:#f6f6f6;border:1px solid #006666;padding:0em  0.5em;color:#000;-webkit-box-shadow:2px 1px 1px #006666;">'''BiBi '''</small>]]    04:11, 15 August 2011 (PDT)
 
: {{c|Support}} Iz Really Good ! Especialy when french punctuation adds spaces where other languages doesn't ! I approve of this, it sure will be useful for every localisation. [[User:Tturbo|<span style="font-family:TF2 Build; color:#70B04A ">Tturbo</span>]] [[File:Killicon_ambassadorhs_unused.png|50px|link=User:Tturbo]] <sub><sub>([[File:Speech voice.png|20px|link=User talk:Tturbo]] / [[File:Intel neutral pickedup.png|20px|link=Special:Contributions/Tturbo]])</sub></sub> 08:48, 15 August 2011 (PDT)
 
* Okay. Here we go. Local teams, please read your [[Team Fortress Wiki:Translation progress|local discussion]]. --[[File:Login_Soldier.png|link=User:Daniil]][[User:Daniil|Daniil]] 13:20, 17 August 2011 (PDT)
 
  
== New update? ==
+
[[https://wiki.teamfortress.com/wiki/Team_Fortress_Wiki:Wiki_Birthday#Official.E2.84.A2_Team_Fortress_Energy_Drink]] you see this page on the wiki contain a team fortress wiki energie drink with a link for have it but it don't work and is not secure, can someone help me ? <small>— ''The preceding unsigned comment was added by'' '''[[User:Nonolemage|Nonolemage]]''' ([[User talk:Nonolemage|talk]]) • ([[Special:Contributions/Nonolemage|contribs]]) 2023-12-21, 13:46 UTC</small>
  
I just got the typical "Steam has finished downloading Team Fortress 2" message. No, I did not recently start reinstalling TF2. I do believe an update has occurred, gentleman. Why has nobody said anything about this yet? [[User:404 User Not Found|404 User Not Found]] 15:00, 15 August 2011 (PDT)
+
:Please sign your messages using <nowiki>~~~~</nowiki>.
::Oh special, my TF2 is crashing on load now. What did Valve do now? [[User:404 User Not Found|404 User Not Found]] 15:00, 15 August 2011 (PDT)
+
:The website appears to be down and no archive of it exists, so unless someone here happens to have a copy we can't do much.<br>[[File:BLU Wiki Cap.png|20px|link=List of Wiki Cap owners]] | [[Help:Group rights|<span style="color:green;font-family:TF2 Build;">s</span>]] | [[User:GrampaSwood|<font color="DB9C1F">GrampaSwood</font>]] [[File:PraisetheSun.png|20px|alt=Praise the Sun!]] ([[User talk:GrampaSwood|<font color="DB9C1F">talk</font>]]) ([[Special:Contributions/GrampaSwood|<font color="DB9C1F">contribs</font>]]) 13:46, 21 December 2023 (UTC)
:Because it just patched, be more patient we don't get thing done before we know when they happen. Also, I doubt this is appropriate discussion, of course updates are going to happen. - http://i.imgur.com/6vKcd.png[[User:Nixshadow|<span style="text-shadow:#869 0 0 5px; color:#a8b;"><u>nixshadow</u>]]</span> <span style="text-shadow:#859 0 0 5px; color:#a8b">([[User talk:Nixshadow|t]]|[[Special:Contributions/Nixshadow|c]])</span> 15:02, 15 August 2011 (PDT)
 
::Yeah, it's totally appropriate discussion. No two ways about it....or however that saying goes... [[User:404 User Not Found|404 User Not Found]] 15:03, 15 August 2011 (PDT)
 
:::If it was this page would be filled with over 100 topics about 9 mb updates. - http://i.imgur.com/6vKcd.png[[User:Nixshadow|<span style="text-shadow:#869 0 0 5px; color:#a8b;"><u>nixshadow</u>]]</span> <span style="text-shadow:#859 0 0 5px; color:#a8b">([[User talk:Nixshadow|t]]|[[Special:Contributions/Nixshadow|c]])</span> 15:04, 15 August 2011 (PDT)
 
::::.....Touche. [[User:404 User Not Found|404 User Not Found]] 15:06, 15 August 2011 (PDT)
 
  
== Getting item contributors involved: The Concept and Design section ==
+
== Multiple Suggestions related to Infobox, etc ==
  
So I was looking around the Wiki and right now we're basically set with gameplay stuff on the English pages. This site is packed to the brim with weapon stats, paint images, etc. And those are great! But a lot of people, myself included, like to know more about the design of TF2 and the items in it. I've already started to outreach with the groundwork of this idea by collecting concept art from contributors, but I feel we can go further. Right now we have some trivia elements like "this item was originally named blah blah and had blah blah as a texture" and for many article, that's okay. But many, many items have much longer, more detailed designs behind them. The Tomislav for example, went through 3 or 4 revisions (which we have images of, we have pages of critiques from others on the item). In March the contributor was contacted by Valve stating they wanted the item in the game. The creator is the youngest contributor of TF2 items ever, and this is a fact Valve has toted. A nice bunch of paragraphs could easily be written outlining the development history of Tomislav. And then there's the Shogun pack. There's an entire history of that shogun pack hidden deep in Kritzkast's archives that we only start to mention. Stuff like Sega contacting all of the polycount winners and Laro being the only one to actually respond. Sega specifically wanting Geisha hair for medic.
+
Hi. I have been wanting to write this in the past, but, well, finally here it is. I have a couple suggestions about things related to infobox, and other things to make the design of the Wiki flow better on certain articles. I will be posting here as it covers a multitude of topics, as opposed to posting each one of them on their respective templates. When adding "Support" and "Not Support" on your responses, please make sure to add the number (and letter) behind to specify what you are supporting (or not supporting) as a change (like: "1-c"). With that said, let's get going:
  
This also ties in with another problem I noticed. We have this large group of people who directly own a portion of this game, and are easily approachable, and yet we neglect this wealth of information that could easily fill up interesting sections. All these contributed hats and weapons lacking any sort of meaningful trivia, despite the creator standing right there, ready to be contacted and asked questions.
+
<hr>
  
Obviously not every page would need such a section, but for many items, the story of the item is just not nearly as interesting in one line of trivia. I feel like as a TF2 wiki, we can remain true to the gameplay of the game while still adding things people would expect and find interesting on a wiki. Outside of game stories.  
+
1) Implement a way on the {{code|Item infobox}} template where if a style or class has only one team-color compared to other styles with team-colors, include an icon in the middle of both teams. For instance:
  
[[User:Balladofwindfishes/sandbox|Right here is the Shiv article redone with the new section and removed redundant design trivia.]]
+
a) The Heavy variant of the [[Team Captain]] only has one color, but the page right now includes a duplicate of the RED variant as a workaround. What I suggest is doing this: [https://i.imgur.com/YgQHk5z https://i.imgur.com/YgQHk5z]. Make the Heavy variant only one file, and center it. It should be pretty clear that because of the image is in the middle, is that it looks like that on both teams.
  
Please think about this a bit before just saying no. This is something not many game wikis have the luxury of doing. We're unique in that we have the community who designs large portions of the game and are easily approachable. Let's not ignore that resource. [[User:Balladofwindfishes|Balladofwindfishes]] 18:30, 16 August 2011 (PDT)
+
b) For items with styles that only has one color (not team-colored), do the same thing as well. In the example of [[Close Quarters Cover]], include the "Alert" style on the infobox in the middle of the "RED" and "BLU" sections of the infobox, something like this: [https://i.imgur.com/lARBQME https://i.imgur.com/lARBQME].
:{{c|Support}} We need stuff like that, makes the article more interesting. {{n}}[[File:User_Heffebaycay_stslogo.png|link=]] [[User:Cructo|<span style="font-weight:bold;font-family: Segoe UI"><font color="black">Cructo]]</font></span>  <span style="font-size:10px;font-weight:bold;font-family: helvetica"><font color="black"><nowiki>[</nowiki>[[User_talk:Cructo|T]]<nowiki>][</nowiki>[[Special:Contributions/Cructo|C]]<nowiki>]</nowiki></font></span> 18:37, 16 August 2011 (PDT)
 
:{{c|Neutral}} It's an interesting idea, but I think that it would be useful to canvass (I can use buzzwords too! ;)) the community, perhaps using the Steam Fora initially, in order to gauge the level of interest. If there is community support, then that would indicate that the content would be of interest and would be worth compiling. --- [[File:Killicon_pumpkin.png|40px|link=User:Esquilax]] <font face="georgia" size="2">[[User:Esquilax|Esquilax]]</font> 18:39, 16 August 2011 (PDT)
 
::I can ask Facepunch, Polycount and SUF and feel out the interest, if more people think this is an issue. FP/Polycount might be valuable places to gauge interest on a contributor level, especially since that's where 99% of the information for the section would come from.  [[User:Balladofwindfishes|Balladofwindfishes]] 18:41, 16 August 2011 (PDT)
 
:::{{c|Support}}I second the notion of getting contributers more involved.  The developement of the games items etc. is just as, if not more, interesting as the gameplay '''<span style="font-family:Terminal; font-size:120%; color:#0cff00; font-style:;">[[File:User_BC_sigimage.png|33px|link=User:BC]]****[[User:BC|BC]]</span>'''<sup>[[User talk:BC|talk]]</sup> 18:43, 16 August 2011 (PDT)
 
::{{C|comment}} Daimao and Nzdjh both thought it was a good idea, plus Political Gamer seems interesting in getting map contributors on board. [[User:Balladofwindfishes|Balladofwindfishes]] 06:17, 17 August 2011 (PDT)
 
::: Well, here's a Sandbox of my idea, with the Shiv written out. The Shiv is nice because it's got a good source of development history. [[User:Balladofwindfishes/sandbox|Here is the Shiv article redone with the new section and removed redundant design trivia.]] [[User:Balladofwindfishes|Balladofwindfishes]] 08:14, 17 August 2011 (PDT)
 
:::::{{c|Support}} I found that very interesting to read and don't think it detracted from the article at all. However, I think the positioning of the section was a bit off, I think it may be better if the section was moved to below say the Achievements section? I feel it's more important to have all the information relevant to actual gameplay presented first, before a section on the item's history is presented. -[[User:Mr. Magoolachub|Mr. Magoolachub]] 19:12, 17 August 2011 (PDT)
 
:::::: Alright, I changed up the order a bit, does lit look better now? [[User:Balladofwindfishes|Balladofwindfishes]] 11:29, 17 August 2011 (PDT)
 
::::::: Much better :D -[[User:Mr. Magoolachub|Mr. Magoolachub]] 19:12, 17 August 2011 (PDT)
 
:::::::: I'm hesitant to begin working on more though, I'd really like some more input. [[User:Balladofwindfishes|Balladofwindfishes]] 09:21, 18 August 2011 (PDT)
 
:[[User:Maggosh/Sandbox|The section, revised.]] Fixed some inaccuracies, moved information around to make it flow better. If anyone wants to proofread this as well, by all means, proceed. [[User:Maggosh|mag]][[User talk:Maggosh|gosh]] 10:14, 18 August 2011 (PDT)
 
:: Wow Maggosh, you knocked it out of the park! [[User:Balladofwindfishes|Balladofwindfishes]] 12:21, 18 August 2011 (PDT)
 
::: Why thank you. [[User:Maggosh|mag]][[User talk:Maggosh|gosh]] 06:42, 19 August 2011 (PDT)
 
  
== Hat levels in articles ==
+
c) For items that are not team-colored, but have class-specific variants, include a new part colored in grey called "Both Teams", and include each image on the middle as well. For example, the [[Dead Little Buddy]] have 3 model variants, one for Pyro, one for Demoman, and the other for the remaining classes. The idea is this: [https://i.imgur.com/xPD9PMO https://i.imgur.com/xPD9PMO].
  
With [[August_18,_2011_Patch|recent update]] we got an ability to see hat levels in-game. But we still have "Level 1-100" in articles (unless this is a special case). I suggest change this to "Level 1-100 Hat" where possible. <b>[[User:DrAkcel|<font FACE="Arial" color="#41627E">DrAkcel</font>]]</b> <sup>([[User_talk:DrAkcel|<font FACE="Arial" color="#25587E">T</font>]] | [[Special:Contributions/DrAkcel|<font FACE="Arial" color="#25587E">C</font>]])</sup> 00:28, 19 August 2011 (PDT)
+
d) Although I do not have a mock-up right now, I thought of also doing the same as above for items that has only one color. So, for instance, the [[Jumper's Jeepcap]] would have a "Both Teams" section, and it would include the "UNPAINTED" variant on the center. Items with styles with just one color, like [[Mustachioed Mann]], would be similar to Dead Little Buddy, including each style on the infobox, alongside their names. Items like [[Carl]] that has no styles, but is neutral-colored, would also have the "Both Teams" part.
  
:This can be changed in {{tl|Item infobox}} so that hats with no other specific levels can be displayed as "Level 1-100 Hat". I'll edit this now so people don't have to edit every hat page. [[user:seb26|<small style="background:#f9f9f9;border:1px solid #0070FF;padding:0em 0.5em;color:#000;-webkit-box-shadow:2px 1px 1px #8BBEFF;">'''seb26'''</small>]] 03:19, 19 August 2011 (PDT)
+
<hr>
  
::Ok {{c|done}} [[user:seb26|<small style="background:#f9f9f9;border:1px solid #0070FF;padding:0em 0.5em;color:#000;-webkit-box-shadow:2px 1px 1px #8BBEFF;">'''seb26'''</small>]] 03:33, 19 August 2011 (PDT)
+
2) Get rid of the current "2D" images of Weapons, and use "Item icons" instead. The 2D weapon images are not consistent throughout the Wiki. They have different lighting, different angles, and so on. What I suggest is doing something similar to another Wiki I also contributed (one related to a TF2 sourcemod): [https://i.imgur.com/vbvPbGP https://i.imgur.com/vbvPbGP]. This looks extremely clean, and every page would have in this angle. The 2D image only includes the RED variant, just like we use RED classes on our cosmetic previews.
  
== Added Team Fortress skins removed ==
+
<hr>
  
Today I edited all of the skins from Team Fortress to make them presentable (They are the actual skins from the model, the game shows only whats in the UV map, however it is still shown in the skin), and after getting permission on the IRC, to upload them, I proceeded to do so and then edited the page to include the newly uploaded images.
+
3) Add the "RED" and "BLU" sections on the infobox for Weapon pages, even if the 3D image allows you to switch between teams. Right now, the RED variant is used as the 2D image (for team-colored weapons), while the 2D BLU variant awkwardly sits on the Gallery section. My suggestion would be this: [https://i.imgur.com/dM9z7Oo https://i.imgur.com/dM9z7Oo]
  
They were removed unfortunately. I'm unsure why, as Team Fortress Classic images are there, as well as Team Fortress 2 images, so why not Team Fortress as well?
+
<hr>
  
Thank you.
+
4) For cosmetic pages that has styles alongside class changes on the Painted Variants table, include additional buttons that include class icons. The idea is to remove clutter on pages with a lot of tabs to choose from (see [https://wiki.teamfortress.com/w/index.php?title=Boarder%27s_Beanie&oldid=3594086 this page]). In technical terms, the style buttons would be responsible to change the "style" part of the filename, while the class buttons would change the class part of the filename. If the first class is chosen, then the code needs to get rid of the class part of the filename, as the first class is always the default: [https://i.imgur.com/QmQCLsK https://i.imgur.com/QmQCLsK]
  
[[User:TeamXlink|TeamXlink]] 10:30, 19 August 2011 (PDT)
+
a) Additionally, text could be placed on each row, one for "Style:", and the other for "Class:" for the second row, just so it's a little more intuitive and understandable for everyone.
: Only your Sniper image on the [[Sniper]] page was removed...  they're still on all the other pages so I guess you can put it back for sake of consistency. -[[User:RJackson|<span class="modbg" style="margin-right:1px;text-shadow: #538237 1px 1px 0px;">RJ</span>]] 11:09, 19 August 2011 (PDT)
 
  
:: But none of them should be there at all. They're really unneeded, shoehorned in. I mean really, we don't have their TF2 textures up in the galleries, it's just unnecessary. The models that use the textures are included in the galleries, they're the first images for every one. I took care to make sure they were all in chronological order. --[[User:SilverHammer|SilverHammer]] 18:28, 24 August 2011 (PDT)
+
<hr>
  
== "Added new Weapon:" Or "Added Weapon:" ==
+
5) Include "infobox images" for separate styles, and add buttons that let you change it. The idea is to include identical images (with identical classes and facial flexing), with the only thing changing the model. For example, [[Main Cast]] would look like this: [https://imgur.com/a/OmTIYVs https://imgur.com/a/OmTIYVs].
  
I've noticed an inconsistency in the update history of the classes. Sometimes it will say "Added new Weapon:" other times it will say "Added Weapon:".
+
<hr>
  
Which should I be using?
+
6) Include more sections on the Gallery for items with more than one Style. In the past, the [[Robot Chicken Hat]] page did include all 9 classes on the Gallery section, with 2 separate sections, one with the "Beak" style, and the other with "Beakless" style. It would follow the same rule as "5)", with both images looking identical facial-flex and pose-wise. Some pages like [[Dead of Night]] wouldn't include all classes on each section. Classes with lack of grenades wouldn't be there.
  
Thank you.
+
'''Edit:''' Some users asked for an example, so, when I talked about the Robot Chicken Hat, it originally [https://wiki.teamfortress.com/w/index.php?title=Robot_Chicken_Hat&oldid=1679218 looked like this]. The images don't exist anymore, but you can still see how it looked like. When I wrote the suggestion, I thought something about that (though it could have been changed a little, like include an "Other" title for the remaining images that aren't related to the class images), but, after Swood's suggestion, I'd say that using Tabs would be more ideal, something akin to how we do on the Tournament Medal pages.
  
[[User:TeamXlink|TeamXlink]] 10:31, 19 August 2011 (PDT)
+
I did an example on my 2nd Sandbox page. I thought something about this: [https://wiki.teamfortress.com/w/index.php?title=User:Gabrielwoj/Sandbox2&oldid=3598538 https://wiki.teamfortress.com/w/index.php?title=User:Gabrielwoj/Sandbox2&oldid=3598538] (note that a couple images, namely the infobox team-colors, and paint cans, does not show up properly due to the page's name being different, if this were to be pasted onto the actual page, it would show just as fine). I decided to not make the Tabs centered as regular cosmetic pages are usually not centered, unlike Tournament Medals / Community Medal ones. I also decided to make the gallery width "485px", so it shows 3 images per row, and looks pretty nice and cool with whatever's below that does not require a Tabs section.
  
== The great Wiki clock! ==
+
<hr>
  
Hey guys. Check out the clock at the top of the page at [[portal:Main Page|The Portal Wiki]].  Do you guys think this is worth implementing on the TF Wiki? The difference being instead of displaying UTC, it would display PDT as PDT is the timezone used for talk-page signatures; this would give a quick reference point when seeing how long ago a comment was added - useful for users in timezones other than PDT.
+
7) Lastly. Items that include noticeable team-color differences could also get "Single Color" paint can previews on both teams, even if the paint look identical on the area that is paintable. When Paints were first introduced, they were mostly applied to cosmetics that used the same texture on either team. Now, nowadays, we have cosmetics that include team-colored parts that are not paintable, alongside other parts that are. So, for instance, [[Brawling Buccaneer]] would have its Painted variants table from <nowiki>{{Painted variants}}</nowiki> to <nowiki>{{Painted variants full}}</nowiki>, and single color paint can previews for the BLU team would be made, to show how the paint looks like, and despite being painted in the same area, the rest of the item is in another color. Readers might want to know how an item looks on the BLU team. This would take a long time too make for the entirety of the Wiki, and would be a project that would require remaking some paint variants if they do not have Rotation values saved, or if there's another issue that doesn't make them 1:1, but I think it would look good, and useful as well.
  
Bear in mind this can be implemented per-user via a user's <code>User:SomeUser/vector.js</code> file.  This discussion's whether or not it should be implemented site-wide.  Yay or Nay? -[[User:RJackson|<span class="modbg" style="margin-right:1px;text-shadow: #538237 1px 1px 0px;">RJ</span>]] 15:07, 19 August 2011 (PDT)
+
<hr>
: {{c|Yes}} I suggested it, bcuz I love it. -[[User:RJackson|<span class="modbg" style="margin-right:1px;text-shadow: #538237 1px 1px 0px;">RJ</span>]] 15:07, 19 August 2011 (PDT)
 
: {{c|No}} Unneeded. You can just check your clock. {{n}}[[File:User_Heffebaycay_stslogo.png|link=]] [[User:Cructo|<span style="font-weight:bold;font-family: Segoe UI"><font color="black">Cructo]]</font></span>  <span style="font-size:10px;font-weight:bold;font-family: helvetica"><font color="black"><nowiki>[</nowiki>[[User_talk:Cructo|T]]<nowiki>][</nowiki>[[Special:Contributions/Cructo|C]]<nowiki>]</nowiki></font></span> 15:08, 19 August 2011 (PDT)
 
: {{c|No}} The .01 seconds it takes to look at the bottom right of my monitor will continue to suffice. [[User:SS2R|SS2R]] 15:10, 19 August 2011 (PDT)
 
:: {{c|comment}} Consider that not everybody's time-zone is PDT. I'm UTC - I'd have to go and find out how many hours back PDT is and then invent math.  This would provide the same reference your clock does for users in other timezones. -[[User:RJackson|<span class="modbg" style="margin-right:1px;text-shadow: #538237 1px 1px 0px;">RJ</span>]] 15:12, 19 August 2011 (PDT)
 
:: I can't see any reason why it's important to know when a response was made on a talk page.  The important things are WHO responded and what the beef is of what they say.  I could care less if they said it at 12:01am or 4:16pm. [[User:SS2R|SS2R]] 15:20, 19 August 2011 (PDT)
 
:{{c|Oppose}} I don't like that clock >: It changes every second, which attract my eyes to there, thus distracts me from the article. And no I'm not in the PDT time zone either — [[User:WindPower|<span style="font-weight:bold;">Wind</span>]] 18:53, 19 August 2011 (PDT)
 
:{{c|comment}} I don't like the clock, but i find cache purging very useful <b>[[User:DrAkcel|<font FACE="Arial" color="#41627E">DrAkcel</font>]]</b> <sup>([[User_talk:DrAkcel|<font FACE="Arial" color="#25587E">T</font>]] | [[Special:Contributions/DrAkcel|<font FACE="Arial" color="#25587E">C</font>]])</sup> 00:43, 20 August 2011 (PDT)
 
:{{c|neutral}} I like bells and whistles as much as the next guy, but I don't think I'd miss it if it weren't there. -- [[Image:User Alex2539 Sig.png|47px|link=User:Alex2539|Alex2539]] - {{mod}} <sub>([[User_talk:Alex2539|talk]] | [[Special:Contributions/Alex2539|contribs]])</sub> -- 06:39, 20 August 2011 (PDT)
 
: {{c|Yes}} Great idea. [[User:Plummaster|Plummaster]] 06:41, 20 August 2011 (PDT)
 
: {{c|Support}} "What was that, Sandvich? Put a clock? Good idea!" Now seriously: most members probably never thought of it, but have you tried keeping track of long discussions on talk pages? Specially when they have no signature, people place signatures without <nowiki>~~~~</nowiki> etc? It's tough as hell. Specially when you're trying to place {{tlx|unsigned}} templates and such. Also, I keep a [[Team Fortress Wiki:Translation progress/pt-br/to-do|list of translations]] to be done for [[Team Fortress Wiki:Translation progress/pt-br|PT-BR]], and you have no idea how hard it is to place time marks without having a perfectly synched built-in computer clock compared to the Wiki clock, which is shared by all members. Most of you might not even notice these stuff, but they do make the difference on active discussions. {{n}} {{User:EpicEric/Sig/Image|RED}} {{User:EpicEric/Sig/Text|Epic|#5885A2}} {{User:EpicEric/Sig/Text|Eric|#B8383B}} {{User:EpicEric/Sig/Image|BLU}}{{User:EpicEric/Sig/Extra}} 08:44, 20 August 2011 (PDT)
 
: {{c|No}} &ndash; a clock thing on recent changes would be OK but I think it would be annoying on every page and especially to readers who probably won't find it that useful. I also have my own utc clock already :3 [[user:seb26|<small style="background:#f9f9f9;border:1px solid #0070FF;padding:0em 0.5em;color:#000;-webkit-box-shadow:2px 1px 1px #8BBEFF;">'''seb26'''</small>]] 15:20, 20 August 2011 (PDT)
 
: {{c|Oppose}} Unnecessary, and easily overlooked even if implemented. [[User:Coreycubed|coreycubed]] / [[User talk:Coreycubed|talk]] 07:15, 22 August 2011 (PDT)
 
: {{c|Oppose}} That clock shows the wrong time for me anyway so meaningless. --<span style="font-size:83%;border: 1px solid #FF0000;background:#FFFFFF">[[User:Swarfega|<font style="background: #FF0000" face="Arial" color="#FFFFFF">'''&nbsp;Swarfega&nbsp;'''</font>]][[User talk:Swarfega|<font style="background:#FFFFFF" face="Arial" color="#FF0000">'''&nbsp;T'''</font>]] [[Special:Contributions/Swarfega|<font style="background:#FFFFFF" face="Arial" color="#FF0000">'''&nbsp;C&nbsp;'''</font>]]</span> 04:15, 25 August 2011 (PDT)
 
  
== Tournament Medals article seperation ==
+
8) For items that has several styles / classes on the infobox (such as [[Manndatory Attire]], [[Beaten and Bruised]] and [[Boarder's Beanie‎]]), make the Infobox template show less of them by default, and include a button with a caption "↓ Show remaining ↓". If possible, make the last one have a "fade" effect, so it's perfectly clear what the button is about. My idea was to include at least 10 of these sections, then fade (because if it reaches 10 of these, it means there's more than one Style per class, where other pages would include 9 of these per class, though, it could be shortened if needed, but personally I would go with 10 sections before the button and fade shows up). It would look like this: [https://i.imgur.com/jh6geu6 https://i.imgur.com/jh6geu6]
  
Currently the Tournament Medal pages have a shared page for all ranks of medals. It would probably be best to separate them, but I'm going to go ahead and take a consensus on if this should be done, and if so, should it be done now, or when the medals are released? - http://i.imgur.com/6vKcd.png[[User:Nixshadow|<span style="text-shadow:#869 0 0 5px; color:#a8b;"><u>nixshadow</u>]]</span> <span style="text-shadow:#859 0 0 5px; color:#a8b">([[User talk:Nixshadow|t]]|[[Special:Contributions/Nixshadow|c]])</span> 02:50, 20 August 2011 (PDT)
+
<hr>
:{{c|Support}} We have separate pages for [[Duel badges]] and ID badges, so, i don't see any reason we created only one page for these <b>[[User:DrAkcel|<font FACE="Arial" color="#41627E">DrAkcel</font>]]</b> <sup>([[User_talk:DrAkcel|<font FACE="Arial" color="#25587E">T</font>]] | [[Special:Contributions/DrAkcel|<font FACE="Arial" color="#25587E">C</font>]])</sup> 02:52, 20 August 2011 (PDT)
 
:{{c|Oppose}} I'm against it, but only because I prefer the ''opposite'' action take place. I think that the Dueling Badges and 119th medals should have been consolidated into just two respective pages. That said though, I'm still somewhat opposed to it because it would mean creating a ridiculous number of nearly identical pages for the sake of consistency. There are 10 UGC medals, 3 GWJ medals and 4 ETF2L medals; that's 17 new pages all nearly identical pages created. I'm not against it just because it's a lot of work (which admittedly someone else will do), but because I can't fathom how the Wiki would benefit in any way from it. Who's really going to say: "Thank God for this separate article. Now I know what these two slightly different silver-coloured UGC badges look like and can compare them side-by-side"? So, I say no. Anyone going solely for consistency might want to consider instead consolidating the other badge pages. -- [[Image:User Alex2539 Sig.png|47px|link=User:Alex2539|Alex2539]] - {{mod}} <sub>([[User_talk:Alex2539|talk]] | [[Special:Contributions/Alex2539|contribs]])</sub> -- 07:21, 20 August 2011 (PDT)
 
:{{c|Oppose}} Alex2539 said pretty much everything I wanted to say. 17 practically identical pages is counter-productive. I would also support the merging of the duelling badges and 119th medal articles. '''<span style="font-family:Georgia;font-size:83%;">—[[File:User Moussekateer signature sprite.png|31px|link=User:Moussekateer]][[User:Moussekateer|<span style="color:black">Moussekateer</span>]]·[[User talk:Moussekateer|<span style="color:black;font-size:82%;">talk</span>]]</span>''' 12:15, 20 August 2011 (PDT)
 
:{{c|Oppose}} &ndash; there is nothing different at all about any of the new medals apart from their picture, and these are noted in the gallery section. 17 new pages for the sake of 'consistency' is a waste of time and effort [[user:seb26|<small style="background:#f9f9f9;border:1px solid #0070FF;padding:0em 0.5em;color:#000;-webkit-box-shadow:2px 1px 1px #8BBEFF;">'''seb26'''</small>]] 15:20, 20 August 2011 (PDT)
 
:{{c|Oppose}}, for the earlier mentioned reasons by Alex2539, plus a new one; I am a translator. I am not particularly inclined into having to basically translate the same page 17 times. When you can copy paste a page from another page and change just the names and a sentence, you know that they are better off merged. Like Moussekateer, I'd also support the merger of the duelling badges and the 119th medal articles. Additionally, I'd also like to see the propaganda hats remerged again with their normal counterparts. Sometimes less is just more. -- <span style="font-family:TF2 Build;font-size:90%;">[[File:Killicon train.png|40px|link=User:Hefaistus]] [[User:Hefaistus|<font color="#FF9933">Hefaistus</font>]]</span> - [[User talk:Hefaistus|<span style="color:black;font-size:82%;">talk</span>]] 03:55, 21 August 2011 (PDT)
 
  
== New paint table ==
+
'''Edit: ''' 9) Regarding the Styles section. If we include Styles on the infobox, even for items that look the same on either team, is it really necessary to include the "Styles" section on the page, alongside the table, if everything would be on the Infobox? It seems redundant to keep both of them, but, I'd only get rid of the Styles section after everything is added to the infobox, including the single-color Styles on it. Additionally, certain pages that has Styles that change between classes are a little confusing at the moment. [[Manndatory Attire]] has only Scout's styles being demonstrated on the table, despite each class changing the visuals.
  
I created a new version of [[Paint can]] table, that can be seen here [[User:DrAkcel/Sandbox2]]. The main template is [[User:DrAkcel/Sandbox|here]]. Any comments on this? <b>[[User:DrAkcel|<font FACE="Arial" color="#41627E">DrAkcel</font>]]</b> <sup>([[User_talk:DrAkcel|<font FACE="Arial" color="#25587E">T</font>]] | [[Special:Contributions/DrAkcel|<font FACE="Arial" color="#25587E">C</font>]])</sup> 09:00, 21 August 2011 (PDT)
+
a) Originally I was going to suggest a class-switcher button, similar to the "4)", but, if "1)" is implemented, I don't see any reason to keep the Styles section. Please let me know if you think there should be either: "An arrange of buttons that lets you change classes on the Styles table" or "Getting rid of the Styles section entirely as it would be redundant with all the styles on the infobox once the "1)" suggestion is implemented.
:{{c|Oppose}} I like the overall design of the table, but it doesn't fit the schema used on other pages (color, formentioned design). [[File:Userimg-real alien.jpg|25px]] [[User:Real alien|<span style="font-family:TF2 Build; color:#3366cc ">real_alien</span>]] ([[User talk:Real alien|T]]/[[Special:Contributions/Real alien|C]]) 09:05, 21 August 2011 (PDT)
 
  
== TF2 Crafting Tool ==
+
b) The only problem that getting rid of the Styles section would be problematic for items that has barely any difference unpainted, but has more notable differences when paintable. Items like [[Onimann]] mostly change its visuals when painted between styles, and if there's no section for it. However, the painted variants table, alongside the main summary on the top of the page, would both visually show the difference, as well would explain in text what each style does in terms of paint.
[[User:Roebuck5996|Roebuck5996]] 11:20, 21 August 2011 (PDT)
 
  
Hey I'm new to the wiki and just trying to throw an idea out there. I don't know how we could get this to fully work but ill just see if the idea attracts anyone.
+
<hr>
  
Alright, so basically an online crafting tool. When new updates come out and the recipes are trying to be found, why not have an online crafting tool where you can test different recipes without wasting your precious guns on tokens or angering yourself by not having the certain gun it could need to craft. There might be a crafting tool online, but adding one that could be used in the wiki would be very convenient. Just another reason to visit the wiki.
+
Please let me know your thoughts below. Notice that I'm not sure if I would be able to implement some of these suggestions, specially the ones for the "Item infobox" template. If there's enough support, I'd appreciate anyone who could implement suggested changes / additions. [[File:User Gabrielwoj Signature Icon.png|15px|Headphones style when?|link=User:Gabrielwoj]] - [[File:User Gabrielwoj Signature 1.png|link=User:Gabrielwoj]] ▪ [[File:User Gabrielwoj Signature 2.png|link=Special:Contribs/Gabrielwoj]] - [[File:User Gabrielwoj Signature 3.png|link=User talk:Gabrielwoj]] 21:13, 28 December 2023 (UTC)
  
I'm just throwing this idea out there. Any feedback would be appreciated!
+
:1. I think that section should be dedicated to showing off the team colours rather than different styles for different classes. If a cosmetic looks different on different classes I would prefer a different box for it similar to the "Styles" section.
 +
:2/3. That's fine by me, though I would also want to add a second button to it for the BLU variant rather than stuffing it in the Gallery.
 +
:4/5. I like this.
 +
:6. I like this, although I would suggest we use the {{tl|Tabs}} template for it.
 +
:7. I like this too, but it would require a ton of work and I'm not sure we'd be able to make it through.
 +
:8. I'm not sure that I'm a fan of collapsing a bunch of them. I would prefer having them sorted by class instead similar to {{tl|Tabs}}.
 +
:9. See answer on 1.<br>[[File:BLU Wiki Cap.png|20px|link=List of Wiki Cap owners]] | [[Help:Group rights|<span style="color:green;font-family:TF2 Build;">s</span>]] | [[User:GrampaSwood|<font color="DB9C1F">GrampaSwood</font>]] [[File:PraisetheSun.png|20px|alt=Praise the Sun!]] ([[User talk:GrampaSwood|<font color="DB9C1F">talk</font>]]) ([[Special:Contributions/GrampaSwood|<font color="DB9C1F">contribs</font>]]) 21:59, 28 December 2023 (UTC)
  
Thanks!
+
::1 {{c|+|Agree}} - All of these changes look very nice, I don't have anything to say about them.
 +
::2 / 3 {{c|?|Not sure / changes}} - Would the change to using weapon icons include BLU weapon icons as well? If it does, I would rather have the 2D BLU image in the main infobox when you click on BLU and then switch to the 2D image instead of it being below the main image.
 +
::4 {{c|+|Agree}} - This also looks nice.
 +
::5 {{c|-|Disagree}} - I don't know how I feel about this, I feel like the painted variants sorta already accomplish the goal of knowing what the cosmetic would look like with the different styles. It would also take a lot of work to recreate a lot of infobox images just for this.
 +
::6 {{c|-|Disagree}} - I have the same thoughts about this as 5, it would take a lot of work to redo a bunch of galleries when the styes / painted variants section already get the job done.
 +
::7 {{c|+|Sorta Agree}} - This would look nice, however it would again take a lot of work to get done.
 +
::8 {{c|+|Agree / changes}} - I like the idea, though I agree with what Swood said with that it would look better if it was just in tabs instead.
 +
::9 {{c|?|Not sure}} - I sort of agree with the idea of removing the styles section, but I also do like how there's a sort of simplified section for seeing all of the styles instead of it only being part of the infobox and painted variants.
 +
::[[User:Andrew360|<span style="font-family:TF2 Build; color:#038d3a ">Andrew360</span>]] [[File:Edit_icon.png|20px|link=Special:Contributions/Andrew360]] [[File:Speech typing.png|25px|link=User_talk:Andrew360]] [[File:Photo Badge Decal Example.png|15px|link=https://wiki.teamfortress.com/wiki/Special:ListFiles?limit=25&user=Andrew360&ilshowall=0]] 03:27, 29 December 2023 (UTC)
  
-Roebuck5996
+
:::1 {{c|-|Disagree}} - Same reason with Swood, I think the style section should do the job.
:Every recipe can be seen in item schema, so we have no need to "waste" metal. <b>[[User:DrAkcel|<font FACE="Arial" color="#41627E">DrAkcel</font>]]</b> <sup>([[User_talk:DrAkcel|<font FACE="Arial" color="#25587E">T</font>]] | [[Special:Contributions/DrAkcel|<font FACE="Arial" color="#25587E">C</font>]])</sup> 11:11, 21 August 2011 (PDT)
+
:::2 {{c|+|Agree}} - Good idea!
:Hello. First, please sign your posts with <nowiki>~~~~</nowiki>. Second, there's one [http://seanj.afraid.org/craft/# here]. Third, this is not what the Wiki is about. {{n}} {{User:EpicEric/Sig/Image|RED}} {{User:EpicEric/Sig/Text|Epic|#5885A2}} {{User:EpicEric/Sig/Text|Eric|#B8383B}} {{User:EpicEric/Sig/Image|BLU}}{{User:EpicEric/Sig/Extra}} 11:12, 21 August 2011 (PDT)
+
:::3 {{c|+|Sorta Agree}} - Instead of taking space in infobox, Why don't we use the same button used on 3D images?
 +
:::4 {{c|+|Agree}} - Yes.
 +
:::5 {{c|+|Agree}} - Looks nice, but considered what Andrew says we might not getting those done in recent.
 +
:::6 {{c|+|Agree}} - We are gonna do a lot of work then I guess.
 +
:::7 {{c|+|Agree}} - Same with Andrew360
 +
:::8 {{c|?|Not sure}} - Looks good, though yeah, why not use {{tl|Tabs}}?
 +
:::9 {{c|?|Disagree.. or Sorta Agree}} - If I have to choose one from infobox and style section, I would take style section. In my opinion the infoboxs shouldn't be too long and contain too much information, comparing to a small space on the right side of the page, I think the style section can display the information better. If 8 gets passed then I'm fine with it too. (I just don't want to see infobox gets longer than the page itself.)
 +
:::[[User:Profiteer|Profiteer(奸商)the tryhard]] ([[User talk:Profiteer|talk]]) 06:16, 29 December 2023 (UTC)
  
(Hopefully im editing this right this time.)
+
::::1 {{c|+|Sorta Agree}} - Eh, doesn't matter to me either way.
DrAkcel, im saying this could be used to figure out the recipes before they are published to the wiki, so they could be found quicker and put on the site quicker. Eric sorry about not signing the post, I'm new to the wiki and was not aware, also the site you posted is not loading for me for some reason. It was just a suggestion and I thought that it would fit in with the site, sorry about the misinterpretation.[[User:Roebuck5996|Roebuck5996]] 11:20, 21 August 2011 (PDT)
+
::::2 {{c|?|Not sure}} - I wanna see how it would look first.  
: You can use [http://willitcraft.com/ Will It Craft?] for this purpose as well. Hope that helps :) [[User:Coreycubed|coreycubed]] / [[User talk:Coreycubed|talk]] 08:00, 22 August 2011 (PDT)
+
::::3 {{c|+|Agree}} - I was kinda the one to start the whole "shoving the blue variant in the gallery" and have always wondered why there wasn't a color toggle for the 2D variants.
:: I see what you're getting at, but the crafting recipes haven't needed to be "found" for a while now. Ever since the [[March 15, 2011 Patch]] every recipe is listed within TF2 on the crafting screen as soon as they are available. Instead of guessing, all we need to do is check the recipe list in-game when an item is added or made craftable. A tool like this would indeed have been useful at one time, but not anymore. -- [[Image:User Alex2539 Sig.png|47px|link=User:Alex2539|Alex2539]] - {{mod}} <sub>([[User_talk:Alex2539|talk]] | [[Special:Contributions/Alex2539|contribs]])</sub> -- 12:43, 22 August 2011 (PDT)
+
::::4 {{c|+|Strongly agree}} - I wish it was like this since the beginning!
 +
::::5 {{c|?|Not sure}} - I like the idea, but it will take a '''lot''' of work updating all the pages and such with the change.
 +
::::6 {{c|?|Not sure}} - Same answer as 5.
 +
::::7 {{c|+|Agree}} - I'm only saying yes because we'll only have to edit the templates which are used across all translation pages.
 +
::::8 {{c|-|Somewhat disagree}} - There aren't very many items that have loads of different styles like this, I think I'd wait until we get something like a shirt or coat that includes a load of different styles (with team variants).
 +
::::9 {{c|-|Strongly disagree}} - Yeah it is necessary to have a styles section, because they mostly show examples of what they look like on the character wearing it. I know that the infobox has styles too, but they're only the raw models.
 +
::::[[User:ShadowMan44|ShadowMan44]] ([[User talk:ShadowMan44|talk]]) 01:52, 30 December 2023 (UTC)
  
== Standards for identical items ==
+
:::::So, after some user's responses, I'd like to mention a couple things. In regards to most of "2)" and "3)" responses, here's something I didn't mention. There would be a slight problem for items that are not team-colored if we just implemented a RED and BLU image switcher. The idea of using "Item icons" with the RED variant / neutral-color variant, would that it would make everything consistent and nice looking, While "RED" and "BLU" 2D images are usually very consistent too, the current "2D" images used on weapon pages are all over the place. Using the "Item icon" in conjunction with the RED and BLU team-colors means we could use already existing images on the Wiki, too. Not that I would have a problem if new images had to be created for the Neutral-Colored weapons, but, I still think that using the Item icons would highly benefit here, since how nice they look on weapons.
  
Looking through certain character's weapon lists (eg. Demoman + Pyro's melee slot), it is very messy when you consider that half of the weapons are identical (Eyelander = HHHT = Nessie's 9 Iron, Bottle = Frying Pan = Saxxy etc.). For example, the demoman's melee page:
+
:::::However, if we go with a RED and BLU switcher, what we could perhaps do is team-colored Item icons, yeah that would be awesome. Not only that, but we also have Item icons for Australiums, and, I even made Australium Festivized icons for TF2B a while ago, that is only used there and not on the Wiki, at the moment.
  
{| class="wikitable grid" width="100%"
+
:::::GrampaSwood 6) Yeah, I didn't think of this, but using Tabs on the Gallery would be pretty good, something we already do in Tournament Medal pages, actually.
! class="header" width="10%" | Weapon
+
 
! class="header" width="5%"  | Kill Icon
+
:::::GrampaSwood, Andrew360, Profiteer 7) While I can't promise I will be on the Wiki forever, and, with my statement on my userpage being correct (that I won't be as active in 2024), making BLU team-colored variants on "Standalone" models is a faster process than when making when loaded as a "weapon" (e.g.: Cosmetic loaded on a player model). The reason I did all the [[Boarder's Beanie]] paint variants is solely because it's a standalone model, I was able to generate the paint variants very quickly (and in high quality and proper colors). I can still do every single style and class on BLU as well, for the Single Color paint variants, for the Beanies, I just haven't done since we are still discussing this.
! class="header" width="7%" | Ammo<br/>Loaded
+
 
! class="header" width="5%"  | Ammo<br/>Carried
+
:::::My Laptop is currently not being used. I have thought of the idea of making an HLMV machine, and letting paint variants being made while I do other things. This is something I thought about in the past, but I would require another monitor (which I can buy, no problem), but I also would need time, something I will not have that much starting 2024. However, I'm also in the point where I feel like I have contributed quite a lot for the Wiki already, so I'm kinda conflicted if I should really do this or not. I would only require to re-install Windows, re-configure HLMV (which can be painful), and things like that, before I can make it an idle HLMV machine that makes paint variants.
! class="header" width="10%" | Damage Range
+
 
! class="header" width="30%" | Notes / Special Abilities
+
:::::ShadowMan44 7) Correct, currently, the "Painted variants full" template states that mouse-hovered "Single colors" states that "due to how the cosmetic's textures are set up, it changes colors between teams". This would require to be changed appropriately, somehow, though I don't think that yet another Painted variants template should be made. It should be possible to just add a parameter of some sort.
|-
+
 
! {{Table icon|Bottle|Stock}}
+
:::::Gabrielwoj, Andrew360 5) Despite me suggesting this, I was also not too sure about it, but I decided to post it as a matter of discussion. In most cases, Styles just change the look of an item, without changing the placement of the model, or the model itself. In some other cases, however, it does change something [[Liquor Locker]], [[Pocket-Medes]], etc. While it would be an interesting idea, and I do have a couple cosmetics with all styles made already, most of the rest would require to be remade. This could also be a little difficult for regular HLMV users, as refreshing the model viewer gets rid of the facial flex entirely, but not on HLMV++. While you can unload and load submodels without having to refresh, HLMV does read from "$color2" instead of "$colortint_base", which means if someone forgets about that on an older cosmetic, they'd need to refresh after fixing it from the .vmt.
| align="center" | {{Icon killicon|weapon=Bottle}}
+
 
| N/A
+
:::::Profiteer 9) That's a good point. I guess if the Styles section was more populated (actually shows differences between classes), then I suppose that items like [[Manndatory Attire]] and [[Boarder's Beanie]] wouldn't require that huge amount of styles being shown on the table. But then, there's another problem. Items already show their unpainted RED and BLU variants on the infobox, and how exactly could we categorize "exceptions" to be only on the Styles section if we follow your idea?
| N/A
 
| '''Base''': 65
 
'''[[Crit]]''': 195
 
|
 
{{Info}}The Bottle will break upon a successful Critical hit (purely cosmetic feature).
 
|-
 
! {{Table icon|Eyelander|Unlock}}
 
| align="center" | {{Icon killicon|weapon=Eyelander}}
 
| N/A
 
| N/A
 
| '''Base''': 65
 
'''[[Crit]]''': 195
 
|
 
{{Pro}}Has 37% longer melee range.
 
  
{{Pro}}Every killing blow decapitates the enemy, increasing its head counter. Every head taken raises user's speed (7.5%) and health points (15) to a maximum of 4 times each life.
+
:::::ShadowMan44 9) I'm not quite sure if I understood what you said. The styles table on both the Style section and infobox use the same exact images, same files, with some exceptions like the [[Dead of Night]] and [[Pocket-Medes]]. This is why I mentioned it being redundant, because in most cases, both sections use the same images. [[File:User Gabrielwoj Signature Icon.png|15px|Headphones style when?|link=User:Gabrielwoj]] - [[File:User Gabrielwoj Signature 1.png|link=User:Gabrielwoj]] ▪ [[File:User Gabrielwoj Signature 2.png|link=Special:Contribs/Gabrielwoj]] - [[File:User Gabrielwoj Signature 3.png|link=User talk:Gabrielwoj]] 11:21, 30 December 2023 (UTC)
  
{{Con}}Lowers maximum health by 25 points.
+
::::::So [[User:Tekinz|Tekinz]] and [[User:Mgpt|Mgpt]] talked with me via Steam and Discord DMs, and I'd like to post their opinions on this. Tekinz asked me to post on my behalf, explaining what he told me instead of directly quoting him, while mgpt allowed me to directly translate what he told me. With that said, here's what they had to say:
  
{{Con}}No random Critical hits.
+
::::::Tekinz: He told me that he agrees with most of my proposed update and changes, while pin-pointing some specific numbers with further explanation. He adds that for "7)", it would be a huge amount of work, and we would need quite a few active image creators to be able to achieve it in a timely manner, but otherwise it would be a general improvement to the pages. On "8)", he adds that he has no real problems with and thinks it's pretty good, mentioning that if combined with "1)", it would look great. On "9)", he mentioned that it's probably a good idea considering how the Styles section is located pretty far on the page and that it would probably be better to have them focused to the infobox since it's much closer to the top, alongside the rest of relevant images. He further adds that the Styles section always seemed not as important since it was too close to the Trivia and Patch Notes, while also being beneath the huge Painted Variants table that overshadows it.
|-
 
! {{Table icon|Pain Train|Craft}}
 
| align="center" | {{Icon killicon|weapon=Pain Train}}
 
| N/A
 
| N/A
 
| '''Base''': 65
 
'''[[Crit]]''': 195
 
|
 
{{Pro}}Doubles capture power for points and carts.
 
  
{{Con}}Raises bullet vulnerability by 10%.
+
::::::mgpt:
|-
+
::::::{{c|+|Agree}} 1. Everything looks okay to me, if it's easy to implement;
! {{Table icon|Scotsman's Skullcutter|Craft}}
+
::::::{{c|+|Agree}} 2. I did take a look on some weapons, and I agree in using "Item icons";
| align="center" | {{Icon killicon|weapon=Scotsman's Skullcutter}}
+
::::::{{c|+|Agree}} 3. I saw the comments, and Andrew360's idea, and I agree, it has my vote;
| N/A
+
::::::{{c|+|Agree}} 4. You got my vote, very good;
| N/A
+
::::::{{c|-|Disagree}} 5. I agree with Andrew360 and Profiteer, I don't think that it's worth the work, considering there's already images below on the infobox, alongside the painted variants;
| '''Base''': 78
+
::::::{{c|Info}} 6. It ends up being the same as "5)", however, I'd like to see an example how it would look like;
'''[[Crit]]''': 234
+
::::::{{c|+|Agree}} 7. I'm not sure if I noticed completely, but would that be switching the template from "Painted variants" to "Painted variants full" In several cosmetics, like how it was done in [[Brigade Helm]]? If so, I don't see a problem;
|  
+
::::::{{c|Info}} 7. An idea to the template. Wouldn't it look better if it was something like this, with 2 buttons? [https://i.imgur.com/LVXXb4C https://i.imgur.com/LVXXb4C] Or is it being done currently like it's on the page so it's possible to compare both teams at the same time? Probably that;
{{Pro}}Has 37% longer melee range.
+
::::::{{c|+|Agree}} 8. I like the idea, however, the information still continue to be too deep on the page, wouldn't be better to only show 4 or 5, instead of 9?;
 +
::::::{{c|Info}} 9. a) "An arrange of buttons that lets you change classes on the Styles table". In the example of [[Beaten and Bruised]], the images wouldn't be anymore on the infobox, correct?;
 +
::::::{{c|Info}} I like "8)"'s idea, but if "9)" is applied, then number "8)" is discarded. [[File:User Gabrielwoj Signature Icon.png|15px|Headphones style when?|link=User:Gabrielwoj]] - [[File:User Gabrielwoj Signature 1.png|link=User:Gabrielwoj]] ▪ [[File:User Gabrielwoj Signature 2.png|link=Special:Contribs/Gabrielwoj]] - [[File:User Gabrielwoj Signature 3.png|link=User talk:Gabrielwoj]] 12:16, 3 January 2024 (UTC)
  
{{Pro}}Deals 20% more damage.
+
:::::::I also replied to mgpt regarding some of his questions, so I had the following to say:
 +
:::::::7) On number "7)", it would be including previews like how it's done on "Single Color" paint cans on the BLU team, even if when they are applied on the same area, the paint color looks identical to the RED team. Currently, we only use "Painted variants full" in cases of items that has different colorization between teams, such as the case of [[Stout Shako]];
 +
:::::::7. a) I liked the idea of including RED and BLU on the top, it would be very intuitive. '''Post-thoughts:''' After re-reading his thoughts on this one, I saw that the original idea would be buttons, while I first thought they were simply two sections that would separate the teams more properly, visually. I thought if maybe that by doing so, we could include a faint red and a faint blue background to separate them both, and make the template a little more nice to look at, as currently there's a bunch of paint variants all included in one table.
 +
:::::::8) In regards to the default quantity, it would still be discussed, but the main idea would be something that could be expanded to show the remaining. I finished the [[Boarder's Beanie]] images, and the infobox ended up being very lengthy. The table for Painted variants will probably change if "4)" is implemented.
 +
:::::::9) The images would still stay on the infobox section, but the idea would be that on the Styles table, it would include an array of buttons with each of the classes icons, so it could be changed, similar to what it has been suggested on "4)". The only thing that, if "1)" is implemented, the Styles section may not be as necessary anymore. [[File:User Gabrielwoj Signature Icon.png|15px|Headphones style when?|link=User:Gabrielwoj]] - [[File:User Gabrielwoj Signature 1.png|link=User:Gabrielwoj]] ▪ [[File:User Gabrielwoj Signature 2.png|link=Special:Contribs/Gabrielwoj]] - [[File:User Gabrielwoj Signature 3.png|link=User talk:Gabrielwoj]] 12:16, 3 January 2024 (UTC)
  
{{Con}}Lowers speed by 15% on wearer.
+
{{Outdent|7}} 1 {{c|?|Not sure}} It sure would be easy to implement but I feel this would discount the usefulness of the class gallery or style section.<br>
 +
2/3 {{c|+|Agree}} It would clean up the inconsistencies from the 2D weapon images and make them extremely consistent. The item icons are used all over the wiki in subtle ways such as in crafting recipes or in big lists of weapons but it's time for those to be the defacto 2D image for weapons. Bring Shugo-style to the infobox!<br>
 +
4 {{c|+|Agree}} Adding the class icons in place of the class name plus sorting the paint table by class would greatly improve the user experience. (I always stress when uploading paint galleries with multiple styles that I may upload to the incorrect style/class)<br>
 +
5 {{c|-|Disagree}} On top of remaking all the infobox images being an immense amount of work, I feel this would also take away from the usefulness of the style box.<br>
 +
6 {{c|?|Not sure}} I would be more open to this than #5 but I often find that the class gallery images often take me the most time to complete and be happy with. Trying to find good and unique poses and appropriate facial flexes for all 9 classes takes me a fair amount of time. I wish I was faster at it.<br>
 +
7 {{c|?|Not sure}} I kind of agree on this point but I feel it could just be on a cosmetic-by-cosmetic basis. Like we do now, I think, we could only implement this on hats that would benefit from a full paint gallery.<br>
 +
8 {{c|+|Agree}} I agree with the others on this point, {{tl|Tabs}} would be great for this. I am more for moving the class styles out of the infobox and moving them to the style box. I feel more and more pages suffer from having a long infobox with the inclusion of more all-class, multi-style hats. If they were moved to the style box with tabs, I think many pages would look a whole lot cleaner and compact.<br>
 +
9 {{c|-|Disagree}} See #8<br>
 +
[[User:H20verdrive|H20verdrive]] ([[User talk:H20verdrive|talk]]) 01:22, 7 January 2024 (UTC)
 +
:I've been mildly intimidated, procrastinating voting on this for a week, but here we go:
 +
:1. {{c|+|Agree}} Very good stuff.
 +
:2. {{c|?|Abstain}} Not sure about this, it might seem awkward on some items. Like others have said I'd want to see it first.
 +
:3. {{c|+|Weak Agree}} Seems necessary, but I wonder if there's a more cohesive way to display them.
 +
:4. {{c|+|Agree}} Looks nice, more visual and less clutter.
 +
:5. {{c|+|Weak Agree}} Seems alright.
 +
:6. {{c|?|Abstain}} It seems a bit clunky and as someone said, might take a lot of work, but theoretically seems useful.
 +
:7. {{c|+|Weak Agree}} As H20verdrive said, probably an item-by-item basis (maybe a "limited run" at first for the articles that need it most?) is best.
 +
:8. {{c|+|Agree}} Looks cool; long infoboxes do need help, but I think it's most contingent upon all-class items.
 +
:9. {{c|-|Weak Disagree}} As all others said, this needs tweaking and removing Styles might be too radical, BUT the "arrange of buttons" might work.
 +
:Overall, if I had to give a vote for the ''whole package'', {{c|+|Agree, with tweaking}}.--[[File:Leaderboard class allclass.png|15px|link=]] [[User:Akolyth|<span style="font-size: 14px; font-family: Trebuchet MS">'''Akolyth'''</span>]] ([[User_talk:Akolyth|talk]]) 02:21, 10 January 2024 (UTC)
 +
::Well, we got a lot of responses with this discussion, thank you everyone for reading and replying. I guess we could start making some of these proposed changes? Ones that got the most positive votes, while discarding ones that didn't get much positive reception. Perhaps let's talk what should be the best options according to your guys voting. I don't have time to actually write up new template codes and stuff at the moment, however some already have templates available for that (#7), and others should be a little more straightforward in changing (I would imagine that including the Shugo style icons for weapons be quite straightforward, if that would go through). [[File:User Gabrielwoj Signature Icon.png|15px|Headphones style when?|link=User:Gabrielwoj]] - [[File:User Gabrielwoj Signature 1.png|link=User:Gabrielwoj]] ▪ [[File:User Gabrielwoj Signature 2.png|link=Special:Contribs/Gabrielwoj]] - [[File:User Gabrielwoj Signature 3.png|link=User talk:Gabrielwoj]] 00:26, 27 January 2024 (UTC)
 +
:::Swood suggested me to make a table having total votes from everyone:
 +
{| class="wikitable"
 +
|-
 +
| Suggestion 1 || {{c|+|Agree}}: '''7''' || {{c|-|Disagree}}: '''1''' || {{c|?|Abstain}}: '''2'''
 +
|-
 +
| Suggestion 2 || {{c|+|Agree}}: '''7''' || {{c|-|Disagree}}: '''0''' || {{c|?|Abstain}}: '''1'''
 +
|-
 +
| Suggestion 3 || {{c|+|Agree}}: '''9''' || {{c|-|Disagree}}: '''0''' || {{c|?|Abstain}}: '''1'''
 +
|-
 +
| Suggestion 4 || {{c|+|Agree}}: '''10''' || {{c|-|Disagree}}: '''0''' || {{c|?|Abstain}}: '''0'''
 +
|-
 +
| Suggestion 5 || {{c|+|Agree}}: '''4''' || {{c|-|Disagree}}: '''4''' || {{c|?|Abstain}}: '''2'''
 +
|-
 +
| Suggestion 6 || {{c|+|Agree}}: '''4''' || {{c|-|Disagree}}:  '''1''' || {{c|?|Abstain}}: '''4'''
 
|-
 
|-
! {{Table icon|Frying Pan|Promotional}}
+
| Suggestion 7 || {{c|+|Agree}}: '''8''' || {{c|-|Disagree}}: '''0''' || {{c|?|Abstain}}: '''1'''
| align="center" | {{Icon killicon|weapon=Frying Pan}}
 
| N/A
 
| N/A
 
| '''Base''': 65
 
'''[[Crit]]''': 195
 
|  
 
{{Info}}Same as the [[Bottle]]'s attributes.
 
 
|-
 
|-
! {{Table icon|Horseless Headless Horsemann's Headtaker|Craft}}
+
| Suggestion 8 || {{c|+|Agree}}: '''8''' || {{c|-|Disagree}}: '''1''' || {{c|?|Abstain}}: '''2'''
| align="center" | {{Icon killicon|weapon=Horseless Headless Horsemann's Headtaker}}
 
| N/A
 
| N/A
 
| '''Base''': 65
 
'''[[Crit]]''': 195
 
| <small>[[Halloween]] item.</small>
 
{{Info}}Same as the [[Eyelander]]'s attributes.
 
 
|-
 
|-
! {{Table icon|Claidheamh Mòr|Craft}}
+
| Suggestion 9 || {{c|+|Agree}}: '''2''' || {{c|-|Disagree}}: '''3''' || {{c|?|Abstain}}: '''4'''
| align="center" | {{Icon killicon|weapon=claidheamohmor}}
+
|}
| N/A
+
My own votings have been included too. I agree with all of the changes I proposed except "5)", which I only suggested since I already had some Style images laying around on my computer, ready to be uploaded if it were to be accepted. [[File:User Gabrielwoj Signature Icon.png|15px|Headphones style when?|link=User:Gabrielwoj]] - [[File:User Gabrielwoj Signature 1.png|link=User:Gabrielwoj]] ▪ [[File:User Gabrielwoj Signature 2.png|link=Special:Contribs/Gabrielwoj]] - [[File:User Gabrielwoj Signature 3.png|link=User talk:Gabrielwoj]] 17:49, 31 January 2024 (UTC)
| N/A
+
 
| '''Base''': 65
+
== Userbox, and creator page ==
'''[[Crit]]''': 195
+
 
|  
+
Hey! I have a question, how i add userbox and how i add some decoration to my page like evryone did ? [[User:Nonolemage|Nonolemage]] ([[User talk:Nonolemage|talk]]) 13:21, 8 January 2024 (UTC)
{{Pro}}Has 37% longer melee range.
+
 
 +
:For userboxes see [[Team Fortress Wiki:User info boxes]]. Otherwise, the rest of the decoration is up to you. You may be interested in {{tl|User infobox}}.<br>[[File:BLU Wiki Cap.png|20px|link=List of Wiki Cap owners]] | [[Help:Group rights|<span style="color:green;font-family:TF2 Build;">s</span>]] | [[User:GrampaSwood|<font color="DB9C1F">GrampaSwood</font>]] [[File:PraisetheSun.png|20px|alt=Praise the Sun!]] ([[User talk:GrampaSwood|<font color="DB9C1F">talk</font>]]) ([[Special:Contributions/GrampaSwood|<font color="DB9C1F">contribs</font>]]) 13:27, 8 January 2024 (UTC)
 +
 
 +
::Thanks for the info box ! But how exactly i decorate my page ? Like how i use custom image or something like thats ? Did you have a page thats can help me to do this ?[[User:Nonolemage|Nonolemage]] ([[User talk:Nonolemage|talk]]) 13:59, 9 January 2024 (UTC)
 +
 
 +
:::[[Help:Images]] may help you with how to place images, for images to use, simply upload them using [[Special:Upload|the upload page]]. The correct format for images only used on your User page is "User Nonolemage [file name]", so for example "User Nonolemage profile picture.png" or "User Nonolemage scout loadout.jpg". When uploading them on the upload page, include <nowiki>[[Category:User images]]</nowiki> in the summary box. This should be done for every image you want to use on your User page.
 +
 
 +
:::As for more complicated design, that is usually done using CSS and/or Javascript. I can't help you much with that.<br>[[File:BLU Wiki Cap.png|20px|link=List of Wiki Cap owners]] | [[Help:Group rights|<span style="color:green;font-family:TF2 Build;">s</span>]] | [[User:GrampaSwood|<font color="DB9C1F">GrampaSwood</font>]] [[File:PraisetheSun.png|20px|alt=Praise the Sun!]] ([[User talk:GrampaSwood|<font color="DB9C1F">talk</font>]]) ([[Special:Contributions/GrampaSwood|<font color="DB9C1F">contribs</font>]]) 14:08, 9 January 2024 (UTC)
 +
 
 +
::::Thanks you a lot ! You realy helped me ! [[User:Nonolemage|Nonolemage]] ([[User talk:Nonolemage|talk]]) 14:10, 9 January 2024 (UTC)
 +
 
 +
== Civilian Image ==
 +
 
 +
Should we change the image of the [[Civilian]] ? Because it's the scout in A pose but the civilain got some real texture thats can be use and found [[User:Nonolemage|Nonolemage]] ([[User talk:Nonolemage|talk]]) 12:54, 11 January 2024 (UTC)
 +
 
 +
:That is how the Civilian class looked when it was still available in TF2, [[Civilian (Classic)]] is the TFC version.<br>[[File:BLU Wiki Cap.png|20px|link=List of Wiki Cap owners]] | [[Help:Group rights|<span style="color:green;font-family:TF2 Build;">s</span>]] | [[User:GrampaSwood|<font color="DB9C1F">GrampaSwood</font>]] [[File:PraisetheSun.png|20px|alt=Praise the Sun!]] ([[User talk:GrampaSwood|<font color="DB9C1F">talk</font>]]) ([[Special:Contributions/GrampaSwood|<font color="DB9C1F">contribs</font>]]) 12:57, 11 January 2024 (UTC)
 +
 
 +
::Oh, but i play a mod of tf2 (tf2c) thats show a finished model of the civilain so maybe i can add a picture of it in the galery for show what it looked finished ? Or it's not important ?[[User:Nonolemage|Nonolemage]] ([[User talk:Nonolemage|talk]]) 13:04, 11 January 2024 (UTC)
 +
 
 +
:::That's not an official version of it, that's fan-made. No Civilian model or textures has been made for TF2.<br>[[File:BLU Wiki Cap.png|20px|link=List of Wiki Cap owners]] | [[Help:Group rights|<span style="color:green;font-family:TF2 Build;">s</span>]] | [[User:GrampaSwood|<font color="DB9C1F">GrampaSwood</font>]] [[File:PraisetheSun.png|20px|alt=Praise the Sun!]] ([[User talk:GrampaSwood|<font color="DB9C1F">talk</font>]]) ([[Special:Contributions/GrampaSwood|<font color="DB9C1F">contribs</font>]]) 13:11, 11 January 2024 (UTC)
 +
 
 +
== Weapon in user page ==
 +
 
 +
Hey it's AGAIN me ! I see some people have a list of weapon they used for evry class but i don't know how to do this, can someone help me ? [[User:Nonolemage|Nonolemage]] ([[User talk:Nonolemage|talk]]) 07:32, 14 January 2024 (UTC)
 +
 
 +
:Well, you could try learning how to use [https://en.wikipedia.org/wiki/Help:Table wikitables], there are also templates like [[Template:Backpack item]] and [[Template:User weapon checklist]] you could use to this effect.<br><span style="background:#393939;padding:2px 12px;font-family: TF2 Build;font-size: 1em;border-radius: 10px 10px 10px 10px;">[[User:Luno|Luno]] <span style="color:#FC0;letter-spacing:-2px">🪐🌕</span> [[User talk:Luno|<span style="color:#fff">Talk</span>]] <span style="color:#559655;letter-spacing:-2px">/</span> [[Special:Contributions/Luno|<span style="color:#fff">Contributions</span>]] <span style="color:#538AC5;letter-spacing:-2px">/</span> [[Team_Fortress_Wiki:Translation_progress/fr|<span style="color:#4d748b">T</span><span style="color:#fff">ea</span><span style="color:#ab4848">m</span>]]</span> 03:20, 15 January 2024 (UTC)
 +
 
 +
== Allweapons Nav template ==
 +
 
 +
Hi! I've created two mockups as potential replacements for the current [[Template:Allweapons Nav|Allweapons Nav]] template. I'd like to get your opinion. You can check out the templates on [[User:Mgpt/Sandbox#Test|my sandbox user page]] ('''Nav 1''' and '''Nav 2'''). The "Secondary" label for "All classes" in '''Nav 2''' appears a bit off, and I'm having trouble fixing it. Thanks! [[User:Mgpt|Mgpt]] ([[User talk:Mgpt|talk]]) 02:59, 16 January 2024 (UTC)
 +
 
 +
:I don't really see what's wrong with the current one.<br>[[File:BLU Wiki Cap.png|20px|link=List of Wiki Cap owners]] | [[Help:Group rights|<span style="color:green;font-family:TF2 Build;">s</span>]] | [[User:GrampaSwood|<font color="DB9C1F">GrampaSwood</font>]] [[File:PraisetheSun.png|20px|alt=Praise the Sun!]] ([[User talk:GrampaSwood|<font color="DB9C1F">talk</font>]]) ([[Special:Contributions/GrampaSwood|<font color="DB9C1F">contribs</font>]]) 11:59, 16 January 2024 (UTC)
 +
:: Outdated/It's not a "real" nav like the others (Hat/Tool Nav). If someone else comments please compare both so you can see the differences [[User:Mgpt|Mgpt]] ([[User talk:Mgpt|talk]]) 16:05, 16 January 2024 (UTC)
  
{{Pro}}Charge duration is increased by 0.5 second.
+
:::I did compare both, but it doesn't exactly answer what's wrong with the current one. If people really wanted it changed I'd go for Nav 1, but I would still like to see stock and non-stock separated.<br>[[File:BLU Wiki Cap.png|20px|link=List of Wiki Cap owners]] | [[Help:Group rights|<span style="color:green;font-family:TF2 Build;">s</span>]] | [[User:GrampaSwood|<font color="DB9C1F">GrampaSwood</font>]] [[File:PraisetheSun.png|20px|alt=Praise the Sun!]] ([[User talk:GrampaSwood|<font color="DB9C1F">talk</font>]]) ([[Special:Contributions/GrampaSwood|<font color="DB9C1F">contribs</font>]]) 16:16, 16 January 2024 (UTC)
 +
::::There's already a nav for them on the weapon page and stock is always the first (they can be in italic, would that work?). I personally prefer Nav 2 because it is actually a nav (not a table) but also consistent with Hat and Tool Nav. Edit: About the availability strings, they shouldn't be there, especially because they're outdated and were added more than 10 years ago. Definitely not the purpose of the template. [[User:Mgpt|Mgpt]] ([[User talk:Mgpt|talk]]) 20:11, 16 January 2024 (UTC)
  
{{Con}}Decreases max health by 15.
+
:::::I'd prefer for them to be separated regardless, if only in a little box above all of them or with a line separating them. Both the current one and both your versions are technically tables either way, I think a differently structured nav doesn't necessarily make it not a nav or somehow inferior.<br>[[File:BLU Wiki Cap.png|20px|link=List of Wiki Cap owners]] | [[Help:Group rights|<span style="color:green;font-family:TF2 Build;">s</span>]] | [[User:GrampaSwood|<font color="DB9C1F">GrampaSwood</font>]] [[File:PraisetheSun.png|20px|alt=Praise the Sun!]] ([[User talk:GrampaSwood|<font color="DB9C1F">talk</font>]]) ([[Special:Contributions/GrampaSwood|<font color="DB9C1F">contribs</font>]]) 20:39, 16 January 2024 (UTC)
  
{{Con}}No random Critical hits.
+
{{outdent|5}} Personally, I prefer Nav 1. I like the structure of the current Weapon Nav the way it is, I just don't like the availability strings cluttering things up, and the taunts needlessly listing which weapons they're for. Nav 1 simplifies things in a way that's easier to read, certainly. I'd also be fine with Stock weapons being separated, perhaps with a "Stock" header and then a line break before the others.  
|-
 
! rowspan="2" | {{Table icon|Ullapool Caber|Craft}}
 
| align="center" | {{Icon killicon|weapon=ullapool caber}}
 
| rowspan="2" | N/A
 
| rowspan="2" | N/A
 
| rowspan="2" | '''Base''': {{tooltip|35|Melee damage}} + {{Tooltip|149|Explosive damage}} <sup>1</sup>
 
'''[[Crit]]''': {{tooltip|105|Melee damage}} + {{Tooltip|300|Explosive damage}} <sup>1</sup>
 
| rowspan="2" |
 
{{Info}}On hit the grenade's 'head' will explode dealing melee damage to the enemy and explosive damage to the user and all enemies around him. The explosion can be triggered also by hitting solid parts of the map and will launch the user upward. Afterwards, it will show signs of damage and will be able to deal only the melee damage and won't explode again until the user respawns or visits a resupply cabinet.
 
  
{{Con}}No random Critical hits.
+
Incidentally, re: "the 'Secondary' label for 'All classes' in Nav 2 appears a bit off, and I'm having trouble fixing it."
|-
+
* That should be a "Melee" label, as you've probably realized by now.
| align="center" |  {{Icon killicon|weapon=ullapool caber explode}}
+
* It's looking off because the single list of weapons you've used isn't enough to fill out the space of the column. You'd need at least three lists to fill out the space that the "All Classes" column takes, so the single list you gave sits in the middle. — [[File:User ThatHatGuy Signature Icon.png|30px|link=User:ThatHatGuy]] 10:21, 17 January 2024 (UTC)
|-
+
: I made some changes, thanks for the input [[User:Mgpt|Mgpt]] ([[User talk:Mgpt|talk]]) 03:18, 18 January 2024 (UTC)
! {{Table icon|Half-Zatoichi|Promotional / Craft}}
 
| align="center" | {{Icon killicon|weapon=half-zatoichi}}
 
| N/A
 
| N/A
 
| '''Base''': 65
 
'''[[Crit]]''': 195
 
|
 
{{Pro}}On kill, restores the player to full health.
 
  
{{Con}}This weapon is Honorbound and once drawn cannot be sheathed until it kills.
+
:: Nav 1 seems almost set to me, I like the Normal quality grey indication, while still being separated by slot. My only slight nitpick now would be that I'd prefer if the non-stock weapons were organized by release order -- at the moment, reskins of stock are still at the top of the non-stock section, which doesn't make ''as much'' sense, now that we've agreed on separating stock into its own box. — [[File:User ThatHatGuy Signature Icon.png|30px|link=User:ThatHatGuy]] 03:33, 18 January 2024 (UTC)
 +
::: I initially added them randomly from the Weapons page, but I'll definitely reorganize them by release order :D I may scrap the all class section, the idea was not to repeat weapons, but we have the Shotgun, so... [[User:Mgpt|Mgpt]] ([[User talk:Mgpt|talk]]) 03:45, 18 January 2024 (UTC)
 +
:::: Updated the template [[User:Mgpt|Mgpt]] ([[User talk:Mgpt|talk]]) 19:01, 22 January 2024 (UTC)
  
{{Info}}A single successful hit will kill an enemy wielding the same weapon.
+
== About the 2023 leak ==
  
|-
+
Hello ! Im a translator of the unused content and i see on the social media a leak from 2023 of some map and iteam thats has been abandoned or unfinished. So i was thinking if i can work on it for make some page on the unused content section. (The leak is from a valve employer) [[User:Nonolemage|Nonolemage]] ([[User talk:Nonolemage|talk]]) 15:52, 22 January 2024 (UTC)
! {{Table icon|Saxxy|Distributed}}
 
| align="center" | {{Icon killicon|weapon=saxxy}}
 
| N/A
 
| N/A
 
| '''Base''': 65
 
'''[[Crit]]''': 195
 
|
 
<small>Limited item from the [[Replay Update]].</small><br />
 
{{Info}}Killed enemies freeze into solid [[Australium]] statues (purely cosmetic feature).
 
|-
 
! {{Table icon|Persian Persuader|Craft}}
 
| align="center" | {{Icon killicon|weapon=Persian Persuader}}
 
| N/A
 
| N/A
 
| '''Base''': 65
 
'''[[Crit]]''': 195
 
|
 
{{Pro}}Halves the time required to recharge a charge.
 
  
{{Con}}No random Critical hits.
+
:As long as you source all of these changes and abide by the [[Team Fortress Wiki:Policies#Leaked content|leaked content policy]]. This leak was also not from a Valve employee, as far as I know.<br>[[File:BLU Wiki Cap.png|20px|link=List of Wiki Cap owners]] | [[Help:Group rights|<span style="color:green;font-family:TF2 Build;">s</span>]] | [[User:GrampaSwood|<font color="DB9C1F">GrampaSwood</font>]] [[File:PraisetheSun.png|20px|alt=Praise the Sun!]] ([[User talk:GrampaSwood|<font color="DB9C1F">talk</font>]]) ([[Special:Contributions/GrampaSwood|<font color="DB9C1F">contribs</font>]]) 15:57, 22 January 2024 (UTC)
  
{{Info}}All ammo collected converts into health.
+
::So if i understand, i donnt have the right to put any picture of anything if it's from a leak ? And by the way, how did the code for cited content from leak work ? And if it's not from a valve employer, from who it's from ? (Sorry for all my question and thanks for anwsering me ;-;) [[User:Nonolemage|Nonolemage]] ([[User talk:Nonolemage|talk]]) 16:08, 22 January 2024 (UTC)
|-
 
! {{Table icon|Nessie's Nine Iron|Craft}}
 
| align="center" | {{Icon killicon|weapon=Nessie's Nine Iron}}
 
| N/A
 
| N/A
 
| '''Base''': 65
 
'''[[Crit]]''': 195
 
|
 
{{Info}}Same as the [[Eyelander]]'s attributes.
 
|}
 
  
 +
:::Don't link to any places that host leaked content (so do not link to a Tweet containing a picture of a leaked model, or containing a link to a Google Drive with the leaked content, etc.), do not directly upload media of leaked content or copy-paste code, and do not link to or upload media of recreations of leaked content. All the information you put on the page should contain a reference to where you got it from (see the examples on the policy). It's likely someone with a Source engine license that leaked everything.<br>[[File:BLU Wiki Cap.png|20px|link=List of Wiki Cap owners]] | [[Help:Group rights|<span style="color:green;font-family:TF2 Build;">s</span>]] | [[User:GrampaSwood|<font color="DB9C1F">GrampaSwood</font>]] [[File:PraisetheSun.png|20px|alt=Praise the Sun!]] ([[User talk:GrampaSwood|<font color="DB9C1F">talk</font>]]) ([[Special:Contributions/GrampaSwood|<font color="DB9C1F">contribs</font>]]) 16:19, 22 January 2024 (UTC)
  
The line "Same as the ....'s attributes." is not very uncommon. It is obvious that there are clones, and thus I don't think that they should be treated as different objects, especially when treating them as the same causes visual clutter and, in my opinion, makes suggestions that aren't applicable. In combat of this, I propose something like this:
+
::::I understand, thanks a lot for your help again and i will do evrything you say ! [[User:Nonolemage|Nonolemage]] ([[User talk:Nonolemage|talk]]) 16:38, 22 January 2024 (UTC)
  
 +
== [[Template:Community Medal Nav|Community Medal Nav]] (closed) ==
  
{| class="wikitable grid" width="100%"
+
I feel a bit lost with the medal scheme and how it has been handled. Where exactly is this template supposed to be used? I know that {{tl|Hat Nav}} lists the same contents, which I recently updated. I think we should either use this one and remove the medal section from Hat Nav or just use Hat Nav, no? Thanks in advance [[User:Mgpt|Mgpt]] ([[User talk:Mgpt|talk]]) 21:28, 24 January 2024 (UTC)
! class="header" width="10%" | Weapon
 
! class="header" width="5%"  | Kill Icon
 
! class="header" width="7%" | Ammo<br/>Loaded
 
! class="header" width="5%"  | Ammo<br/>Carried
 
! class="header" width="10%" | Damage Range
 
! class="header" width="30%" | Notes / Special Abilities
 
|-
 
! {{Table icon|Bottle|Stock}}
 
| align="center" | {{Icon killicon|weapon=Bottle}}
 
| rowspan="3"  align="center" | N/A
 
| rowspan="3"  align="center" | N/A
 
| rowspan="3" | '''Base''': 65
 
'''[[Crit]]''': 195
 
| rowspan="2" |
 
{{Info}}The Bottle will break upon a successful Critical hit (purely cosmetic feature).
 
|-
 
! {{Table icon|Frying Pan|Promotional}}
 
| align="center" | {{Icon killicon|weapon=Frying Pan}}
 
|-
 
! {{Table icon|Saxxy|Distributed}}
 
| align="center" | {{Icon killicon|weapon=saxxy}}
 
|
 
<small>Limited item from the [[Replay Update]].</small><br />
 
{{Info}}Killed enemies freeze into solid [[Australium]] statues (purely cosmetic feature).
 
|-
 
! {{Table icon|Eyelander|Unlock}}
 
| align="center" | {{Icon killicon|weapon=Eyelander}}
 
| rowspan="3" align="center"| N/A
 
| rowspan="3" align="center"| N/A
 
| rowspan="3" | '''Base''': 65
 
'''[[Crit]]''': 195
 
| rowspan="3" |
 
{{Pro}}Has 37% longer melee range.
 
  
{{Pro}}Every killing blow decapitates the enemy, increasing its head counter. Every head taken raises user's speed (7.5%) and health points (15) to a maximum of 4 times each life.
+
:With the ever-increasing MvM medals, we should remove it from the Hat Nav and keep this one. The Hat Nav will cause pages to be too large at some point.<br>[[File:BLU Wiki Cap.png|20px|link=List of Wiki Cap owners]] | [[Help:Group rights|<span style="color:green;font-family:TF2 Build;">s</span>]] | [[User:GrampaSwood|<font color="DB9C1F">GrampaSwood</font>]] [[File:PraisetheSun.png|20px|alt=Praise the Sun!]] ([[User talk:GrampaSwood|<font color="DB9C1F">talk</font>]]) ([[Special:Contributions/GrampaSwood|<font color="DB9C1F">contribs</font>]]) 21:29, 24 January 2024 (UTC)
 +
:: Would adding an [https://i.imgur.com/XeBjHCT.png 'Other' section with two links] for Community and Tournament medals work then? With this approach, we also need to update the "[[Template:Competitive Nav|Competitive play]]" Nav. Also, both templates use images, is there a specific reason for that?
 +
:: Edit: They're also cosmetic items, so they should still be mentioned, in my opinion [[User:Mgpt|Mgpt]] ([[User talk:Mgpt|talk]]) 21:40, 24 January 2024 (UTC)
  
{{Con}}Lowers maximum health by 25 points.
+
:::I would put the 2 links in the hat nav, then keep the medal nav separately. The comp nav can get rid of it imo, and just having a tournament medal link. I prefer having this separate one.<br>[[File:BLU Wiki Cap.png|20px|link=List of Wiki Cap owners]] | [[Help:Group rights|<span style="color:green;font-family:TF2 Build;">s</span>]] | [[User:GrampaSwood|<font color="DB9C1F">GrampaSwood</font>]] [[File:PraisetheSun.png|20px|alt=Praise the Sun!]] ([[User talk:GrampaSwood|<font color="DB9C1F">talk</font>]]) ([[Special:Contributions/GrampaSwood|<font color="DB9C1F">contribs</font>]]) 22:07, 24 January 2024 (UTC)
  
{{Con}}No random Critical hits.
+
:::: I like the template, but it's too big. We don't need images for all the medals: they are exactly the same and this won't scale well if Valve ever allows new medals again (see comp nav). — [[User:Tark|<span style="font-weight:bold;color: #5BC236">Tark</span>]] 00:16, 25 January 2024 (UTC)
|-
 
! {{Table icon|Horseless Headless Horsemann's Headtaker|Craft}}<sup>1<sup>
 
| align="center" | {{Icon killicon|weapon=Horseless Headless Horsemann's Headtaker}}
 
|-
 
! {{Table icon|Nessie's Nine Iron|Craft}}
 
| align="center" | {{Icon killicon|weapon=Nessie's Nine Iron}}
 
|-
 
! {{Table icon|Pain Train|Craft}}
 
| align="center" | {{Icon killicon|weapon=Pain Train}}
 
| align="center" |  N/A
 
| align="center" |  N/A
 
| '''Base''': 65
 
'''[[Crit]]''': 195
 
|
 
{{Pro}}Doubles capture power for points and carts.
 
  
{{Con}}Raises bullet vulnerability by 10%.
+
::::: Disagree with "they're exactly the same," they're clearly, almost all of them, not ''exactly'' the same, but I know that my opinions about all this don't matter too much anyhow. I would be fine with listing the names of the medals instead, but then they'd all have the name of the operation over and over again, and it would be very clunky to look at. That's how it was in the promo nav to begin with, and that's what ''I'' wanted to change -- but then, that would require extra name strings that are just "Shimmering Souvenir", for example, and Swood already said that was too much. The images were my way of compromising on that, considering the Competitive nav already did that, but then ''that's'' wrong too, so whatever, I can't do any of this properly. — [[File:User ThatHatGuy Signature Icon.png|30px|link=User:ThatHatGuy]] 03:47, 25 January 2024 (UTC)
|-
 
! {{Table icon|Scotsman's Skullcutter|Craft}}
 
| align="center" | {{Icon killicon|weapon=Scotsman's Skullcutter}}
 
| align="center" |  N/A
 
| align="center" |  N/A
 
| '''Base''': 78
 
'''[[Crit]]''': 234
 
|
 
{{Pro}}Has 37% longer melee range.
 
  
{{Pro}}Deals 20% more damage.
+
:::::: They are all the same just with a unique hex paint the MVM ones have been reused over and over, there is no model difference between them other than the paint, If the medals were "different" they would have unique models to go alongside them, but back on subject, theres so many of these damn things it would be nice to be able to filter them out entirely. <br>[[User:Cheddar|Cheddar]] ([[User talk:Cheddar|talk]]) 13:57, 25 January 2024 (UTC)
  
{{Con}}Lowers speed by 15% on wearer.
+
{{outdent|7}}
|-
+
By "exactly the same", I meant all the MvM medals that share the same model but have a different paint applied. An average user doesn't care if the medal is pink or green, they are way more interested in the model itself. The same applies to the comp nav: we don't have an icon for every season of each tournament, only for different models.<br>
! {{Table icon|Claidheamh Mòr|Craft}}
+
I personally don't see how extra strings are too much and I agree that the icons look way better than whatever is going on with the comp nav template. My point here is that this template currently is too big and has too much repetitive information to work as a navbox.<br>
| align="center" | {{Icon killicon|weapon=claidheamohmor}}
+
Also, I know that it is common for us to get attached to our creations (in this case, the template), but suggested changes to a template are usual business. Please don't take it personally, your opinions always matter. — [[User:Tark|<span style="font-weight:bold;color: #5BC236">Tark</span>]] 14:06, 25 January 2024 (UTC)
| align="center" |  N/A
 
| align="center" |  N/A
 
| '''Base''': 65
 
'''[[Crit]]''': 195
 
|
 
{{Pro}}Has 37% longer melee range.
 
  
{{Pro}}Charge duration is increased by 0.5 second.
+
:If I remember correctly, the "too many strings" were in reference to another nav, where I suggested removing them and replacing them with links to the operation page's rewards section. There were a few medals for each operation with a link to the same section each time. Having too many strings was in reference to the promo nav, not the one we're talking about.<br>[[File:BLU Wiki Cap.png|20px|link=List of Wiki Cap owners]] | [[Help:Group rights|<span style="color:green;font-family:TF2 Build;">s</span>]] | [[User:GrampaSwood|<font color="DB9C1F">GrampaSwood</font>]] [[File:PraisetheSun.png|20px|alt=Praise the Sun!]] ([[User talk:GrampaSwood|<font color="DB9C1F">talk</font>]]) ([[Special:Contributions/GrampaSwood|<font color="DB9C1F">contribs</font>]]) 14:40, 25 January 2024 (UTC)
  
{{Con}}Decreases max health by 15.
+
:: So if it's suddenly not too much trouble to localize different name strings for use within this nav specifically, for reasons I won't pretend to understand, nor do I care to ask about further, I propose that if we absolutely must, we strip the pictures and the paint splats, and in the case of MVM operations, we have the link to the operation, and then within that category, plain-text names of just the medals, stripped of the operation name and years, when necessary. (That is, "Operation Galvanized Gauntlet Bejeweled Bounty 2023" becomes  "Bejeweled Bounty", and so on. Cleaner, easier to read, and you already get that it's supposed to be within that operation.
  
{{Con}}No random Critical hits.
+
:: I ''would'' fight for the pictures, but it's clear that's not about to happen for me, and it's best for me to give it up and take the bullet, like I always have to. I'll believe that my opinions always matter when they start being correct ones to have. — [[File:User ThatHatGuy Signature Icon.png|30px|link=User:ThatHatGuy]] 14:54, 25 January 2024 (UTC)
|-
+
::: ThatHatGuy I'm not against your template creation but I searched a little more and its being used with {{tl|Hat Nav}} so we need to decide which one we gonna use, because currently, they have the same contents. Given the opinions above, I think a more neutral solution would be to move the Hat Nav contents to these two templates, so they stay similar to each other. [[User:Mgpt|Mgpt]] ([[User talk:Mgpt|talk]]) 18:35, 25 January 2024 (UTC)
! rowspan="2" | {{Table icon|Ullapool Caber|Craft}}
 
| align="center" | {{Icon killicon|weapon=ullapool caber}}
 
| rowspan="2"  align="center" | N/A
 
| rowspan="2"  align="center" | N/A
 
| rowspan="2" | '''Base''': {{tooltip|35|Melee damage}} + {{Tooltip|149|Explosive damage}} <sup>2</sup>
 
'''[[Crit]]''': {{tooltip|105|Melee damage}} + {{Tooltip|300|Explosive damage}} <sup>2</sup>
 
| rowspan="2" |
 
{{Info}}On hit the grenade's 'head' will explode dealing melee damage to the enemy and explosive damage to the user and all enemies around him. The explosion can be triggered also by hitting solid parts of the map and will launch the user upward. Afterwards, it will show signs of damage and will be able to deal only the melee damage and won't explode again until the user respawns or visits a resupply cabinet.
 
  
{{Con}}No random Critical hits.
+
:::: That didn't ''matter'' when some of those event pages, for '''years''', had both the Hat Nav and the Promo Nav on them. The Promo Nav, by definition, has the same stuff that's already on the Hat Nav. Community medals used to be listed individually on there too. Now all of a sudden, there's a ''new'' nav, that I made because Swood wanted to separate the Community Medals into their own page, and suddenly, that's something worthy of being dissected and put under a microscope.  
|-
 
| align="center" |  {{Icon killicon|weapon=ullapool caber explode}}
 
|-
 
! {{Table icon|Half-Zatoichi|Promotional / Craft}}
 
| align="center" | {{Icon killicon|weapon=half-zatoichi}}
 
| align="center" |  N/A
 
| align="center" |  N/A
 
| '''Base''': 65
 
'''[[Crit]]''': 195
 
|
 
{{Pro}}On kill, restores the player to full health.
 
  
{{Con}}This weapon is Honorbound and once drawn cannot be sheathed until it kills.
+
:::: Fix it how you all want. I've said my piece about it, but clearly I don't know what I'm doing. — [[File:User ThatHatGuy Signature Icon.png|30px|link=User:ThatHatGuy]] 00:53, 26 January 2024 (UTC)
 +
::::: closed given the recent discussion [[User:Mgpt|Mgpt]] ([[User talk:Mgpt|talk]]) 02:26, 31 January 2024 (UTC)
  
{{Info}}A single successful hit will kill an enemy wielding the same weapon.
+
== Trivias without confirmations ==
  
|-
+
Since recent policy change now requiring trivias to have linked confirmations from contributors, there are still many old items that have trivias based on speculations (especially items made by Valve which can't really be confirmed). What should be done with them? [[File:User Denied signature.jpg|50px|link=User:Denied]] [[User:Denied|Denied]] [[User talk:Denied|(Talk)]] 09:07, 30 January 2024 (UTC)
! {{Table icon|Persian Persuader|Craft}}
+
:Leave them, we'd have to clear out pretty much most trivia sections otherwise. Unless you find proof of the contrary, just leave them.<br>[[File:BLU Wiki Cap.png|20px|link=List of Wiki Cap owners]] | [[Help:Group rights|<span style="color:green;font-family:TF2 Build;">s</span>]] | [[User:GrampaSwood|<font color="DB9C1F">GrampaSwood</font>]] [[File:PraisetheSun.png|20px|alt=Praise the Sun!]] ([[User talk:GrampaSwood|<font color="DB9C1F">talk</font>]]) ([[Special:Contributions/GrampaSwood|<font color="DB9C1F">contribs</font>]]) 11:02, 30 January 2024 (UTC)
| align="center" | {{Icon killicon|weapon=Persian Persuader}}
+
::What about [https://wiki.teamfortress.com/wiki/Crafty_Hair#Trivia this one]? A promo item that directly references a game from said promotion, but trivia is about completly different character. [[File:User Denied signature.jpg|50px|link=User:Denied]] [[User:Denied|Denied]] [[User talk:Denied|(Talk)]] 08:06, 31 January 2024 (UTC)
| align="center" | N/A
+
:::I believe it's a invalid trivia, though changing the name of character and game would be better compare to completely remove the trivia [[User:Profiteer|<font color="8470FF">Profiteer]] the tryhard ([[User talk:Profiteer|talk]]|[[Special:Contributions/Profiteer|contribute]])</font> 08:20, 31 January 2024 (UTC)
| align="center" | N/A
+
::::"It is based on one of the male soldiers' hairstyles in the video game UFO: Enemy Unknown" in the first paragraph. [[File:User Denied signature.jpg|50px|link=User:Denied]] [[User:Denied|Denied]] [[User talk:Denied|(Talk)]] 08:43, 31 January 2024 (UTC)
| '''Base''': 65
+
:::::Yeah my bad, mention it 2 times is kind of surplus just remove it. [[User:Profiteer|<font color="8470FF">Profiteer]] the tryhard ([[User talk:Profiteer|talk]]|[[Special:Contributions/Profiteer|contribute]])</font> 09:03, 31 January 2024 (UTC)
'''[[Crit]]''': 195
 
|
 
{{Pro}}Halves the time required to recharge a charge.
 
  
{{Con}}No random Critical hits.
+
::::::Promo items should have their reference stated in the intro, not Trivia. Feel free to remove, it is possible that the Crafty Hair is modelled after hair that is modelled after said character.<br>[[File:BLU Wiki Cap.png|20px|link=List of Wiki Cap owners]] | [[Help:Group rights|<span style="color:green;font-family:TF2 Build;">s</span>]] | [[User:GrampaSwood|<font color="DB9C1F">GrampaSwood</font>]] [[File:PraisetheSun.png|20px|alt=Praise the Sun!]] ([[User talk:GrampaSwood|<font color="DB9C1F">talk</font>]]) ([[Special:Contributions/GrampaSwood|<font color="DB9C1F">contribs</font>]]) 12:24, 31 January 2024 (UTC)
  
{{Info}}All ammo collected converts into health.
+
== Reports/Missing template translations reporting erroneous data ==
  
|}
+
It seems like a very [[Team_Fortress_Wiki:Reports/Untranslated_templates/fr|handy feature]] (as handy as the entire reports page), and oddly enough, it seems to report the same thing for all languages (34 templates), and according to the quick look I did, none of them report missing translations?<br>
 +
I don't know who would be able to fix this, if it's even broken to begin with, maybe [[User:Darkid|Darkid]]?<br>
 +
Do note that I didn't touch template translating very much in my time here, I looked up the line numbers using Notepad++. <span style="background:#393939;padding:2px 12px;font-family: TF2 Build;font-size: 1em;border-radius: 10px 10px 10px 10px;">[[User:Luno|Luno]] <span style="color:#FC0;letter-spacing:-2px">🪐🌕</span> [[User talk:Luno|<span style="color:#fff">Talk</span>]] <span style="color:#559655;letter-spacing:-2px">/</span> [[Special:Contributions/Luno|<span style="color:#fff">Contributions</span>]] <span style="color:#538AC5;letter-spacing:-2px">/</span> [[Team_Fortress_Wiki:Translation_progress/fr|<span style="color:#4d748b">T</span><span style="color:#fff">ea</span><span style="color:#ab4848">m</span>]]</span> 03:05, 12 February 2024 (UTC)
  
This has practical applications for all classes, particularly the scout, pyro, engineer, soldier and demoman. I realise that the fact that the HHHT has a giant name makes them both look rather unaesthetic. Nevertheless, it is still an improvement.
+
:For the [https://wiki.teamfortress.com/wiki/Template:Overheal_tool first result] it looks like fr is not declared in the {{Translation switching| line which probably leads to it showing up in that report. I'm going to guess it's the same for all the other ones. [[User:Jh34ghu43gu|Jh34ghu43gu]] ([[User talk:Jh34ghu43gu|talk]]) 03:10, 12 February 2024 (UTC)
 +
::I can take a look, thanks for the ping. [[User:Darkid|'''<span style="color: #db9c1f">Darkid</span>''']] « [[User talk:Darkid|<span style="color: #75735F">Talk</span>]] — [[Special:Contributions/Darkid|<span style="color: #BA0000">Contribs</span>]] » 03:10, 12 February 2024 (UTC)
  
The way items would be grouped would be primarily, the unique weapons would be arranged in order of release date. All weapons which fall under the category of "clone" would then be tucked into its position. This point is relatively questionable, as it is understandable for the newest weapons to be at the bottom, regardless of their (non)unique nature. Perhaps initially, new clones start at the bottom before moving into its correct position after a new update.
+
:::Damn, that was as quick as Dustbowl backcap, I sort of expected the "declare thing", but I doubt each of the members would forget to put it in, if that's the issue.
 +
:::I would also expect hundreds of entries with varying results for every lang, not 34. <span style="background:#393939;padding:2px 12px;font-family: TF2 Build;font-size: 1em;border-radius: 10px 10px 10px 10px;">[[User:Luno|Luno]] <span style="color:#FC0;letter-spacing:-2px">🪐🌕</span> [[User talk:Luno|<span style="color:#fff">Talk</span>]] <span style="color:#559655;letter-spacing:-2px">/</span> [[Special:Contributions/Luno|<span style="color:#fff">Contributions</span>]] <span style="color:#538AC5;letter-spacing:-2px">/</span> [[Team_Fortress_Wiki:Translation_progress/fr|<span style="color:#4d748b">T</span><span style="color:#fff">ea</span><span style="color:#ab4848">m</span>]]</span> 03:24, 12 February 2024 (UTC)
 +
::::Hmm, looks like I might've screwed up when I changed the regex on Feb 1st (or at least, page history shows a major diff there). Fixing that now, should be corrected tomorrow. [[User:Darkid|'''<span style="color: #db9c1f">Darkid</span>''']] « [[User talk:Darkid|<span style="color: #75735F">Talk</span>]] — [[Special:Contributions/Darkid|<span style="color: #BA0000">Contribs</span>]] » 03:59, 12 February 2024 (UTC)
 +
:::::+622,418 bytes coming through, seems about right! Looks like it's working again, thanks Darkid. <span style="background:#393939;padding:2px 12px;font-family: TF2 Build;font-size: 1em;border-radius: 10px 10px 10px 10px;">[[User:Luno|Luno]] <span style="color:#FC0;letter-spacing:-2px">🪐🌕</span> [[User talk:Luno|<span style="color:#fff">Talk</span>]] <span style="color:#559655;letter-spacing:-2px">/</span> [[Special:Contributions/Luno|<span style="color:#fff">Contributions</span>]] <span style="color:#538AC5;letter-spacing:-2px">/</span> [[Team_Fortress_Wiki:Translation_progress/fr|<span style="color:#4d748b">T</span><span style="color:#fff">ea</span><span style="color:#ab4848">m</span>]]</span> 01:52, 13 February 2024 (UTC)
  
Obviously, alongside a change like this, questions regarding what really makes an item identical (eg. is the Saxxy the same as the default melee weapon? Is the amputator the same as the bonesaw?) Before moving onto questions like these however, public opinion must be in favour. Start supporting! [[User:DVDV|DVDV]] 00:40, 22 August 2011 (PDT)
+
== A technical request for "Used by" template ==
  
By the way, if this goes ahead, I want to implement it. I want a hat :P [[User:DVDV|DVDV]] 01:42, 22 August 2011 (PDT)
+
"Localized versions of this template are not necessary." Well, they actually are needed, due to inflection of words in some languages. For Polish, "<nowiki>{{Used by|all}}</nowiki>" and "<nowiki>{{Used by|Soldier|etc.}}</nowiki>" sound fine, but "<nowiki>{{Used by|all-except|</nowiki>" needs translation switching, as it sounds very bad when names of classes are not inflected. I don't know about other languages, but some may require it too. For Polish, here's how it should look to be grammatically correct (only for "<nowiki>{{Used by|all-except|</nowiki>"):
 +
:Scout = Skauta
 +
:Soldier = Żołnierza
 +
:Pyro = Pyro
 +
:Demoman = Demomana
 +
:Heavy = Grubego
 +
:Enginner = Inżyniera
 +
:Medic = Medyka
 +
:Sniper = Snajpera
 +
:Spy = Szpiega
 +
[[File:User Denied signature.jpg|50px|link=User:Denied]] [[User:Denied|Denied]] [[User talk:Denied|(Talk)]] 14:07, 14 February 2024 (UTC)
  
: {{c|Support|all the way!}}. its a lot better then for example to maul description "see homewrecker" either copy paste or group them, don't make things more tedious. This is why i agree with this change.'''<span style="font-family:aharoni; font-size:110%; font-style:italic;">[[File:RED Überneedle.png|42px|link=User:Lexar]] - <span style="text-decoration:underline">[[User:Lexar|Lexar]]</span> - <span style="text-decoration:underline">[[User talk:Lexar|talk]]</span></span>''' 00:34, 22 August 2011 (PDT)
+
:These requests should really be on the template's talk page instead.<br>[[File:BLU Wiki Cap.png|20px|link=List of Wiki Cap owners]] | [[Help:Group rights|<span style="color:green;font-family:TF2 Build;">s</span>]] | [[User:GrampaSwood|<font color="DB9C1F">GrampaSwood</font>]] [[File:PraisetheSun.png|20px|alt=Praise the Sun!]] ([[User talk:GrampaSwood|<font color="DB9C1F">talk</font>]]) ([[Special:Contributions/GrampaSwood|<font color="DB9C1F">contribs</font>]]) 14:13, 14 February 2024 (UTC)
: {{c|Support}} I like the way this looks, it makes sense to group what are essentially the same items together. -[[User:Mr. Magoolachub|Mr. Magoolachub]] 00:36, 22 August 2011 (PDT)
+
::Thanks. I've moved it there. [[File:User Denied signature.jpg|50px|link=User:Denied]] [[User:Denied|Denied]] [[User talk:Denied|(Talk)]] 08:28, 15 February 2024 (UTC)
:{{c|Neutral}} Pros are obvious, but I find the lack of a chronological order disturbing *force grip*. Either to have a cake or eat it. [[File:Userimg-real alien.jpg|25px]] [[User:Real alien|<span style="font-family:TF2 Build; color:#3366cc ">real_alien</span>]] ([[User talk:Real alien|T]]/[[Special:Contributions/Real alien|C]]) 00:55, 22 August 2011 (PDT)
 
:::Don't forget that it still retains some chronology. If you look at the second last paragraph, it's still retained as a secondary sorting method. Don't forget that the date in which the weapon came out is shown on its page. For those looking for new weapons, I made a suggestion which could be used in order to find the more recent weapons.[[User:DVDV|DVDV]] 01:42, 22 August 2011 (PDT)
 
: {{c|Support}} non-redundancy > chronological order [[File:User_SackZement_signature.gif|link=User:SackZement]][[User:SackZement|<span style="font-size:14px;font-family: Tf2 Build"><font color="orange">SackZement]]</font></span> [[User_talk:SackZement|(Talk)]] 01:04, 22 August 2011 (PDT)
 
: {{c|Support}} Looks way better and more organised. [[User:Flamedrac0|Flamedrac0]] 07:03, 22 August 2011 (PDT)
 
: {{c|Support}} And here I was all set to complain about two massive tables on the talk page. That is really cool and how it probably should have been done from the beginning. [[User:Coreycubed|coreycubed]] / [[User talk:Coreycubed|talk]] 07:19, 22 August 2011 (PDT)
 
: {{c|Support}} This does look alot better than the current layout, it also groups the same kind of items together, i like!! [[User:T-Wayne|T-Wayne]] 09:41, 22 August 2011 (PDT)
 
: {{c|Support}} Looks a lot more organized, and it would separate the clone weapons from the ones that are different rather well. -- [[File:User_SyKhotic_CustomPageLink.png|link=User:SyKhotic]] 10:11, 22 August 2011 (PDT)
 
: {{c|Support}} Like what others have said, this looks more organized and there's really no reason I can think of not to implement it. [[File:User RagnarHomsar Userlink.png]] [[User:RagnarHomsar|RagnarHomsar]] 15:38, 22 August 2011 (PDT)
 
: {{c|Support|Probably}} While it doesn't make sense as alphabetical/"regular" chronological orders would, it's a lot easier to see, examine, and compare. {{n}} {{User:EpicEric/Sig/Image|RED}} {{User:EpicEric/Sig/Text|Epic|#5885A2}} {{User:EpicEric/Sig/Text|Eric|#B8383B}} {{User:EpicEric/Sig/Image|BLU}}{{User:EpicEric/Sig/Extra}} 15:46, 22 August 2011 (PDT)
 
: I'm gonna : {{c|disagree}} because it's awkward to look at. A jumbled mess. However, I would be able to {{c|Support|support}} a sorter that defaults to release order. --[[User:SilverHammer|SilverHammer]] 21:26, 22 August 2011 (PDT)
 
::Oh yes, a sorter would be a good idea. [[File:Userimg-real alien.jpg|25px]] [[User:Real alien|<span style="font-family:TF2 Build; color:#3366cc ">real_alien</span>]] ([[User talk:Real alien|T]]/[[Special:Contributions/Real alien|C]]) 23:57, 22 August 2011 (PDT)
 
:::An option to sort by release date would require another column for dates though. If we're trying to make more organised, adding extra columns seems rather redundant to me. [[User:DVDV|DVDV]] 00:08, 23 August 2011 (PDT)
 
The way I see things, the only time chronological order would be required would be if the player is not new to the game and is wanting to know about a recent update. Under these circumstances, leaving the new clone at the bottom until a reasonable time has elapsed would fix the problem. Let's face it, do you really need Mailbox to be at the end when you know what it does?[[User:DVDV|DVDV]] 00:09, 23 August 2011 (PDT)
 
: {{c|Neutral}} It's certainly not worse than the current layout, but it's not quite perfect either. The 4 right columns all look stretched out and weird. I'm not against implementing this but a complete, more compact redesign might be what the doctor ordered here. It certainly makes sense though, I'll give you that. -- [[Image:User Alex2539 Sig.png|47px|link=User:Alex2539|Alex2539]] - {{mod}} <sub>([[User_talk:Alex2539|talk]] | [[Special:Contributions/Alex2539|contribs]])</sub> -- 01:20, 23 August 2011 (PDT)
 
::I think that the HHHT has a big impact on that. If you had a look at it for someone like Pyro, it'd look way better. [[User:DVDV|DVDV]] 01:39, 23 August 2011 (PDT)
 
::: The Bottle/Pan/Saxxy columns look just as odd to me. -- [[Image:User Alex2539 Sig.png|47px|link=User:Alex2539|Alex2539]] - {{mod}} <sub>([[User_talk:Alex2539|talk]] | [[Special:Contributions/Alex2539|contribs]])</sub> -- 01:42, 23 August 2011 (PDT)
 
:{{c|Neutral}} I'm going to say neutral for this, but I am leaning more towards no.  I think it is WAY MORE important to have them chronological than pretty. [[User:SS2R|SS2R]] 01:21, 23 August 2011 (PDT)
 
:{{c|Neutral}} Page becomes kinda empty, doesn't it? --[[File:Login_Soldier.png|link=User:Daniil]][[User:Daniil|Daniil]] 23:13, 23 August 2011 (PDT)
 
::Empty? It's about reducing clutter!
 
  
== Balloon birthday standard for server ? ==
+
== Where can I interact with the community? ==
  
In the german version are atm ballons instead of the bloody death of an enemy. I played on 2 competitive server, and no configs were altered to this. Is this a new feature for a day or two, why is that? [[User:TheDoctor|TheDoctor(without a small pic)]] 16:10, 23 August 2011 (PDT)
+
Is there a discord or something to interact with the community? Thank You.
: It should be. Why? Of cource for players. Most of admins are too lazy to update server configs, but players want to play with new holiday update right after realese. This is my opinion. :3 --[[File:Login_Soldier.png|link=User:Daniil]][[User:Daniil|Daniil]] 23:09, 23 August 2011 (PDT)
 
: [[Birthday mode|Birthday mode is automatically activated on August 24, the release date of the original Team Fortress in 1996.]] -- [[User:Netshroud|{{TF2B|text = Netshroud | quality = unusual | size = 13px}}]] [[File:Killicon_backstab.png|22px|link=User:Netshroud]] <small>([[User_talk:Netshroud|talk]] | [[Special:Contributions/Netshroud|contribs]])</small> 23:11, 23 August 2011 (PDT)
 
  
== 'Community Dustbowl strategy' cleanup. ==
+
[[User:QS Quark|QS Quark]] ([[User talk:QS Quark|talk]]) 13:49, 23 March 2024 (UTC)
  
I can see that the 'Community Dustbowl strategy' page is bit too long. Does anyone else think that we should add collapsible tables for each of the class strategy, so to make the page more compact and and easer for the user to navigate?
+
:You can join the [[IRC]] if you want. There is no Discord (and we also won't make one).<br>[[File:BLU Wiki Cap.png|20px|link=List of Wiki Cap owners]] {{!}} [[Help:Group rights|<span style="color:green;font-family:TF2 Build;">s</span>]] {{!}} [[User:GrampaSwood|<font color="DB9C1F">GrampaSwood</font>]] [[File:PraisetheSun.png|20px|alt=Praise the Sun!]] ([[User talk:GrampaSwood|<font color="DB9C1F">talk</font>]]) ([[Special:Contributions/GrampaSwood|<font color="DB9C1F">contribs</font>]]) 13:59, 23 March 2024 (UTC)
* Can you make an example to see how will it look? --[[File:Login_Soldier.png|link=User:Daniil]][[User:Daniil|Daniil]] 06:18, 24 August 2011 (PDT)
 
* They could be similar to the examples on the [http://en.wikipedia.org/wiki/Wikipedia:Collapsible_tables Wikipedia] article.
 
  
== Should we keel these  ==
+
== April fool's? ==
  
Each [[Scout#Gallery|class gallery]] currently has a texture file from TF tacked on to the end of it. I do not think these are needed, considering they are very low quality, are already present in the first image of every class gallery, and just don't fit in well. Why would we have these textures when we don't have the TF2 class textures. Add those, and the gallery would just look... creepy, I guess. Keep or remove? --[[User:SilverHammer|SilverHammer]] 12:57, 25 August 2011 (PDT)
+
I've been absent a bit because of health issues lately, sorry, but I noticed there's no April Fools thing this year there? :(--[[File:Leaderboard class allclass.png|15px|link=]] [[User:Akolyth|<span style="font-size: 14px; font-family: Trebuchet MS">'''Akolyth'''</span>]] ([[User_talk:Akolyth|talk]]) 02:43, 2 April 2024 (UTC)
:{{c|yes}} keel - if we already have pics of the TF characters then they're redundant. -[[User:RJackson|<span class="modbg" style="margin-right:1px;text-shadow: #538237 1px 1px 0px;">RJ</span>]] 13:04, 25 August 2011 (PDT)
 
:{{c|Oppose}} While not directly related to Team Fortress 2, it is relevant to the series. I think you might be surprised at the amount of people who don't know there were previous versions of tf2, much less that we have one of them very well documented on the wiki. And in addition, I think it's just interesting in general to see the scout (or any class for that matter) on the page as a sort of "visual progression" in the game series. <span style="font-family:TF2 Build;font-size:17px;color:#a13434;">MogDog66[[File:User MogDog66 Service Metal No WhiteSpace.png|24px|link=User:MogDog66]]</span> 21:47, 25 August 2011 (PDT)
 
: {{c|oppose}} If I'm not mistaken, the first image shows two TFC skins while that last one is the QTF texture. You can tell just by looking that they are different and I agree with MogDog that they represent the progression of Team Fortress. I think they should stay. Although ideally, they would be properly mapped onto models instead of just showing the textures. -- [[Image:User Alex2539 Sig.png|47px|link=User:Alex2539|Alex2539]] - {{mod}} <sub>([[User_talk:Alex2539|talk]] | [[Special:Contributions/Alex2539|contribs]])</sub> -- 22:01, 25 August 2011 (PDT)
 
: {{c|oppose}} It's a memento. Definitely keep it. <small>— ''The preceding unsigned comment was added by'' '''[[User:DVDV|DVDV]]''' ([[User talk:DVDV|talk]]) • ([[Special:Contributions/DVDV|contribs]]) </small>
 
: While not entirely identical, they are pretty much completely the same. They look completely awkward. If these are worth keeping, then we should add the regular class textures as well. There are articles for the TF classes, aren't there? A "memento"? That's just a terrible reason. --[[User:SilverHammer|SilverHammer]] 09:20, 26 August 2011 (PDT)
 
: {{c|oppose}} They're not low quality, it's just a game from the mid 90s... that's the quality of the texture itself. It's also the best possible way to show the Quake Fortress players. [[User:Balladofwindfishes|Balladofwindfishes]] 09:22, 26 August 2011 (PDT)
 
: Best possible way? How about, I don't know, the actual models? Isn't there a Quakee Fortress article? --[[User:SilverHammer|SilverHammer]] 09:24, 26 August 2011 (PDT)
 
:: Quake doesn't have a good, solid model viewer as far as I know of, so images of the classes taken in-game probably wouldn't be that high of quality. [[User:Balladofwindfishes|Balladofwindfishes]] 09:31, 26 August 2011 (PDT)
 
: {{c|oppose}} If we have TFC images then we should have TF images. {{n}}[[File:User_Heffebaycay_stslogo.png|link=]] [[User:Cructo|<span style="font-weight:bold;font-family: Segoe UI"><font color="black">Cructo]]</font></span> <span style="font-size:10px;font-weight:bold;font-family: helvetica"><font color="black"><nowiki>[</nowiki>[[User_talk:Cructo|T]]<nowiki>][</nowiki>[[Special:Contributions/Cructo|C]]<nowiki>]</nowiki></font></span> 09:26, 26 August 2011 (PDT)
 
  
== Strange Weapons ==
+
: Probably, yes. Since I didn't notice anything relate to April fools event other than the page itself (normally there will be someone create a April fools sandbox page before April fools event).[[User:Profiteer|<font color="8470FF">Profiteer]] the tryhard ([[User talk:Profiteer|talk]]|[[Special:Contributions/Profiteer|contribute]])</font> 03:45, 2 April 2024 (UTC)
  
Now that strange weapons are starting to track additional criteria other than (or in addition to) kills, such as ubers + assists, sentry kills, sodden players, etc... Would it be a reasonable idea to simply add a small sub-section to the page for each weapon called something to the effect of "Strange variant", and just explain what the strange version of the weapon tracks, or any other strange version-specific information? This information is not included anywhere in the wiki as of yet, as far as I was able to find, so putting it as a sub-section on the page for each original weapon seems logical to me. Thoughts? [[User:Noibn|Noibn]] 10:26, 26 August 2011 (PDT)
+
::The only thing that was planned was a patch, no other efforts were made, unfortunately.<br>[[File:BLU Wiki Cap.png|20px|link=List of Wiki Cap owners]] {{!}} [[Help:Group rights|<span style="color:green;font-family:TF2 Build;">s</span>]] {{!}} [[User:GrampaSwood|<font color="DB9C1F">GrampaSwood</font>]] [[File:PraisetheSun.png|20px|alt=Praise the Sun!]] ([[User talk:GrampaSwood|<font color="DB9C1F">talk</font>]]) ([[Special:Contributions/GrampaSwood|<font color="DB9C1F">contribs</font>]]) 08:17, 2 April 2024 (UTC)

Latest revision as of 19:22, 20 April 2024


Dark Mode

I don't think I even need to explain this. Wikipedia itself has it, so do other wikis. I do have a browser extension for dark mode, and optimally a dark theme for TFwiki should still keep muted earthy orangish tones and such, but at this point with my eye strain I'd take anything. It would encourage more dedicated editing streaks, perhaps, since many of us are night owls too.--Leaderboard class allclass.png Akolyth (talk) 03:23, 16 October 2023 (UTC)

Easier said than done, it's being worked on but we can't promise anything.
BLU Wiki Cap.png | s | GrampaSwood Praise the Sun! (talk) (contribs) 11:13, 16 October 2023 (UTC)

Valve Store

The official Store has been closed down for months now by Valve, and there's no reasonable smidgeon of proof to believe it's coming back any time soon. The Wiki, in many articles, links directly to the Store still, or mentions it, but even tooltips for certain hats will just say they're "not available". This is kind of awkward, and makes the average user waste a click (the horror, I know). And even I get a false hope sometimes that it changed, but it's Valve after all. Should something be done about this, and how? Can there be an automatic disclaimer the Store is gone? Should links be removed? Just let the dead ends sit forever?--Leaderboard class allclass.png Akolyth (talk) 02:44, 18 October 2023 (UTC)

Try to find an archive.org version of it, otherwise just add a tooltip saying it's not available anymore due to store shutdown.
BLU Wiki Cap.png | s | GrampaSwood Praise the Sun! (talk) (contribs) 11:12, 18 October 2023 (UTC)

Painted variants with both Styles and separate Classes images, a design proposal

Hi. So, I have several mockups of things to suggest which I'll be writing it up eventually. For now, I was making changes to the Robot Chicken Hat page, and was thinking about adding class variants to the paint gallery, as each class changes the hat's design a little (taller combs, different beak designs, etc.). However, if I were to make those paint variants per class, the current way we put styles and classes to the table looks... off, to say the least. At the moment, if I were to make it consistent with the rest of the Wiki, it would look like this: https://i.imgur.com/gfdAUBL. But, instead, I thought about this mock-up: https://i.imgur.com/QmQCLsK. Not only this looks more visually appealing, but it also takes a lot less space. The only problem that it may be confusing for cosmetics that separate styles by a group of classes (Cotton Head, Brotherhood of Arms, etc.). So... I thought about just making the class buttons that aren't active a little darker (same thing with the Style name): https://i.imgur.com/Fiw1zRT. Here's another example with the Cotton Head: https://i.imgur.com/ZhkQwGG. Mouse-hovering the class icons could also show their class names ("Pyro, Medic, Spy" and "Other classes" in the case of Cotton Head) Thoughts? Headphones style when? - User Gabrielwoj Signature 1.pngUser Gabrielwoj Signature 2.png - User Gabrielwoj Signature 3.png 13:11, 18 October 2023 (UTC)

I like this proposal, although I think it's not necessary for every page. Only for the ones where the tabs become too much.
BLU Wiki Cap.png | s | GrampaSwood Praise the Sun! (talk) (contribs) 13:15, 18 October 2023 (UTC)

Inconsistency regarding items with one team color, but shows team-colored parts of a player model

Hello. So, when I started adding tabs to the paint variants, and just browsing the Wiki as a whole, I noticed that a couple pages are inconsistent in regards to the unpainted variants. In almost every case of cosmetics that use part of the player model, but only has 1 skin (not team-colored), the team-colors syntax isn't added to the tab, and we only have the UNPAINTED version on the paint variants table (example includes the Soldier's Stash, Horrible Horns on Spy, and much more), but some other pages still shows the BLU variant of a player model despite the item only having one skin (Texas Half-Pants, Millennial Mercenary's Streaming 2Fort style, Exquisite Rack, Battle Bob's With Helmet style, Bacteria Blocker's Headphones style, etc).

Some other pages also includes two identical RED and BLU images for the infobox, just because the item has two materials per team, but still uses the same exact texture and values (basically two identical .vmt files). I don't remember what pages has it now, but there are some pages that has that. I did that on Decorated Veteran since I've heard about doing that in the past before: "even if they look identical, put in two separate uploads". There's also no current way to just show one skin on the infobox (however that's something I'm looking to suggest soon enough on my mega infobox improvements topic).

Because we use the infobox, as well the RED and BLU parts of the paint variants table to show the different Skin Colors of the ITEM, I would say to actually cleaning it up these inconsistencies. So, for instance, on Texas Half-Pants, there wouldn't RED and BLU images for each style, because they look identical on either team, and, there's only two skins on the model (one for the Tan style, the other for the Midnight style [older cosmetics used a different way in handling styles, as opposed to separate models, many old cosmetics would use different skins for styles, and the Item Schema would redirect what skins to use depending on the style chosen]). The colors change on the images right now, because it's the colors of Engi's default pants, but not the actual item model changing colors. Meaning that, the RED / BLU on the infobox would be removed, the BLU_... images would be deleted, and the RED_ images would be moved to the _UNPAINTED.png suffix instead.

Some may argue that, since the team-colored paint can image previews also change the pants colors, that these should stay in, but, I don't agree. These are to show the item's team-colors being affected (both the UNPAINTED versions and the team-colored paint cans), not the player model's team-colors, but let me know what do you think.

Items that have 0 changes on team-colors despite having them (same exact .vmt values), I'd also say to get rid of it, as they provide no real information for the reader other than perhaps modders, so they don't need to go all the way of decompiling models to add team-color support, for instance. Some require close inspection however. The Mann-Bird of Aberdeen looks like to be the case, but the green area is just slightly brighter on BLU. I'd still keep the same colors for Styles and classes (like Team Captain for Heavy), until a more fully-fledged infobox edit comes along the way that adds support to just 1 skin on the infobox (like this: https://i.imgur.com/GQP1ou0). I will still point out many of these on my eventual discussion of infobox changes in another topic. Headphones style when? - User Gabrielwoj Signature 1.pngUser Gabrielwoj Signature 2.png - User Gabrielwoj Signature 3.png 13:43, 18 October 2023 (UTC)

I would support every page having both team colours.
BLU Wiki Cap.png | s | GrampaSwood Praise the Sun! (talk) (contribs) 13:57, 18 October 2023 (UTC)

Articles for individual environmental hazards

Some of the older environmental hazards have their own articles. Specifically, they are: Ghost, Pumpkin bomb, Saw blade, and Train.

These are some fairly simple hazards: ghost goes "boo", pumpkin bomb goes "boom", blade goes "bzzt", and train goes "[Train horn noises]". They all have fairly short articles, and are also covered in the Environmental death article.

I propose we change these four into redirects to the Environmental death article, similar to Pitfall.

As for their Update histories, I have three ideas:

  • Add the section to the Environmental death article and carry them over.
  • Create a separate page for that (similar to the Item timeline pages).
  • Ignore them (essentially already the case for all the hazards that don't have their own articles).

I am ok with Skeletons and the Halloween bosses having their own articles, however, as they are more elaborate (which is noticeable by simply comparing article sizes).

Opinions? - BrazilianNut (talk) 16:36, 19 October 2023 (UTC)

I think some of these pages can add value, such as the specifics in the hazard infobox. I'd push for more articles rather than less, similar to List of game modes, where each hazard has its own page as well as a short description on the overall page. I would prefer this because it would cut down on the clutter on the Environmental death page, for example the pumpkin bomb section is 5 identical hazards that are just reskinned. It would be better to have this in a gallery on its own page, rather than several entries on that page.
BLU Wiki Cap.png | s | GrampaSwood Praise the Sun! (talk) (contribs) 16:40, 22 October 2023 (UTC)
I believe it is better to keep the pages separate, as putting them all together in one could generate a lot of visual clutter, in addition to having a lot of information for the reader to consume at once. Furthermore, it would be complicated to gather all the update histories on the articles. Essentially, we would be taking separate articles and combining them into one big article, where each section (divided by == Section title ==) would be a "complete" article.
Tiagoquix (talk) 18:45, 22 October 2023 (UTC)

A request

In Polish language we don't capitalise most words like in English language and the way quality items have their quality displayed looks like this: Rocket launcher (vintage). The problem is that in Template:Mann-Conomy Nav Vintage quality in Polish and Russian is not capitalised and looks weird in the template where everything is capitalised except this one word. Is it possible to add a new entry in the dictionary for this template only, where 'Vintage' is capitalised for these languages? In Polish it's even more confusing, because Classic and Vintage share the same translation, so it could be shown in the tempalte as 'Vintage quality' (Jakość klasyczna in Polish). User Denied signature.jpg Denied (Talk) 10:28, 24 October 2023 (UTC)

If it's the very first letter that needs to be capitalised, you can use {{ucfirst:<string>}} to turn the first letter into a capital. For example, {{ucfirst:hello world}} generates Hello world.
BLU Wiki Cap.png | s | GrampaSwood Praise the Sun! (talk) (contribs) 11:15, 10 November 2023 (UTC)
Could you help me with this? I've changed it in Template:Mann-Conomy Nav but doesn't seem to capitalise the first letter. User Denied signature.jpg Denied (Talk) 10:54, 17 December 2023 (UTC)
Hmmm, yeah seems like the automatic translation templates automatically uncapitalise it. If you really wanted to implement this you'd have to use the {{lang}} template instead.
BLU Wiki Cap.png | s | GrampaSwood Praise the Sun! (talk) (contribs) 13:49, 17 December 2023 (UTC)
I already did it once and... User Denied signature.jpg Denied (Talk) 14:19, 18 December 2023 (UTC)
Perhaps leave a hidden comment and use {{lang incomplete}}?
BLU Wiki Cap.png | s | GrampaSwood Praise the Sun! (talk) (contribs) 14:27, 18 December 2023 (UTC)
I've coppied how it looked oryginally but now it shows as red link 'VintageVintage'. Could you look what's wrong with this edit? Except equals sign. I've fixed it later. User Denied signature.jpg Denied (Talk) 13:21, 19 December 2023 (UTC)

────────────────────────────────────────────────────────────────────────────────────────────────────Looks like you forgot to add a vertical bar, which made the link [[VintageVintage]].
BLU Wiki Cap.png | s | GrampaSwood Praise the Sun! (talk) (contribs) 13:31, 19 December 2023 (UTC)

Mann Manor/Mountain Lab's history

I feel maps that we know more detailed information on the history of we should actually have written down so it isn't forgotten, such as for example, Mann Manor/Mountain Lab being an art contest was not the original plan in fact the maps used to have textures before but, that's just what I think. The American Boot (talk) 04:34, 10 November 2023 (UTC)

If you think this fact is worth and most player don't know, you can try adding it to Trivia section. Here is a more detailed Trivia guild.Profiteer(奸商)the tryhard (talk) 05:07, 10 November 2023 (UTC)
I'm not sure where this Trivia came from or if there is any source for. The Art Pass Contest page states that Robin Walker said they had a map that hadn't been worked on for a while and they didn't have time to do an art pass on it (which means the map just had dev textures).
BLU Wiki Cap.png | s | GrampaSwood Praise the Sun! (talk) (contribs) 21:34, 10 November 2023 (UTC)

Weapon articles mentioning taunts that aren't kill taunts

I've noticed a few articles for weapons mentioning that those weapons have a unique taunt that is not a kill taunt, or a variation of the default weapon for that slot (which is still not a kill taunt). These are the Lollichop, which mentions it has a unique taunt based on a scene from Meet the Pyro, and the Third Degree and Neon Annihilator, which mention the added guitar sounds, respectively. In comparison, the Cow Mangler 5000, Scottish Resistance, and Ullapool Caber, which also have unique taunts, do not mention them since they're not kill taunts, and the Vita-Saw, which has has a variation of the default taunt, does not mention said variation.

I think we should remove these notes from the Lollichop, Third Degree, and Neon Annihilator, as they are already all noted in the Pyro taunts page.

Speaking of the Pyro taunts page, I think we can move the "as in Meet the Pyro" comment from the Lollichop's description to a new Trivia section and add that Execution is also based in a Meet the Pyro scene (which is not mentioned). - BrazilianNut (talk) 16:45, 7 December 2023 (UTC)

I think variants on an existing taunt should be mentioned, such as different sounds (such as the Third Degree/Neon Annihilator adding guitar sounds and the Vita-Saw having different melodies being played), but the non-kill taunt shouldn't be mentioned (no note about the Lollichop taunt. Although seeing as it's unique to that weapon, I think the Trivia can stay).
BLU Wiki Cap.png | s | GrampaSwood Praise the Sun! (talk) (contribs) 17:14, 7 December 2023 (UTC)

Main menu Smissmas 2023 header localization

'Smissmas 2023' is localized but 'December 7 - January 7' is not. Is it possible to localize it too? User Denied signature.jpg Denied (Talk) 10:29, 17 December 2023 (UTC)

See Dictionary common strings.
BLU Wiki Cap.png | s | GrampaSwood Praise the Sun! (talk) (contribs) 13:37, 17 December 2023 (UTC)
Thanks. User Denied signature.jpg Denied (Talk) 14:19, 18 December 2023 (UTC)

Link of the wiki team fortress energie drink don't work

[[1]] you see this page on the wiki contain a team fortress wiki energie drink with a link for have it but it don't work and is not secure, can someone help me ? The preceding unsigned comment was added by Nonolemage (talk) • (contribs) 2023-12-21, 13:46 UTC

Please sign your messages using ~~~~.
The website appears to be down and no archive of it exists, so unless someone here happens to have a copy we can't do much.
BLU Wiki Cap.png | s | GrampaSwood Praise the Sun! (talk) (contribs) 13:46, 21 December 2023 (UTC)

Multiple Suggestions related to Infobox, etc

Hi. I have been wanting to write this in the past, but, well, finally here it is. I have a couple suggestions about things related to infobox, and other things to make the design of the Wiki flow better on certain articles. I will be posting here as it covers a multitude of topics, as opposed to posting each one of them on their respective templates. When adding "Support" and "Not Support" on your responses, please make sure to add the number (and letter) behind to specify what you are supporting (or not supporting) as a change (like: "1-c"). With that said, let's get going:


1) Implement a way on the Item infobox template where if a style or class has only one team-color compared to other styles with team-colors, include an icon in the middle of both teams. For instance:

a) The Heavy variant of the Team Captain only has one color, but the page right now includes a duplicate of the RED variant as a workaround. What I suggest is doing this: https://i.imgur.com/YgQHk5z. Make the Heavy variant only one file, and center it. It should be pretty clear that because of the image is in the middle, is that it looks like that on both teams.

b) For items with styles that only has one color (not team-colored), do the same thing as well. In the example of Close Quarters Cover, include the "Alert" style on the infobox in the middle of the "RED" and "BLU" sections of the infobox, something like this: https://i.imgur.com/lARBQME.

c) For items that are not team-colored, but have class-specific variants, include a new part colored in grey called "Both Teams", and include each image on the middle as well. For example, the Dead Little Buddy have 3 model variants, one for Pyro, one for Demoman, and the other for the remaining classes. The idea is this: https://i.imgur.com/xPD9PMO.

d) Although I do not have a mock-up right now, I thought of also doing the same as above for items that has only one color. So, for instance, the Jumper's Jeepcap would have a "Both Teams" section, and it would include the "UNPAINTED" variant on the center. Items with styles with just one color, like Mustachioed Mann, would be similar to Dead Little Buddy, including each style on the infobox, alongside their names. Items like Carl that has no styles, but is neutral-colored, would also have the "Both Teams" part.


2) Get rid of the current "2D" images of Weapons, and use "Item icons" instead. The 2D weapon images are not consistent throughout the Wiki. They have different lighting, different angles, and so on. What I suggest is doing something similar to another Wiki I also contributed (one related to a TF2 sourcemod): https://i.imgur.com/vbvPbGP. This looks extremely clean, and every page would have in this angle. The 2D image only includes the RED variant, just like we use RED classes on our cosmetic previews.


3) Add the "RED" and "BLU" sections on the infobox for Weapon pages, even if the 3D image allows you to switch between teams. Right now, the RED variant is used as the 2D image (for team-colored weapons), while the 2D BLU variant awkwardly sits on the Gallery section. My suggestion would be this: https://i.imgur.com/dM9z7Oo


4) For cosmetic pages that has styles alongside class changes on the Painted Variants table, include additional buttons that include class icons. The idea is to remove clutter on pages with a lot of tabs to choose from (see this page). In technical terms, the style buttons would be responsible to change the "style" part of the filename, while the class buttons would change the class part of the filename. If the first class is chosen, then the code needs to get rid of the class part of the filename, as the first class is always the default: https://i.imgur.com/QmQCLsK

a) Additionally, text could be placed on each row, one for "Style:", and the other for "Class:" for the second row, just so it's a little more intuitive and understandable for everyone.


5) Include "infobox images" for separate styles, and add buttons that let you change it. The idea is to include identical images (with identical classes and facial flexing), with the only thing changing the model. For example, Main Cast would look like this: https://imgur.com/a/OmTIYVs.


6) Include more sections on the Gallery for items with more than one Style. In the past, the Robot Chicken Hat page did include all 9 classes on the Gallery section, with 2 separate sections, one with the "Beak" style, and the other with "Beakless" style. It would follow the same rule as "5)", with both images looking identical facial-flex and pose-wise. Some pages like Dead of Night wouldn't include all classes on each section. Classes with lack of grenades wouldn't be there.

Edit: Some users asked for an example, so, when I talked about the Robot Chicken Hat, it originally looked like this. The images don't exist anymore, but you can still see how it looked like. When I wrote the suggestion, I thought something about that (though it could have been changed a little, like include an "Other" title for the remaining images that aren't related to the class images), but, after Swood's suggestion, I'd say that using Tabs would be more ideal, something akin to how we do on the Tournament Medal pages.

I did an example on my 2nd Sandbox page. I thought something about this: https://wiki.teamfortress.com/w/index.php?title=User:Gabrielwoj/Sandbox2&oldid=3598538 (note that a couple images, namely the infobox team-colors, and paint cans, does not show up properly due to the page's name being different, if this were to be pasted onto the actual page, it would show just as fine). I decided to not make the Tabs centered as regular cosmetic pages are usually not centered, unlike Tournament Medals / Community Medal ones. I also decided to make the gallery width "485px", so it shows 3 images per row, and looks pretty nice and cool with whatever's below that does not require a Tabs section.


7) Lastly. Items that include noticeable team-color differences could also get "Single Color" paint can previews on both teams, even if the paint look identical on the area that is paintable. When Paints were first introduced, they were mostly applied to cosmetics that used the same texture on either team. Now, nowadays, we have cosmetics that include team-colored parts that are not paintable, alongside other parts that are. So, for instance, Brawling Buccaneer would have its Painted variants table from {{Painted variants}} to {{Painted variants full}}, and single color paint can previews for the BLU team would be made, to show how the paint looks like, and despite being painted in the same area, the rest of the item is in another color. Readers might want to know how an item looks on the BLU team. This would take a long time too make for the entirety of the Wiki, and would be a project that would require remaking some paint variants if they do not have Rotation values saved, or if there's another issue that doesn't make them 1:1, but I think it would look good, and useful as well.


8) For items that has several styles / classes on the infobox (such as Manndatory Attire, Beaten and Bruised and Boarder's Beanie‎), make the Infobox template show less of them by default, and include a button with a caption "↓ Show remaining ↓". If possible, make the last one have a "fade" effect, so it's perfectly clear what the button is about. My idea was to include at least 10 of these sections, then fade (because if it reaches 10 of these, it means there's more than one Style per class, where other pages would include 9 of these per class, though, it could be shortened if needed, but personally I would go with 10 sections before the button and fade shows up). It would look like this: https://i.imgur.com/jh6geu6


Edit: 9) Regarding the Styles section. If we include Styles on the infobox, even for items that look the same on either team, is it really necessary to include the "Styles" section on the page, alongside the table, if everything would be on the Infobox? It seems redundant to keep both of them, but, I'd only get rid of the Styles section after everything is added to the infobox, including the single-color Styles on it. Additionally, certain pages that has Styles that change between classes are a little confusing at the moment. Manndatory Attire has only Scout's styles being demonstrated on the table, despite each class changing the visuals.

a) Originally I was going to suggest a class-switcher button, similar to the "4)", but, if "1)" is implemented, I don't see any reason to keep the Styles section. Please let me know if you think there should be either: "An arrange of buttons that lets you change classes on the Styles table" or "Getting rid of the Styles section entirely as it would be redundant with all the styles on the infobox once the "1)" suggestion is implemented.

b) The only problem that getting rid of the Styles section would be problematic for items that has barely any difference unpainted, but has more notable differences when paintable. Items like Onimann mostly change its visuals when painted between styles, and if there's no section for it. However, the painted variants table, alongside the main summary on the top of the page, would both visually show the difference, as well would explain in text what each style does in terms of paint.


Please let me know your thoughts below. Notice that I'm not sure if I would be able to implement some of these suggestions, specially the ones for the "Item infobox" template. If there's enough support, I'd appreciate anyone who could implement suggested changes / additions. Headphones style when? - User Gabrielwoj Signature 1.pngUser Gabrielwoj Signature 2.png - User Gabrielwoj Signature 3.png 21:13, 28 December 2023 (UTC)

1. I think that section should be dedicated to showing off the team colours rather than different styles for different classes. If a cosmetic looks different on different classes I would prefer a different box for it similar to the "Styles" section.
2/3. That's fine by me, though I would also want to add a second button to it for the BLU variant rather than stuffing it in the Gallery.
4/5. I like this.
6. I like this, although I would suggest we use the {{Tabs}} template for it.
7. I like this too, but it would require a ton of work and I'm not sure we'd be able to make it through.
8. I'm not sure that I'm a fan of collapsing a bunch of them. I would prefer having them sorted by class instead similar to {{Tabs}}.
9. See answer on 1.
BLU Wiki Cap.png | s | GrampaSwood Praise the Sun! (talk) (contribs) 21:59, 28 December 2023 (UTC)
1 Pictogram plus.png Agree - All of these changes look very nice, I don't have anything to say about them.
2 / 3 Pictogram question.png Not sure / changes - Would the change to using weapon icons include BLU weapon icons as well? If it does, I would rather have the 2D BLU image in the main infobox when you click on BLU and then switch to the 2D image instead of it being below the main image.
4 Pictogram plus.png Agree - This also looks nice.
5 Pictogram minus.png Disagree - I don't know how I feel about this, I feel like the painted variants sorta already accomplish the goal of knowing what the cosmetic would look like with the different styles. It would also take a lot of work to recreate a lot of infobox images just for this.
6 Pictogram minus.png Disagree - I have the same thoughts about this as 5, it would take a lot of work to redo a bunch of galleries when the styes / painted variants section already get the job done.
7 Pictogram plus.png Sorta Agree - This would look nice, however it would again take a lot of work to get done.
8 Pictogram plus.png Agree / changes - I like the idea, though I agree with what Swood said with that it would look better if it was just in tabs instead.
9 Pictogram question.png Not sure - I sort of agree with the idea of removing the styles section, but I also do like how there's a sort of simplified section for seeing all of the styles instead of it only being part of the infobox and painted variants.
Andrew360 Edit icon.png Speech typing.png Photo Badge Decal Example.png 03:27, 29 December 2023 (UTC)
1 Pictogram minus.png Disagree - Same reason with Swood, I think the style section should do the job.
2 Pictogram plus.png Agree - Good idea!
3 Pictogram plus.png Sorta Agree - Instead of taking space in infobox, Why don't we use the same button used on 3D images?
4 Pictogram plus.png Agree - Yes.
5 Pictogram plus.png Agree - Looks nice, but considered what Andrew says we might not getting those done in recent.
6 Pictogram plus.png Agree - We are gonna do a lot of work then I guess.
7 Pictogram plus.png Agree - Same with Andrew360
8 Pictogram question.png Not sure - Looks good, though yeah, why not use {{Tabs}}?
9 Pictogram question.png Disagree.. or Sorta Agree - If I have to choose one from infobox and style section, I would take style section. In my opinion the infoboxs shouldn't be too long and contain too much information, comparing to a small space on the right side of the page, I think the style section can display the information better. If 8 gets passed then I'm fine with it too. (I just don't want to see infobox gets longer than the page itself.)
Profiteer(奸商)the tryhard (talk) 06:16, 29 December 2023 (UTC)
1 Pictogram plus.png Sorta Agree - Eh, doesn't matter to me either way.
2 Pictogram question.png Not sure - I wanna see how it would look first.
3 Pictogram plus.png Agree - I was kinda the one to start the whole "shoving the blue variant in the gallery" and have always wondered why there wasn't a color toggle for the 2D variants.
4 Pictogram plus.png Strongly agree - I wish it was like this since the beginning!
5 Pictogram question.png Not sure - I like the idea, but it will take a lot of work updating all the pages and such with the change.
6 Pictogram question.png Not sure - Same answer as 5.
7 Pictogram plus.png Agree - I'm only saying yes because we'll only have to edit the templates which are used across all translation pages.
8 Pictogram minus.png Somewhat disagree - There aren't very many items that have loads of different styles like this, I think I'd wait until we get something like a shirt or coat that includes a load of different styles (with team variants).
9 Pictogram minus.png Strongly disagree - Yeah it is necessary to have a styles section, because they mostly show examples of what they look like on the character wearing it. I know that the infobox has styles too, but they're only the raw models.
ShadowMan44 (talk) 01:52, 30 December 2023 (UTC)
So, after some user's responses, I'd like to mention a couple things. In regards to most of "2)" and "3)" responses, here's something I didn't mention. There would be a slight problem for items that are not team-colored if we just implemented a RED and BLU image switcher. The idea of using "Item icons" with the RED variant / neutral-color variant, would that it would make everything consistent and nice looking, While "RED" and "BLU" 2D images are usually very consistent too, the current "2D" images used on weapon pages are all over the place. Using the "Item icon" in conjunction with the RED and BLU team-colors means we could use already existing images on the Wiki, too. Not that I would have a problem if new images had to be created for the Neutral-Colored weapons, but, I still think that using the Item icons would highly benefit here, since how nice they look on weapons.
However, if we go with a RED and BLU switcher, what we could perhaps do is team-colored Item icons, yeah that would be awesome. Not only that, but we also have Item icons for Australiums, and, I even made Australium Festivized icons for TF2B a while ago, that is only used there and not on the Wiki, at the moment.
GrampaSwood 6) Yeah, I didn't think of this, but using Tabs on the Gallery would be pretty good, something we already do in Tournament Medal pages, actually.
GrampaSwood, Andrew360, Profiteer 7) While I can't promise I will be on the Wiki forever, and, with my statement on my userpage being correct (that I won't be as active in 2024), making BLU team-colored variants on "Standalone" models is a faster process than when making when loaded as a "weapon" (e.g.: Cosmetic loaded on a player model). The reason I did all the Boarder's Beanie paint variants is solely because it's a standalone model, I was able to generate the paint variants very quickly (and in high quality and proper colors). I can still do every single style and class on BLU as well, for the Single Color paint variants, for the Beanies, I just haven't done since we are still discussing this.
My Laptop is currently not being used. I have thought of the idea of making an HLMV machine, and letting paint variants being made while I do other things. This is something I thought about in the past, but I would require another monitor (which I can buy, no problem), but I also would need time, something I will not have that much starting 2024. However, I'm also in the point where I feel like I have contributed quite a lot for the Wiki already, so I'm kinda conflicted if I should really do this or not. I would only require to re-install Windows, re-configure HLMV (which can be painful), and things like that, before I can make it an idle HLMV machine that makes paint variants.
ShadowMan44 7) Correct, currently, the "Painted variants full" template states that mouse-hovered "Single colors" states that "due to how the cosmetic's textures are set up, it changes colors between teams". This would require to be changed appropriately, somehow, though I don't think that yet another Painted variants template should be made. It should be possible to just add a parameter of some sort.
Gabrielwoj, Andrew360 5) Despite me suggesting this, I was also not too sure about it, but I decided to post it as a matter of discussion. In most cases, Styles just change the look of an item, without changing the placement of the model, or the model itself. In some other cases, however, it does change something Liquor Locker, Pocket-Medes, etc. While it would be an interesting idea, and I do have a couple cosmetics with all styles made already, most of the rest would require to be remade. This could also be a little difficult for regular HLMV users, as refreshing the model viewer gets rid of the facial flex entirely, but not on HLMV++. While you can unload and load submodels without having to refresh, HLMV does read from "$color2" instead of "$colortint_base", which means if someone forgets about that on an older cosmetic, they'd need to refresh after fixing it from the .vmt.
Profiteer 9) That's a good point. I guess if the Styles section was more populated (actually shows differences between classes), then I suppose that items like Manndatory Attire and Boarder's Beanie wouldn't require that huge amount of styles being shown on the table. But then, there's another problem. Items already show their unpainted RED and BLU variants on the infobox, and how exactly could we categorize "exceptions" to be only on the Styles section if we follow your idea?
ShadowMan44 9) I'm not quite sure if I understood what you said. The styles table on both the Style section and infobox use the same exact images, same files, with some exceptions like the Dead of Night and Pocket-Medes. This is why I mentioned it being redundant, because in most cases, both sections use the same images. Headphones style when? - User Gabrielwoj Signature 1.pngUser Gabrielwoj Signature 2.png - User Gabrielwoj Signature 3.png 11:21, 30 December 2023 (UTC)
So Tekinz and Mgpt talked with me via Steam and Discord DMs, and I'd like to post their opinions on this. Tekinz asked me to post on my behalf, explaining what he told me instead of directly quoting him, while mgpt allowed me to directly translate what he told me. With that said, here's what they had to say:
Tekinz: He told me that he agrees with most of my proposed update and changes, while pin-pointing some specific numbers with further explanation. He adds that for "7)", it would be a huge amount of work, and we would need quite a few active image creators to be able to achieve it in a timely manner, but otherwise it would be a general improvement to the pages. On "8)", he adds that he has no real problems with and thinks it's pretty good, mentioning that if combined with "1)", it would look great. On "9)", he mentioned that it's probably a good idea considering how the Styles section is located pretty far on the page and that it would probably be better to have them focused to the infobox since it's much closer to the top, alongside the rest of relevant images. He further adds that the Styles section always seemed not as important since it was too close to the Trivia and Patch Notes, while also being beneath the huge Painted Variants table that overshadows it.
mgpt:
Pictogram plus.png Agree 1. Everything looks okay to me, if it's easy to implement;
Pictogram plus.png Agree 2. I did take a look on some weapons, and I agree in using "Item icons";
Pictogram plus.png Agree 3. I saw the comments, and Andrew360's idea, and I agree, it has my vote;
Pictogram plus.png Agree 4. You got my vote, very good;
Pictogram minus.png Disagree 5. I agree with Andrew360 and Profiteer, I don't think that it's worth the work, considering there's already images below on the infobox, alongside the painted variants;
Pictogram info.png Info 6. It ends up being the same as "5)", however, I'd like to see an example how it would look like;
Pictogram plus.png Agree 7. I'm not sure if I noticed completely, but would that be switching the template from "Painted variants" to "Painted variants full" In several cosmetics, like how it was done in Brigade Helm? If so, I don't see a problem;
Pictogram info.png Info 7. An idea to the template. Wouldn't it look better if it was something like this, with 2 buttons? https://i.imgur.com/LVXXb4C Or is it being done currently like it's on the page so it's possible to compare both teams at the same time? Probably that;
Pictogram plus.png Agree 8. I like the idea, however, the information still continue to be too deep on the page, wouldn't be better to only show 4 or 5, instead of 9?;
Pictogram info.png Info 9. a) "An arrange of buttons that lets you change classes on the Styles table". In the example of Beaten and Bruised, the images wouldn't be anymore on the infobox, correct?;
Pictogram info.png Info I like "8)"'s idea, but if "9)" is applied, then number "8)" is discarded. Headphones style when? - User Gabrielwoj Signature 1.pngUser Gabrielwoj Signature 2.png - User Gabrielwoj Signature 3.png 12:16, 3 January 2024 (UTC)
I also replied to mgpt regarding some of his questions, so I had the following to say:
7) On number "7)", it would be including previews like how it's done on "Single Color" paint cans on the BLU team, even if when they are applied on the same area, the paint color looks identical to the RED team. Currently, we only use "Painted variants full" in cases of items that has different colorization between teams, such as the case of Stout Shako;
7. a) I liked the idea of including RED and BLU on the top, it would be very intuitive. Post-thoughts: After re-reading his thoughts on this one, I saw that the original idea would be buttons, while I first thought they were simply two sections that would separate the teams more properly, visually. I thought if maybe that by doing so, we could include a faint red and a faint blue background to separate them both, and make the template a little more nice to look at, as currently there's a bunch of paint variants all included in one table.
8) In regards to the default quantity, it would still be discussed, but the main idea would be something that could be expanded to show the remaining. I finished the Boarder's Beanie images, and the infobox ended up being very lengthy. The table for Painted variants will probably change if "4)" is implemented.
9) The images would still stay on the infobox section, but the idea would be that on the Styles table, it would include an array of buttons with each of the classes icons, so it could be changed, similar to what it has been suggested on "4)". The only thing that, if "1)" is implemented, the Styles section may not be as necessary anymore. Headphones style when? - User Gabrielwoj Signature 1.pngUser Gabrielwoj Signature 2.png - User Gabrielwoj Signature 3.png 12:16, 3 January 2024 (UTC)

──────────────────────────────────────────────────────────────────────────────────────────────────── 1 Pictogram question.png Not sure It sure would be easy to implement but I feel this would discount the usefulness of the class gallery or style section.
2/3 Pictogram plus.png Agree It would clean up the inconsistencies from the 2D weapon images and make them extremely consistent. The item icons are used all over the wiki in subtle ways such as in crafting recipes or in big lists of weapons but it's time for those to be the defacto 2D image for weapons. Bring Shugo-style to the infobox!
4 Pictogram plus.png Agree Adding the class icons in place of the class name plus sorting the paint table by class would greatly improve the user experience. (I always stress when uploading paint galleries with multiple styles that I may upload to the incorrect style/class)
5 Pictogram minus.png Disagree On top of remaking all the infobox images being an immense amount of work, I feel this would also take away from the usefulness of the style box.
6 Pictogram question.png Not sure I would be more open to this than #5 but I often find that the class gallery images often take me the most time to complete and be happy with. Trying to find good and unique poses and appropriate facial flexes for all 9 classes takes me a fair amount of time. I wish I was faster at it.
7 Pictogram question.png Not sure I kind of agree on this point but I feel it could just be on a cosmetic-by-cosmetic basis. Like we do now, I think, we could only implement this on hats that would benefit from a full paint gallery.
8 Pictogram plus.png Agree I agree with the others on this point, {{Tabs}} would be great for this. I am more for moving the class styles out of the infobox and moving them to the style box. I feel more and more pages suffer from having a long infobox with the inclusion of more all-class, multi-style hats. If they were moved to the style box with tabs, I think many pages would look a whole lot cleaner and compact.
9 Pictogram minus.png Disagree See #8
H20verdrive (talk) 01:22, 7 January 2024 (UTC)

I've been mildly intimidated, procrastinating voting on this for a week, but here we go:
1. Pictogram plus.png Agree Very good stuff.
2. Pictogram question.png Abstain Not sure about this, it might seem awkward on some items. Like others have said I'd want to see it first.
3. Pictogram plus.png Weak Agree Seems necessary, but I wonder if there's a more cohesive way to display them.
4. Pictogram plus.png Agree Looks nice, more visual and less clutter.
5. Pictogram plus.png Weak Agree Seems alright.
6. Pictogram question.png Abstain It seems a bit clunky and as someone said, might take a lot of work, but theoretically seems useful.
7. Pictogram plus.png Weak Agree As H20verdrive said, probably an item-by-item basis (maybe a "limited run" at first for the articles that need it most?) is best.
8. Pictogram plus.png Agree Looks cool; long infoboxes do need help, but I think it's most contingent upon all-class items.
9. Pictogram minus.png Weak Disagree As all others said, this needs tweaking and removing Styles might be too radical, BUT the "arrange of buttons" might work.
Overall, if I had to give a vote for the whole package, Pictogram plus.png Agree, with tweaking.--Leaderboard class allclass.png Akolyth (talk) 02:21, 10 January 2024 (UTC)
Well, we got a lot of responses with this discussion, thank you everyone for reading and replying. I guess we could start making some of these proposed changes? Ones that got the most positive votes, while discarding ones that didn't get much positive reception. Perhaps let's talk what should be the best options according to your guys voting. I don't have time to actually write up new template codes and stuff at the moment, however some already have templates available for that (#7), and others should be a little more straightforward in changing (I would imagine that including the Shugo style icons for weapons be quite straightforward, if that would go through). Headphones style when? - User Gabrielwoj Signature 1.pngUser Gabrielwoj Signature 2.png - User Gabrielwoj Signature 3.png 00:26, 27 January 2024 (UTC)
Swood suggested me to make a table having total votes from everyone:
Suggestion 1 Pictogram plus.png Agree: 7 Pictogram minus.png Disagree: 1 Pictogram question.png Abstain: 2
Suggestion 2 Pictogram plus.png Agree: 7 Pictogram minus.png Disagree: 0 Pictogram question.png Abstain: 1
Suggestion 3 Pictogram plus.png Agree: 9 Pictogram minus.png Disagree: 0 Pictogram question.png Abstain: 1
Suggestion 4 Pictogram plus.png Agree: 10 Pictogram minus.png Disagree: 0 Pictogram question.png Abstain: 0
Suggestion 5 Pictogram plus.png Agree: 4 Pictogram minus.png Disagree: 4 Pictogram question.png Abstain: 2
Suggestion 6 Pictogram plus.png Agree: 4 Pictogram minus.png Disagree: 1 Pictogram question.png Abstain: 4
Suggestion 7 Pictogram plus.png Agree: 8 Pictogram minus.png Disagree: 0 Pictogram question.png Abstain: 1
Suggestion 8 Pictogram plus.png Agree: 8 Pictogram minus.png Disagree: 1 Pictogram question.png Abstain: 2
Suggestion 9 Pictogram plus.png Agree: 2 Pictogram minus.png Disagree: 3 Pictogram question.png Abstain: 4

My own votings have been included too. I agree with all of the changes I proposed except "5)", which I only suggested since I already had some Style images laying around on my computer, ready to be uploaded if it were to be accepted. Headphones style when? - User Gabrielwoj Signature 1.pngUser Gabrielwoj Signature 2.png - User Gabrielwoj Signature 3.png 17:49, 31 January 2024 (UTC)

Userbox, and creator page

Hey! I have a question, how i add userbox and how i add some decoration to my page like evryone did ? Nonolemage (talk) 13:21, 8 January 2024 (UTC)

For userboxes see Team Fortress Wiki:User info boxes. Otherwise, the rest of the decoration is up to you. You may be interested in {{User infobox}}.
BLU Wiki Cap.png | s | GrampaSwood Praise the Sun! (talk) (contribs) 13:27, 8 January 2024 (UTC)
Thanks for the info box ! But how exactly i decorate my page ? Like how i use custom image or something like thats ? Did you have a page thats can help me to do this ?Nonolemage (talk) 13:59, 9 January 2024 (UTC)
Help:Images may help you with how to place images, for images to use, simply upload them using the upload page. The correct format for images only used on your User page is "User Nonolemage [file name]", so for example "User Nonolemage profile picture.png" or "User Nonolemage scout loadout.jpg". When uploading them on the upload page, include [[Category:User images]] in the summary box. This should be done for every image you want to use on your User page.
As for more complicated design, that is usually done using CSS and/or Javascript. I can't help you much with that.
BLU Wiki Cap.png | s | GrampaSwood Praise the Sun! (talk) (contribs) 14:08, 9 January 2024 (UTC)
Thanks you a lot ! You realy helped me ! Nonolemage (talk) 14:10, 9 January 2024 (UTC)

Civilian Image

Should we change the image of the Civilian ? Because it's the scout in A pose but the civilain got some real texture thats can be use and found Nonolemage (talk) 12:54, 11 January 2024 (UTC)

That is how the Civilian class looked when it was still available in TF2, Civilian (Classic) is the TFC version.
BLU Wiki Cap.png | s | GrampaSwood Praise the Sun! (talk) (contribs) 12:57, 11 January 2024 (UTC)
Oh, but i play a mod of tf2 (tf2c) thats show a finished model of the civilain so maybe i can add a picture of it in the galery for show what it looked finished ? Or it's not important ?Nonolemage (talk) 13:04, 11 January 2024 (UTC)
That's not an official version of it, that's fan-made. No Civilian model or textures has been made for TF2.
BLU Wiki Cap.png | s | GrampaSwood Praise the Sun! (talk) (contribs) 13:11, 11 January 2024 (UTC)

Weapon in user page

Hey it's AGAIN me ! I see some people have a list of weapon they used for evry class but i don't know how to do this, can someone help me ? Nonolemage (talk) 07:32, 14 January 2024 (UTC)

Well, you could try learning how to use wikitables, there are also templates like Template:Backpack item and Template:User weapon checklist you could use to this effect.
Luno 🪐🌕 Talk / Contributions / Team 03:20, 15 January 2024 (UTC)

Allweapons Nav template

Hi! I've created two mockups as potential replacements for the current Allweapons Nav template. I'd like to get your opinion. You can check out the templates on my sandbox user page (Nav 1 and Nav 2). The "Secondary" label for "All classes" in Nav 2 appears a bit off, and I'm having trouble fixing it. Thanks! Mgpt (talk) 02:59, 16 January 2024 (UTC)

I don't really see what's wrong with the current one.
BLU Wiki Cap.png | s | GrampaSwood Praise the Sun! (talk) (contribs) 11:59, 16 January 2024 (UTC)
Outdated/It's not a "real" nav like the others (Hat/Tool Nav). If someone else comments please compare both so you can see the differences Mgpt (talk) 16:05, 16 January 2024 (UTC)
I did compare both, but it doesn't exactly answer what's wrong with the current one. If people really wanted it changed I'd go for Nav 1, but I would still like to see stock and non-stock separated.
BLU Wiki Cap.png | s | GrampaSwood Praise the Sun! (talk) (contribs) 16:16, 16 January 2024 (UTC)
There's already a nav for them on the weapon page and stock is always the first (they can be in italic, would that work?). I personally prefer Nav 2 because it is actually a nav (not a table) but also consistent with Hat and Tool Nav. Edit: About the availability strings, they shouldn't be there, especially because they're outdated and were added more than 10 years ago. Definitely not the purpose of the template. Mgpt (talk) 20:11, 16 January 2024 (UTC)
I'd prefer for them to be separated regardless, if only in a little box above all of them or with a line separating them. Both the current one and both your versions are technically tables either way, I think a differently structured nav doesn't necessarily make it not a nav or somehow inferior.
BLU Wiki Cap.png | s | GrampaSwood Praise the Sun! (talk) (contribs) 20:39, 16 January 2024 (UTC)

──────────────────────────────────────────────────────────────────────────────────────────────────── Personally, I prefer Nav 1. I like the structure of the current Weapon Nav the way it is, I just don't like the availability strings cluttering things up, and the taunts needlessly listing which weapons they're for. Nav 1 simplifies things in a way that's easier to read, certainly. I'd also be fine with Stock weapons being separated, perhaps with a "Stock" header and then a line break before the others.

Incidentally, re: "the 'Secondary' label for 'All classes' in Nav 2 appears a bit off, and I'm having trouble fixing it."

  • That should be a "Melee" label, as you've probably realized by now.
  • It's looking off because the single list of weapons you've used isn't enough to fill out the space of the column. You'd need at least three lists to fill out the space that the "All Classes" column takes, so the single list you gave sits in the middle. — User ThatHatGuy Signature Icon.png 10:21, 17 January 2024 (UTC)
I made some changes, thanks for the input Mgpt (talk) 03:18, 18 January 2024 (UTC)
Nav 1 seems almost set to me, I like the Normal quality grey indication, while still being separated by slot. My only slight nitpick now would be that I'd prefer if the non-stock weapons were organized by release order -- at the moment, reskins of stock are still at the top of the non-stock section, which doesn't make as much sense, now that we've agreed on separating stock into its own box. — User ThatHatGuy Signature Icon.png 03:33, 18 January 2024 (UTC)
I initially added them randomly from the Weapons page, but I'll definitely reorganize them by release order :D I may scrap the all class section, the idea was not to repeat weapons, but we have the Shotgun, so... Mgpt (talk) 03:45, 18 January 2024 (UTC)
Updated the template Mgpt (talk) 19:01, 22 January 2024 (UTC)

About the 2023 leak

Hello ! Im a translator of the unused content and i see on the social media a leak from 2023 of some map and iteam thats has been abandoned or unfinished. So i was thinking if i can work on it for make some page on the unused content section. (The leak is from a valve employer) Nonolemage (talk) 15:52, 22 January 2024 (UTC)

As long as you source all of these changes and abide by the leaked content policy. This leak was also not from a Valve employee, as far as I know.
BLU Wiki Cap.png | s | GrampaSwood Praise the Sun! (talk) (contribs) 15:57, 22 January 2024 (UTC)
So if i understand, i donnt have the right to put any picture of anything if it's from a leak ? And by the way, how did the code for cited content from leak work ? And if it's not from a valve employer, from who it's from ? (Sorry for all my question and thanks for anwsering me ;-;) Nonolemage (talk) 16:08, 22 January 2024 (UTC)
Don't link to any places that host leaked content (so do not link to a Tweet containing a picture of a leaked model, or containing a link to a Google Drive with the leaked content, etc.), do not directly upload media of leaked content or copy-paste code, and do not link to or upload media of recreations of leaked content. All the information you put on the page should contain a reference to where you got it from (see the examples on the policy). It's likely someone with a Source engine license that leaked everything.
BLU Wiki Cap.png | s | GrampaSwood Praise the Sun! (talk) (contribs) 16:19, 22 January 2024 (UTC)
I understand, thanks a lot for your help again and i will do evrything you say ! Nonolemage (talk) 16:38, 22 January 2024 (UTC)

Community Medal Nav (closed)

I feel a bit lost with the medal scheme and how it has been handled. Where exactly is this template supposed to be used? I know that {{Hat Nav}} lists the same contents, which I recently updated. I think we should either use this one and remove the medal section from Hat Nav or just use Hat Nav, no? Thanks in advance Mgpt (talk) 21:28, 24 January 2024 (UTC)

With the ever-increasing MvM medals, we should remove it from the Hat Nav and keep this one. The Hat Nav will cause pages to be too large at some point.
BLU Wiki Cap.png | s | GrampaSwood Praise the Sun! (talk) (contribs) 21:29, 24 January 2024 (UTC)
Would adding an 'Other' section with two links for Community and Tournament medals work then? With this approach, we also need to update the "Competitive play" Nav. Also, both templates use images, is there a specific reason for that?
Edit: They're also cosmetic items, so they should still be mentioned, in my opinion Mgpt (talk) 21:40, 24 January 2024 (UTC)
I would put the 2 links in the hat nav, then keep the medal nav separately. The comp nav can get rid of it imo, and just having a tournament medal link. I prefer having this separate one.
BLU Wiki Cap.png | s | GrampaSwood Praise the Sun! (talk) (contribs) 22:07, 24 January 2024 (UTC)
I like the template, but it's too big. We don't need images for all the medals: they are exactly the same and this won't scale well if Valve ever allows new medals again (see comp nav). — Tark 00:16, 25 January 2024 (UTC)
Disagree with "they're exactly the same," they're clearly, almost all of them, not exactly the same, but I know that my opinions about all this don't matter too much anyhow. I would be fine with listing the names of the medals instead, but then they'd all have the name of the operation over and over again, and it would be very clunky to look at. That's how it was in the promo nav to begin with, and that's what I wanted to change -- but then, that would require extra name strings that are just "Shimmering Souvenir", for example, and Swood already said that was too much. The images were my way of compromising on that, considering the Competitive nav already did that, but then that's wrong too, so whatever, I can't do any of this properly. — User ThatHatGuy Signature Icon.png 03:47, 25 January 2024 (UTC)
They are all the same just with a unique hex paint the MVM ones have been reused over and over, there is no model difference between them other than the paint, If the medals were "different" they would have unique models to go alongside them, but back on subject, theres so many of these damn things it would be nice to be able to filter them out entirely.
Cheddar (talk) 13:57, 25 January 2024 (UTC)

──────────────────────────────────────────────────────────────────────────────────────────────────── By "exactly the same", I meant all the MvM medals that share the same model but have a different paint applied. An average user doesn't care if the medal is pink or green, they are way more interested in the model itself. The same applies to the comp nav: we don't have an icon for every season of each tournament, only for different models.
I personally don't see how extra strings are too much and I agree that the icons look way better than whatever is going on with the comp nav template. My point here is that this template currently is too big and has too much repetitive information to work as a navbox.
Also, I know that it is common for us to get attached to our creations (in this case, the template), but suggested changes to a template are usual business. Please don't take it personally, your opinions always matter. — Tark 14:06, 25 January 2024 (UTC)

If I remember correctly, the "too many strings" were in reference to another nav, where I suggested removing them and replacing them with links to the operation page's rewards section. There were a few medals for each operation with a link to the same section each time. Having too many strings was in reference to the promo nav, not the one we're talking about.
BLU Wiki Cap.png | s | GrampaSwood Praise the Sun! (talk) (contribs) 14:40, 25 January 2024 (UTC)
So if it's suddenly not too much trouble to localize different name strings for use within this nav specifically, for reasons I won't pretend to understand, nor do I care to ask about further, I propose that if we absolutely must, we strip the pictures and the paint splats, and in the case of MVM operations, we have the link to the operation, and then within that category, plain-text names of just the medals, stripped of the operation name and years, when necessary. (That is, "Operation Galvanized Gauntlet Bejeweled Bounty 2023" becomes "Bejeweled Bounty", and so on. Cleaner, easier to read, and you already get that it's supposed to be within that operation.
I would fight for the pictures, but it's clear that's not about to happen for me, and it's best for me to give it up and take the bullet, like I always have to. I'll believe that my opinions always matter when they start being correct ones to have. — User ThatHatGuy Signature Icon.png 14:54, 25 January 2024 (UTC)
ThatHatGuy I'm not against your template creation but I searched a little more and its being used with {{Hat Nav}} so we need to decide which one we gonna use, because currently, they have the same contents. Given the opinions above, I think a more neutral solution would be to move the Hat Nav contents to these two templates, so they stay similar to each other. Mgpt (talk) 18:35, 25 January 2024 (UTC)
That didn't matter when some of those event pages, for years, had both the Hat Nav and the Promo Nav on them. The Promo Nav, by definition, has the same stuff that's already on the Hat Nav. Community medals used to be listed individually on there too. Now all of a sudden, there's a new nav, that I made because Swood wanted to separate the Community Medals into their own page, and suddenly, that's something worthy of being dissected and put under a microscope.
Fix it how you all want. I've said my piece about it, but clearly I don't know what I'm doing. — User ThatHatGuy Signature Icon.png 00:53, 26 January 2024 (UTC)
closed given the recent discussion Mgpt (talk) 02:26, 31 January 2024 (UTC)

Trivias without confirmations

Since recent policy change now requiring trivias to have linked confirmations from contributors, there are still many old items that have trivias based on speculations (especially items made by Valve which can't really be confirmed). What should be done with them? User Denied signature.jpg Denied (Talk) 09:07, 30 January 2024 (UTC)

Leave them, we'd have to clear out pretty much most trivia sections otherwise. Unless you find proof of the contrary, just leave them.
BLU Wiki Cap.png | s | GrampaSwood Praise the Sun! (talk) (contribs) 11:02, 30 January 2024 (UTC)
What about this one? A promo item that directly references a game from said promotion, but trivia is about completly different character. User Denied signature.jpg Denied (Talk) 08:06, 31 January 2024 (UTC)
I believe it's a invalid trivia, though changing the name of character and game would be better compare to completely remove the trivia Profiteer the tryhard (talk|contribute) 08:20, 31 January 2024 (UTC)
"It is based on one of the male soldiers' hairstyles in the video game UFO: Enemy Unknown" in the first paragraph. User Denied signature.jpg Denied (Talk) 08:43, 31 January 2024 (UTC)
Yeah my bad, mention it 2 times is kind of surplus just remove it. Profiteer the tryhard (talk|contribute) 09:03, 31 January 2024 (UTC)
Promo items should have their reference stated in the intro, not Trivia. Feel free to remove, it is possible that the Crafty Hair is modelled after hair that is modelled after said character.
BLU Wiki Cap.png | s | GrampaSwood Praise the Sun! (talk) (contribs) 12:24, 31 January 2024 (UTC)

Reports/Missing template translations reporting erroneous data

It seems like a very handy feature (as handy as the entire reports page), and oddly enough, it seems to report the same thing for all languages (34 templates), and according to the quick look I did, none of them report missing translations?
I don't know who would be able to fix this, if it's even broken to begin with, maybe Darkid?
Do note that I didn't touch template translating very much in my time here, I looked up the line numbers using Notepad++. Luno 🪐🌕 Talk / Contributions / Team 03:05, 12 February 2024 (UTC)

For the first result it looks like fr is not declared in the {{Translation switching| line which probably leads to it showing up in that report. I'm going to guess it's the same for all the other ones. Jh34ghu43gu (talk) 03:10, 12 February 2024 (UTC)
I can take a look, thanks for the ping. Darkid « TalkContribs » 03:10, 12 February 2024 (UTC)
Damn, that was as quick as Dustbowl backcap, I sort of expected the "declare thing", but I doubt each of the members would forget to put it in, if that's the issue.
I would also expect hundreds of entries with varying results for every lang, not 34. Luno 🪐🌕 Talk / Contributions / Team 03:24, 12 February 2024 (UTC)
Hmm, looks like I might've screwed up when I changed the regex on Feb 1st (or at least, page history shows a major diff there). Fixing that now, should be corrected tomorrow. Darkid « TalkContribs » 03:59, 12 February 2024 (UTC)
+622,418 bytes coming through, seems about right! Looks like it's working again, thanks Darkid. Luno 🪐🌕 Talk / Contributions / Team 01:52, 13 February 2024 (UTC)

A technical request for "Used by" template

"Localized versions of this template are not necessary." Well, they actually are needed, due to inflection of words in some languages. For Polish, "{{Used by|all}}" and "{{Used by|Soldier|etc.}}" sound fine, but "{{Used by|all-except|" needs translation switching, as it sounds very bad when names of classes are not inflected. I don't know about other languages, but some may require it too. For Polish, here's how it should look to be grammatically correct (only for "{{Used by|all-except|"):

Scout = Skauta
Soldier = Żołnierza
Pyro = Pyro
Demoman = Demomana
Heavy = Grubego
Enginner = Inżyniera
Medic = Medyka
Sniper = Snajpera
Spy = Szpiega

User Denied signature.jpg Denied (Talk) 14:07, 14 February 2024 (UTC)

These requests should really be on the template's talk page instead.
BLU Wiki Cap.png | s | GrampaSwood Praise the Sun! (talk) (contribs) 14:13, 14 February 2024 (UTC)
Thanks. I've moved it there. User Denied signature.jpg Denied (Talk) 08:28, 15 February 2024 (UTC)

Where can I interact with the community?

Is there a discord or something to interact with the community? Thank You.

QS Quark (talk) 13:49, 23 March 2024 (UTC)

You can join the IRC if you want. There is no Discord (and we also won't make one).
BLU Wiki Cap.png | s | GrampaSwood Praise the Sun! (talk) (contribs) 13:59, 23 March 2024 (UTC)

April fool's?

I've been absent a bit because of health issues lately, sorry, but I noticed there's no April Fools thing this year there? :(--Leaderboard class allclass.png Akolyth (talk) 02:43, 2 April 2024 (UTC)

Probably, yes. Since I didn't notice anything relate to April fools event other than the page itself (normally there will be someone create a April fools sandbox page before April fools event).Profiteer the tryhard (talk|contribute) 03:45, 2 April 2024 (UTC)
The only thing that was planned was a patch, no other efforts were made, unfortunately.
BLU Wiki Cap.png | s | GrampaSwood Praise the Sun! (talk) (contribs) 08:17, 2 April 2024 (UTC)