Difference between revisions of "Template talk:Item infobox"

From Team Fortress Wiki
Jump to: navigation, search
("Medieval" yes/no info?)
m (Request for /fr)
 
(61 intermediate revisions by 33 users not shown)
Line 1: Line 1:
== Some thoughts ==
+
{{Talk archive
 +
| arc1name = Archive 1
 +
| arc1link = Template talk:Item infobox/Archive 1
 +
}}
  
* Ammo section needs to be hidden for melee weapon unless any of it's parameters are defined (the Sandman has 1 ammo for example).
+
== Craftable tag ==
* No need to support {{code|name-override}}, {{code|NAME}}, {{code|name}} and {{code|title}} at all (i.e. pick just one). We should stamp that out so we don't have to do it all over again.
 
** Also only need two different parameters that deal with the name, as you noted {{code|loadout-name}} that includes things like {{code|the}}, {{code|der}}, {{code|el}}, {{code|la}} etc. and {{code|name}} for cases where there page name != item name (e.g. all language pages)
 
* Document what the trade/paint/craft/rename parameters do by default (I guess this will come with extended documentation)
 
* How are we defining the tradability of stock weapons? Are they untradable because they aren't accessible by default? Or are they tradable because they can be renamed and then traded?
 
* {{tl|Class name}} in conjunction with {{code|used-by}} to solve the same issue that was solved with slot names.
 
* Does {{code|backpack-image}} need support?
 
These aren't criticism, just immediate problems that need solving that I am sure you are aware of anyway. Your work is excellent and invaluable! -- [[User:Pilk|Pilk]] <sub>([[User talk:Pilk|talk]])</sub> 12:31, 8 November 2010 (UTC)
 
  
:Only just noticed this, lol.
+
There seems to be quite some confusion around the "Craftable" tag, I propose we change it to "Usable in<nowiki><br></nowiki> Crafting". Although this may not work in all languages.<br>[[File:BLU Wiki Cap.png|20px|link=Wiki Cap]] | [[Help:Group rights|<span style="color:green;font-family:TF2 Build;">s</span>]] | [[User:GrampaSwood|<font color="DB9C1F">GrampaSwood</font>]] ([[User talk:GrampaSwood|<font color="DB9C1F">talk</font>]]) 12:14, 23 August 2023 (UTC)
:* That's a good idea, I'll work that in.
 
:* I added them in case somebody tries to add a display title /after/ we parse the pages. I will still change all instances to 'name', however. But this is just a little backwards compatibility.
 
:* {{c|Done}}.
 
:* This is an issue I'm leaving to others to decide, as I don't believe a solution within the template is the best idea when you consider user friendliness and technical workability with translation switching. There are so many variations that it's impossible to define within the infobox.
 
:* I'm not sure. I was planning on leaving 'used-by' as a simple text parameter as there wasn't any need to categorize or anything so no switch was required. It's certainly possible to have it as: "{{code|1={{!}} used-by = scout}}" and then autotranslate through the class name template, but when you consider it, most users translate the link already (i.e. {{code|[[Scout/ru|Разведчик]]}}).
 
:* I can't think of any circumstances where 'backpack-image' would need to be used, as all the backpack images have been uploaded to file names matching the page names. User pages, etc, can simply just use a file redirect. I'll be phasing it out anyway when I parse over pages.
 
:Thanks heaps for these notes, though, Pilk :) [[User:Seb26|<font color="#0B61A4">'''seb26'''</font>]] [[User talk:Seb26|<span style="font-size:95%;">[talk]</span>]] 06:37, 9 November 2010 (UTC)
 
  
==Description contributor==
+
: Nope. That's what the tooltip is for + that's how the game labels this attribute. <!-- problem in chair, not in computer --> — [[User:Tark|<span style="font-weight:bold;color: #5BC236">Tark</span>]] 12:50, 23 August 2023 (UTC)
How to deal with description contributor (for hat) ? Add to contributed-by or it needs a new param to be created ? --[[User:Giraf|Giraf]] 09:45, 19 November 2010 (UTC)
 
:What do you mean description? That field is just for the name of the contributor, what information do you want to add? [[User:Moussekateer|Moussekateer]] 09:54, 19 November 2010 (UTC)
 
