Team Fortress Wiki:Discussion/Archive 35

The following discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.

See ya'll

Been fun contributing while it lasted, it's weird how there's no way to deactivate your account. ShadowMan44 (talk) 23:10, 3 July 2021 (UTC)

Goodbye, Pardner. I wish you luck and a merry life.

Lolimsogreat21 (talk) 09:41, 4 July 2021 (UTC)Lolimsogreat21

Random questions regarding the Wiki

I have a couple questions regarding the wiki:

1. With the Template:Steamid template in Item infoboxes, should there only be a profile ID, or should there be a set name for each creator? From what I've seen, some pages have only the ID as a parameter, others have and ID and a name. Personally, it seems like having WindBOT update the names seems ripe for abuse by scrupulous creators seeking to put inappropriate names onto the TF2 Wiki.
2. When tournament medal pages only have one medal, is a tabs gallery really necessary? Would it be sufficient to just have a normal gallery like cosmetic pages do? (Example of a page which could have just a gallery)
3. Some tournament medal (and other pages) seem to have Template:clr placed in place where it wouldn't make sense, though I'm wondering if there happens to be a reason I'm not aware of.
   • Example 1
   • Example 2; other game modes with only one map do not have clr on the same page

Memayz (talk) 00:53, 7 July 2021 (UTC)

Template:clr separates two floating elements. Just preview how it would look without clr in the example 2: In the example 1 however, not sure why it is there.

In order to keep consistency, it would be better to keep tabs gallery only in tournament and community medals pages · Ashe (talk) 01:35, 7 July 2021 (UTC)

I appreciate your input, I look forward to see what others think. I think page consistency is important, but in edge cases where only one medal is displayed, I personally think a regular gallery looks much better. Memayz (talk) 03:12, 10 July 2021 (UTC)

"Disambiguation" for names of weapons used in several languages

I propose this kind of "template" for redirects that are used in more than 1 language.

El nombre que estás buscando es usado en varios idiomas. Por favor, selecciona el idioma del artículo que desea ver.

O nome que você está procurando é usado em vários idiomas. Selecione o idioma do artigo que deseja visualizar. (USED GOOGLE TRANSLATE)

TRANSLATED: The name you are looking at is used in several languages. Please select the language of the article you wish to see.

• Español (Spanish)
• Português do Brasil (Portuguese of Brazil)

· Ashe (talk) 22:03, 8 July 2021 (UTC)

Unfortunately, language support was an afterthought. While it's allowed, creating language redirects is a bit troublesome. It confuses users and (translated) names change way more often than English.

Take this search for example: 9dXnvZi.png - They are perfectly valid for Portuguese, Brazilian Portuguese and Spanish. I speak Brazilian Portuguese, so the expected behavior is a pt-br redirect, but they're all for Spanish pages.

I personally dislike and disagree with this suggestion because it clutters the search bar to the point of rendering it useless and unhelpful. Languages with different alphabets and writing systems (Russian, Chinese, Japanese and Korean) are the only ones that are able to make good use of this feature. — Tark lm(pt-br) 22:21, 8 July 2021 (UTC)

Alright, i didn't consider the search bar, but my idea was for people that use the url bar for search articles, like https://wiki.teamfortress.com/wiki/Pistola. What did I proposed isn't a language redirect, is basiclly a disambiguation.

In fact, if someone search via the search bar "Pistola" and opens the article Pistola expecting to find the article in his language, then he would see this disambiguation and would click in the article in his language · Ashe (talk) 22:39, 8 July 2021 (UTC)

List of Self-Made item owners revival

The List of Self-Made item owners page, part of a group of other lists, was recently deleted outright for being too outdated and too much of a hassle to deal with. Before this, I started drafting a remake of the page on my userpage.

I would really like to see this page get remade, but the format has to change at least in some capacity. There's a few issues, and I'll list them along with possible solutions.

• ISSUE 1: There's way too much to document, and some of it changes a lot
  
  • Right now, you have to get backpack links for every single person and every single Self-Made item they hold. That's a lot to document.
    
  • An item's backpack link will change if the item's state is changed. This includes, but isn't limited to, things like changing the name or description, painting, or adding a killstreak effect.
    
  • Inventories can go private or unprivate at any moment.
    
  • This applies to every list, as well.
    
    

SUGGESTED CHANGE:
Remove the backpack link section altogether. It feels like way too much of a hassle and not many people come to check them out anyway.

• ISSUE 2: The page is too big, loading and saving changes takes too long
  
  • Due to the page's size, even in the currently incomplete state that my remake is in, takes long to load and to save changes when editing.
    
  • This will become even more of an issue as updates to the page go on.
    
    

SUGGESTED CHANGE:
Split the list into multiple pages. This is necessary at this point, considering my remake hasn't even passed the 2012s yet. There's multiple ways we could split it. Currently, the list is everyone in one page, in order of when they first had an item added into the game. This means there's no duplicate entries of people. There's a few ways we could split it up:

• Alphabetically (No duplicate entries, could still be a lot to handle)
  
• By year (Duplicate entries, would be easier to handle)
  
• By update (Duplicate entries, not recommended as some items were added in completely random patches)

Me and a lot of others would like to see this page alive and updated. I want that to be done as efficiently as possible. Please discuss. ~ Boba 19:50, 10 July 2021 (UTC)

The rework of the list documenting the self made item owners was a long time coming, its very nice to see someone taking the initiative. I think that the idea of sorting it by year is the best one out of the three given, at least I would say so...Anyway, I'm quit busy right now, but I would certainly like to help you with that project of yours. Care to give instructions? Lolimsogreat21 (talk) 20:23, 10 July 2021 (UTC)Lolimsogreat21

Right now, I just need a general idea of what should be done here. I'm waiting for more people to reply. Thanks though, I'll let you know. ~ Boba 20:44, 10 July 2021 (UTC)

I have considered a lot of possibilities, including the ones you suggested above, before accepting the delete proposal. The page barely had any traffic, it just wasn't worth it.

First things first: Why should we restore this list? Apart from being outdated, the page was deleted because it was useless and because there are dedicated websites for item lists out there, such as tf2tools.net. — Tark lm(pt-br) 21:41, 10 July 2021 (UTC)

First off: by that logic, all the other item list pages should be removed as well. TF2Tools chugs far behind by months, sometimes provides incorrect dates, and even just skips certain people entirely (you'll especially notice that with the few recent updates, there's quite a few people missing). There’s no doubt that the low traffic of the page was in no small part due to how outdated it was. I genuinely believe this page can still be salvaged. If all the other lists should stay up, which I believe they should, then this should come back up as well. The point of the TFWiki is to be a one-stop-shop for all TF information, rather than just being a hub to point you to other sites which can't be as reliable. I have the intention to spearhead this and get it to a point where it will never become as outdated as it was again. I’d need others, including the staff, to back me on this. The majority of the technical work is already done - I remember you specifically even helped me with building up the template it uses to make it more suited for the rework. All it needs is approval and a decision on what to do in terms of the issues, and then I can chip away at it until it’s done. With that being said, I want people to contribute to this discussion giving their opinions on what should be done with both the backpack links and splitting up the page. ~ Boba 22:41, 10 July 2021 (UTC)

I accepted the delete request because it wasn't useful and a burden to update. I still fail to see a reason to keep and maintain such a page, especially considering its low access rate, ever-increasing size and lack of proper maintenance in the past. — Tark lm(pt-br) 03:27, 11 July 2021 (UTC)

All of the issues you've just mentioned would be fixed with this rework, and I've even said so before. I'm sorry you view it that way. The very least you could do is give the feedback that I requested. ~ Boba 04:58, 11 July 2021 (UTC)

It's good to know that someone is fixing these. Personally, I support remove the backpack link section and change them all to alphabetically sorted. I do check these pages sometimes, but it's more of just for fun like just to see "who contributed the most?"
From the readers' view, what's their purpose to visit these list? If I have to actually to find who made the item, I could just open that item's page and there's contributors list in the page. If I have to find the person's all contributions, I know their name and I could easily find the person in the alphabetically sorted list. Break them into year or update could make doing these more harder because you have to figure out the which year or update first.
With that said, what about the {{Backpack Item Link}} in most of the item pages? They also contains backpack IDs, It's painful to update these and you have to do it in all the languages' pages. Do we have to also remove the backpack IDs from it? or is it possible to somehow merge them, like make a dictionary or "database", so the item page can automatically read the contributors from there, and all the item list also read the data from there? --Alex┋T 03:49, 11 July 2021 (UTC)

You bring up some good points, but by that logic things like the List of Electric Badge-aloo owners should be removed as well, because the Electric Badge-aloo has all of the contributors on the workshop page.

{{Backpack Item Link}} is simply just an easy way to display backpack links and nothing more. It will not automatically update when backpack links inevitably get updated. ~ Boba 04:58, 11 July 2021 (UTC)

As you said above "The point of the TFWiki is to be a one-stop-shop for all TF information", pages like "List of Electric Badge-aloo owners" could still exist so people know who has that item. Maybe there's situation that a contributor listed on steam workshop did't get the item? Or someone not listed on steam workshop contributor list get the item too?
Oops it looks like that breaks what I said above, you can't reliably find the contributors from the item owners list. How the lists is gonna be sorted is down to what purpose people visit these lists. Since these lists are owners of special items, people will more likely want to know 'who' owns one items' self-made version from this lists, then sort from the items' name instead of contributors' name alphabetically may be better (and also solves problem of contributors changing their name and mess up the list). --Alex┋T 07:31, 11 July 2021 (UTC)

some template use italic to indicate title name is wrong in some language

Meet the team video is linked in every classes' nav template, such as Meet the Medic in the Template:Medic_Nav. It uses italic to indicate the title name of a video.

In Simplified Chinese, however, uses “Guillemet” or “double angle brackets” to indicate the title of a book, video, article, song. Use italic to indicate these things in Simplified Chinese is wrong. Many other language uses different way to indicate similar things too.

 Meet the Medic
 拜见医生
 《拜见医生》

Should we make a template that can display appropriate marks depends on language in these places? Or such template already exists in this Wiki? Or should we just fix them by using {{lang}} in every template that have such issue?

--Alex┋T 10:02, 21 July 2021 (UTC)

Seems like a template similar to {{dec}} is sufficient.
GrampaSwood (talk) 10:17, 21 July 2021 (UTC)

Made a template, I only added support for zh-hans and zh-hant, By the way, I'm not sure if other language follows the same rule, what if one language uses different punctuation to indicate book title and video title?--Alex┋T 11:16, 21 July 2021 (UTC)

Translated meet the team videos

So recently I noticed some pages use an unofficially translated (subtitled, not dubbed) video on their meet the team videos. I recently changed this, however I thought it may be possible to replace this with a video on the wiki channel that has subtitles for several different languages (All taken from the transcript on the pages, for example). For any users that we do have that speak the language, they could verify it. Not sure how the other languages could be done (Perhaps STS could assist, not sure if they want to though). This seems like a way better option than replacing them with unknown people's translations.
GrampaSwood (talk) 17:35, 24 July 2021 (UTC)

 Support ~ Boba 18:23, 24 July 2021 (UTC)

 Support · Ashe (talk) 18:36, 24 July 2021 (UTC)

 Sounds great. Maybe we should only add the languages that someone verified, and leave others until someone did so. Looks like a pretty big project there.--Alex┋T 03:11, 25 July 2021 (UTC)

 Support Dereko supports, with concern that how we will execute it in terms of action. For Simplified Chinese, translated videos (which are qualified in my perspective) from personal channels have been inserted on video pages since resources from Bilibili became available, for the cause that those videos have never been officially uploaded on Bilibili. Of course the only "official" for the trailers should be those who originally created them, but inserting videos translated and uploaded by us still means something -

What I am more worried about is the example brought by the use of personal sources, which may produce unwanted results without proper principle. Thus, translated videos uploaded by Wiki channel may not provide more help to viewers, at least for most Chinese players, but it will make a lot of sense for our content management. 10:01, 25 July 2021 (UTC)

Unused content policy

Should there be an unused policy content? I personally think content that wasn't publicly released by Valve, or at some point available through TF2's files, should not be hosted on the wiki. It's very hard to verify that these are actually legit without directly linking to the hosted stuff itself which Eric Smith has said should not be done. An exception for this is referencing the recent 2020 code leak, as we've also gotten permission to say "This is from the 2020 code leak" (but nothing else).
GrampaSwood (talk) 18:10, 4 August 2021 (UTC)

 Support code snippets, leaked models, etc. should not be allowed. ~ Boba 18:12, 4 August 2021 (UTC)

 Strongly oppose It should stay, and you should provide proof of that email with Eric S. The content is verifiable and has patch date information for when it was found and added. The reslist stuff was recently found to be added when cp_degrootkeep was for example. It's literally not hard at all to verify this stuff. Just because you two have some predisposition against a user that doesn't edit here anymore (but does write up edits for me to make on his behalf, yes I saw your not so sneaky tfwiki-staff discussion) doesn't mean an entire subsection of already well-documented and verified info should be removed. Grow up. Thefixer2021 (talk) 18:16, 4 August 2021 (UTC)

No need for the aggressiveness and this is nothing against 404, however, this is ban evasion. Eric mail, it wasn't a sneaky discussion either because it is a publicly logged channel.
GrampaSwood (talk) 18:22, 4 August 2021 (UTC)

This only covers leaked source code, the June Build is a leaked pre-release build, as such it would not fall under these restrictions K1ngD3D3D3 (talk) 18:28, 4 August 2021 (UTC)

No aggressiveness intended. Intonation is impossible to get through text alone, mind. And I fail to see how having someone else write edits and pass them on to me is ban evasion. I was not the one banned. The logic fails. Thefixer2021 (talk) 18:27, 4 August 2021 (UTC)

Are you sure 404UNF is coming to you to make edits here? Because from his contributions on TCRF, it sounds like you came to him to make edits. Your story's logic fails. ~ Boba 18:33, 4 August 2021 (UTC)

Most of the stuff that Thefixer2021 was posting is coming from TCRF which is a site that documents cut content in video games, unfortunately, most of the TF2 articles are written by 404UNF. K1ngD3D3D3 (talk) 18:35, 4 August 2021 (UTC)

