Template talk:Software: Difference between revisions
(automatically repair discussion (indenting will need to be done manually)) |
m (Reverted edits by DiscussionRepairBot (talk) to last revision by WisdomBot) Tag: Rollback |
||
Line 2: | Line 2: | ||
== Parameter p == | == Parameter p == | ||
text = Before <code>p=4</code> comes into use, I'd like to suggest to change it such that <code>p=4</code> delivers the {{tl|game name | {{Message | ||
| user = Popcorn | |||
| time = 16:38, 4 Apr 2022 | |||
| text = Before <code>p=4</code> comes into use, I'd like to suggest to change it such that <code>p=4</code> delivers the {{tl|game name}} look with no icon and instead p=5 delivers the {{tl|game color}}. I'm thinking of sentences that have the game icon at the beginning, like the {{tl|base point}} templates, for example: "{{tf2}} This is a [[point entity]] available in {{Team Fortress 2|3}}". | |||
}} | }} | ||
text = Thanks, good solution! By the way, I just realized, that this template would also have the potential to replace the {{tl|in | {{Message | ||
| user = Popcorn | |||
| time = 3:12, 5 Apr 2022 | |||
| text = Thanks, good solution! By the way, I just realized, that this template would also have the potential to replace the {{tl|in}} templates, for example allow p=only and add the following switch case, however, I'm unsure if all those different but similar expressions (only, since, removed, not, also) would make this template unnecessarily complicated and whether that is useful at all. <br /> <code><small><nowiki>|only=<span style="background-color:#202020;font-weight:bold;padding:2px;{{border-radius|4px}}"><span title="{{{name}}}" style="color:{{{col|#ADD8E6}}}">(''only'' in [[File:{{{ico}}}|link={{{name}}}{{{suf|}}}|{{{name}}}]])</span></span></nowiki></small></code> | |||
}} | }} | ||
text = I thought about this idea too, but there is a problem with it: translations. The standard would be "(also in <game1> and <game2>)" for example, but it would be possible to replace "also" with other text, but writing the same values over and over again is not a good idea. If it were possible to add a set of translations to this template, and if a person wrote "suf=:es", then the text would be in Spanish according to the standard. There is also another problem: adding multiple icons. That is, you can try to add 2 variables, one will be responsible for the text at the beginning, the second for the text after, and in general, you can enter other icons in the text after, and the color will be taken from the main icon, but in other icons you will have to enter the "suf" parameter again and they will not be related to the main icon in any way. But the idea is good and I will try to improve it to avoid all problems. | {{Message | ||
| user = Max34 | |||
| time = 5:06, 5 Apr 2022 | |||
| text = I thought about this idea too, but there is a problem with it: translations. The standard would be "(also in <game1> and <game2>)" for example, but it would be possible to replace "also" with other text, but writing the same values over and over again is not a good idea. If it were possible to add a set of translations to this template, and if a person wrote "suf=:es", then the text would be in Spanish according to the standard. There is also another problem: adding multiple icons. That is, you can try to add 2 variables, one will be responsible for the text at the beginning, the second for the text after, and in general, you can enter other icons in the text after, and the color will be taken from the main icon, but in other icons you will have to enter the "suf" parameter again and they will not be related to the main icon in any way. But the idea is good and I will try to improve it to avoid all problems. | |||
}} | |||
{{Message | |||
| user = Popcorn | |||
| time = 6:44, 5 Apr 2022 | |||
| Right, I forgot about that. | |||
}} | |||
text = I just realized that we could allow {{tlc|csgo|p{{= | {{Message | ||
| user = Popcorn | |||
| time = 15:51, 18 Apr 2022 | |||
| text = I just realized that we could allow {{tlc|csgo|p{{=}}only}} by adding <code>only, since, not, removed</code> right above <code>in</code> in the #switch statement so that {{param|p}} can be passed to {{tl2|in text}} instead of {{param|type}}. Roughly speaking, I mean: | |||
<pre style="color:#ddd; background-color:#444; border-color:#666"> | <pre style="color:#ddd; background-color:#444; border-color:#666"> | ||
Line 28: | Line 45: | ||
}} | }} | ||
Yes, it's a great idea to get rid of "type". It just seemed to me before that if I didn't do it, I would have to write all the parameters in [[Template:New icon]] many times, but most likely I thought so before I did [[Template:in text]]. The parameter is called "p" because it stands for "parameter", but yes, it can be replaced with {{{1 | {{Message | ||
| user = Max34 | |||
| time = 17:49, 18 Apr 2022 | |||
| edited = 18:18, 18 Apr 2022 | |||
| Yes, it's a great idea to get rid of "type". It just seemed to me before that if I didn't do it, I would have to write all the parameters in [[Template:New icon]] many times, but most likely I thought so before I did [[Template:in text]]. The parameter is called "p" because it stands for "parameter", but yes, it can be replaced with {{{1}}} if needed. <s>Just write an answer if it really needs to be replaced and I will do it</s> (nvrm I already started doing it). I did not think that all this fuss with icons would last so long.. but on the other hand, it is interesting to do it. | |||
}} | }} | ||
== Generic Doc for game icon templates == | == Generic Doc for game icon templates == | ||
{{Message | |||
| user = Popcorn | |||
| time = 6:44, 5 Apr 2022 | |||
| I created a generic doc at {{tl2|hl2}} and would spread it in the next days like I did with {{tl2|csgo}}. I was thinking whether that documentation should be on the page [[Template:new icon/doc2]] or something, however the examples of the doc would be broken on it. | |||
}} | }} | ||
I think it's worth renaming from "Template:Hl2/doc" to "Template:Icons_doc" or something like that. I have almost completed the structure of working with "in" templates, but there are many translations missing because I do not know all languages. Unfortunately, I didn't find a way to write multiple icons so that they are all connected, so I'll just make an additional parameter that will be written after the main icon. | {{Message | ||
| user = Max34 | |||
| time = 6:54, 5 April 2022 | |||
| I think it's worth renaming from "Template:Hl2/doc" to "Template:Icons_doc" or something like that. I have almost completed the structure of working with "in" templates, but there are many translations missing because I do not know all languages. Unfortunately, I didn't find a way to write multiple icons so that they are all connected, so I'll just make an additional parameter that will be written after the main icon. | |||
}} | |||
Well, I don't think [[:Category:Game icons/doc]] is a good place for a /doc since it itself is a new category that we don't actually need and also we would have to write <code>:Category</code> as parameter in every transclusion of {{tlc|documentation | {{Message | ||
| user = Popcorn | |||
| time = 16:11, 5 Apr 2022 | |||
| Well, I don't think [[:Category:Game icons/doc]] is a good place for a /doc since it itself is a new category that we don't actually need and also we would have to write <code>:Category</code> as parameter in every transclusion of {{tlc|documentation}} to not have them added to that new /doc Category. I'd suggest going back to [[Template:Icon doc]] or [[Template:Hl2/doc]]. It's getting confusing with all the different page names. | |||
}} | }} | ||
Ok, there is still a problem: It is awful to make changes to [[icon doc]] that can't be previewed. That's why I had put it to [[Template:Hl2/doc]] in the first place. Idea: Move it back and redirect [[icon doc]] to it. This way, any game icon template can use the "clean" <code>:icon doc</code> as doc page and there is no <includeonly> madness when editing the generic doc. Problem is, we can no longer move to Template:Hl2/doc because it has a (negligible) history by now, so I'm thinking of performing an improper page movement or finding a way to ask an admin to do that. | {{Message | ||
| user = Popcorn | |||
| time = 17:59, 6 Apr 2022 | |||
| Ok, there is still a problem: It is awful to make changes to [[icon doc]] that can't be previewed. That's why I had put it to [[Template:Hl2/doc]] in the first place. Idea: Move it back and redirect [[icon doc]] to it. This way, any game icon template can use the "clean" <code>:icon doc</code> as doc page and there is no <includeonly> madness when editing the generic doc. Problem is, we can no longer move to Template:Hl2/doc because it has a (negligible) history by now, so I'm thinking of performing an improper page movement or finding a way to ask an admin to do that. | |||
}} | |||
Yes, there are similar things on the site, for example, I wanted to replace one icon with a new one and change .gif to .png, but I could not rename the file page because the new name does not match the file type. And when I tried to load a png, it couldn't load it because the file's page name had the wrong format. In other words, an endless loop. When loading a new texture, you can change the name of the page, but not when you load a new image over an existing one. I understand you, I will return everything to [[Template:Hl2/doc]]. If you have any more ideas on how to improve this idea with better icons, then it's better to write about it now, because I plan to remake all icons with a new structure. I can only add that I had one idea about auto-translation: if the page uses the [[Template:Lang]] template, then it somehow sends the article suffix to the article and already there, if icon templates are used, they put this suffix in "suf" parameter by default. This way you won't need to write the "suf" parameter all the time in other languages, but I have absolutely no idea how to do it, so it's still an idea for now. | {{Message | ||
| user = Max34 | |||
| time = 20:17, 6 Apr 2022 | |||
| Yes, there are similar things on the site, for example, I wanted to replace one icon with a new one and change .gif to .png, but I could not rename the file page because the new name does not match the file type. And when I tried to load a png, it couldn't load it because the file's page name had the wrong format. In other words, an endless loop. When loading a new texture, you can change the name of the page, but not when you load a new image over an existing one. I understand you, I will return everything to [[Template:Hl2/doc]]. If you have any more ideas on how to improve this idea with better icons, then it's better to write about it now, because I plan to remake all icons with a new structure. I can only add that I had one idea about auto-translation: if the page uses the [[Template:Lang]] template, then it somehow sends the article suffix to the article and already there, if icon templates are used, they put this suffix in "suf" parameter by default. This way you won't need to write the "suf" parameter all the time in other languages, but I have absolutely no idea how to do it, so it's still an idea for now. | |||
}} | |||
== Nearly all icons shouldn't omit text! == | == Nearly all icons shouldn't omit text! == | ||
{{Message | |||
| user = Lxm6 | |||
| time = 12:06, 28 Mar 2023 | |||
| They did with these: | |||
# {{hl2}} | |||
# {{hl2|in}} | # {{hl2|in}} | ||
# {{hl2|only}} | # {{hl2|only}} | ||
Line 57: | Line 99: | ||
== Users should have more options about where icons will be == | == Users should have more options about where icons will be == | ||
text = <s>They did with these:</s><br /> | {{Message | ||
{{hl2|2 | | user = Lxm6 | ||
| time = 19:15, 9 Apr 2023 | |||
| edited = 19:50, 9 Apr 2023 | |||
| text = <s>They did with these:</s><br /> | |||
{{hl2|2}}<br /> | |||
{{hl2|4}}<br /> | {{hl2|4}}<br /> | ||
{{hl2|4.1}}<br /> | {{hl2|4.1}}<br /> | ||
Line 136: | Line 182: | ||
== Why use a number for the display method? == | == Why use a number for the display method? == | ||
Using only a number is quite confusing to newcomers. | {{Message | ||
| user = Amicdict | |||
| time = 19:40, 2 May 2023 | |||
| Using only a number is quite confusing to newcomers. | |||
Kial uzi nombron por montronto de metodo? Uzas nur nombron konfuzantus komencantojn | Kial uzi nombron por montronto de metodo? Uzas nur nombron konfuzantus komencantojn. | ||
}} | }} | ||
{{Message | |||
| user = Popcorn | |||
| time = 8:44, 26 May 2023 | |||
| {{autolang|Numbers are short and convenient. Assigning names to styles would be unnecessary, unnecessarily difficult, and hardly intuitive. If you don't know what to choose as a parameter, guessing a number is much faster than guessing some name. | |||
|de=Zahlen sind kurz und praktisch. Den Stilen Namen zuzuweisen wäre unnötig, unnötig schwer und wohl kaum intuitiv. Wenn Du nicht weißt, was Du als Parameter wählen kannst, geht das Raten einer Zahl viel schneller als das Erraten von irgendeinem Namen.}} | |||
{{Message | |||
| user = SirYodaJedi | |||
| time = 13:49, 26 May 2023 | |||
| The alt names are rarely used anyway; I just go to the applicable [[Template:Hl2]], [[Template:Dod]], [[Template:P2ce]], etc and click edit to check the {{code|{{!}} name# {{=}} }} parameter when I need to use one. | |||
}} | }} | ||
> Numbers are short and convenient. | }} | ||
{{Message | |||
| user = Amicdict | |||
| time = 9:51, 26 May 2023 | |||
| > Numbers are short and convenient. | |||
{{autolang|Numbers are indeed short yes. but how are they convenient in this case? What about editors who aren't programmers?|eo=Nombroj tre ja mallonga jes; sed kiel tioj lertaj en tia ĉi kazo? ĉu vi pensis pri redaktistoj ne programistaj? | {{autolang|Numbers are indeed short yes. but how are they convenient in this case? What about editors who aren't programmers?|eo=Nombroj tre ja mallonga jes; sed kiel tioj lertaj en tia ĉi kazo? ĉu vi pensis pri redaktistoj ne programistaj?}} | ||
>Assigning names to styles would be unnecessary, unnecessarily difficult, and hardly intuitive. | >Assigning names to styles would be unnecessary, unnecessarily difficult, and hardly intuitive. | ||
Line 152: | Line 211: | ||
{{autolang|Uh, how and why?|eo=Kiel kaj kial?}} | {{autolang|Uh, how and why?|eo=Kiel kaj kial?}} | ||
}} | }} | ||
{{autolang|You would need the style names in a list if you want to use one at all. Numbers on the other hand are known by everybody, even by non-prorgammers. This makes numbers convenient: You just need to know that the styles have numbers and not names, from then on you don't really need to look up again, especially with our small number of styles.<br>Well: What should the names for the three styles that we have be? No matter what we two say: Not everyone will give the same answer to this question, making names not intuitive in this case. All the names that we two might come up with are things that we and everyone else would have to remember. Numbers (speaking of 1,2,...) are already there.<br>I'm referring to this template and not to generality; In different cases names would make more sense but not here in my opinion. | {{Message | ||
|de=Stilnamen müssten in einer Liste verfügbar sein, um überhaupt einen davon nutzen zu können. Zahlen kenne ich auch ohne eine Liste, selbst als Nicht-Programmierer. In dieser Hinsicht sind Zahlen praktisch: Man muss bloß verstanden haben, dass die Stile Nummern haben und keine Namen, von dann an muss man nicht unbedingt erneut nachschlagen, insbesondere nicht bei unserer kleinen Stilanzahl.<br>Naja: Wie sollten Namen für die drei Stile, die wir haben, lauten? Egal, wie wir beide es sehen: Auf diese Frage wird bestimmt nicht jeder dieselbe Antwort geben, also: Nicht intuitiv. Alles, was wir uns an Namen ausdenken würden, müssten wir und alle anderen sich merken. Zahlen (wenn wir von 1,2,... reden) muss man sich nicht ausdenken.<br>Ich beziehe mich auf diese Vorlage, nicht auf die Allgemeinheit; In anderen Fällen wären Namen durchaus sinnvoller, aber ich finde, hier nicht. | | user = Popcorn | ||
| time = 12:35, 26 May 2023 | |||
| {{autolang|You would need the style names in a list if you want to use one at all. Numbers on the other hand are known by everybody, even by non-prorgammers. This makes numbers convenient: You just need to know that the styles have numbers and not names, from then on you don't really need to look up again, especially with our small number of styles.<br>Well: What should the names for the three styles that we have be? No matter what we two say: Not everyone will give the same answer to this question, making names not intuitive in this case. All the names that we two might come up with are things that we and everyone else would have to remember. Numbers (speaking of 1,2,...) are already there.<br>I'm referring to this template and not to generality; In different cases names would make more sense but not here in my opinion. | |||
|de=Stilnamen müssten in einer Liste verfügbar sein, um überhaupt einen davon nutzen zu können. Zahlen kenne ich auch ohne eine Liste, selbst als Nicht-Programmierer. In dieser Hinsicht sind Zahlen praktisch: Man muss bloß verstanden haben, dass die Stile Nummern haben und keine Namen, von dann an muss man nicht unbedingt erneut nachschlagen, insbesondere nicht bei unserer kleinen Stilanzahl.<br>Naja: Wie sollten Namen für die drei Stile, die wir haben, lauten? Egal, wie wir beide es sehen: Auf diese Frage wird bestimmt nicht jeder dieselbe Antwort geben, also: Nicht intuitiv. Alles, was wir uns an Namen ausdenken würden, müssten wir und alle anderen sich merken. Zahlen (wenn wir von 1,2,... reden) muss man sich nicht ausdenken.<br>Ich beziehe mich auf diese Vorlage, nicht auf die Allgemeinheit; In anderen Fällen wären Namen durchaus sinnvoller, aber ich finde, hier nicht.}} | |||
}} | }} | ||
Line 177: | Line 239: | ||
{{autolang|For each of your argument why are names still used in this template?|eo=Por ĉiu via argumento, kial nomoj ankoraŭ uziĝas en ĉi tiu ŝablono?}} - [[User:Amicdict|Amicdict]] ([[User talk:Amicdict|talk]]) 12:37, 31 May 2023 (PDT) | {{autolang|For each of your argument why are names still used in this template?|eo=Por ĉiu via argumento, kial nomoj ankoraŭ uziĝas en ĉi tiu ŝablono?}} - [[User:Amicdict|Amicdict]] ([[User talk:Amicdict|talk]]) 12:37, 31 May 2023 (PDT) | ||
> {{autolang|Can also substitute those numbers to words like <code>name</code> and <code>ico</code> and <code>col</code>. | {{Message | ||
|eo=Povas anstataŭigi tiujn nombrojn al vortoj kvazaŭ <code>name</code> kaj <code>ico</code> kaj <code>col</code>. | | user = Popcorn | ||
| time = 15:31, 1 Jun 2023 | |||
|> {{autolang|Can also substitute those numbers to words like <code>name</code> and <code>ico</code> and <code>col</code>. | |||
|eo=Povas anstataŭigi tiujn nombrojn al vortoj kvazaŭ <code>name</code> kaj <code>ico</code> kaj <code>col</code>.}} | |||
For each style you have a variant with an icon and one without, one with black background and one without. Do you think three names suffice? | For each style you have a variant with an icon and one without, one with black background and one without. Do you think three names suffice? | ||
Line 222: | Line 287: | ||
Are you planning a change or are you just discussing? If you suggest a more precise change in functionality and usage then I can refer to that and don't need to give any proofs that no one needs. | Are you planning a change or are you just discussing? If you suggest a more precise change in functionality and usage then I can refer to that and don't need to give any proofs that no one needs. | ||
I also like proofs. But I'm not capable of prooving what the majority of the wiki editors prefers or what they will prefer in the long run.<br> | {{Message | ||
| user = Popcorn | |||
| time = 0:27, 6 Jun 2023 | |||
| I also like proofs. But I'm not capable of prooving what the majority of the wiki editors prefers or what they will prefer in the long run.<br> | |||
If you feel like adding these names to the cases of the #switch statement of this template, go ahead. I personally would advise against it. Allowing multiple words for the same effect might only be more complicated and getting rid of one is unnecessary work. I won't explain it any further.<br> | If you feel like adding these names to the cases of the #switch statement of this template, go ahead. I personally would advise against it. Allowing multiple words for the same effect might only be more complicated and getting rid of one is unnecessary work. I won't explain it any further.<br> | ||
Apart from that, I don't know what you want me to answer. | Apart from that, I don't know what you want me to answer. | ||
}} | |||
== Flag to change "in" to "for" or "on" == | == Flag to change "in" to "for" or "on" == | ||
I'd like to add a {{param|except | {{Message | ||
| user = SirYodaJedi | |||
| time = 9:53, 2 Jun 2023 | |||
| I'd like to add a {{param|except}} parameter, which would result in {{code|<nowiki>{{hl2|except}}</nowiki>}} becoming '''(''except'' for {{hl2}})'''. It has a slightly different (generally more positive) usecase than the {{param|not}}; I've used it a [[Steam/SteamPipe|couple]] [[Skybox (GoldSrc)|times]] already by manually typing it out. | |||
}} | |||
{{Message | |||
| user = Popcorn | |||
| time = 12:05, 2 Jun 2023 | |||
| Sounds ok. Even though its meaning is pretty identical to {{tlc|hl2|not}}, {{tlc|hl2|except}} may be more fitting in sentences. Maybe we should use the same color for both due to the similar meaning? | |||
{{Message | |||
| user = SirYodaJedi | |||
| time = 13:25, 2 Jun 2023 | |||
| Sure, it probably can share a color; it means basically the same thing, with only the connotation and word flow being different. | |||
}} | }} | ||
}} | }} | ||
{{Message | |||
| user = SirYodaJedi | |||
| time = 18:25, 22 Jun 2023 | |||
| I ended up using {{param|addtext-front}} instead (like so: {{sven|in|addtext-front=''except''}}), since I'm using it as a positive thing, not a negative thing. I do think there should be a flag can change "in" in the various thingies to "for" or "on", though. | |||
}} | }} | ||
Line 244: | Line 326: | ||
{{Unresolved}} | {{Unresolved}} | ||
{{pre|<nowiki>{{ps1|4|link=http://example.com | {{Message | ||
| user = Lxm6 | |||
| time = 4:39, 20 Jul 2023 | |||
| {{pre|<nowiki>{{ps1|4|link=http://example.com}} | |||
{{ps2|4|link=http://example.com}} | {{ps2|4|link=http://example.com}} | ||
{{ps3|4|link=http://example.com}} | {{ps3|4|link=http://example.com}} | ||
Line 253: | Line 338: | ||
== Change color and icon == | == Change color and icon == | ||
It would be very cool if we could change the icon and the color. For example {{tlc|<nowiki>csgo|4|col=white</nowiki> | {{Message | ||
| user = Mr. SystemError | |||
| time = 11:50, 17 Apr 2024 | |||
| edited = 19:11, 17 Apr 2024 | |||
| 1 = It would be very cool if we could change the icon and the color. For example {{tlc|<nowiki>csgo|4|col=white</nowiki>}} would be {{csgo}}{{tint|color=white|'''Counter-Strike: Global Offensive'''}} | |||
}} and {{tlc|<nowiki>csgo|icon=Icon-Portal2.png</nowiki>}} would be {{portal2}}{{csgo|3.1}} | }} and {{tlc|<nowiki>csgo|icon=Icon-Portal2.png</nowiki>}} would be {{portal2}}{{csgo|3.1}} |
Revision as of 15:56, 17 June 2024

Comments on talk pages should be signed with "~~~~", which will be converted into your signature and a timestamp.
Parameter p
(using Template:Message) Template:Text --Popcorn (talk) 16:38, 4 Apr 2022 (UTC)
(using Template:Message) Template:Text --Popcorn (talk) 3:12, 5 Apr 2022 (UTC)
(using Template:Message) Template:Text --Max34 (talk) 5:06, 5 Apr 2022 (UTC)
(using Template:Message) Right, I forgot about that.
--Popcorn (talk) 6:44, 5 Apr 2022 (UTC)
(using Template:Message) Template:Text --Popcorn (talk) 15:51, 18 Apr 2022 (UTC)
(using Template:Message) Yes, it's a great idea to get rid of "type". It just seemed to me before that if I didn't do it, I would have to write all the parameters in Template:New icon many times, but most likely I thought so before I did Template:in text. The parameter is called "p" because it stands for "parameter", but yes, it can be replaced with {{{1}}} if needed. Just write an answer if it really needs to be replaced and I will do it (nvrm I already started doing it). I did not think that all this fuss with icons would last so long.. but on the other hand, it is interesting to do it.
--Max34 (talk) 17:49, 18 Apr 2022 (UTC)
Generic Doc for game icon templates
(using Template:Message) I created a generic doc at {{hl2}} and would spread it in the next days like I did with {{csgo}}. I was thinking whether that documentation should be on the page Template:new icon/doc2 or something, however the examples of the doc would be broken on it. --Popcorn (talk) 6:44, 5 Apr 2022 (UTC)
(using Template:Message) I think it's worth renaming from "Template:Hl2/doc" to "Template:Icons_doc" or something like that. I have almost completed the structure of working with "in" templates, but there are many translations missing because I do not know all languages. Unfortunately, I didn't find a way to write multiple icons so that they are all connected, so I'll just make an additional parameter that will be written after the main icon.
--Max34 (talk) 6:54, 5 April 2022 (UTC)
(using Template:Message) Well, I don't think Category:Game icons/doc is a good place for a /doc since it itself is a new category that we don't actually need and also we would have to write :Category
as parameter in every transclusion of {{documentation}}
to not have them added to that new /doc Category. I'd suggest going back to Template:Icon doc or Template:Hl2/doc. It's getting confusing with all the different page names.
--Popcorn (talk) 16:11, 5 Apr 2022 (UTC)
(using Template:Message) Ok, there is still a problem: It is awful to make changes to icon doc that can't be previewed. That's why I had put it to Template:Hl2/doc in the first place. Idea: Move it back and redirect icon doc to it. This way, any game icon template can use the "clean" :icon doc
as doc page and there is no <includeonly> madness when editing the generic doc. Problem is, we can no longer move to Template:Hl2/doc because it has a (negligible) history by now, so I'm thinking of performing an improper page movement or finding a way to ask an admin to do that.
--Popcorn (talk) 17:59, 6 Apr 2022 (UTC)
(using Template:Message) Yes, there are similar things on the site, for example, I wanted to replace one icon with a new one and change .gif to .png, but I could not rename the file page because the new name does not match the file type. And when I tried to load a png, it couldn't load it because the file's page name had the wrong format. In other words, an endless loop. When loading a new texture, you can change the name of the page, but not when you load a new image over an existing one. I understand you, I will return everything to Template:Hl2/doc. If you have any more ideas on how to improve this idea with better icons, then it's better to write about it now, because I plan to remake all icons with a new structure. I can only add that I had one idea about auto-translation: if the page uses the Template:Lang template, then it somehow sends the article suffix to the article and already there, if icon templates are used, they put this suffix in "suf" parameter by default. This way you won't need to write the "suf" parameter all the time in other languages, but I have absolutely no idea how to do it, so it's still an idea for now.
--Max34 (talk) 20:17, 6 Apr 2022 (UTC)
Nearly all icons shouldn't omit text!
(using Template:Message) They did with these:
- (in
)
- (only in
)
- (in all games since
)
- (not in
)
- (also in
)
Icons should not replace text in most situations. --Lxm6 (talk) 12:06, 28 Mar 2023 (UTC)
Users should have more options about where icons will be
(using Template:Message) Template:Text --Lxm6 (talk) 19:15, 9 Apr 2023 (UTC)
Why use a number for the display method?
(using Template:Message) Using only a number is quite confusing to newcomers.
Kial uzi nombron por montronto de metodo? Uzas nur nombron konfuzantus komencantojn. --Amicdict (talk) 19:40, 2 May 2023 (UTC)
(using Template:Message)


You can help our editors by replacing or deleting this template on the Pages that use this template. Once no more pages use this template, it should be Marked for deletion.
Additional notes:
Use #switch parser function instead. Example
{{#switch: {{language}}
| #default = English
| ja = 日本語
| zh-tw = 中文(台灣)
}}
(using Template:Message) The alt names are rarely used anyway; I just go to the applicable Template:Hl2, Template:Dod, Template:P2ce, etc and click edit to check the | name# = parameter when I need to use one.
--SirYodaJedi (talk) 13:49, 26 May 2023 (UTC)
--Popcorn (talk) 8:44, 26 May 2023 (UTC)
(using Template:Message) > Numbers are short and convenient.


You can help our editors by replacing or deleting this template on the Pages that use this template. Once no more pages use this template, it should be Marked for deletion.
Additional notes:
Use #switch parser function instead. Example
{{#switch: {{language}}
| #default = English
| ja = 日本語
| zh-tw = 中文(台灣)
}}
>Assigning names to styles would be unnecessary, unnecessarily difficult, and hardly intuitive.


You can help our editors by replacing or deleting this template on the Pages that use this template. Once no more pages use this template, it should be Marked for deletion.
Additional notes:
Use #switch parser function instead. Example
{{#switch: {{language}}
| #default = English
| ja = 日本語
| zh-tw = 中文(台灣)
}}
--Amicdict (talk) 9:51, 26 May 2023 (UTC)
(using Template:Message)


You can help our editors by replacing or deleting this template on the Pages that use this template. Once no more pages use this template, it should be Marked for deletion.
Additional notes:
Use #switch parser function instead. Example
{{#switch: {{language}}
| #default = English
| ja = 日本語
| zh-tw = 中文(台灣)
}}
--Popcorn (talk) 12:35, 26 May 2023 (UTC)
> You would need the style names in a list if you want to use one at all.


You can help our editors by replacing or deleting this template on the Pages that use this template. Once no more pages use this template, it should be Marked for deletion.
Additional notes:
Use #switch parser function instead. Example
{{#switch: {{language}}
| #default = English
| ja = 日本語
| zh-tw = 中文(台灣)
}}
> Numbers on the other hand are known by everybody, even by non-prorgammers.


You can help our editors by replacing or deleting this template on the Pages that use this template. Once no more pages use this template, it should be Marked for deletion.
Additional notes:
Use #switch parser function instead. Example
{{#switch: {{language}}
| #default = English
| ja = 日本語
| zh-tw = 中文(台灣)
}}
> This makes numbers convenient: You just need to know that the styles have numbers and not names, from then on you don't really need to look up again, especially with our small number of styles.


You can help our editors by replacing or deleting this template on the Pages that use this template. Once no more pages use this template, it should be Marked for deletion.
Additional notes:
Use #switch parser function instead. Example
{{#switch: {{language}}
| #default = English
| ja = 日本語
| zh-tw = 中文(台灣)
}}
…
> Well: What should the names for the three styles that we have be? No matter what we two say: Not everyone will give the same answer to this question, making names not intuitive in this case.


You can help our editors by replacing or deleting this template on the Pages that use this template. Once no more pages use this template, it should be Marked for deletion.
Additional notes:
Use #switch parser function instead. Example
{{#switch: {{language}}
| #default = English
| ja = 日本語
| zh-tw = 中文(台灣)
}}
---


You can help our editors by replacing or deleting this template on the Pages that use this template. Once no more pages use this template, it should be Marked for deletion.
Additional notes:
Use #switch parser function instead. Example
{{#switch: {{language}}
| #default = English
| ja = 日本語
| zh-tw = 中文(台灣)
}}
- Amicdict (talk) 12:37, 31 May 2023 (PDT)
(using Template:Message) >


You can help our editors by replacing or deleting this template on the Pages that use this template. Once no more pages use this template, it should be Marked for deletion.
Additional notes:
Use #switch parser function instead. Example
{{#switch: {{language}}
| #default = English
| ja = 日本語
| zh-tw = 中文(台灣)
}}
For each style you have a variant with an icon and one without, one with black background and one without. Do you think three names suffice?
> Using only a number is quite confusing to newcomers.
>


You can help our editors by replacing or deleting this template on the Pages that use this template. Once no more pages use this template, it should be Marked for deletion.
Additional notes:
Use #switch parser function instead. Example
{{#switch: {{language}}
| #default = English
| ja = 日本語
| zh-tw = 中文(台灣)
}}
Why do I need proof and you don't?
> For each of your argument why are names still used in this template?
Because they are already established across many wiki pages for quite some time.
---
Are you planning a change or are you just discussing? If you suggest a more precise change in functionality and usage then I can refer to that and don't need to give any proofs that no one needs.
--Popcorn (talk) 15:31, 1 Jun 2023 (UTC)
>>


You can help our editors by replacing or deleting this template on the Pages that use this template. Once no more pages use this template, it should be Marked for deletion.
Additional notes:
Use #switch parser function instead. Example
{{#switch: {{language}}
| #default = English
| ja = 日本語
| zh-tw = 中文(台灣)
}}
> For each style you have a variant with an icon and one without, one with black background and one without. Do you think three names suffice?


You can help our editors by replacing or deleting this template on the Pages that use this template. Once no more pages use this template, it should be Marked for deletion.
Additional notes:
Use #switch parser function instead. Example
{{#switch: {{language}}
| #default = English
| ja = 日本語
| zh-tw = 中文(台灣)
}}
> Why do I need proof and you don't?


You can help our editors by replacing or deleting this template on the Pages that use this template. Once no more pages use this template, it should be Marked for deletion.
Additional notes:
Use #switch parser function instead. Example
{{#switch: {{language}}
| #default = English
| ja = 日本語
| zh-tw = 中文(台灣)
}}
> Because they are already established across many wiki pages for quite some time.


You can help our editors by replacing or deleting this template on the Pages that use this template. Once no more pages use this template, it should be Marked for deletion.
Additional notes:
Use #switch parser function instead. Example
{{#switch: {{language}}
| #default = English
| ja = 日本語
| zh-tw = 中文(台灣)
}}
---
Are you planning a change or are you just discussing? If you suggest a more precise change in functionality and usage then I can refer to that and don't need to give any proofs that no one needs.
(using Template:Message) I also like proofs. But I'm not capable of prooving what the majority of the wiki editors prefers or what they will prefer in the long run.
If you feel like adding these names to the cases of the #switch statement of this template, go ahead. I personally would advise against it. Allowing multiple words for the same effect might only be more complicated and getting rid of one is unnecessary work. I won't explain it any further.
Apart from that, I don't know what you want me to answer.
--Popcorn (talk) 0:27, 6 Jun 2023 (UTC)
Flag to change "in" to "for" or "on"
(using Template:Message) I'd like to add a {{{except}}} parameter, which would result in {{hl2|except}} becoming (except for ). It has a slightly different (generally more positive) usecase than the {{{not}}}; I've used it a couple times already by manually typing it out.
--SirYodaJedi (talk) 9:53, 2 Jun 2023 (UTC)
(using Template:Message) Sounds ok. Even though its meaning is pretty identical to {{hl2|not}}
, {{hl2|except}}
may be more fitting in sentences. Maybe we should use the same color for both due to the similar meaning?
(using Template:Message) Sure, it probably can share a color; it means basically the same thing, with only the connotation and word flow being different. --SirYodaJedi (talk) 13:25, 2 Jun 2023 (UTC) --Popcorn (talk) 12:05, 2 Jun 2023 (UTC)
(using Template:Message) I ended up using {{{addtext-front}}} instead (like so: (except'in )), since I'm using it as a positive thing, not a negative thing. I do think there should be a flag can change "in" in the various thingies to "for" or "on", though.
--SirYodaJedi (talk) 18:25, 22 Jun 2023 (UTC)
It is possible by using the {{in}} template. You can write this: {{in|{{src13mp}}|text=except in}}
and it will look like this: (except in )
Mr. System Error(T - C) 15:01, 4 May 2024 (PDT)
Add external links
☒ Unresolved.
(using Template:Message)
{{ps1|4|link=http://example.com}} {{ps2|4|link=http://example.com}} {{ps3|4|link=http://example.com}} {{ps4|4|link=http://example.com}} {{ps5|4|link=http://example.com}}
--Lxm6 (talk) 4:39, 20 Jul 2023 (UTC)
Change color and icon
(using Template:Message) It would be very cool if we could change the icon and the color. For example {{csgo|4|col=white}}
would be Counter-Strike: Global Offensive --Mr. SystemError (talk) 11:50, 17 Apr 2024 (UTC) and
{{csgo|icon=Icon-Portal2.png}}
would be Counter-Strike: Global Offensive