Point script template: Difference between revisions

From Valve Developer Community
Jump to navigation Jump to search
No edit summary
(Also exists in TF2)
Line 1: Line 1:
{{Ent not in fgd|nolink=1|because=[[point_template]] already is an accessible option}}
{{Ent not in fgd|nolink=1|because=[[point_template]] already is an accessible option}}


{{l4d2 point|point_script_template}}
{{l4d2 point|point_script_template}} It is also available in {{tf2|4}}.
It is a version of [[point_template]] readjusted to work for spawning-on-runtime, such as VScripts.
It is a version of [[point_template]] readjusted to work for spawning-on-runtime, such as VScripts.



Revision as of 18:33, 21 December 2022

Icon-NotInFGD.png
This entity is not in the FGD by default.
It should not be put directly in a map because point_template already is an accessible option.

Template:L4d2 point It is also available in Team Fortress 2 Team Fortress 2. It is a version of point_template readjusted to work for spawning-on-runtime, such as VScripts.

Thepoint_templateentity relies on compiled data from the map file to function properly, so trying to spawn entities with apoint_templatemade by scripts will return it having no templates and fail, even though it still can delete its own template entities.

This entity is identical topoint_template, so things like name fixup behavior quirks should still be taken into account.

When compiling Entity Groups,point_template entities are converted topoint_script_template.

Keyvalues

Template 1 (Template01) to Template 16 <targetname>
Targetname(s) to search for entities to template. These can be exact matches, or wildcards (*). If multiple entities are matched, all entities will be included in the template.


Flags

Template:Fl PointTemplate

Inputs

ForceSpawn
Spawn an instance of the template at the original position.


Outputs

Template:O PointTemplate

See also