Template talk:Hat Nav

Demoman's Fro

Should this be considered hatless or not? --Jordan 22:57, 8 October 2010 (UTC)

Do people on trading servers treat it as a hatless or not? But also, is the Demoman wearing a hat? For the former, I don't know. For the latter, definitely not. But he is wearing a headband, and the Sniper has a headband, and that's not hatless. In summary, I don't know, but probably not. yyler (talk) 16:40, 3 November 2010 (UTC)

Capitalization

Needs proper capitalization for names of hats. They're proper nouns. Words after the first one deserve a capital letter.

--Mhmm 03:40, 1 July 2010 (UTC)

No. -- Smashman... _{(t • s)} 03:47, 1 July 2010 (UTC)

I have a copy of the HatNav with capitalisation. All that's needed is the capitalised versions of all the hats to be moved to the non-capitalised ones before I implement it. I see you're getting on with some of that now, I'll help you. --RJackson 03:56, 1 July 2010 (UTC)

It seems consensus has been reach to change to proper capitalisation. Previously the policy was different to keep consistency. Feel free to update this template. -- Pilk _(talk) 04:01, 1 July 2010 (UTC)

Category: Hats

Currently the template includes Category:Hats on every page it is transcluded in. While this is, for the most part, a good thing, there are a number of miscellaneous items where including Cat:Hats is probably a bad thing, as they are not hats. It's been a while since I've used parserfunctions, and I'm a little rusty with them, but I believe something like the below would not include Cat:Hats if the parameter category was passed to the template args, and was not blank? I guess it could be expanded so that if the category parameter is passed then the value of the category parameter is the name of the category included, but I cant remember how the switch statements worked either.

{{#if:{{{category|}}}|<includeonly>{{lang cat|Hats}}</includeonly>|}}

In other words, could someone a little more experienced check it over before I go causing havok? Cheers. Lamb 22:08, 2 October 2010 (UTC)

Your syntax would work perfectly, however, it'd probably be better if we just remove {{lang cat}} from the hat nav altogether, considering that pages are placed in Hat and Misc categories automatically by the infobox. Thanks for the suggestion, though. seb26 [talk] 22:12, 2 October 2010 (UTC)

Fair enough, I had not noticed that the infobox also included the categories. Lamb 22:15, 2 October 2010 (UTC)

Splitting badges from misc. items

Just like hatless and polycount are separated from hats. Looks like crap here but you'll get the point.

--Kid Of The Century 16:34, 4 October 2010 (UTC)

Consider changing? This template is getting huge

Should we consider splitting this into several class-specific templates or similar? After the Polycount update, this has mutated out of control. It often takes up more space than the content of the actual pages now. ~ lhavelund ^{(t ▪ c)} 19:14, 13 October 2010 (UTC)

At the very least, I think the template should have a separate section for hatless items, like there's a category at the bottom for Misc. items. What bothers me most about this template isn't its size so much as it is flatout unorganized and just looks messy. I feel like just shifting things around and organizing the template would make it much more manageable in terms of size, but honestly I don't know much about editing templates so I'm afraid to mess with it myself. Evang7 17:57, 21 October 2010 (UTC)

Change from vertical table to horizontal list

I'm thinking that with the number of stuff there is now (and it'll only get bigger), it may be a good idea to lose the table format and put this template into more of a row-list format like this:

Looking at the current template, this idea takes up three-fifths the space (approximately) and doesn't have large blank chunks in the middle of nowhere. Maybe we could even use small icons, although that would look pretty cluttered. Toomai Glittershine 17:54, 28 October 2010 (UTC)

Uh, shall I bump this? (Large recent edit numbers have probably hidden this suggestion.) Toomai Glittershine 20:40, 29 October 2010 (UTC)

(Maybe Template:Allweapons Nav could also benefit from this idea, although since weapons need to be organized a bit more than just a bunch of rows it may not work out.) Toomai Glittershine 20:58, 29 October 2010 (UTC)

 Support-Shine[] 20:44, 29 October 2010 (UTC)

 Support: Also, maybe try adding mini-icons like for the weapons? Or would that make it too big again? --CruelCow 20:48, 29 October 2010 (UTC)

Icons would look cool, but I think it would look too big again if we have both icons and text. So it'd look like Template:Achievements. Toomai Glittershine 20:54, 29 October 2010 (UTC)

 Comment: It's not bad. The original template was sort of designed assuming the classes would have a fairly equal number of hats, and that Valve wasn't going to add several hundred thousand hats in the future. My only suggestion for this right now is to split the All column into two parts, which I decided to just edit into your suggestion if you don't mind. MK 03:52, 30 October 2010 (UTC)

Seems like a good idea. Toomai Glittershine 13:41, 30 October 2010 (UTC)

 Support We should do it right now. Daff 18:00, 31 October 2010 (UTC)

 Support Looks better and takes much less space than present template. It could be also useful for Template:Allweapons Nav. --Parseus ( | talk) 12:52, 1 November 2010 (UTC)

Is there a way to give this suggestion more exposure, so it can get more opinions? Toomai Glittershine 00:14, 1 November 2010 (UTC)

I have linked this page from the {{CentralDiscussion}} template which is displayed at the top of recent changes and on the Main Page. seb26 [talk] 04:30, 1 November 2010 (UTC)

 Support - I like this new look. Less blocky, easier to read names.--Focusknock s 19:32, 1 November 2010 (UTC)

 Er...: I would like to see just a little more space in between the rows, right now it looks kinda cramped. Also, the fact that classes without misc items take up only one line in the template bothers me. Still probably cleaner than what we have now. -The Neotank ( | Talk) 19:44, 1 November 2010 (UTC)

Alternating background color on the rows may make it more clear. MK 09:17, 2 November 2010 (UTC)

 Comment: Stick with the icons if we're doing a new one. Visual/Image recognition is a great deal easier on users than words, as the players can identify classes much more quickly by looking at the icons associated with each class. --Vaught 18:05, 2 November 2010 (UTC)

You mean like this? (points to change) Toomai Glittershine 21:28, 2 November 2010 (UTC)

Looks way better for me. --Parseus ( | talk) 17:36, 3 November 2010 (UTC)

 Comment Just wondering - could it be possible to use effectively translation switching with that list? It would be easier to maintain than it could be in the present version. --Parseus ( | talk) 17:54, 3 November 2010 (UTC)

While I don't really know much about translation switching, the code is a lot simpler compared to the current version, so adding the functionality in would most likely be easier. Toomai Glittershine 20:29, 3 November 2010 (UTC)

 Support Yesh, I like diz. We could change it to make the hatless follow the hats' release dates though (Example: Baseball Bill's Sports Shine coming before Troublemaker's Tossle Cap and after Baker Boy in the list.) -- OluapPlayer _(t) 21:24, 3 November 2010 (UTC)

Seeing as there is a bunch of supports with no opposes, should this be implemented soon? Toomai Glittershine 00:35, 4 November 2010 (UTC)

If you do, please keep in mind that it needs the new poker items added first. --CruelCow 13:09, 4 November 2010 (UTC)

Collapsible sections

These templates are getting very large now, so I say we have individually collapsible sections, obviously class sections and have the section for the current hat/weapon the only one open first. This way if a user is interested in a hat for another class they can simply open another section and it'll save plenty of space which is currently being entirely used up. Opinions? – Smashman _(talk) 23:20, 13 December 2010 (UTC)