Following the original thought on this chain -- a leaked model (to use a concrete example) feels very similar to leaked source code. Sure, it's not text and can't be opened by a simple program, but it's just data that was extracted from the game.

If it enriches our understanding of the game (e.g. by shedding light on design decisions or showing the development of a map) then I feel that it has a place on this wiki. However, much like the guidance we have on leaked source code, the content should not be hosted on this wiki.

Also, much like content that is readily accessible in the game, this wiki is not trying to re-host all of the game's content. In my opinion, cut or unused content is no different from regular content in that regard: it should not be uploaded "just because we have it".

Regardless of our decision, I think we should have a TFW: page documenting the policy (TFW:Unused Content Policy sounds good to me), and also a template which we can use when citing said content (that links back to our decision).

Darkid « Talk — Contribs » 03:14, 5 August 2021 (UTC)

 Strongly oppose This shouldn't apply to builds which have game assets such as the June 2007 build, it was leaked after the 2020 code leak and the email, and should not fall under these restrictions. The email only mentions code assets cannot be posted. K1ngD3D3D3 (talk) 19:23, 4 August 2021 (UTC)

Damm, this discussion quickly derailed into something not quit related to unused content.

Lolimsogreat21 (talk) 19:34, 4 August 2021 (UTC)Lolimsogreat21

This applies to anything that is not released by Valve itself or not accessible through the in-game files (Old or new). The e-mail did not specifically mention anything else but it also goes without saying that this stuff that wasn't put out by Valve shouldn't be here. Unless Valve specifically mentions it's allowed to be posted here and to what extent, it should not be hosted or linked to in any way here (and anything that is on the wiki that falls under this should be removed).
GrampaSwood (talk) 19:36, 4 August 2021 (UTC)

This is derailing the discussion, if either of you want to continue this I'll gladly do so on my own talk page. But keep this on-topic. I'll open up a topic there.
GrampaSwood (talk) 18:35, 4 August 2021 (UTC)

I wish to have some clarification. Just what is "unused content" in this question?

* I first thought you were asking about unreleased content? (The more I think, no.)

* We have several Category:Unused content pages about Valve's abandoned developmental content with its own Template:Unused Content Nav; these seem to be long acceptable to the wiki.

* Then there are the many unused content sections in serveral different types of articles:

* e.g., Botkiller_weapons#Unused_content, Stahlhelm#Unused_content, Engineer_taunts#Unused_content, Mercenary_Park#Unused_content, etc.

* You are probably not talking about Category:Cut content; but, which has some overlap with Category:Unused content, and Category:Beta and unused content.

To me, unused content has specifically meant content found in game files that are not present in any form of game play, regardless of the reason it it is not present in play. But from your openting sentence, you seem to mean something very different.

Even so, such coverage of the above sorts of unused content hasn't been a problem, as far as I understand.

Really, do you specifically mean Valve Intellectual Property that Valve did not publish with intent of making available to the Community under terms of use? All patched game content is Valve IP, but it is published IP. Even if it is in the published game files, it is published IP; even if unused. It is unpublished IP if it is found in anything besides Valves intended publications, whether someone leaked images, video, memos, or source code, stole development configurations of game files, or snuck some phone video; each of these is broadly illegal, as I understand, as least in my business.

Would the term non-free content be useful here? We have applicable policy on that.[1]

However, whether or not any unused content of any particular type, fair or illegal, is covered as a topics in their own right is completely separate from the question of using published or unpublished material (especially unfree material) to speculate about the pre-release development history and the obvious fact that maps change in during development, and listing any evidence (published or leaked) of such changes is essentially XofY. This could be a separate discussion.

M I K A D O 282 ⊙⊙⊙⊙⊙⊙ ⊙⊙ ⊙⊙ (talk | contribs) (Help Wanted!) 04:18, 5 August 2021 (UTC) 13:14, 5 August 2021 (UTC)

It would really be any kind of content, unused content is just the broad name of anything that has gone unused in the game. This includes unused content in the game's files, hence why I made the separation for content that is, or has at some point been, in the game's files. Unused content such as unused voicelines that remain in the files are therefore perfectly okay to use. Content that has been gathered from a build of the game from 2005 (for example) would not be okay to use, because it's content that Valve did not intend to get out. Unless Valve says so otherwise, any of such content should not be hosted on a Valve-endorsed space.
GrampaSwood (talk) 13:22, 5 August 2021 (UTC)

 Agreed ^^ with this last statement ^^ · Ashe (talk) 20:29, 5 August 2021 (UTC)

Mikado has got the right idea. The primary concern about leaked content here is that hosting licensed, private (non-free) source code and/or assets are essentially a form of redistribution of paid software and/or to publish a trade secret, both of which are considered an illegal act, and Valve could take legal action if they deemed it necessary. Yes, unused/unreleased content that exist in the game files are fine to document, and beta content should be fine as well, so long as it is under published IP. The TF2 source code is a trade secret, and we've only been permitted to reference it, as cited by Eric S. in that email.  Wookipan (talk | contribs) 21:24, 6 August 2021 (UTC)

I agree with Wookipan (and therefore, with Mikado). As much as I love unused content, it's not supposed to be here. This is the official TF2 Wiki, afterall. This Wiki is also hosted by Valve themselves (as far as I know), leaked content should be (and is) a big no-no. - ▪ - 23:24, 6 August 2021 (UTC)

 Switzerland Sorry for being neutral here but my open source bias is known and incompatible. I will say that Valve expects us to document as fans are wont to do. And they only ever say what is required to mitigate their legal risk and therefore profit. My opinion before has been more or less that we should abide by their requests in good faith, but don't go overboard to make them happy. They pay lawyers to figure out exactly how to mitigate their legal risk about these things while also staying sane in their instructions to us. My personal view on it is: Documenting historical content is important and useful. So long as we can verify that it came from the game itself and was in fact in the dev pipeline at some stage. Can't staff hold a quick consensus meeting on such things to cleanroom verify that the content does exist and in the game? It's the usual wiki-thing to do. Valve themselves probably appreciate it too. Or at least they damn well better unless they don't like keeping memory of their own accomplishments and growth. Like some kinda dweebs. *looks pointedly at no one in particular* -- Lagg 05:58, 8 August 2021 (UTC)

(Forgive the not voting because I have trouble parsing the proposal.) About the time I encountered a moose on the trail (OK, maybe it was miles and maybe a day before I was within a few meters of a momma moose and her calf) I think I figured out what Grampa Swood was after. As far as I understand this, under the broad term of "Unused content", there is content that is acceptable for use in the wiki (typically publicly accessable in the Patched game files) and there is content that is not acceptable, but this distinction is not clearly defined in our policy. We do have relevant policies on the subject, but because these policies are on narrower focus pages, the edit-lawyer may claim that they don't apply to such-and-such. For example: 

• Image policies describe exclusion of non-free images, but the same rules should apply to all uploaded content.
• Trivia policies expressly exclude speculation; but, generally all of this wiki should avoid speculation.
• Unreleased content policy / prerelease content is already excluded from Cosmetics and Trivia. 

So, just carefully write the policy to define exclusion of non-free content, particularly everything and anything of Valve's IP that could never be accessed by users under either Premium or FTP license.

@Lagg: Wikipedia has something of open source underpinning AFAIK, but with the realization that assuming a fundamental right to self-ownership. So, if I may vamp, only the self may free what is self-owned; from which follows the concept that anyone may free what they own, but only what they own. I may free what is of my self, but I may not free anything that is of Lagg's self. M I K A D O 282 ⊙⊙⊙⊙⊙⊙ ⊙⊙ ⊙⊙ (talk | contribs) (Help Wanted!) 01:24, 15 August 2021 (UTC)

OK, but what should we do with Invasion? In fact, all the information, with the exception of concept arts, we have from a huge leak in October 2003. The developers mentioned this only in passing when they mentioned the creation of the TF2 style.

PrisonShift3r (talk) 19:22, 19 August 2021 (UTC)

Interesting question. I've never really questioned the ancient page, but never really looked deep into it; it is enough for me to know that Invasion existed for a while, and, especially, that the particular appearances and personalities of the TF2 classes originated in Invasion.

We have established that leaked content may be referenced, but, I am concerned with the sparse sourcing and citation. I think it is possible to find and cite more developer comments.

My concern is about proper licensing on the images. The many class images that were copied from Valve's official TF2 gallery are fine for us to use, but their description files probably don't correctly cite that attribution. Also, without researching in detail, I suspect some are screenshots of leaked content, which were are not supposed to use.

Perhaps you could invite Darkid to comment.

M I K A D O 282 ⊙⊙⊙⊙⊙⊙ ⊙⊙ ⊙⊙ (talk | contribs) (Help Wanted!) 02:36, 25 August 2021 (UTC)

Volunteers for First Cloakening(TM) now accepted

I don't want to put anything on the IRC channel page until I know what actually happens once I send Libera staff a cloak request. I've never actually used a cloak myself despite literal decades of IRC because I like my domain. So kind of new to this bit.

If anyone wants a cloak (the thingy that makes it so you have tfwiki/editor/lagg instead of your IP address) put me the name you want here. Try to keep it close to the wiki name since that's the whole spirit of project-namespaced cloaks. -- Lagg 06:34, 8 August 2021 (UTC)

I volunteer as tribute -- how about darkid? Darkid « Talk — Contribs » 03:28, 9 August 2021 (UTC)

I volunteer as the most active TF Wiki contributor atm, name tidb { TidB | t | c } 14:51, 9 August 2021 (UTC)

Sent and IRC / cloak request sections restored. -- Lagg 15:02, 9 August 2021 (UTC)

I volunteer as the man who "lives and breathes the wiki" (Quote I saw in a Discord once), name grampaswood.
GrampaSwood (talk) 15:04, 9 August 2021 (UTC)

Additional templates for punctuation

I would like to propose templates for opening parenthesis, closing parenthesis, and colon - something like {{op}}, {{cp}}, and {{colon}}, respectively.

Japanese, Simplified Chinese, and Traditional Chinese have their own characters for parenthesis and colon. While French uses the same characters, colons are isolated in sentences (unlike other languages that have it stuck to the end of the word right before it).

- BrazilianNut (talk) 03:09, 19 August 2021 (UTC)

 Agreed. Also, for example, "5 seconds" is «5秒» in japanese, without space, so {{space}} should exist too · Ashe (talk) 03:26, 19 August 2021 (UTC)

Combine parentheses templates to one could be easier to use, like {{Title}}. About a space template I don’t think that’s necessary. There’s not much place we could use that template, and most of time we could ignore that or could be manually fixed. --Alex┋T 03:58, 23 August 2021 (UTC)

Launch Options

I would like to elaborate on certain launch options so I have a request: Would it be okay to start making pages dedicated to certain launch options like:

 -insecure - Disable Valve Anti Cheat (VAC). 

The insecure part would link to a page that would:

1. Lead to a page about insecure mode

2. Would provide helpful info on how to use it

3. Have proper formatting and links

Can I create pages like these for people who want more info on something? CodingIsFun (talk) 16:01, 10 September 2021 (UTC)

It sounds like they'd be very small pages that wouldn't really be worth all having an individual page.
GrampaSwood (talk) 16:41, 10 September 2021 (UTC)

Could I still add pages that I definitely think need more detail?

CodingIsFun (talk) 16:46, 10 September 2021 (UTC)

The best thing would be to make the pages on your sandbox and then we can see how large the pages approx. are. However, that can lead to a lot of wasted effort if it turns out to be not worth it.
GrampaSwood (talk) 16:52, 10 September 2021 (UTC)

I'm relatively new to customising my account, how does a sandbox work? And how do I make custom pages on the sandbox?

CodingIsFun (talk) 17:02, 10 September 2021 (UTC)

Simply take your user page URL (https://wiki.teamfortress.com/wiki/User:CodingIsFun), add a / and type whatever. For example, https://wiki.teamfortress.com/wiki/User:CodingIsFun/Sandbox. Internal links work too, User:CodingIsFun/Sandbox. "Sandbox" can be anything, such as User:CodingIsFun/insecure. Just create the page on there, and that's a user space page.
GrampaSwood (talk) 17:05, 10 September 2021 (UTC)

Can I turn that into real page once I'm done?

CodingIsFun (talk) 17:34, 10 September 2021 (UTC)

It's better to link them here once done so people can take a proper look at what the pages would look like. Like I said, it may result in wasted effort.
GrampaSwood (talk) 17:46, 10 September 2021 (UTC)

Creation of "Boss" category

I've been surfing through the pages for the Halloween map bosses, and I find it a bit weird that they're all labelled as "other" in categories instead of having their own dedicated category for bosses. Does anyone else feel like this would be necessary/helpful at all? GoodMudkip (talk) 16:05, 21 September 2021 (UTC)GoodMudkip

  Sure! Feel free to create it. — Tark lm(pt-br) 17:25, 21 September 2021 (UTC)

Thank you very much for the go-ahead. However, I'm still somewhat new here, and I don't know how to create a new catagory. Is there anywhere on here that I can look that will teach me how to make one? GoodMudkip (talk) 15:47, 22 September 2021 (UTC)GoodMudkip

Simply add Category:Halloween boss to the appropriate pages, then go to this page and simply create the page with something such as "A list of all Halloween bosses".
GrampaSwood (talk) 15:52, 22 September 2021 (UTC)

Thanks for elaborating. I'll get right on it! GoodMudkip (talk) 16:23, 22 September 2021 (UTC)GoodMudkip

In ancient times our pioneers established a category for this: Category:Halloween bosses, with boss articles you may want to edit included in its subcategories, thus a new category shouldn't be added. Dereko thanks you for pointing out this anyway. 11:19, 26 September 2021 (UTC)

I totally missed that! Thanks for noticing it, Dereko. — Tark lm(pt-br) 04:46, 29 September 2021 (UTC)

Dereko´s plans to cleanup Halloween category

Based on findings from topic "Creation of "Boss" category", Dereko considers Category:Halloween bosses a bloated template, as there are too many pages inside making it difficult to have a convenient search.

Dereko believes the source of the problem is that we have put a lot of articles into the main category and its sub categories at the same time, while doing so would make main category more swelling and subs less useful.

In light of this, Dereko suggests making a cleanup to the category, that is to keep those pages in sub categories only. For example, we could remove Cauldron from Category:Halloween while keeping it in Category:Halloween maps.

If approved by people, when the school network conditions turn better, Dereko would be happy to handle the task as a valuable change to go practise medicine experience. 11:56, 26 September 2021 (UTC)

Agreed, it's just a mess of collapsible categories.
GrampaSwood (talk) 12:39, 26 September 2021 (UTC)

  Let me know if you need any help. — Tark lm(pt-br) 04:45, 29 September 2021 (UTC)

Mobile Support

as anybody who's opened the wiki on mobile will notice, the wiki is... not well-suited to mobile browsing. there's a limit to how good it can be, but at the very least, we could implement something along the lines of what Wikipedia has. I'm willing to personally put in the work to make this happen (though I doubt I'd be quick about it). thing is, I doubt I have the necessary permissions, and I don't really know where to start even if I do (though [2] seems like a good bet). I guess I'm just starting a petition to get somebody to implement a mobile version of the wiki. Kestrelguy (talk) 15:09, 27 September 2021 (UTC)

