Trigger transition: Difference between revisions
Jump to navigation
Jump to search
m (Updated old entity format to {{this is a}}. This action was perfomed by a bot.) |
Thunder4ik (talk | contribs) m (→top: Unicodifying, replaced: {{language subpage → {{langsp) |
||
| Line 1: | Line 1: | ||
<!-- When this page is updated to {{langsp}} or {{ | <!-- When this page is updated to {{langsp}} or {{langsp}} instead of {{lang}}, please move {{this is a}} to the base page, as it is automatically translated. -->{{lang|Trigger transition}}|title=trigger_transition}} | ||
{{toc-right}} | {{toc-right}} | ||
{{subpage|[[Level Transitions]]}} | {{subpage|[[Level Transitions]]}} | ||
Revision as of 04:02, 9 January 2024
|title=trigger_transition}}
trigger_transition is an e2 available in all 
Source games.
It controls which entities go through a level transition. Trigger_transitions should be named the same as the info_landmark which is associated with a particular trigger_changelevel. Any entities which are within the trigger_transition brush volume will then go to the next map. The player must also be inside the brush volume.
In 
Portal 2, transition triggers can also be used with point_changelevel. In this case, the entity does not need to be named.
Keyvalues
- 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
Inputs
Outputs
See also
- Level Transitions
- info_landmark
- trigger_changelevel
- trigger_transition
- point_changelevel (only in )
- info_changelevel (only in
)