::Valve launched a contest to add descrption to hats. So now some hats have two contributors: one for the model and one for the description of the hat. For example, the Bloke's Bucket Hat: AAA_BATTERY is the contributor of the model and Reclaimer077 is the contributor of the description (ie Gone Snipin'.) --[[User:Giraf|Giraf]] 10:08, 19 November 2010 (UTC)
 
:::I see what you mean. Well the person who contributed the description is already documented in the article but I suppose moving it to the infobox might make sense. [[User:Moussekateer|Moussekateer]] 10:10, 19 November 2010 (UTC)
 
::::We already have a description info in the trivia for each hat. I don't think we should saturate the infobox. The person who wrote the description is not nearly as important as the person that made the model. Just sayin' &ndash; [[User:Smashman|<span class="mod">Smashman</span>]]<sub>&nbsp;([[User_talk:Smashman|talk]])</sub> {{sta}} 11:02, 19 November 2010 (UTC)
 
:::::Well I think there should be a more elegant way of displaying the description winners but yea I agree the infobox is getting cluttered. [[User:Moussekateer|Moussekateer]] 11:09, 19 November 2010 (UTC)
 
  
==Availability==
+
::On the item it says "not usable in crafting", which I think is a lot easier to understand than "Craftable" (especially because several people have been confused by this term). It's also not immediately obvious that there is a toolip, especially because it's kinda blocked by the link underline. Tooltips also aren't viewable on mobile, and this is the only term that requires it (besides the "craft no.", but that could be changed to "craftable" in that case). Maybe change how the tooltip is done instead?<br>[[File:BLU Wiki Cap.png|20px|link=Wiki Cap]] | [[Help:Group rights|<span style="color:green;font-family:TF2 Build;">s</span>]] | [[User:GrampaSwood|<font color="DB9C1F">GrampaSwood</font>]] ([[User talk:GrampaSwood|<font color="DB9C1F">talk</font>]]) 13:25, 23 August 2023 (UTC)
I'm going to suggest that since this template already performs automatic categorization for [[Primary]], [[Secondary]] and [[Melee]] weapons, that this be extended to automatically categorize weapons into <nowiki>[[Category:Stock Weapons]]</nowiki> and such too. I think it could easily be done using the Availability parameter. [[File:Infisig.png|60x60px|link=User:Infi^|Infi^]] {{adm}} 22:08, 4 December 2010 (UTC)
+
::: {{c|Nope}} It would honestly appear less harmonic and look slightly out of place compared to the other labels. I think a better compromise would be is to change the tooltip style, as you mentioned. I've thought about making a custom tooltip component (which should also fix the mobile issue) for a while now, so maybe now's the time to get down to it. Perhaps add in an icon prefix exclusive for infobox labels to better highlight it as an interactive element. — [[User:Wookipan|<span style="color:#db9c1f">'''Wookipan'''</span>]] <small>([[User_talk:Wookipan|talk]] | [[Special:Contributions/Wookipan|contribs]])</small> 21:10, 23 August 2023 (UTC)
  
== "Medieval" yes/no info? ==
+
:::{{pro}}'''Agree''' with GrampaSwood. - [[User:BrazilianNut|BrazilianNut]] ([[User talk:BrazilianNut|talk]]) 13:33, 23 August 2023 (UTC)
 +
:::: I agree with Wookipan's suggestion of modifying how tooltips display to fix the issue. I do agree that confusion regarding this vs the availability designation of "craft" could be argued for, and I think Wookipan's solution is the way to go about it. I have my own gripes with the "craft number" variable on the infobox, since it was briefly mentioned, as none of the cosmetics in the last ten years have actually been craftable to have them; but that's a different complaint. — [[File:User ThatHatGuy Signature Icon.png|30px|link=User:ThatHatGuy]] [[File:User ThatHatGuy Signature Talk.png|30px|link=User talk:ThatHatGuy]] [[File:User ThatHatGuy Signature Contribs.png|30px|link=Special:Contributions/ThatHatGuy]] 01:33, 29 August 2023 (UTC)
 +
{{outdent|4}} <!-- outdenting at 4? Preposterous! -->
 +