Maybe you should put your request at Team Fortress Wiki talk:Technical requests. --Alex┋T 03:36, 28 September 2021 (UTC)

you're right. it just didn't occur to me. Kestrelguy (talk) 02:07, 29 September 2021 (UTC)

Thanks for raising this issue. Mobile support is something I'd like to improve as well, but introducing new extensions is a challenge, partly because our server administrator is quite busy.

Until a proper extension is installed, we could implement a few CSS and JS changes to better accommodate mobile visitors. Assuming you are familiar with using the wiki on mobile, can you provide some examples of what works and what doesn't? We can't do a complete overhaul right now, but we can at least try to improve the experience.

Thanks! — Tark lm(pt-br) 04:59, 29 September 2021 (UTC)

Here are some suggestions I have:
1. Device without a mouse cannot see the information under the {{tooltip}}. TF Wiki uses this template in various places. Potential plugin to fix this.
2. Left sidebar cannot be hidden and takes up huge screen space on small vertical screen.
3. Text/web content won't resize automatically on my iPhone with Safari. It shows the whole desktop style page with small content, you have to zoom in and constantly move the zoomed web page to see the contents.
--Alex┋T 14:14, 29 September 2021 (UTC)

As Tark said, I don't think we're going to install any plugins, but we can definitely look into alternative sidebar styling, and fix {{tooltip}} -- both of these should be addressable with just CSS/JS. The overall page rendering (text size / mobile layout) is not something we can easily change without a large overhaul.

Darkid « Talk — Contribs » 11:15, 1 October 2021 (UTC)

That's at least something that will improve the experience on touchscreen tablets. I enjoy browsing the TF Wiki on my iPad, but there's {{tooltip}} in many charts, that the information under it is invisible without a mouse to hover on. Hope you could tap on it and do the same thing instead. Sidebar hiding is also useful in every vertical screen. Page resize is pretty critical to phone browsing, I don't like that mediawiki mobile plugin either, it changes almost everything and looks bad. Most of the people only browsing the Wiki on the mobile. I think some simple text auto resize, and picture or chart auto rearrange is enough for browsing the Wiki for now. --Alex┋T 06:13, 2 October 2021 (UTC)

the sidebar isn't a huge problem for me on Android with Firefox, but the whole lack of page resizing is a problem for me, too. this also results in a lot of buttons that are too small for fingers to click on. I can't go to my watchlist, for example, without zooming in like 600%. Kestrelguy (talk) 01:03, 1 October 2021 (UTC)

I'll only say that I'm not a fan of Web 2.0/"modern" web design in general. Most sites' mobile forms are frankly trash or mediocre-at-best, and have an annoying aesthetic; often the mobile theme is slower than desktop (even when using a browser like Brave that stops ads etc.)! On Wikipedia itself I use an alternate theme for editing with a "vintage" (without looking primitive) aesthetic, since Wiki's mobile theme isn't terrible but is still kind of queasy and irritating. If TFWiki adopts a real mobile theme, please please please keep the "feel" of desktop mode, with all its sharp edges and shading, and don't over-simplify it. I promise I don't mean to sound abrasive, it's just sickening to see so many sites follow the leader of flabby rounded minimalism, when a mobile theme ought to inherit its philosophy from the source (desktop site structure).-- Akolyth (talk) 01:25, 1 October 2021 (UTC)

The "modern" design shouldn't matter tbh. Even TF2 has changed its design in the main menu. The TF2's 2012 main menu looks way different to the 2021's main menu for example · Ashe (talk) 04:37, 1 October 2021 (UTC)

I'm not a huge fun of the modern rounded design that some modern programs force more and more either. I fully support more mobile TF wiki support, however I do, also, wish the style was kept the same as desktop. I'd also like to add that I haven't really had a problem with the current mobile wiki and the buttons (even really small ones) are surprisingly clickable I also main Sniper, so maybe I'm just accurate.
GrampaSwood (talk) 13:58, 1 October 2021 (UTC)

The wiki need's an update.

i know this can be a bit repeating subject, but when will our wiki get updates? eg dark mode, wikipedia style (more modern in my view.), what do we need to do to does this happen?

MaxwellWagner (talk) 14:08, 7 October 2021 (UTC)

If you'd like to request anything specific, try Team Fortress Wiki:Technical requests. I don't really see what needs updating on the wiki other than cache servers. The styling looks fine and nothing outdated about it, besides the mobile support which has already been discussed above.
GrampaSwood (talk) 14:20, 7 October 2021 (UTC)

Wikipedia Manual of Style and Hyperlinks as Section Headers

recently I happened to be reading Wikipedia's Manual of Style on hyperlinking, because I'm that sort of person. one element mentioned was that section headers should never be links when possible. instead, a "see also" or "main article" template should be used. this wiki follows that rule occasionally, but in some cases, such as "related achievements" sections, it breaks it with abandon.
the Wikipedia Manual of Style is only relevant in the first place for two reasons. obviously, it sets a precedent for other wikis. additionally, though, Help:Contents says to check Wikipedia's Manual of Style "when in doubt."
I suppose my question is, dœs this wiki intend to follow Wikipedia's Manual of Style? if it dœsn't, should it? Kestrelguy (talk) 16:06, 10 October 2021 (UTC)

I think we should follow Wikipedia's manual, yes. — Tark lm(pt-br) 10:24, 20 October 2021 (UTC)

Backpack Item Links

I don't think this has been discussed yet :P Almost all of the cosmetic pages use {{Backpack Item Link|steamid|itemid}} -an example: Classy Capper, the 3rd contributor has their inventory set as private as I am writing this... if any of the contributors decide to private their profile/inventory, it doesn't update automatically and will likely take a while for someone to update. So, should we just use {{Steamid|x}}, like in the Steam Workshop (the links just lead to the profile)? This wouldn't require someone to update backpack links/change to {{Steamid}}, and would make the articles more -consistent-? In the other hand, it's something that could take a while/not worth to change. What's your opinion on this? Thanks :) Mgpt (talk) 20:20, 13 October 2021 (UTC)

Is it worth updating every existing article? No.

Should we use this format from now on? Yes. — Tark lm(pt-br) 20:28, 13 October 2021 (UTC)

Although I'd like to say, if people do general edits to pages (Like BrazilianNut does) it could be updated and with that slowly update them all.
GrampaSwood (talk) 20:34, 13 October 2021 (UTC)

Yeah, if we're going to change it, I'd recommend creating a new tracking category for it. That said, it is nice to have a direct link to the item... Darkid « Talk — Contribs » 21:43, 13 October 2021 (UTC)

While a direct link would be nice, it's pretty impossible to keep track of everyone's inventory by hand. Needless to say, the wiki is multilingual, so while English may be updated quite frequently, most languages are forgotten.

We could, in theory, scrape this data automagically and generate a dictionary with item ids. This would pretty much solve this issue, but I personally believe it's useless effort. — Tark lm(pt-br) 22:59, 13 October 2021 (UTC)

I added the SteamID template to all the SF XIII cosmetic pages. Mgpt (talk) 00:17, 18 October 2021 (UTC)

Higly against removing bp links. Even if someone set their backpack or profile to private, then the link will still correctly redirect to the correct owner, the reader just won't be able to directly see the item in the backpack. There's no reason to remove them as this happens rather rarely and even if so it still fills its purpose. Also, anyone can just change bp link to steamid if they want, but again, its not necesarry. Denied (Talk) 07:39, 28 October 2021 (UTC)

I agree with Denied. I don't see a point in changing this format if it works with both public and private backpacks. - BrazilianNut (talk) 08:54, 28 October 2021 (UTC)

The main concern here is that people can modify their items (changing their ids) or private their backpacks and both yield the same result: an useless link.

As much as I'd like a better solution, we don't have the manpower to keep them up to date. — Tark 20:25, 28 October 2021 (UTC)

┌────────────────────────────────────────────────────────────────────────────────────────────────────┘  Support. yes.... daddy likes.... ~ Boba 01:09, 29 October 2021 (UTC)

 Keep. We are going to continue using {{Backpack Item Link|steamid|itemid}}. — Tark 17:40, 30 October 2021 (UTC)

Changes to the wiki design to be more compatible with dark mode

Due to the recent trend of "i want my app to have dark mode", the design the wiki has interferes with the "Dark mode" option that some browsers have (mainly Opera GX, but it is very probable that other browsers may want to add it too).
Examples:
Not edited, dark Main Page
Not edited, dark random weapon page
Also, the current color of the body is too white
I propose: 1. Change the default design to have less gradients (which is done by using some images), make the body less bright, and keep current as "classic" in preferences (PREFERABLE). or 2. Add an option in preferences with dark mode option.
Why first is preferable? Because most of the visitors don't know about preferences.
Examples. This is what i've been using by changing my own common.css page:
Edited, normal Main Page
Edited, normal same random page
Dark Main Page
Dark, same random page
· Ashe (talk) 20:28, 18 October 2021 (UTC)

I think it would look cool if we used similar colors from the achievement icons. Primary background color is dark grey, and have the elements on the page being white or orange. - ▪ - 22:12, 18 October 2021 (UTC)

I like the idea, but updating the CSS for a feature outside our control is not something I'd like to deal with. — Tark lm(pt-br) 10:23, 20 October 2021 (UTC)

About adding every language to 'Updated localization files' changelogs

Is it really necessary? Does anyone even care about that? If so they can always check diff or tf2 tracker to see what was changed. Denied (Talk) 07:33, 28 October 2021 (UTC)

Don't see why it shouldn't be on there. In the same way that you could say the items that were added in a case aren't necessary to add, because they can always check the TF2 case in-game for the cosmetics or go to the case page.
GrampaSwood (talk) 10:24, 28 October 2021 (UTC)

Except people actually care about about items from cases. What language was updated for localization files is not even close to be this important, in my opinion (localization files are just a big meme at this point for the community). Denied (Talk) 16:50, 28 October 2021 (UTC)

How the community sees a patch note is completely irrelevant though, translators can be interested in which languages are updated so they don't have to check if theirs is updated on the diff or tracker every time. I don't see much harm in keeping this stuff either. For translators, it's simple one extra line of translation work.
GrampaSwood (talk) 17:03, 28 October 2021 (UTC)

I honestly don't think this discussion is necessary at all. Going by this logic, people can just check the TF2 Blog to read patch notes, and I don't think we're going to remove them anytime soon.

It's an improvement, there are no downsides in adding more information. This is a wiki. — Tark 20:18, 28 October 2021 (UTC)

Alrighty. Denied (Talk) 06:21, 29 October 2021 (UTC)

Adding item filenames to the Basic Information tab for all items?

It may be useful and more informative to add one more tab to the Basic Information section of items that shows their internal filenames. This would make it easier for modders to locate items and overall let people know about items that have slight differences between their titles and filenames.

For example, Gifting Man From Gifting Land is known as "generous" in tf2_misc_dir. Demo's Snapped Pupil is internally referred to as "eyephoto." So on and so forth. The three issues I can see with adding this are:

