User talk:Amicdict

Comments on talk pages should be signed with "~~~~", which will be converted into your signature and a timestamp.
I'm the 8.558kBind guy.
PSA: conflicts in the archer_proxy and base_boss pages
They both use template pairs that intend to show the same thing: Template:KV Targetname + Template:KV BaseEntity pair, and Template:I Targetname + Template:I BaseEntity pair. So this is what the page ends up looking like this:
How the page is displayed
KeyValues section
- Name (targetname) <string>[ Edit ]
- The name that other entities refer to this entity by, via Inputs/Outputs or other keyvalues (e.g.
parentname
ortarget
).
Also displayed in Hammer's 2D views and Entity Report.See also: Generic Keyvalues, Inputs and Outputs available to all entities
Inputs section
My Proposal
TheTargetname
templates, Template:KV Targetname and Template:I Targetname are actually deprecated, and theBaseEntity
templates are the currently maintained and more updated ones, so I advise against using any of them.
BUT if you still are thinking about theTargetname
templates, I request that when using{{KV Targetname}}
template, do it like this:
{{KV Targetname|basehl2=1}}
- Name (targetname) <string>[ Edit ]
- The name that other entities refer to this entity by, via Inputs/Outputs or other keyvalues (e.g.
parentname
ortarget
).
Also displayed in Hammer's 2D views and Entity Report.See also: Generic Keyvalues, Inputs and Outputs available to all entities
As for the{{I Targetname}}
template, there isn't a way to control what infomation is displayed, so I won't give any suggestions on how to use it.
One more thing, give the Show Preview and Show Changes buttons some tries, they're very helpful before you publish edits! I use Show Preview after pasting my VDC edit .HTML file drafts to a page, then Show Changes to write out a summary, or an alternate method to double-check on edits.
I'll fix these issues as soon as I can since I have exams this week. Amicdict (talk) 12:47, 24 May 2021
FYI to KV_WeaponSpawn
FYI, "WeaponSpawn" and "WeaponSpawnSingle" is only for
Stop for a while, please
<code style="padding:0" title="Template: MultiPage THE OWL (talk) 5:10, 2 Apr 2023 is not for the Talk namespace. This is an international namespace, so it doesn't need {{MultiPage}}
.
Also, I would like you to stop moving pages for a while, otherwise we will have to fix everything again for a very long time. The use of {{MultiPage}}
presupposes the correction of everything on the pages (text formatting, template parameters, etc.), including the removal of suffixes and language categories.
">{{MultiPage THE OWL (talk) 5:10, 2 Apr 2023 is not for the Talk namespace. This is an international namespace, so it doesn't need {{MultiPage}}
.
Also, I would like you to stop moving pages for a while, otherwise we will have to fix everything again for a very long time. The use of {{MultiPage}}
presupposes the correction of everything on the pages (text formatting, template parameters, etc.), including the removal of suffixes and language categories.}}
{{MultiPage}}
.">{{MultiPage Amicdict (talk) 21:37, 2 Apr 2023 is not for the Talk namespace. This is an international namespace, so it doesn't need {{MultiPage}}
.}}
Ah, sorry. I will keep that in mind.
{{MultiPage}}
presupposes the correction of everything on the pages (text formatting, template parameters, etc.), including the removal of suffixes and language categories. Oh, well I didn't realize. I didn't see that. Removal of language categories is easy; I moved pages using the :-suffix to /-suffix explicitly so that the links to the pages using the old :-suffix don't get messed up.
Well, if I can't immediately use{{MultiPage}}
, where are we supposed to start then? Damn, I noticed this message just now :/
Well, now the template has instructions for moving pages. See "Using MultiPage on existing pages". THE OWL (talk) 15:37, 22 Apr 2023