Heya folks, as I mentioned earlier in this discussion, I've been working on a custom tooltip component. You may test it out here [[User:Wookipan/Sandbox]]. It works on mobile, too, and I've made sure that tooltips with links in them become unclickable on mobile devices, which instead adds a little link icon (with the link) inside of the tooltip's contents, as mobile users can't exactly "hover" over elements in the same way as with using a mouse and would instead be directed to the page. '''Note:''' if it does not work, try refreshing the page a few times until everything seems to work properly (this is due to cache issues because of how the code is executed on userpages).
  
I think it would make sense to add a tag indicating whether a weapon is usable in Medieval Mode. Thoughts? [[User:Zrephel|Zrephel]] 08:52, 18 December 2010 (UTC)
+
I've also added icons for the item infobox labels.
:Makes sense to me. -- [[User:Pilk|Pilk]] <sub>([[User talk:Pilk|talk]])</sub> 08:55, 18 December 2010 (UTC)
+
 
 +
Please leave any feedback here. Thanks. — [[User:Wookipan|<span style="color:#db9c1f">'''Wookipan'''</span>]] <small>([[User_talk:Wookipan|talk]] | [[Special:Contributions/Wookipan|contribs]])</small> 21:00, 5 September 2023 (UTC)
 +
:I think we can just move the "craftable" tag to the bottom, nexto to craft number, and rename it to "crafting". Thus, the harmony won't break and it won't confuse users anymore. This issue has been confusing me for a long time and Valve changed it in [[October_6,_2010_Patch|this patch from 2010]]. · [[User:Ashe|<font color="DB9C1F">Ashe</font>]] ([[User talk:Ashe|<font color="DB9C1F">talk</font>]]) 23:05, 26 December 2023 (UTC)
 +
 
 +
::I like Wookipan's model; however, if the problem is tooltips not working with links on mobile, then there needs to be a way to not make the i symbols be links (because, currently, it seems they are). - [[User:BrazilianNut|BrazilianNut]] ([[User talk:BrazilianNut|talk]]) 03:53, 27 December 2023 (UTC)
 +
 
 +
:::The info symbols are part of the links themselves, and as mentioned, I've taken this into account and designed it to disable the links on mobile devices (or smaller screen sizes) to prevent the user from being directed to the page. Could you tell me which browser and device you've encountered this on?
 +
:::On a different note; due to some internal errors with the Wiki, I won't be able to properly implement this anytime soon. I am working on a solution/workaround, however in the meantime I wouldn't mind just moving the order of things as Ashe suggested, if it can help clear up the confusion. [[User:Wookipan|<span style="color:#db9c1f">'''Wookipan'''</span>]] <small>([[User_talk:Wookipan|talk]] | [[Special:Contributions/Wookipan|contribs]])</small> 22:18, 20 January 2024 (UTC)
 +
 
 +
== Request for /fr ==
 +
 
 +
This is a small visual request, punctuation in French puts a space before a double point {{code|:}}. If someone could push that exception/override, it would be appreciated, so I know how to do it in the future since the field in question is a little visually complex to digest, which made me want to edit the common string instead, but that's not ideal.<br>Field in question: {{code|Equip region:}} <span style="background:#393939;padding:2px 12px;font-family: TF2 Build;font-size: 1em;border-radius: 10px 10px 10px 10px;">[[User:Luno|Luno]] <span style="color:#FC0;letter-spacing:-2px">🪐🌕</span> [[User talk:Luno|<span style="color:#fff">Talk</span>]] <span style="color:#559655;letter-spacing:-2px">/</span> [[Special:Contributions/Luno|<span style="color:#fff">Contrib.</span>]] <span style="color:#538AC5;letter-spacing:-2px">/</span> [[Team_Fortress_Wiki:Translation_progress/fr|<span style="color:#4d748b">T</span><span style="color:#fff">ea</span><span style="color:#ab4848">m</span>]]</span> 15:46, 27 September 2024 (UTC)
 +
: done [[User:Mgpt|Mgpt]] ([[User talk:Mgpt|talk]]) 15:56, 27 September 2024 (UTC)

Latest revision as of 15:56, 27 September 2024

Talk archives
Intel blu idle.png Archive 1

Craftable tag