1: It would require an edit on basically every item article on the wiki. Doesn't mean it's not possible, but it would be quite time consuming (I'd love to help, though! Browsing with GFCScape is quite fun for me.)

2: There would need to be some way to refer to items that have multiple, separate internal filenames. This usually applies to the multi-class items. The Earbuds exist in each class' items folder separately (demo_earbuds, scout_earbuds, etc.)

3: The wiki's "Item infobox" would need to be changed to accommodate the new descriptors.

Here's an example of how this could be done, using an abbreviated infobox:

For items like the Snapped Pupil:

| type = cosmetic | used-by = Demoman | directory = demo | filename = eyephoto

For multi-class items like the Earbuds, which exist in each of the class' folders separately:

| type = cosmetic | used-by = All classes | directory = Something conveying that it exists in all class folders, yet not all_class | filename = (class)_earbuds

Finally, for all_class items like the Gifting Man From Gifting Land, which exist in the all_class folder, but have separate models for each class.

| type = cosmetic | used-by = All classes | directory = all_class | filename = generous_(class)

Sloeber (talk) 22:26, 1 November 2021 (UTC)

Way too much work that would be useful for way too few people. - BrazilianNut (talk) 22:47, 1 November 2021 (UTC)

Agreed with BrazilianNut, too much work that's not really beneficial to a majority of people.
GrampaSwood (talk) 23:04, 1 November 2021 (UTC)

If you are having trouble finding items, I suggest looking for an "internal file names" list. Here's something from the Garry's Mod Guides section that may help you. As for what others said, I agree, it's something very little people would use. Aditionally, you can look up in tf/scripts/items_game.txt. Open the file, press Ctrl+F, write/paste the name of the item, and check the "model_player" string to know where the item is located in the game files. - ▪ - 23:51, 1 November 2021 (UTC)

It's not particularly hard to do, it's rather easy actually,. But could you elaborate on why and how this information could help modders?

I assume if you're a modder you already have the basic knowledge to find this information on your own, so I'm not sure if the trouble is really worth it. — Tark 15:22, 2 November 2021 (UTC)

What exactly constitutes a "Community Strategy Stub?"

I've seen a number of strategy articles labelled as stubs that are incredibly detailed and seemingly complete, such as https://wiki.teamfortress.com/wiki/Community_Gravel_Pit_strategy. While I'm aware that there are a number of other articles that are nowhere near complete, the fact that such articles can be so fleshed out and still be labelled as stubs begs the question: What exactly constitutes a Community strategy page to be labelled a stub? How much information does it need? How well organized does it have to be? I feel like having a better grasp on what determines if an article is in desperate need of additional information can help me figure out how best to contribute to the progression of the Project. GoodMudkip (talk) 15:40, 3 November 2021 (UTC)

Eh. The reason why these stubs are present are not because the strategy in question is incomplete, but because the stubs are outdated. You see, once someone plasters a stub onto a page, they usually don't bother to go back and revert that stub, even if the page in question gets updated. Hence, why there are so many useless stubs lying around everywhere. If you want to see how "complete" a strategy page actually is, you should visit Team Fortress Wiki:Community Strategy project page, which contains a table tracking the status of every strategy page known to man.

Lolimsogreat21 (talk) 16:07, 3 November 2021 (UTC)Lolimsogreat21

Thanks for elaborating. Though if the reason so many of these pages are still considered stubs is that no one's bothered to re-evaluate their stub status, then someone needs to get on that and remove the stub blurbs on some of them. I'll make sure to check out the project page though. GoodMudkip (talk) 20:06, 3 November 2021 (UTC)

Rot, trans, and light values page

I can't find that one page that has a long table with the HLMV registry values for rotation, translation, light position etc. used for the cosmetic images on their wiki pages. Could someone please link it? Memayz (talk) 15:28, 5 November 2021 (UTC)

Found it: Template:Painted_variants/Tutorial/Rotations Memayz (talk) 15:37, 5 November 2021 (UTC)

Bugs and Unused content sections throughout the Wiki

Some pages have some extremely outdated bugs, for instance, Gunslinger. I play this game a lot (not to brag), and I haven't had the problem where you can build mini-sentries with regular wrenches, neither I had my first-person view having the Gunslinger + Wrench, I also never manged to build or see mini level 3 Sentry Guns (I think that was a bug to the Engineer Robot, never mind). This is just one page, other pages have lots of other outdated bugs. Some cosmetics has some strange bugs that doesn't seem to apply anymore or should be in another page (the Cozy Camper Jarate dissappearing is due to an issue of the translucent effect not working properly in the entire game, not only the Cozy Camper. The same problem happens with the majority of translucid items, such as the Halloween "ghost pets", so should we add that to the other translucid cosmetics/weapons or just mention somewhere else universally?).

The problem is that not all bug fixes are listed in the Patch Notes, so we are unaware when things get fixed or not. As for unused content (unused content for items RELEASED in the game, by the way, not unreleased items), a lot of old item pages have the "This item is set up to be paintable, but the ability to do so has been disabled." (with some pages have slightly different wording). Some items have that info added, others don't. For me, I don't think just because the texture is set to be paintable that would necessarily be a paintable item, some item creators use just 1 texture for both teams (maybe bypassing the limitation to have other textures for other areas of the item, for more detail). The way the paintability works is that there's an white area on the texture that is "unpainted", and it also has an alpha mask covering that area. On the material files, the string "colortint_base" is what adds the color to the cosmetic, so both teams can use the same texture but use different materials. So yeah, should we keep this piece of unused content up or should we remove it? - ▪ - 21:35, 8 November 2021 (UTC)

It's a tricky thing to figure out which bugs are outdated and which aren't. Ideally, bugs would be removed with proper proof that shows the bug no longer happens. However, as is often with these bugs, there are no steps for reproduction and so we can't really be sure. Furthermore, I think a bug being mentioned as fixed doesn't immediately guarantee it being fixed. As for the unused content bit, it seems more like (pre-)workshop trivia than unused content, but I think it can fit in unused content if we decide to keep it (which I'm for).
GrampaSwood (talk) 21:47, 8 November 2021 (UTC)

Yeah, and you are correct, there has been cases where the patch notes stated something was fixed but wasn't actually (or was not fixed properly). And there's some bugs that happen due to external factors (minimizing the game on full-screen and getting it back up causes a plethora of issues), so it's hard to know. Well, I wouldn't consider the paintability thing pre-workshop trivia because these items are still "paintable" in the item's textures/materials, just not set up to be painted in the schema. Some of those items are not even "marketed" on the workshop as paintable either. I will add this information to the missing pages then (and make it consistent on the few pages that is written differently), but I'll have to figure it out which pages are missing. I do recall seeing lots of cosmetics on TFMV that had paintability but the page on the Wiki didn't mentioned anything ("paintable" cosmetics that are not marked as paintable in the schema appears as "VMT ColorTint Base" in TFMV, while unpaintable cosmetics is grayed out with the "Not paintable" string). - ▪ - 22:07, 8 November 2021 (UTC)

Additionally, should we make pictures to show the unused paintability on those items? The Neon Annihilator page has an image showing the unused paint variants on the Gallery section, I think the Most Wanted page also had on the gallery for some time, but it was removed. Just stating that the item is paintable is not enough information, in my opinion. Maybe we should add like details on where the item's unused paintability comes from (so, on the Caped Crusader page, it should state that it paints the cape area), and add an image to the gallery section showing the unused paint variants. But let's not add the Paint Variant Table for those items who are not paintable by the schema, so it doesn't confuse readers. Another idea would be making a sub-page like Most Wanted/Unused Paint Variant Table or something, and make use of the table itself on that page, while linking said page somewhere on the main page. TFMV has an option to make a single image showing all paint variants. The only problem is that the Paint Can order is not the same as the one used on the Wiki. Another option would making the paint pics separately, and use SpriteSheeter, a program that lets you easily organize images into one huge sheet, while keep everything centralized and consistent (Example of multiple images combined into one using SpriteSheeter, on another Wiki). - ▪ - 12:29, 9 November 2021 (UTC)

I think adding an example of what it would look like painted is a good idea.
GrampaSwood (talk) 12:39, 9 November 2021 (UTC)

Pyroland demonstrations

It has been decided that new Pyroland demonstration videos will no longer be made. I believe, for uniformity sake, that we should remove existing Pyroland videos as well. We should not have some articles with them and some articles without them; all should be either one or the other. - BrazilianNut (talk) 07:49, 9 November 2021 (UTC)
EDIT: Maybe we could have the Pyroland demonstration video updated to show one cosmetic being credited as the assistant and one cosmetic being credited as the killer. - BrazilianNut (talk) 08:03, 9 November 2021 (UTC)

The current plan is to not remove any existing ones but add a single video that demonstrates every kind of Pyroland demonstration (So assists with kills, kill credit, etc.). I think it should be that the videos are removed from item pages, but not removed from the wiki channel (Maybe an added "Archived:" in front of the title, with an explanation in the comments).
GrampaSwood (talk) 11:18, 9 November 2021 (UTC)

Yeah, I suggest reading Wind's response on this topic here, as well my thoughts on it. - ▪ - 12:29, 9 November 2021 (UTC)

Special Taunts on Class Pages

I have always wondered about this, why not include the Special Taunts for each class on their respective pages, as well listing the All-Class taunts? Each class page has sections for their weapons (which includes multi/all-class weapons), their cosmetics, all-class cosmetics, as well item sets. Considering Special Taunts are also considered items, I think we should add a table of sorts to include them. Maybe include them below the "Taunt Attack" section and above the "Item sets". We can use a table similar to the cosmetic one to use the backpack icons/item icons instead of the class actually doing the taunt, but unlike the cosmetic table, the tables should always be open (both class-specific and all-class ones), due to the fact that there's not many special taunts compared to cosmetics. Below the "Special Taunts" section, include a "Main article: Special Soldier taunts" or something.

I think in general, Special Taunts pages (like Rancho Relaxo) themselves should include the responses that happens during the taunt, or at least include a link to the Special section for that taunt in specific. The problem in adding the link to the Soldier taunts#Special page is that you can't specify the page to go to a specific taunt, only a specific section.

Additionally, I think the Class taunts page should be reworked on. I think we should add the taunts themselves to the class pages, and move the responses on the Soldier responses page. So I will propose the following ideas:

a) Include the Special taunts section below "Taunt Attack" and above the "Item sets" section, and include a Main Article link to the special taunts;

b) Make a section for taunts for each class page. The section is called "Taunts", which includes both "Weapon taunts" (the terminology that is used in-game when selecting a taunt on the taunt selector) and "Special taunts". Below the "Taunts" section, add a "Main Article: [Class] taunts" link.

  c) Get rid of the class taunt pages, and move everything to their respective class pages. Move the responses to the class responses page, and include a link to Soldier responses#Taunt-related responses somewhere on the Taunts section.

My vote is for "c)". - ▪ - 11:56, 10 November 2021 (UTC)

Weapons are a big deal for the classes, so I don't think we should touch anything there. "Taunt Attack" is also something that can affect other players, so I think it's ok to have them listed in the classes' articles too. Things like "Cosmetic items" and "Item sets" could be removed and replaced with links to existing pages, such as List of [class] cosmetics and Item sets (this one with a # directly to the class' sets), in See also. We could then add a link to the [Class] taunts articles there as well.

I don't know where to stand regarding the "[Class] taunts" pages, though, as I see pros and cons to having the responses both in the articles for the taunts and in the "[Class] taunts" articles. - BrazilianNut (talk) 15:25, 10 November 2021 (UTC)

tf2 status

can an thing related to tf2 status (if is down, or up) be added to the main wiki page?

MaxwellWagner (talk) 01:12, 21 November 2021 (UTC)

Doesn't really seem necessary. This website should work if you're curious, but it's not really a necessary feature for the wiki imo.
GrampaSwood (talk) 15:00, 4 December 2021 (UTC)

Update history

suggestion: change from "oldest date to newest date" to "newest date to oldest date"
reason: easier to update, easier to see new changes. Angustia (talk) 14:13, 4 December 2021 (UTC)

I don't see much point in this, it's not really hard to update the update history nor is it hard to scroll down on it and having to do this on every single page to date is way too large of a task.
GrampaSwood (talk) 15:19, 4 December 2021 (UTC)

Simple class link templates

I suggest to add the templates Template:Scout, Template:Soldier, etc, ({{Soldier}}) to simply make a link to those class articles. This is shorter and simpler than Template:class link with the parameter noimg=true ({{class link|Soldier|noimg=true}}) or, when translating, [[Soldier/es|Soldier]] · Ashe (talk) 23:34, 4 December 2021 (UTC)

I don't really understand what's wrong with {{Class link}}? You're saying it's "too long"? As in, around the same length as {{Item link}} which gets a fair amount of use? I really don't want us to have highly specialized templates, that defeats the purpose (and maintainability) of those templates. Darkid « Talk — Contribs » 05:11, 5 December 2021 (UTC)

Then what's the point of have {{item link}} if users can "simply" write [[Pretty Boy's Pocket Pistol/es|Pistola de Bolsillo del Guaperas]]. If {{class link}} would link to class articles without the class emblem, it would be fine. A dumb solution would be to change the template to not show the emblem by default, but that would break practically the whole wiki, so my suggestion is more ideal · Ashe (talk) 17:04, 5 December 2021 (UTC)

Item link is actually more, because it's doing localization for you, so it's [[Pretty Boy's Pocket Pistol/es|{{item name|Pretty Boy's Pocket Pistol}}]]. And, obviously, a longer name is a more extreme example; be careful that you're not arguing reducto ad absurdum.

There is a balance between having templates for everything (at which point nothing on the wiki is WYSIWYG) and no templates (at which point there is a lot of duplication). In general, I tend to fall more on the side of more templates, but those are not always easier for translators.

My rule of thumb is, if a template only has a single use-case, then it's costing more in terms of abstraction than it's saving in terms of code re-use. There are exceptions, of course (the dictionary is one humungous exception for this), but this helps me to not turn everything into a template just because I can.

If the default value isn't helpful, how about another template which has a different set of defaults? That way, you're still re-using code with a template, but avoiding needless article clutter.

Darkid « Talk — Contribs » 18:32, 5 December 2021 (UTC)

Oh yeah, that's another option. Something like this:

{{class link|{{{1}}}|noimg=true}}

In a template called {{cl}}, for example · Ashe (talk) 19:37, 5 December 2021 (UTC)

Update:  Done · Ashe (talk) 17:08, 11 September 2022 (UTC)

Cosmetic perspective

I don't think an official consensus on this exists, and if it does I can't find it. But from which perspective are articles written? For example, if a baseball cap has a logo on the left side (When looking from the front), would this be described as "With a logo on the left side" (Third person perspective when looking at hat) or "With a logo on the right side" (First person perspective when wearing the hat).

I'd vote for third person, because that way the people reading the article can compare it to the infobox's image.
GrampaSwood (talk) 11:56, 5 December 2021 (UTC)

 Agree Third person also matches how you see the hat on other people, as well as in the loadout preview in-game. Darkid « Talk — Contribs » 12:30, 5 December 2021 (UTC)

Over which eye does the Demoman wear an eye patch? I think we will all agree it's his left eye, but from a third person perspective, it's his right eye.

What's the driver's side on a car (outside the UK)? I think we will all agree it's the left side, but from a third person perspective, one could say it's the right side if they are looking from the front.

If an item has defined front and back, the first person perspective should always be used. - BrazilianNut (talk) 18:58, 5 December 2021 (UTC)

 Disagree I agree with BrazilianNut · Ashe (talk) 19:43, 5 December 2021 (UTC)

When describing a model, first person perspective. In img subtitle, third person perspective. Angustia (talk) 20:37, 5 December 2021 (UTC)

The brand new {{item description}}™ template and dictionary

Hi fools.

When displaying items around the wiki, either through infoboxes or other templates, please make sure to use the new {{item description}} template (and update {{dictionary/descriptions}} accordingly). This works exactly the same as the {{item name}} template you're all used to and must be transcluded on English pages as well.

Thanks. — Tark 19:00, 10 January 2022 (UTC)

Please note that this change is not retroactive. Articles created prior to this message are not supposed to be manually updated.

Do NOT update old articles. Please treasure your time. — Tark 19:12, 10 January 2022 (UTC)

Fan-made TF2 songs pages

Howdy, fellas! I know there's a good handful of beloved fan-made songs for TF2 mercs and stuff. Is it worth making an article/page about? Just wanted to hear someone's opinion on this, maybe we could start a conversation? Like (if you have one) what is your favorite Team Fortress 2 fan-song?

