Template:Ent: Difference between revisions
Jump to navigation
Jump to search
m (Use <onlyinclude>.) |
(Removed padding from <code> i.e. the gap at its ends. Should look much nicer e.g. if {{ent}} is followed by a punctuation mark. Please give an example where this change is a problem when reverting this.) |
||
| Line 1: | Line 1: | ||
{{lang|Template:Ent}} | {{lang|Template:Ent}} | ||
<onlyinclude><includeonly><code>[[{{{1}}}]]{{#if:{{{2|}}}| {{{2|}}}|}}</code></includeonly></onlyinclude> | <onlyinclude><includeonly><code style=padding:0>[[{{{1}}}]]{{#if:{{{2|}}}| {{{2|}}}|}}</code></includeonly></onlyinclude> | ||
This template is a faster and cleaner way of marking text as both a link and code. Its primary use is on entity names, but it is used on other things too, such as VMT parameters and console commands. | This template is a faster and cleaner way of marking text as both a link and code. Its primary use is on entity names, but it is used on other things too, such as VMT parameters and console commands. | ||
Revision as of 19:20, 17 May 2022
This template is a faster and cleaner way of marking text as both a link and code. Its primary use is on entity names, but it is used on other things too, such as VMT parameters and console commands.
The syntax is simple. {{ent|logic_relay}} would return as logic_relay.
Optionally, you can specify a second field of text to not be counted as a link.
{{ent|sv_cheats|1}} would give you sv_cheats 1.