Logic collision pair: Difference between revisions

From Valve Developer Community
Jump to navigation Jump to search
No edit summary
(Which kinds of names are accepted, and when.)
Line 7: Line 7:
{{KV|Attachment 1|target_destination|The first entity.}}
{{KV|Attachment 1|target_destination|The first entity.}}
{{KV|Attachment 2|target_destination|The second entity.}}
{{KV|Attachment 2|target_destination|The second entity.}}
{{Note| These targetnames are evaluated at enable time. !activator and !caller are not accepted.}}
{{KV|Start with collisions disabled|boolean|If '''Yes''', starts with collisions between the pair disabled.  If '''No''', starts with collisions between the pair enabled.}}
{{KV|Start with collisions disabled|boolean|If '''Yes''', starts with collisions between the pair disabled.  If '''No''', starts with collisions between the pair enabled.}}
{{KV Targetname}}
{{KV Targetname}}

Revision as of 07:19, 18 September 2019

Template:Base point

Entity description

It can be used to enable/disable VPhysics collisions between two target entities.

Keyvalues

Attachment 1 ([todo internal name (i)]) <targetname>
The first entity.
Attachment 2 ([todo internal name (i)]) <targetname>
The second entity.
Note.pngNote: These targetnames are evaluated at enable time. !activator and !caller are not accepted.
Start with collisions disabled ([todo internal name (i)]) <boolean>
If Yes, starts with collisions between the pair disabled. If No, starts with collisions between the pair enabled.
Name (targetname) <string>[ Edit ]
The name that other entities refer to this entity by, via Inputs/Outputs or other keyvalues (e.g. parentname or target).
Also displayed in Hammer's 2D views and Entity Report.
See also:  Generic Keyvalues, Inputs and Outputs available to all entities

Inputs

EnableCollisions
Enable collisions between the first and second entity.
DisableCollisions
Disable collisions between the first and second entity.


Outputs