Mine isThe Most Fashionable Factionby The Stupendium

Blue theRAT85 (talk) 03:06, 29 January 2022 (UTC)

I don't think this is necessary, there are simply too many songs and too little information for it to be really worth making a page for. It would consist of one or two line(s) of text, maybe a small infobox, and the video itself. Similarly, there aren't any pages about SFMs/gmod videos.
GrampaSwood (talk) 11:12, 29 January 2022 (UTC)

Available qualities

Hello! I didn't find any topic about this in specific, so maybe this should be discussed. So, if the item is not available in a specific quality anymore, should it be removed? Two examples: Corpse Carrier and Coffin Kit. I already made the edits (1 2) in Template:Dictionary/quad, should have posted this first, I'm sorry for that :P

Now about the available qualities, I'll give an example (and this applies to most of the Halloween items), the Zipperface currently only shows "Mann Co. Store" in the Unique quality, so my question is: What should really be included? The available "ways" of getting the item at the moment (would be something like this: "Mann Co. Store, Halloween Package & Halloween Transmute"), or every way: "Mann Co. Store, Mann Co. Supply Crate #51, Haunted Halloween Gift on Ghost Fort, Halloween Package & Halloween Transmute". There are other situations like the Limited Late Summer Pack items ("only" one way), the Smissmas 2014/2013/2012 items... the same with weapons, the Crossing Guard for example. What do you think? Mgpt (talk) 22:25, 3 February 2022 (UTC)

The available qualities is meant to be for non-exploited ways of obtaining the item (i.e. no Vintage for Bill's Hat, because it's not a legit way of getting it, but rather a mistake on Valve's part), so the available quality of the Corpse Carrier and Coffin Kit should stay as they're completely legitimate ways of obtaining them.

As for the 2nd question, I think all ways to get an item should be listed.
GrampaSwood (talk) 22:41, 3 February 2022 (UTC)

The qualities were added back in this edit and I will rework Dictionary/quad (2nd question) once QuAD/list/Sandbox is implemented. Closed :D Mgpt (talk) 01:44, 26 March 2022 (UTC)

Item origins (promotional)

I've noticed there's no real consensus on where an item's origin should go, sometimes it's put in the first paragraph (E.g. Widowmaker) but other times it's put in trivia (E.g. Dread Hiding Hood).

I personally propose that with promotional items only, it's put in the main paragraph. This is because the main paragraph is where the item is always described, with promotional items their design is always taken from the associated game which is why I think it should be mentioned in the main paragraph. For other items (non-promotional), it should remain in the trivia imo.
GrampaSwood (talk) 12:26, 3 March 2022 (UTC)

Makes more sense when it's in the first paragraph / main description of the item at the top. So I would go for following the style that it's on the Widowmaker's page. Though there might be some promotional items that aren't so obvious in its design, like the Tom Clancy's Ghost Recon: Future Soldier items. Do we know if any of these items are based off anything from that game in specific or the Tom Clancy's franchise as a whole? I guess in cases like these, not having information regarding the origin of the item is alright too. - ▪ - 12:43, 3 March 2022 (UTC)

I agree with Gabrielwoj, it makes more sense to have it in the paragraph introducing the item, though I would put it in the part mentioning the pre-purchase deal- maybe at the beginning of the sentence before mentioning the Genuine quality. The reason being so the game is not mentioned twice in a single paragraph to avoid redundancy. What do you all think? Yossef | Talk | Contributions 14:15, 3 March 2022 (UTC)

How about, for promotional items only, we start the description with "It is the [thing] / It is based on the [thing] from [media]" and then proceed to describe its appearance?

Examples:

• "The Dread Hiding Hood is a promotional cosmetic item for the Sniper. It is the hood worn by Garret from the video game Thief; a dark, team-colored hood and face mask..."
• "The Widowmaker is a (...) weapon for the Engineer. It is based on the Widowmaker TX from the video game Deus Ex: Human Revolution; a futuristic tan shotgun..." (we could also expand the description to more than just "futuristic tan shotgun").

This way, even though the original media's name is repeated, the mentions are somewhat spaced from one another. - BrazilianNut (talk) 16:03, 3 March 2022 (UTC)

 Support I like this idea a lot.
GrampaSwood (talk) 16:06, 3 March 2022 (UTC)

 Support Yes, me too. - ▪ - 16:22, 3 March 2022 (UTC)

 Support Yeah, I prefer this wording than my suggestion. Yossef | Talk | Contributions 16:30, 3 March 2022 (UTC)

 Support Certainly, the fact that it is a promotional item should be stated in the lead. IMO, placing statements about promotions into Trivia is diminishing to the thing promoted, especially charities. And, by the time it the item is recognized for its promotion, what the item represents is usually Obvious and therefore not Trivia, and of all the many simple observations that we place in the lead, this may be the most justifiable.

M I K A D O 282 ⊙⊙⊙⊙⊙⊙ ⊙⊙ ⊙⊙ (Contact Mikado282 (SM)) | contribs) (Help Wanted!) 18:10, 5 March 2022 (UTC)

I think there should be a page listing and describing cosmetic item effects

it would be nice to have a list of all "special" cosmetics items, and what effects they have, like say you listed "Elf ignition, Jolly jingler, Elf care provider, Elf defense, Seasonal employee, Bootie time, Jingle belt, Reindeerobeanie, Elf-made bandanna" as "items that make a jingle sound on walking" and having all cosmetics that give you pyrovision under a pyrovision effect tab "ball-kicking boots" would be "spawns a ball"

it would just be nice having all theese cosmetics with special effects listed under a page, as there is no such page/list now

also i do not know much about editing wikis, and creating new pages, and i dont want to do edit a bunch of pages and end up doing more harm than good, if my idea is not good Jones Edison (talk) 17:33, 17 March 2022 (UTC)

Category:Cosmetic items that make noise lists all cosmetic items that make noise, this section of the Pyroland page mentions Pyroland items. Not sure if it's worth to have a page like that.
GrampaSwood (talk) 16:34, 17 March 2022 (UTC)

Reworking paint variant tables from Medic's shirt cosmetics with the lower coat visible

Hi. In the past, I have reworked some paint variant table pictures that did not show the entire cosmetic, such as the Surgeon's Sidearms and Shogun's Shoulder Guard. In the first one, only the part with the hand was being shown. I reworked to include what's inside Medic's pockets, because the colors of that changes between teams, and there was no way to know that beforehand. In the case of the Shoulder Guard, only the collar area was being shown, and there was no way to know the BLU variation of the arm attachment that the cosmetic adds. I plan in re-making those again without the classes' heads, but anyway, just mentioning those here.

Since then, I was always wondering about certain Medic cosmetics. Some Medic cosmetics features elements that goes all the way down to his lower coat, reaching his boots. Cosmetics like Colonel's Coat and Heat of Winter has this, and it changes per team. But right now, due to how the paint variant pictures are being shown, there's no way to know about this change.

My suggestion would be remaking those with the lower coat region being shown. Yes, this means the image will be taller and the paint differences will be smaller to notice, but reader's can simply click the images to enlarge. They can click on any paint variant and keep pressing Left or Right on the gallery viewer. This was the case with Lurker's Leathers. I couldn't just remove the part of the pants since it changed per team, so I included the entire Spy body (although now that I see, I could probably remake those without Spy's head and feet). This cosmetic alone was the reason I added the "Click on the images to enlarge them." on the Painted variants template description.

I can also remake items like Der Wintermantel and Foppish Physician, even if the lower coat area doesn't really change per team (actually, Der Wintermantel's white areas is SLIGHTLY different per team).

Here's an Imgur album I made showing a preview how these would look, showing the lower part of the coat: https://imgur.com/a/vJMe9lG.

Additionally, the Dead of Night on the Medic has the same thing too. If you paint the item with the "Dark" style selected, the colors of the trim at the lower part of the coat will also paint. Not sure if there's something we can do about that, maybe just additional text on the main summary would help.

Please let me know about this before I work on these paint variants, which will take a while to make considering I have to rely on a model that lets me hide the Pants and Shoes manually (which means I have to disable these bodygroups manually PER paint change).

Sadly, because I don't have Photoshop, I'm unable to make a texture that hides the pants and boots without having the colors being washed out (which happens with gimp_vtf plugin). Omolong did most (if not all) the file replacements for paint variant tables, and from what I remember, he used Photoshop. I tried many different things but was unable to get the textures look like default. With this custom model that lets me hide stuff, the colors are okay, there's extremely small differences between the original model and this one, differences so small that reader's will probably not notice. I also tried decompiling the Medic model, removing the Pants and Shoes area, and recompiling, but the lighting and certain parts got a bit messed up, so I discarded that.

If someone has Photoshop, I can send some steps on how to make the texture hide the parts I want. It uses a technique with the alpha mask and a string on the material (.vmt) that hides parts of the model based on the white areas in the Alpha Mask. I have the Alpha Mask with the lower coat region being shown saved. - ▪ - 13:22, 23 March 2022 (UTC)

I do have Photoshop, do you mean you want someone to help edit a texture file? Maybe I can help. --Alex┋T 05:06, 24 March 2022 (UTC)

I need a modified version of medic_red.vtf and medic_blue.vtf to include this alpha mask (make sure to click Download and not save directly from the preview, to retain the quality of the image). Download the medic_shirt+belt_materials.zip provided on the Rotations page. Download the Photoshop plugin for importing/exporting .VTF files: http://nemstools.github.io/files/psvtfplugin1011.zip (more info here: https://nemstools.github.io/subpages/Comments/VTF_Plug-In_for_Photoshop-page1.html).

Import the medic_red.vtf from the medic_shirt+belt_materials.zip I provided, and replace the alpha mask with the one I provided. I don't know how photoshop works, but if there's an overwrite functionality, it may retain the quality and all other settings from before, making the texture quality lossless. If not, maybe select "Uncompressed texture" on the "Templates" section when exporting the .vtf. Select "Eight Bit Alpha (Format Specific)" on the flags. Include mipmaps and thumbnail. Do the same for medic_blue.vtf.

This should work. If you have VTFEdit, compare the quality between two textures by opening both files (the original one from the .zip and the new one with the new alpha mask applied), and see if the new one has a lower quality / is darker. If not, then that worked how I wanted, without the texture suffering quality loss.

Thanks. - ▪ - 13:50, 24 March 2022 (UTC)

Oh wow the plugin requires a 32-bit version Photoshop! lucky enough I checked my old PC it still has a 32-bit Photoshop installed. I got to choose "Uncompressed texture with Alpha" or it won't let me select the "Eight Bit Alpha" so I did that. The file size get significantly bigger somehow. I downloaded VTFEdit and opened the textures and I didn't see any difference. Here's the download for replaced texture. Hope they would work! --Alex┋T 15:58, 24 March 2022 (UTC)

I tried, for some reason I can't see a difference on VTFEdit, but on HLMV, they still look desaturated. Apparently even Omolong's texture replacements have this problem, but our .vtf edits still gets more desaturated than his replacements.

I appreciate your help, but I think I'll rely with an alternative method. I have a pack made by NeoDement that is a custom model that lets me change custom bodygroups (I can disable the pants, shoes, hands, glasses, etc.). The differences between the original model in the game is very little (there are some small differences on the lighting/shadows, most likely due to recompiliation issues). Now, I would like to ask. What do you think it's the best choice here?

• Leave the paint variants for Colonel's Coat and Heat of Winter like they are.
• Or re-make them to include the lower part of the coat?

I still think the second option is better. These two items are different between teams and so far, there are no ways to visualize that on the page. The other items, Der Wintermantel, Foppish Physician, I can remake these too, to keep consistent with the other two cosmetics. - ▪ - 16:23, 24 March 2022 (UTC)

That’s very weird. I will try experimenting with them tomorrow.
Not sure about how noticeable the difference is between the custom model, but I still like the second option to include the lower part of the coat, for all the coats. (That sounds like a lot of work!) It makes it at least looks like a actual coat. Your previews in Imgur looks fantastic.
For the Dead of Night, I believe a text explanation and a couple of image (maybe a GIF?) demonstrating the difference should be enough, just to let the reader have a idea how the lower part is different. —Alex┋T 17:30, 24 March 2022 (UTC)

New template that supports "single color" paint can for both teams

A while ago, it was discovered that the Frenchman's Beret singular colors changes per team. This is due how the texture is set up. Rather than the texture being colored in white to accomodate the white colored alpha mask (that determines where it should paint), this hat has no alpha mask at all. And on RED team, the base texture is green, while on the BLU team, the base texture is yellow. Due to the lack of alpha mask and white colored parts on the main texture, the paint tool will simply "merge" with the colors already in there. This is the reason as to why this hat shows up like this when painted in Tinge.

This isn't the only cosmetic with this. The Defiant Spartan also has a similar issue. The Defiant Spartan does have an alpha mask, but the base texture is still RED and BLU, and not white. This causes errors when painting, just notice the darker paints being merged with RED/BLU colors.

Other cosmetics with similar problems include:

• Antarctic Parka (notice how the darker paints have little to no effect);
• Kapitan's Kaftan (small changes between teams, the BLU team's texture causes Single Color paints to be a little brighter than RED's texture).
• There might be more.

So what's our plan here? I have made this template with a proposed dual-team single colored paint cans to be used in those special scenarios. How does it look? I think it looks pretty snazzy, and seem to work properly on a page. There might be a problem with other languages, though, if their paint can names are too lengthy. The table may also break if the window size of the reader's browser is too small.

If this is okay, what pages should we enforce this rule on? I gave you 4 examples, the only one that is the least different per team is Kapitan's Kaftan, but there's still a small difference with the brightness. Of course that there might be other cosmetics with the same situation. - ▪ - 18:38, 23 March 2022 (UTC)

Alternate version with each Single Color paint can being compared side-by-side per team. I think I prefer this one, it's easier to understand and it's consistent with the Team colors we already have established on the Wiki. Please tell me which one's your favorite.

 Alternate Version - ▪ - 21:35, 23 March 2022 (UTC)

I like the alternative version. But it feels very overwhelmed when I tried it on actual page, like tons of images slapped to your face. Hope it could be a horizontally scrollable table (only the single colors part) so there's only couple of columns shown at a time, and there could be a button to spread the whole table wide. Then the Team colors section could be aligned to the left. --Alex┋T 05:44, 24 March 2022 (UTC)

