Template talk:Ent

This is the discussion page of Template:Ent. 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.

I think that if Jeff would know XML, he could simply create a new tag in the CSS itself, called <ent>. That would leave the question, what is easier to write - "{{ent|path_track}}" or "<ent path_track/>"? --Andreasen (talk) 10:21, 23 Sep 2007 (UTC)

Not much of a difference really...--Ts2do (talk) 12:06, 23 Sep 2007 (UTC)

The big difference would be if Valve allowed us to set the CSS on our user settings page. In that way Jeff would get his highlighting, while I could just read the ents as plain text, at the same time.  --Andreasen (talk) 12:11, 23 Sep 2007 (UTC)

Actually, as this template means that entities will always be linked to, Jeff is against it, as this is considered excess use of linking. Unless you can write [[{{ent|func_wholly}}]], XML tags seems like the only possibility (and don't consider writing a "{{nolinkent| }}", please). --Andreasen (talk) 20:27, 23 Sep 2007 (UTC)

One Template, two Purposes

If I may ask, why use this template for two completely different purposes? (1. a code-style link, 2. the first sentence for an entity page)
If we want to revolutionize {{Point ent}}, then I'd suggest doing the first step with a new template, and not with this simple template that is being used on nearly every page. Extending {{Ent}} for two distinct purposes makes it unnecessarily hard to find the pages that use {{Ent}} for just one of the two purposes. And honestly, isn't it annoying to write {{Ent|mode=entity|...}} every time? Why not make a new template? Template:Entity is still open. --Popcorn (talk) 20:52, 23 January 2023

We originally wanted to move {{Point ent}} to {{Ent}} when it was finished improvement. I think it's a good idea that making a new template on a new page. I will move the template later.
Before the mode has deprecated by all pages, we can't delete the code for compatibility. --1416006136 (talk) 01:03, 24 January 2023 (UTC)

Merge with Template:Command

Both this template and {{Command}} use almost the same exact code, it doesnt make sense for the same template to be duplicated. We should merge these into smth like {{Codelink}}, with a shortcut of {{Cl}}. --Equalizer5118 (talk) 16:07, 22 Mar 2024

You're right, i can help with moving. --NOUG4AT (talk) 16:55, 22 Mar 2024

Template:Ent/param2usecheck

Ok, that's clever to find where {{{2}}} is used. But why? --popcorn (talk) 02:30, 25 December 2024 (PST)

The plan is to use Ent template only for entities and nothing else so param 2 is unneeded. I just haven't got to actually editing all of it --Nescius (talk) 02:54, 25 December 2024 (PST)

Ah, {{cmd}} has been invented for that. Good to know. That change then must be reflected at Help:Templates. --popcorn (talk) 03:13, 25 December 2024 (PST)