Template talk:Console command: Difference between revisions

From Valve Developer Community
Jump to navigation Jump to search
No edit summary
No edit summary
Line 34: Line 34:
}}</nowiki>}} I suppose it would also make sense to instead simply make this template more like {{tl|entity}}, adding things like a sentence and game categorization.
}}</nowiki>}} I suppose it would also make sense to instead simply make this template more like {{tl|entity}}, adding things like a sentence and game categorization.


Alternatively, an internal, more basic template handling things like categories, titles, and the text based off it (the internal templates) parameters could be managed by an external template doing the heavy lifting (such as autolang and types to input the right strings and categories to the internal templates) might work.
Alternatively, an internal, more basic template handling things like categories, titles, and the text based off it (the internal templates) parameters could be managed by an external template doing the heavy lifting (such as autolang and types to input the right strings and categories to the internal templates) might work. I can elaborate on how it might work if necessary.
}}
}}

Revision as of 12:23, 15 August 2023

Icon-message-48px.png
This is the discussion page of Template:Console command. To add a comment, use the Edit button near the headline of the appropriate section. To create a new section, you can use the Add topic button at the top of this page.
Comments on talk pages should be signed with "~~~~", which will be converted into your signature and a timestamp.

Moving to {{entity}}

(using Template:Message)  Should we continue to use this template, or modify {{entity}} to categorize and change the titles, with some modifications, such as the equivelant of Category:Source Base Entities being Category:Console commands, and changing the title to be lowercase and with underscores, but not embed it within {{code}}? (the same would apply to {{console variable}}.) I'm leaning towards the latter.  --Pee (talk) 18:39, 15 Aug 2023 (UTC)


(using Template:Message)  I changed the title to use {{code}} to be more uniform with Entity. I would be open to merging the two templates, however that might just cause a spaghetti code situation. If we combine this and entity, then we will likely have to combine {{Shader}} and the likes as well  --Equalizer5118 (talk) 18:44, 15 Aug 2023 (UTC)


(using Template:Message)  I also think that plain text with underscores look ugly. I prefer sv_cheats over sv_cheats as monospace text looks more uniform  --Equalizer5118 (talk) 18:45, 15 Aug 2023 (UTC)


(using Template:Message)  My main point was mentioning a few possible changes that could be made, not necessarily whether or not it's in code (though i do think it shouldn't be in code). As for a spaghetti template, something like this might work fairly well (maybe even with changing the name of the name of the base page):

Template:entity
{{#switch: {{{type|}}} |#default={{error|Missing required argument "type"}} |e0|e1|e2|e3|e4|e5={{entity/entity|whatever|arguments|are|necessary|to|pass}} |convar|command={{entity/console|whatever|arguments|are|necessary|to|pass}} |c0={{entity/qc|whatever|arguments|are|necessary|to|pass}} }}

I suppose it would also make sense to instead simply make this template more like {{entity}}, adding things like a sentence and game categorization.

Alternatively, an internal, more basic template handling things like categories, titles, and the text based off it (the internal templates) parameters could be managed by an external template doing the heavy lifting (such as autolang and types to input the right strings and categories to the internal templates) might work. I can elaborate on how it might work if necessary.  --Pee (talk) 18:57, 15 Aug 2023 (UTC)