I don't know if I like the idea of a scrollable table. What I can do, however, is making the same size as the default paint variants, but include more rows to include the BLU alternate versions. So it would be something like: An Extraordinary Abundance of Tinge (RED), An Extraordinary Abundance of Tinge (BLU), Color No. 216-190-216 (RED), Color No. 216-190-216 (BLU) on the first row, then goes to the next row. But on this case... it would be too many rows to scroll for. I still think the alternative one I present may look better, unedited. I just can't imagine right now how it looks since we don't have the BLU single-colored paints for the Frenchman's Beret or other cosmetics for a better visualization.

I'm thinking about moving the template to Template:Painted variants full, I think that's a good name for the template. The most important thing right now is to include the BLU single colored paints for these cosmetics. If there's a design change to the table that should be made, that can simply be modified via the template. - ▪ - 12:59, 24 March 2022 (UTC)

I tried the template with Defiant Spartan and this cosmetics had BLU painted pictures. I'm also thinking maybe we could make it 4 columns but it's inside a vertical scrollable box so it's not too long. Anyway can we make all the cells left aligned, so some of them not floating in the center? --Alex┋T 13:44, 24 March 2022 (UTC)

I think having the table have 4 columns per row, and include a vertical scrollbar might be ideal, actually (having a horizontal scrollbar would be weird). The template needs to have a similar height size with the standard one, though. Had no idea the Defiant Spartan had the BLU variants already made. Apparently someone has worked on a similar table like mine before: User:Rebmcr/Template:Painted variants/team. I don't know how to implement the scrollbar, though. Feel free to modify my "Sandbox2" page.

Something else I thought was painting the background behind "Paint Can Name (RED)" as RED and "Paint Can Name (BLU)" as BLUE, to make it easier to understand, but I wasn't sure if that would be confusing (blue background for the lime paint?!?!?). - ▪ - 14:00, 24 March 2022 (UTC)

I think the current template without the scrollbar might be enough. Look how it looks on the Frenchman's Beret page. - ▪ - 16:23, 24 March 2022 (UTC)

┌────────────────────────────────────────────────────────────────────────────────────────────────────┘ I could imagine adding a bright blue and red background behind text make the text hard to read and hurting your eyes, use a light blue and red might work though. How about replacing the (RED) or (BLU) in the text with a red or blue dot? That will look more elegant and clean. (Will it be difficult for colorblind people to distinguish between red and blue dots? Maybe Text, or a hidden tooltip, is still important. )
They looks ok on Frenchman's Beret, let’s just leave it like that and stop make it more complicated, it’s only on a few pages anyways. —Alex┋T 17:44, 24 March 2022 (UTC)

Here's a few other findings I managed to... well, find:

Tip: After opening the album, right-click an image, and open in a new tab. Do the same for the BLU variation and compare both by switching tabs, it's easier this way.

• Cosmetic with noticeable changes per team:
  • Stout Shako: https://imgur.com/a/5JJAnqU - RED team has more noise on the texture, while the BLU team is more clean. However, the BLU team version paints the paint darker than the RED team;
  • Backbiter's Billycock: https://imgur.com/a/EW0zKSz - Weird paint effect on the BLU team. Color No. 216-190-216 becomes Drab-ish on BLU team, peculiar;
  • Backbiter's Billycock (again): https://imgur.com/a/d6MRIe8 - The BLU team colors on the Paint Variant Table are wrong. The person who did the paint variants did not realized that the BLU team version used a different texture. What he most likely did was change the colors to the BLU team variants of Paint Cans on the _red.vmt material. Curiously, the "December 3, 2010" revision of the Team Spirit BLU paint image of this cosmetic was correct, it was later redone incorrectly;
  • Fancy Fedora: https://imgur.com/a/PKLViSE - The stripe of the hat is part of the paint effect. Due to this, some paints shows the stripe being colored differently on BLU;
  • Ellis' Cap (somewhat noticeable): https://imgur.com/a/8kiMZAj - The cosmetic uses two different textures due to the team-colored background of the truck. However, the rest of the texture is a bit different. Just notice how green-ish the RED version is when painted with Tinge.
• Bright paints not so noticeable, Dark paints very noticeable:
  • Antarctic Parka: https://imgur.com/a/JWbJdbR - Has a similar issue to Defiant Spartan, related to textures.
• Brighter on BLU:
  • Kapitan's Kaftan: https://imgur.com/a/pgizvoI - Paints are brighter while on the BLU team.
• Noise:
  • Vintage Tyrolean: https://imgur.com/a/oDbfPJO - Other than the noise on the texture, the BLU version is a bit more shinier;
  • Tyrant's Helm: https://imgur.com/a/68oT2QE - A little more noticeable than Vintage Tyrolean.
• Barely any difference:
  • Wiki Cap: https://imgur.com/a/TDhLuv8 - Yep. There's an extremely small difference between both RED and BLU team's textures when painting. Not going to do it;
  • Dr. Whoa (at least on Medic, unsure about Spy): https://imgur.com/a/Mq4nxug - BLU team is just slightly darker. Don't think it's needed either.

I'm going to work and upload on Stout Shako and the Billycock for sure, probably Ellis Cap too. Unsure about the Fancy Fedora... and unsure about the rest. I think the "Noise" ones aren't needed, only the Tyrant's Helm that is a little more darker on BLU. Stout Shako's Team-dependant Paint Cans might be wrong too. I'll later investigate if the French Beret and Defiant Spartan's have the same issue too. Please let me know on this discussion regarding these.

P.S.: I will check these in-game before uploading them to the Wiki. For extra measure. - ▪ - 21:19, 24 March 2022 (UTC)

So here's screenshots taken in-game showing that these indeed happen in-game (also took screenshots of already made ones, the Frenchman's Beret and Defiant Spartan): https://imgur.com/a/YC699pK (once again, I recommend right-clicking and opening in a new tab).

Taken at high-quality settings and on 1920x1080 resolution. I don't want to put an URL on every single file upload with the proof in-game on the "file changes" summary, so I'm posting here instead.

The Kapitan's Kaftan is hard to notice on these screenshots, but I provided the texture for the RED and BLU version. Notice how the white area is brighter in BLU? Well, that's the reason as to why the paint is affected this way on the BLU team.

The BLU Vintage Tyrolean's texture is slightly darker due to how the texture's noise/shadowing differs from the RED team. BLU Tyrant's Helm is slightly darker than RED team, as well some "blotches" on the texture.

Was unable to check team-colored paints in-game as it seems it always applies the RED paint regardless of the team (on any cosmetic), but, at least I know that two different .vmts and textures are used on these cosmetics.

If other people could join in the discussion to determine/discuss which cosmetics I should make extra BLU paint variants, it would be very helpful. - ▪ - 14:54, 25 March 2022 (UTC)

Should all bugs in articles have a report in Source-1-Games github?

I've thinking about this for a while. The Valve's official repo for Source games allows users to report issues with games. So, should all bugs from items have a link to an issue in said repo? Example: I want to report that the Caber can't minicrit with shields, so i should first open an issue in the repo and then I add the bug to the Ullapool Caber article with a link to the issue. This may help because Github allows to add images and videos in issues (we would'nt depend of YT or Imgur) · Ashe (talk) 17:25, 21 April 2022 (UTC)

This would be significantly increase the barrier of entry for people + require a third-party account, although it is a great solution.
GrampaSwood (talk) 17:33, 21 April 2022 (UTC)

Bot not updating gameinfo template

It appears that WindBOT is refusing to update Template:Dictionary/gameinfo for a few months already. Can someone look into it? Denied (Talk) 13:59, 27 April 2022 (UTC)

Please contact WindPower regarding matters with his bot or start a discussion on the bot's talk page, as this is sadly beyond our control. — Wookipan (talk | contribs) 20:41, 27 April 2022 (UTC)

Alright. Thanks. Denied (Talk) 08:47, 6 May 2022 (UTC)

Prices for games in PLN

I have absolutely no idea how to do it, so I'm asking for any help. Is there a way to change prices for games for /pl from euro to polish złoty (pln) the same way as it works now for prices in the mann co. store showed in infoboxes? Denied (Talk) 09:06, 6 May 2022 (UTC)

This request is directly related to your question above, once the issue is fixed we will be able to add more currencies. — Tark 12:21, 6 May 2022 (UTC)

Correction: I actually added support for pln back in July 2021 🤦‍♂️.

It should work now. Please let me know if you face any issues. — Tark 12:36, 6 May 2022 (UTC)

It works now. Many thanks. Denied (Talk) 16:30, 6 May 2022 (UTC)

Automate all the things

Hi foolks.

Two important Main page sections have been upgraded to better accommodate our workflow: the Did you know... and Feature article sections. Dyk facts are now refreshed every 15 days and the featured article is refreshed once a month. While this saves us a lot of work by reusing existing good content, some content may be slightly outdated due to previous ^{and future?? maybe???} updates.

I'd like to ask you to keep an eye out for outdated featured blurbs and facts and to update them as needed. A list of dyk facts is available here and a list of featured blurbs can be found here. Please delete any existing translations when updating outdated content, as they are also likely outdated.

Note for translators: I don't recommend translating the new dyk list for the time being (as some content may be completely rewritten or removed), but if you wanna do it anyways, please message me so that I can enable the new dyk section for your language. I'll update this message once everything is ready.

Thanks. — Tark 20:03, 12 May 2022 (UTC)

Hi all! Apologies for the delay. Both templates are ready for translation. — Tark 17:32, 22 August 2022 (UTC)

Gallery Consistency

Hi, I believe that nobody brought this topic up, if someone did, please redict me to that post...

Either way, for many of us that edits, we see that usually the "code" "<gallery perrow ="3">" orders the gallery in 3 rows. Usually this is used for multi-class cosmetic items, for example:

• Tux
• Earbuds
• Bill's Hat

But what about the cosmetic items that are NOT multi-class:

• Beep Man
• Archimedes

Moreover, what about other types of items as well:

• Saxxy
• Golden Frying Pan (Half used)
• Dispenser
• Golden Wrench

I believe that there should be a line explicitly stating when and where the perrow code should be applied, this way we create consistency between articles.

As always, I'm eager to hear your opinions on the matter. xoxo Yossef | Talk | Contributions 12:12, 17 May 2022 (UTC)

I'd like to ask why 'perrow' is even used. I've tried to see how it looks both on pc and mobile, and images scale correctly on both. Denied (Talk) 12:46, 17 May 2022 (UTC)

 Disagree – As much as I'm all for page consistency, I feel that you may be overthinking this a little. perrow is simply used to divide the number of cells in the row of a gallery, usually evenly, as it provides the best visual result compared to odd cells. There need not be an explicit rule in place to state the usage of it as it's really just a matter of editorial judgement on when and where to use it. For instance, galleries that contain lots of cells, like on the Golden Frying Pan, would end up expanding the page length and extend scroll time if the first-person views happened to be divided into rows of 3 – the class galleries consist of only 9 cells which isn't a too high number.

You could also take the single gallery cell on Archimedes under "Valve Store merchandise" and place it into the main gallery and use perrow to divide each row into cells of 3 to make it even. Golden Wrench, however, is inconsistant in comparison to the Golden Frying Pan, so feel free to change that.

As a good rule of thumb: Try to avoid perrow on galleries that consist of too many cells. Generally, try to divide the rows if you can achieve an even number of cells, specifically on class galleries. — Wookipan (talk | contribs) 20:50, 17 May 2022 (UTC)

Sorry for the late response... I believe that there should be a stated somewhere when and where to use the perrow, since every user has a different judgement and having a subjective "rule", will likely cause inconsistency in the articles. Furthermore, it may create conflict between users since they will start undoing each others edits.

I propose the following:

• Use "<gallery perrow ="3">" on multi-class cosmetic items articles.
• Use "<gallery perrow ="5">" (or 4) on articles regarding games like one.
• NO perrow on weapons, single class items, or any remaining type of articles.

Once again, by making an objective rule we will avoid in user conflicts and inconsistencies. As always, this is just my opinion, and I am happy to hear what everyone thinks, even if you disagree with my "proposal" or thoughts. xoxo Yossef | Talk | Contributions 08:11, 22 May 2022 (UTC)

For the cosmetic pages, I think there's no need to replace <gallery perrow="3"> with <gallery> (too many using perrow="3" right now). I see there's no problem on using perrow="3" on a gallery with just one image or two, let's keep it this way. On other articles (tools, weapons, events, etc) and some cosmetic pages (e.g Archimedes or Balloonicorn), whenever its needed, we just adapt the gallery. Mgpt (talk) 02:29, 29 May 2022 (UTC)

Well, it has no visual effect in the frontend aside from being viewable in the source. I wouldn't advise you to run through all articles just to remove an attribute for the sake of consistency – that sort of task is better suited for a bot – but I'm not going to stop you either if that's what you really want.

Sorry, but I still see this as a trivial matter. Having a ruleset in place to explicitly state the usage of the perrow attribute would cause more confusion than anything, and I can almost guarantee that most users wouldn't adhere to such a small detail. Wikipedia does have some technical notes related to its usage, but those are not "rules" but instructions. I'd still choose to leave it to editorial judgement and common sense, but if you really want such rules pushed, then please make a draft in your user space and present it here first. — Wookipan (talk | contribs) 20:29, 9 June 2022 (UTC)

Interwiki table update

Can someone please update the "l4d" interwiki link from http://left4dead.wikia.com/wiki/$1 to https://left4dead.fandom.com/wiki/$1? -- PanchamBro (talk • contributions) 15:25, 1 July 2022 (UTC)

 Done. — Tark 19:33, 1 July 2022 (UTC)

Some wiki things I need opinions on

A long while ago I made some bug guidelines, if anyone wants to give feedback on them that'd be appreciated. Use the talk page here (the current feedback has already been worked into it).

I've also got 2 templates that I made ages ago, one for personal use (Explainer) and one for general discussion use (vote). Not sure if anyone sees use in either of these 2 templates, the idea behind the vote template is to create an easy overview of everyone's standpoints (not indended to remove the discussion altogether, just intended to be put at the top of a discussion that may get very large so people's  support and  against don't get buried in discussion).