There seems to be quite some confusion around the "Craftable" tag, I propose we change it to "Usable in<br> Crafting". Although this may not work in all languages.
BLU Wiki Cap.png | s | GrampaSwood (talk) 12:14, 23 August 2023 (UTC)

Nope. That's what the tooltip is for + that's how the game labels this attribute. — Tark 12:50, 23 August 2023 (UTC)
On the item it says "not usable in crafting", which I think is a lot easier to understand than "Craftable" (especially because several people have been confused by this term). It's also not immediately obvious that there is a toolip, especially because it's kinda blocked by the link underline. Tooltips also aren't viewable on mobile, and this is the only term that requires it (besides the "craft no.", but that could be changed to "craftable" in that case). Maybe change how the tooltip is done instead?
BLU Wiki Cap.png | s | GrampaSwood (talk) 13:25, 23 August 2023 (UTC)
Pictogram nope.png Nope It would honestly appear less harmonic and look slightly out of place compared to the other labels. I think a better compromise would be is to change the tooltip style, as you mentioned. I've thought about making a custom tooltip component (which should also fix the mobile issue) for a while now, so maybe now's the time to get down to it. Perhaps add in an icon prefix exclusive for infobox labels to better highlight it as an interactive element. — Wookipan (talk | contribs) 21:10, 23 August 2023 (UTC)
Pictogram plus.png Agree with GrampaSwood. - BrazilianNut (talk) 13:33, 23 August 2023 (UTC)
I agree with Wookipan's suggestion of modifying how tooltips display to fix the issue. I do agree that confusion regarding this vs the availability designation of "craft" could be argued for, and I think Wookipan's solution is the way to go about it. I have my own gripes with the "craft number" variable on the infobox, since it was briefly mentioned, as none of the cosmetics in the last ten years have actually been craftable to have them; but that's a different complaint. — User ThatHatGuy Signature Icon.png User ThatHatGuy Signature Talk.png User ThatHatGuy Signature Contribs.png 01:33, 29 August 2023 (UTC)

──────────────────────────────────────────────────────────────────────────────────────────────────── Heya folks, as I mentioned earlier in this discussion, I've been working on a custom tooltip component. You may test it out here User:Wookipan/Sandbox. It works on mobile, too, and I've made sure that tooltips with links in them become unclickable on mobile devices, which instead adds a little link icon (with the link) inside of the tooltip's contents, as mobile users can't exactly "hover" over elements in the same way as with using a mouse and would instead be directed to the page. Note: if it does not work, try refreshing the page a few times until everything seems to work properly (this is due to cache issues because of how the code is executed on userpages).

I've also added icons for the item infobox labels.

Please leave any feedback here. Thanks. — Wookipan (talk | contribs) 21:00, 5 September 2023 (UTC)

I think we can just move the "craftable" tag to the bottom, nexto to craft number, and rename it to "crafting". Thus, the harmony won't break and it won't confuse users anymore. This issue has been confusing me for a long time and Valve changed it in this patch from 2010. · Ashe (talk) 23:05, 26 December 2023 (UTC)
I like Wookipan's model; however, if the problem is tooltips not working with links on mobile, then there needs to be a way to not make the i symbols be links (because, currently, it seems they are). - BrazilianNut (talk) 03:53, 27 December 2023 (UTC)
The info symbols are part of the links themselves, and as mentioned, I've taken this into account and designed it to disable the links on mobile devices (or smaller screen sizes) to prevent the user from being directed to the page. Could you tell me which browser and device you've encountered this on?
On a different note; due to some internal errors with the Wiki, I won't be able to properly implement this anytime soon. I am working on a solution/workaround, however in the meantime I wouldn't mind just moving the order of things as Ashe suggested, if it can help clear up the confusion. — Wookipan (talk | contribs) 22:18, 20 January 2024 (UTC)

Request for /fr

This is a small visual request, punctuation in French puts a space before a double point :. If someone could push that exception/override, it would be appreciated, so I know how to do it in the future since the field in question is a little visually complex to digest, which made me want to edit the common string instead, but that's not ideal.
Field in question: Equip region: Luno 🪐🌕 Talk / Contrib. / Team 15:46, 27 September 2024 (UTC)

done Mgpt (talk) 15:56, 27 September 2024 (UTC)