Trigger teleport: Difference between revisions
		
		
		
		
		
		Jump to navigation
		Jump to search
		
				
		
 Note:Any entity can be used as the teleport destination, including players.
Note:Any entity can be used as the teleport destination, including players.
 Note:
Note:
 Tip:You can use !self to use the origin of this entity as the landmark.
Tip:You can use !self to use the origin of this entity as the landmark.
 Note:Some SDK versions list trigger_teleport flag 32 as "Preserve angles even when a local landmark is not specified" but may actually behave according the newer flags above. To achieve the angle-preserving behavior, you can instead specify !activator for the landmark property.
Note:Some SDK versions list trigger_teleport flag 32 as "Preserve angles even when a local landmark is not specified" but may actually behave according the newer flags above. To achieve the angle-preserving behavior, you can instead specify !activator for the landmark property.
		
	
|  (-added class hierarchy) | |||
| Line 9: | Line 9: | ||
| {{KV|Remote Destination|intn=target|target_destination|The entity specifying the point to which entities should be teleported.  Usually either a [[info_teleport_destination]] or [[info_target]].}} | {{KV|Remote Destination|intn=target|target_destination|The entity specifying the point to which entities should be teleported.  Usually either a [[info_teleport_destination]] or [[info_target]].}} | ||
| {{note|''Any'' entity can be used as the teleport destination, including players.}} | {{note|''Any'' entity can be used as the teleport destination, including players.}} | ||
| {{note|<code>target</code> can be manipulated in real time using [[AddOutput]].}} | |||
| {{warning|{{csgo}} Teleport to a killed teleport destination entity will crash your client/server.}} | {{warning|{{csgo}} Teleport to a killed teleport destination entity will crash your client/server.}} | ||
Revision as of 13:14, 16 January 2023
|  Class hierarchy | 
|---|
| CTriggerTeleport | 
|  triggers.cpp | 
Template:Base brush It is a trigger that teleports entities that touch its volume. Entities are teleported to the Remote Destination, and have their angles set to that of the Remote Destination's angles. If a Local Destination Landmark is specified, teleported entities are offset from the target by their initial offset from the landmark, and their angles are left alone.
Keyvalues
- Remote Destination (target) <targetname>
- The entity specifying the point to which entities should be teleported. Usually either a info_teleport_destination or info_target.
 Note:Any entity can be used as the teleport destination, including players.
Note:Any entity can be used as the teleport destination, including players. Note:
Note:target can be manipulated in real time using AddOutput.
- Local Destination Landmark (landmark) <targetname>
- If specified, then teleported entities are offset from the target by their initial offset from the landmark.
 Tip:You can use !self to use the origin of this entity as the landmark.
Tip:You can use !self to use the origin of this entity as the landmark.
- Name (targetname) <string>[ Edit ]
- The name that other entities refer to this entity by, via Inputs/Outputs or other keyvalues (e.g. parentnameortarget).
 Also displayed in Hammer's 2D views and Entity Report.See also: Generic Keyvalues, Inputs and Outputs available to all entities
- Filter Name (filtername) <filter>
- Name of filter entity to test against activators.
- Start Disabled (StartDisabled) <boolean>
- Stay dormant until activated (with theEnableinput).
Flags
| 
 
 
 
 
 
 
 
 | 
 Note:Some SDK versions list trigger_teleport flag 32 as "Preserve angles even when a local landmark is not specified" but may actually behave according the newer flags above. To achieve the angle-preserving behavior, you can instead specify !activator for the landmark property.
Note:Some SDK versions list trigger_teleport flag 32 as "Preserve angles even when a local landmark is not specified" but may actually behave according the newer flags above. To achieve the angle-preserving behavior, you can instead specify !activator for the landmark property.Inputs
| 
 
 
 
 | 
Outputs
| 
 
 
 
 
 
 | 




































