Trigger teleport: Difference between revisions
Jump to navigation
Jump to search
Tip:You can use env_fade to smoothen the player's perspective while teleporting (0.6 seconds is a good duration to start with). If you're intending to teleport players in multiplayer, remember to set the triggering player only flag!
Note:Any entity can be used as the teleport destination, including players.
Tip:This can be changed if necessary by using AddOutput.
Warning:
Teleport to a killed teleport destination entity will crash your client/server.
Tip:You can use !self to use the origin of this entity as the landmark.
Local Destination Landmark Usage Player position relative to the landmark (when teleported) is transferred to the destination.
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.
mNo edit summary |
(-BaseTrigger templates) |
||
| Line 5: | Line 5: | ||
{{tip|You can use {{ent|env_fade}} to smoothen the player's perspective while teleporting (0.6 seconds is a good duration to start with). If you're intending to teleport players in multiplayer, remember to set the [[Env_fade#Flags|''triggering player only'' flag]]!}} | {{tip|You can use {{ent|env_fade}} to smoothen the player's perspective while teleporting (0.6 seconds is a good duration to start with). If you're intending to teleport players in multiplayer, remember to set the [[Env_fade#Flags|''triggering player only'' flag]]!}} | ||
==Keyvalues== | ==Keyvalues== | ||
| Line 22: | Line 20: | ||
{{KV Targetname}} | {{KV Targetname}} | ||
{{KV | {{KV BaseTrigger}} | ||
==Flags== | ==Flags== | ||
{{Fl | {{Fl BaseTrigger}} | ||
{{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== | ==Inputs== | ||
{{I | {{I BaseTrigger}} | ||
==Outputs== | ==Outputs== | ||
{{O | {{O BaseTrigger}} | ||
{{sensor brush}} | {{sensor brush}} | ||
Revision as of 08:15, 8 August 2023
 Class hierarchy
|
|---|
| CTriggerTeleport |
| triggers.cpp
|
Template:Entity 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.
Tip:You can use env_fade to smoothen the player's perspective while teleporting (0.6 seconds is a good duration to start with). If you're intending to teleport players in multiplayer, remember to set the triggering player only flag!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.Tip:This can be changed if necessary by using AddOutput.Warning: Teleport to a killed teleport destination entity will crash your client/server.
- 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.
- 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
|
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.Inputs
|
Outputs
|