Point template: Difference between revisions
m (→Notes on name fixup: simplified) |
(turned things into templates, and resimplified + reformatted a lot of things) |
||
| Line 2: | Line 2: | ||
|zh-cn =Point_template:zh-cn | |zh-cn =Point_template:zh-cn | ||
}} | }} | ||
{{base point|point_template}} It turns an entity, or set of entities, into a single template that can be instanced anywhere, and multiple times. | {{base point|point_template}} It turns an entity, or set of entities, into a single template that can be instanced anywhere, and multiple times. When activated, this entity will spawn the entities in the template at the same positions, relative to this entity, that they had when this entity was created. This will be their original positions if the point_template has not been moved.bTo spawn the template in other places, an [[env_entity_maker]] can be used | ||
Any [[logic_relay]] within the template, if it has one, will fire its OnSpawn output when spawned. | |||
{{bug|In {{insurgency}}{{doi}}, this entity is broken and will usually crash the game. Although if the gamemode is set to training in {{insurgency}}, it will work normally.}} | |||
{{bug|In {{csgo}}, spawning a [[func_breakable_surf]] with this entity will crash the game.}} | |||
{{note|[[S_PreserveEnts]] cannot be instanced by this entity.}} | {{note|[[S_PreserveEnts]] cannot be instanced by this entity.}} | ||
If there are interdependencies (entity I/O, hierarchy, or other name references) between the entities | === Name Fix-up === | ||
in the template, the entities in the template will have their names changed and the interdependencies will | If there are interdependencies (entity I/O, hierarchy, or other name references) between the entities in the template, the entities in the template will have their names changed and the interdependencies will be reconnected to the changed names. The name change format is as follows: '<original name>&0000', where the 0000 will be replaced with the current global template instance, so wildcard searches for '<original name>*' will still find them. | ||
be reconnected to the changed names. The name change format is as follows: '<original name>&0000', where the 0000 | |||
will be replaced with the current global template instance, so wildcard searches for '<original name>*' will still find them. | |||
Name fixing is ''only'' for template entities spawned by output. The outputs of the point_template are ''not'' name fixed, and neither are the outputs of other objects referring to template entities. | Name fixing is ''only'' for template entities spawned by output. The outputs of the point_template are ''not'' name fixed, and neither are the outputs of other objects referring to template entities. | ||
| Line 31: | Line 19: | ||
With fixup on, the first (batch of) entities spawned will be postfixed<code>&0002</code>. If<code>spawnflag 2</code>is active, the unremoved entity will have its name postfixed with<code>&0001</code>. | With fixup on, the first (batch of) entities spawned will be postfixed<code>&0002</code>. If<code>spawnflag 2</code>is active, the unremoved entity will have its name postfixed with<code>&0001</code>. | ||
If you don't want the name fixup to happen, because you're only spawning the template once, or you want inputs to trigger all instances of the template, check the 'Preserve entity names' spawnflag. | |||
{{warning| Point_template ''will not'' do any name fixuppance in the parameter override boxes of its templated entities.}} | |||
=== Tutorial === | === Tutorial === | ||
A [[Respawning_Items|tutorial]] has been created for respawning items using this entity. | A [[Respawning_Items|tutorial]] has been created for respawning items using this entity. | ||
== Keyvalues == | == Keyvalues == | ||
{{KV | {{KV PointTemplate}} | ||
== Flags == | == Flags == | ||
{{Fl PointTemplate}} | |||
== Inputs == | == Inputs == | ||
{{I PointTemplate}} | |||
{{I | |||
== Outputs == | == Outputs == | ||
{{O PointTemplate}} | |||
{{O | |||
== See also == | == See also == | ||
Revision as of 00:43, 19 March 2021
Template:Otherlang2 Template:Base point It turns an entity, or set of entities, into a single template that can be instanced anywhere, and multiple times. When activated, this entity will spawn the entities in the template at the same positions, relative to this entity, that they had when this entity was created. This will be their original positions if the point_template has not been moved.bTo spawn the template in other places, an env_entity_maker can be used
Any logic_relay within the template, if it has one, will fire its OnSpawn output when spawned.
Bug:In 
, this entity is broken and will usually crash the game. Although if the gamemode is set to training in , it will work normally. [todo tested in ?]Bug:In 
, spawning a func_breakable_surf with this entity will crash the game. [todo tested in ?]
Note:S_PreserveEnts cannot be instanced by this entity.Name Fix-up
If there are interdependencies (entity I/O, hierarchy, or other name references) between the entities in the template, the entities in the template will have their names changed and the interdependencies will be reconnected to the changed names. The name change format is as follows: '<original name>&0000', where the 0000 will be replaced with the current global template instance, so wildcard searches for '<original name>*' will still find them.
Name fixing is only for template entities spawned by output. The outputs of the point_template are not name fixed, and neither are the outputs of other objects referring to template entities.
The special targetnames (!self and such) work on spawned objects, so a trigger_multiple with an output to!activatorcan be used to affect individual spawned objects. Wildcards can refer to all entities spawned by a fix-up-enabled point_template.
With fixup on, the first (batch of) entities spawned will be postfixed&0002. Ifspawnflag 2is active, the unremoved entity will have its name postfixed with&0001.
If you don't want the name fixup to happen, because you're only spawning the template once, or you want inputs to trigger all instances of the template, check the 'Preserve entity names' spawnflag.
Warning: Point_template will not do any name fixuppance in the parameter override boxes of its templated entities.Tutorial
A tutorial has been created for respawning items using this entity.
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
Inputs
- ForceSpawn
- Spawn an instance of the template at the original position.
Outputs
See also
- env_entity_maker - automatic respawning and/or spawning at a different location
- npc_maker - an alternative spawning entity, also with optional automatic respawning
point_script_template - version of point_template catered to VScripting