The explainer template I've made for personal use on my userpage, but I thought it may also be useful for explaining vague patch notes or if something needs more explaining in the damage and function time tables but don't want to make the tables too large.
GrampaSwood (talk) 15:31, 26 July 2022 (UTC)

I really like the vote template you created :). Very simple and as you mentioned, it is better to have one big picture of who agrees or disagrees in a subject. My only concern is that, based on what i’ve seen, not all the proposals that people bring gets the necessary traffic in order to make a whole table, usually we get three comments and thats it. I may be wrong, but I feel that it won’t be a game changer, because of what I mentioned.

As for the Explainer template, I’m all on making templates in order to save time and enhance the workflow. Despite this, I was not yet in the need for it, but that does not mean that it is a bad template, I’m sure that users that usually interact more with newcomers or other users, might find the template useful for any scenarios that might incur. Yossef | Talk | Contributions 20:42, 27 July 2022 (UTC)

Yeah I thought the same about the vote table, it's merely for stuff such as the recent Talk:Taunts discussion about the names of taunts. It can allow for easy voting while the actual discussing can be easily done regardless.

I've also received mgpt's opinion on this, they stated the explainer template could be useful as well as the vote template "for discussions that really need it" (<which is what my intention was). Just putting it here to collect opinions in the same place.
GrampaSwood (talk) 20:46, 27 July 2022 (UTC)

Wow that's a lot of {{Tooltip}}! I don't like these because they are not visible on the mobile devices without a mouse. --Alex┋T 13:24, 30 July 2022 (UTC)

Unusual effects table

Hello everyone, I need your opinion on this table, copied from the Summer 2021 one (just an example of many: Unusual effects). This table doesn't use parentheses, which are different in the chinese language. What do you think? Thanks. Mgpt (talk) 17:44, 31 July 2022 (UTC)

  Great idea, though I think it's best to keep "RED" and "BLU" black instead of team-colored. - BrazilianNut (talk) 17:52, 31 July 2022 (UTC)

Removed the colors, thanks :D Mgpt (talk) 20:28, 2 August 2022 (UTC)

Gallery images that show what's visible during normal gameplay

I believe such images should not be included in galleries, as they show what can already be seen in-game during normal gameplay, has already been described in the description, and can be considered an equivalent of obvious trivia ("Something that is inevitably discovered simply by playing the game or casually studying the subject in question").

I'm talking things like the back of the Bolshevik Biker, which everyone who is or meets a Heavy wearing it can see, not things like the back face of the Snowwing, which is usually blocked by the Scout's backpack. - BrazilianNut (talk) 17:26, 4 August 2022 (UTC)

I think one thing that might be neat is displaying the back in the infobox image as well as the front (if necessary), as that's what it's for anyways. Although I'd say it'll have to be a case-by-case basis, the Bolshevik Biker already has the workshop image showing the back too. I'd say either do what I said or remove them altogether if it's obvious in gameplay (although do note that the trivia guidelines don't apply outside of trivia).
GrampaSwood (talk) 17:27, 4 August 2022 (UTC)

First rank for the Spirit of Giving is not being translated to other languages

Despite added translations, the first rank is not changing its name for other languages. This happens to all languages. Changing the name in Template:Spirit Of Giving ranks from 'none' to its correct name from Template:Dictionary/items#Strange ranks returns red link. Denied (Talk) 20:01, 7 August 2022 (UTC)

Not sure where you don't see it being translated, on all the Spirit of Giving pages the first rank is translated properly.
GrampaSwood (talk) 20:07, 7 August 2022 (UTC)

Late reply, but the issue was resolved by Tark. Denied (Talk) 15:40, 19 August 2022 (UTC)

Adding alt text to images

There doesn't seem to be a consistent method of adding alt text to pictures found in articles, which is a major accessibility barrier. It would be great if this could be managed somehow. Crabguy (talk) 20:20, 18 August 2022 (UTC)

So for images using [[File:]], the alt parameter should work fine. Images in the <gallery> tag can also use the |alt=, but it should be between the description text and the filename such as

File:Scout.png|The Scout from Team Fortress 2|The Scout. As for any templates, a separate parameter would have to be added.
GrampaSwood (talk) 20:37, 18 August 2022 (UTC)

While we appreciate the initiative, adding alt texts manually to images would be an awful lot of work for something that won't hold that much value to us.

In terms of accessibility for screen readers, articles generally are well-written and tend to go in-depth about its content. In some cases, image thumbnails have visible text which describe the image.

Unfortunately, we've had users in the past that wanted to take on big tasks like this one, only to never fully go through with them, which left some inconsistencies or had us clean up after them, so we're sometimes skeptical on the delivery.

If you still believe that this is needed, we could add automatic support for it through the necessary templates, in the same way that Wikipedia does; however, galleries and such would need to be done manually. — Wookipan (talk | contribs) 22:04, 18 August 2022 (UTC)

Staff emergency meeting

Staff emergency meeting. — Tark 14:16, 10 October 2022 (UTC)

Adding a notice to Talk pages

Denied has recently made a suggestion that I agree with. In their words: "Every talk page needs some edit note like THIS IS NOT A PLACE FOR DISCUSSIONS OUTSIDE OF THE ITEM ITSELF. FOR COMMUNITY DISCUSSIONS GO TO THE STEAM FORUMS."

While not necessarily with those words or formatting, I do believe adding such a notice could discourage new contributors from adding topics, sometimes creating entirely new talk pages in the process, with questions like "how do i shot bullet?" or statements such as "pootis man is funny" while teaching them the proper place for them. - BrazilianNut (talk) 16:58, 1 September 2022 (UTC)

I'm neutral on this, I'll support it but I also think it's not too large of an issue currently. Also try avoiding using {{Quotation}} on talk pages as it breaks them.
GrampaSwood (talk) 17:03, 1 September 2022 (UTC)

I think the more common misuse of talk pages is to use the talk page for talking about the page's subject, but they can both be encompassed in one message. BrazilianNut, are you picturing something like this being on MediaWiki:Newarticletext? Naleksuh (talk) 20:20, 1 September 2022 (UTC)

No, I'm not, Naleksuh, and that's the misuse I was trying to say, but I admit I failed to convey that thanks to bad examples and maybe some poor wording. - BrazilianNut (talk) 22:20, 1 September 2022 (UTC)

If you didn't mean that, then what did you mean? I was hoping you would elaborate rather than simply saying no. Naleksuh (talk) 06:24, 2 September 2022 (UTC)

An editnotice similar to Brain Bucket or Chicken Kiev is what I imagine he means, but on every page starting with Talk:.
GrampaSwood (talk) 10:57, 2 September 2022 (UTC)

What GrampaSwood said; I meant a red edit notice, like the ones for those two articles, at the start of Talk pages telling contributors that a Talk page is for discussing the article itself, not for asking questions or making comments about the article's subject (like using a weapon's Talk page to ask how to best utilize it or to comment how they think it should be buffed/nerfed), and that they should use the Steam Forums for such things (maybe providing a link as well).

Apologies for any confusion caused by bad examples or by making my messages too short. - BrazilianNut (talk) 12:17, 2 September 2022 (UTC)

That's a tough nut. It might help to tokenize the page titles in the tag, somehow. "This <item's> Discussions are for talking about issues within the <item's> page, not for talking about the <item>." That is not easy to pose or parse. Imagine the translators. You may have mentioned this, but if you go with the tag, it should clearly state to the reader that it has a link to the full explanation of the policy.

M I K A D O 282 ⊙⊙⊙⊙⊙⊙ ⊙⊙ ⊙⊙ (Contact Mikado282 (SM)) | (contribs) (Help Wanted!) 13:20, 2 September 2022 (UTC)

 Nope. It's possible, but the amount of work involved in adding and maintaining it is far greater than simply reverting the edit and messaging the user. — Tark 21:26, 2 September 2022 (UTC)

Create an exception for an item link from the dictionary

Please read the discussion here.
Does anyone know how to create that kind of exception? Tiagoquix (talk) 19:41, 7 September 2022 (UTC)

Pages with the fewest revisions - redirects

Pages with the fewest revisions (long loading) -- there are many redirects here with names in other languages, such as Spanish and Russian. Are they OK to be in the Wiki or should they be deleted? Tiagoquix (talk) 02:18, 19 September 2022 (UTC)

Unless redirects are actively harmful, there is no reason to remove them.
GrampaSwood (talk) 09:39, 19 September 2022 (UTC)

Item schema updates with blog posts

How do we go about updates with blog posts but no actual updates? For example, TF2 was not updated on October 11th 2021 outside of an item schema update and a blog post, but October 11, 2021 Patch exists. Also the "Patch 2" for September 26, 2022 Patch even though I'm pretty sure patch 2 was item schema only. Do these count as updates? Should they at least be flagged? Naleksuh (talk) 03:04, 27 September 2022 (UTC)

Update: Eric Smith confirmed that there were really 2 patches today. Though the point remains about the first one. Naleksuh (talk) 04:48, 27 September 2022 (UTC)

They are Patches. Updates and Patches are synonymous. AFAIK, there was no Blog post for these Patches. What do you mean tagged?

M I K A D O 282 ⊙⊙⊙⊙⊙⊙ ⊙⊙ ⊙⊙ (Contact Mikado282 (SM)) | (contribs) (Help Wanted!) 00:37, 28 September 2022 (UTC)

I think you may have misunderstood me. I mean that there was a post announcing an update/patch but the game was not actually updated. What happened was an item schema update, and the change to Corpse Carriers was announced there. There was no hlds email, nor any update to install. Naleksuh (talk) 18:19, 28 September 2022 (UTC)

CSS pages deletion request

Since I can't mark them for deletion, could the TF Wiki's staff delete them for me? Thanks in advance.
User:Tiagoquix/common.css & User:Tiagoquix/vector.css Tiagoquix (talk) 22:51, 27 September 2022 (UTC)

I can delete most pages, but I can not delete or edit these. It has high protection that I can't touch.

M I K A D O 282 ⊙⊙⊙⊙⊙⊙ ⊙⊙ ⊙⊙ (Contact Mikado282 (SM)) | (contribs) (Help Wanted!) 00:55, 28 September 2022 (UTC)

 Done — Tark 11:42, 28 September 2022 (UTC)

Module:Availability

The winter2016 parameter links redirect to the wrong page. I also made a topic to add drop-expired. Could someone look at it? Thanks Mgpt (talk) 22:38, 8 October 2022 (UTC)

 Fixed. Thanks. — Tark 17:41, 10 October 2022 (UTC)

contributed-by auto update

Can we have some ways to auto update contributed-by for cosmetics for different languages? Lot of times only English get updated and updating all other languages is repetitive and exhausting. Hope there could be a contributed-by dictionary or a bot that auto sync this. --Alex┋T 22:54, 9 October 2022 (UTC)

It would be really helpful to have a dictionary for that, however updating the current pages would be very time consuming.

You can force WindBOT to recheck the page, and it should automatically sync the contributed-by parameter. Here is an example: 1) input, 2) result. — Tark 14:35, 10 October 2022 (UTC)

Hope it can be a scheduled work for all cosmetics page for the bot :/ something like every 2 weeks sync all contributed-by of recent added cosmetics, and every 6 month sync all contributed-by of all cosmetics. --Alex┋T 02:30, 11 October 2022 (UTC)

200k celebration

Hello everyone, this is a reminder to let you all know that we are fast approaching 200,000 registered users.
Last milestone which was 100K, happened back in 2019 (3 years ago), this is a good opportunity to give everyone a pat on the back for bringing the wiki to where it is today.
At the time of writing, we are at 199,535, we can positively estimate that we will reach 200K in the next few days or in the coming weeks.

Luno 🎃 16:53, 15 October 2022 (UTC)

Maybe we can do something different this time around. Instead of HLMV shots of people's loadouts, why not invite 32 players on an empty server and do screenshots there or something? I dunno. The only problem is that there would be a limit of 32 players. Last year, we had exactly 32 people on the group photo. - ▪ - 17:35, 15 October 2022 (UTC)

  I think that making some sort of celebration is a wonderful idea, I personally think that doing another HLMV shot is not a bad take. Moreover, one of the downsides of going to an empty server, is that not everyone shares the same time-zones, it could be difficult for everyone to join a server at the same time, in my opinion. Yossef • Talk 17:49, 15 October 2022 (UTC)

True, maybe someone who is good at SFM could do a SFM poster or something, for variety's sake. I'm not good with SFM. But, we can continue with the HLMV shot. We have more people working on images now, so each one can work on a few loadouts collaboratively. - ▪ - 17:59, 15 October 2022 (UTC)

If we can get a group photo with HLMV or SFM done, then maybe we could somehow get 3 celebrations throughout 3 different time zones so that everyone could celebrate on a server or something. It would need some planning obviously, but I think it could work.
Andrew360 18:08, 15 October 2022 (UTC)

I remember when 100K hit, I was personally not part of the celebration since I was not made aware it was happening, I'm very surprised to see how soon 200K was reached though.

Luno 🎃 18:16, 15 October 2022 (UTC)

Ooh, if we're doing another celebration, I definitely want to be a part of it. My loadout's a Wiki Cap, Cuban Bristle Crisis, and the Commissar's Coat, just like last time. I'd like to be holding either my Factory New Top Shelf Minigun or Golden Frying Pan. If we're doing a group shot in a server, I probably won't be around to be on it, but I'd try. — 08:41, 17 October 2022 (UTC)

I don't know how this was done last celebration, but I made a page for how we could organize HLMV image requests. The page is right here, pending means that the user hasn't approved their image yet in case they want a different pose or some small changes. Thoughts?
Andrew360 15:41, 17 October 2022 (UTC)

  I like that format, pretty intuitive and straightforward. Let us know when whoever wants to participates can fill the request table ♥. Yossef • Talk 19:27, 17 October 2022 (UTC)

Alright then, I made a new page where all the images and requests will be now. The page is right here, if any other image makers want to complete requests/add images to the image table then go ahead!
Andrew360 21:10, 17 October 2022 (UTC)

┌────────────────────────────────────────────────────────────────────────────────────────────────────┘ Not to be a party popper, but the majority of our registered users are spam bots. We are, however, approaching 70k articles, which is worth celebrating. — Tark 00:07, 18 October 2022 (UTC)

User:Tark Where do you get the number of spam bots from? If you can find it automatically, what are CheckUsers doing? Also, "not to be a party popper", but the majority of our articles are the same article over and over in other languages. So there aren't really anywhere near 70k articles. Naleksuh (talk) 00:16, 18 October 2022 (UTC)

And then like last time, Gabrielwoj will tell you that it's just for fun, bots are mostly part of TF2 culture anyways, and we could make the cheese wheel chart argument pointing out all the shy users/those that don't know what they're doing/one offs, on the other hand 100k articles sounds like a big celebration, its years off though it seems, but we're getting there.

Luno 🎃 00:20, 18 October 2022 (UTC)

Also, my own loadout image is reserved, I just haven't done yet (pls don't get from my userpage). Just letting image editors know. - ▪ - 00:57, 18 October 2022 (UTC)

Here is a list of newly-made accounts. They're mostly bots.
GrampaSwood (talk) 10:12, 18 October 2022 (UTC)

Also, information for image creators: We should use the default lightrot on all of these loadout pictures, so no picture looks too drastically different from the other, in terms of lighting. The default values for lightrot are (0.000000 180.000000 0.000000). - ▪ - 12:16, 18 October 2022 (UTC)

We hit 200k users (and bots), by the way. - ▪ - 01:21, 19 October 2022 (UTC)

Cheers to that ! 🥂 Here is to many more years of translating, polishing, and new contributors.

Luno 🎃 03:17, 19 October 2022 (UTC)

So now that all the image requests are complete, I think we should make a deadline for requests so that we can make the full group photo and make the userbox soon. I was thinking maybe October 24th should be the deadline. As for the in game server celebration idea, I was thinking the 3 times could be 4 AM EST, 10 AM EST, and 6 PM EST, and the day we do this should be on a weekend. Thoughts?
Andrew360 14:42, 20 October 2022 (UTC)

┌────────────────────────────────────────────────────────────────────────────────────────────────────┘ Sounds nice, would have been nicer to do the end of the month or even the end of Scream Fortress, I feel like there are still a lot of people that are unaware of this little celebration, to me it feels a little like a family gathering rather than a simple number celebration, which is sweet in a way, hopefully mostly everyone was made aware so that they had a chance to hop on.

Luno 🎃 21:57, 20 October 2022 (UTC)

Looks like one more person has submitted a request, so I'll move the deadline to October 28th now in case more people add requests.
Andrew360 14:36, 24 October 2022 (UTC)

Thoughts on this group photo? Is there anything that should be changed/are there any other last requests? Andrew360 14:37, 29 October 2022 (UTC)

Some of the characters are bigger than the rest, probably will require resizing some of them (my Scout, for instance, looks the biggest out of the group), while the Pyro looks the smallest. I think some of the classes could be more close to each other like the 100k group image. The Demoman at the right is floating a little, too. I can try adjusting these things if you would like. - ▪ - 15:47, 29 October 2022 (UTC)

Same opinion here, some mercs looks small and/or are spaced apart. But otherwise amazing job on the group image. Decimate (talk) 18:29, 29 October 2022 (UTC)

Looks like me (the BLU pyro) and a few other people only have the upper body and shorter than other people. --Alex┋T 20:34, 29 October 2022 (UTC)

Alrighty then, I tried to make everyone a bit more closer together and I tried to scale some of the images. If this still isn't good enough, then maybe Woj or someone else could try to make the group photo.
Andrew360 20:08, 30 October 2022 (UTC)

After I'm done with the 3 upcoming paint variants I'm about to upload, I'll make my own version with a different filename (not a replacement). The 2nd version looks a lot better than the first, but I think a few things could be resized, which I'll be doing on my version. - ▪ - 14:09, 31 October 2022 (UTC)

Here's my version. I made everyone facing right on the right side, and everyone facing left on the left side. The Demoman wielding the Scottish Handshake was made on the middle since he is mostly facing center. Me, Andrew and Luno are around the middle to represent the image creators for the image:

If this is the preferred version, feel free to rename the file to File:200k-groupphoto.png - ▪ - 13:12, 2 November 2022 (UTC)

┌────────────────────────────────────────────────────────────────────────────────────────────────────┘Sorry for extending the image border LOL.
GrampaSwood (talk) 13:17, 2 November 2022 (UTC)

All good bro. Gotta flex that Australium Amby. - ▪ - 13:22, 2 November 2022 (UTC)

Amazing work guys, you outdid yourselves ♥ Yossef • Talk 13:48, 2 November 2022 (UTC)

Thank. I find it a bit ironic that the 200k group photo has less people on it than the 100k one. But hey, what can ya' do? Some people come and go, it's still a nice ol' group picture. - ▪ - 14:21, 2 November 2022 (UTC)

It looks great! I also agree that I wish more people joined, but it's still good. Maybe at 300k if we still want to do another group photo we'll get more people, though it will probably be a while before 300k.
Andrew360 15:35, 2 November 2022 (UTC)

Well done all, looks great! Hope that we can get an even bigger celebration planned for 250k/300k. Epsilonal (talk) 23:43, 2 November 2022 (UTC)

It looks like everyone agrees with this version of the image, however AlexT told me that the grenades on his image should've been hidden, so I uploaded a new version of his image without grenades. So for the final group photo if you could change AlexT's image to the new version that would be appreciated. Then when the final group photo is uploaded we also need to make a userbox for it.
Andrew360 16:15, 7 November 2022 (UTC)

I updated the image with the latest revision of AlexT's loadout. - ▪ - 17:00, 7 November 2022 (UTC)

The Australium Frontier Justice goes across almost all of the Heavy to the right. Can you turn it to face the camera more? It doesn't look like any of the other characters have this problem, looks like it is just that one that is covering up other characters. Naleksuh (talk) 20:38, 9 November 2022 (UTC)

That looks fine to me. It's not covering anyone's face, so I don't see the problem, and the Heavy in question has the cosmetics being fully visible. The 100k picture had some instances of that, too. - ▪ - 21:31, 9 November 2022 (UTC)

I didn't see the 100K picture, but it won't be a big deal if people think it looks better this way. Naleksuh (talk) 22:42, 9 November 2022 (UTC)

I made the userbox. It's here: {{User 200k registered}}. It's a little larger in height than the 100k one, but I think it looks good. - ▪ - 15:06, 10 November 2022 (UTC)

Thank you everyone that participated; the picture and template are amazing. Good job <3 Yossef • Talk 18:54, 10 November 2022 (UTC)

┌────────────────────────────────────────────────────────────────────────────────────────────────────┘Thanks everyone! The group photos looks great! and Thanks Andrew360 for making my portrait 3 times :D. --Alex┋T

Community announcers with a large amount of response

So the {{Audio Nav}} states that community announcers should be on the map page rather than having their own page. However, Davy Jones has its own responses page. I suggest that for announcers with large amount of voice lines, such as the Crasher voice lines and the Bread Space voice lines, they should get their own page. This would reduce the amount of clutter on the page. I suggest it would have to be judged on a case-by-case basis. For example, the Crasher announcers have 100+ voice lines, but the Toastmaster only has 10.
GrampaSwood (talk) 21:46, 29 October 2022 (UTC)

 Agreed · Ashe (talk) 21:54, 29 October 2022 (UTC)

  I agree with that statement. However, for consistency sake, I think that perhaps making an additional “category” can be created for announcers with few voice lines, in the same Nav. This category can be called something around “Minor Announcers”.

Yossef • Talk 21:59, 29 October 2022 (UTC)

How about a "Community announcers" page instead of one page for every announcer with lots of lines? - BrazilianNut (talk) 22:28, 29 October 2022 (UTC)

Could also work, I'm in favour of either.
GrampaSwood (talk) 22:48, 29 October 2022 (UTC)

Wait, I misread your idea Swood. I would prefer @BrasilianNut 's idea, because of Halloween Boss voice responses · Ashe (talk) 23:26, 29 October 2022 (UTC)

  I like BrazilianNut's idea better. Furthermore, this will help us in the future when more possible announcers are added to the game. Yossef • Talk 09:40, 31 October 2022 (UTC)

I would agree with Gramps on his first post, there should be a subpage for announcers who only have basic lines for like KoTH and Control Point maps. But, all of the announcer voices are on either Payload maps or that one Player Destruction map Farmageddon. However Braziliannut's idea is probably the best way to go about doing this, the page is going to be absolutely massive as a result of mixing all of them in there at once though.ShadowMan44 (talk) 23:27, 30 October 2022 (UTC)

  In case you haven't done this yet. Honestly, I don't see the point. IMO, list of responses specific to a map should be on the map's page. Clutter could be controlled by collapsing the section. Just on opinion. A reason that Davey Jones should have been worked into tbe map's page is that his cue lines are integral to the map's mechanics, so, the list should be integral to the page. Astronaut will probably only ever have unintelligible responses on one map.

M I K A D O 282 🎃🎃🎃🎃🎃🎃 🎃🎃 🎃🎃 (Contact Mikado282 (SM)) | (contribs) (Help Wanted!) 02:00, 10 November 2022 (UTC)

  +1 for "Community announcers page" — Tark 01:42, 21 November 2022 (UTC)

Twinkle in TF2wiki?

I wonder if we can import some practical tools like Twinkle to maintain a page? It can also help us to combat vandalism.(And do a lot of stuffs...)---- BEUFK-Contributions-Talk 12:52, 23 November 2022 (UTC)

Looking through some of its functionality, it seems like it doesn't offer much useful functionality for users here. Mods/editors here are active enough to be able to catch vandalism quite quickly anyway and its other features seem to be just buttons to quickly add {{delete}} or open up a discussion for deletion (which is already very easy).
GrampaSwood (talk) 13:07, 23 November 2022 (UTC)

Excellent idea, but we don't have the Gadgets extension enabled :c — Tark 15:16, 23 November 2022 (UTC)

Any guide on how to create good User: page?

So I was wandering around the wiki and noticed how great some User: pages look and I just can't create a good one. Is there any guides for it? Yaroslav (talk) 15:55, 30 November 2022 (UTC)

You can check user pages of other users and use a bit of everything you like on your page, or if you know css you can create something more complex. Or shamelessly copy someone's else page :))). Denied (Talk) 18:19, 30 November 2022 (UTC)

Personally, it may require some CSS skills...---- BEUFK-Contributions-Talk 02:27, 1 December 2022 (UTC)

Slap some plain text up and claim you'll eventually make it better :) Jh34ghu43gu (talk) 04:22, 1 December 2022 (UTC)

You should learn some CSS, and Since this wiki is based on MediaWiki, you can use Templates, User boxes, etc. Just surf on some user pages and if you like it, take some code from it (if allowed to).

You need to make unique, something you would like to see all day! -- https://wiki.teamfortress.com/wiki/Category:Templates -- And the User info Boxes Remember not editing anything that is not yours, Have fun in your journey.

⇨ maxwel (talk) 01:40, 22 January 2023 (UTC)

Russian wiki's cosmetic items "Update list" is done incorrectly?

Before I start, there is an example:

(English) The Glengarry Bonnet was added to the game. (Item name is listed. It's Glengarry Bonnet).

(Portuguese) A Boina de Glengarry foi adicionada ao jogo. (Item name is listed. It's Boina de Glengarry).

(Russian) Предмет был добавлен в игру. (Item name is not listed). It should be Гленгарри была добавлена в игру (Item name is listed. It's Гленгарри).

So almost every Russian cosmetic page lacks name of a cosmetic item in update list.

Should it be fixed or anything?

I changed some cosmetic pages. (It doesn't only focus on update list, so if you going to revert it back please only revert that). I think it would take a week to "fix" it for every cosmetics listed on Cosmetics page.

Here is more examples:

(English) Added a community-contributed description for the Texas Ten Gallon. (Item name is listed. It's Texas Ten Gallon).

(Portuguese) Adicionada uma descrição contribuída pela comunidade aos Dez-Galões do Texas. (Item name is listed. It's Dez-Galões do Texas).

(Russian) Добавлено описание от сообщества. (Item name is not listed). It should be Добавлено описание от сообщества для Большой техасской шляпы (Item name is listed. It's Большая техасская шляпа).

(English) The Whoopee Cap can now be uncrated with Unusual quality. (Item name is listed. It's Whoopee Cap).

(Español) La Corona de Yupi ahora puede ser obtenida en aspecto Inusual. (Item name is listed. It's Corona de Yupi).

(Russian) Теперь может быть необычного типа. (Item name is not listed). It should be Молодежная корона теперь может быть необычного типа. (Item name is listed. It's Молодежная корона).

Yaroslav (talk) 19:58, 3 December 2022 (UTC)

I wouldn't say they are incorrect; I would say they use a different format. I have seen articles that use "This item was added to the game" instead of "[Item] was/were added to the game" and articles that use "Updated the description" instead of "Updated the description for [Item]."

While the update history is mostly 1:1 with the official patch notes, there are instances of differences between them, such as new items being part of a case ("[Item] was added to the game" in the update history versus "Added the [Case] / Contains [#] new community-created cosmetic items" in the patch notes) or a note that mentions different items ("Updated models/materials for [Item]" in the update history versus "Updated models/materials for [Item] and [Other Item]" in the patch notes).

I would say that, as long as the wording is left as close to the original as possible, it's fine. What should not be done is, for example, having the update history read "Changed the description" when the patch note reads "Updated the description." - BrazilianNut (talk) 22:03, 3 December 2022 (UTC)

Patch notes references

Should we use == References ==, or === References ===? Tiagoquix (talk) 01:32, 8 December 2022 (UTC)

I think == References == is the correct one but there are some patch pages with === References ===. Mgpt (talk) 13:42, 8 December 2022 (UTC)

Yeah, probably == References == is the one we should use. We could add a global filter, I think. Tiagoquix (talk) 14:35, 8 December 2022 (UTC)

  There is an inconsistency in the patch notes in this regard. In my opinion, I prefer keeping it the same as the other articles, that means using this == References ==. Yossef • Talk 15:01, 8 December 2022 (UTC)

  +1 for == References ==. - BrazilianNut (talk) 15:12, 8 December 2022 (UTC)

 Agree On a personal note, the "References" is certainly as important as the other parts of an article.------BEUFK-Contributions-Talk 12:28, 10 December 2022 (UTC)

== References == should be used.
GrampaSwood (talk) 00:21, 31 January 2023 (UTC)