Info landmark: Difference between revisions
Jump to navigation
Jump to search

mNo edit summary |
m (Removed {{cls}}, moved {{CD}} code to a reasonable position.) |
||
Line 8: | Line 8: | ||
|engine=2 | |engine=2 | ||
|in=0 | |in=0 | ||
}} {{ent|mode=entity|info_landmark|type=e0}} | }} | ||
{{CD|CPointEntity|file1=subs.cpp}} | |||
{{ent|mode=entity|info_landmark|type=e0}} | |||
It acts as a landmark for [[Level Transitions]]. There should be a corresponding '''info_landmark''' entity in the next map. Entities will be transitioned to the next level relative to the info_landmark entities. | It acts as a landmark for [[Level Transitions]]. There should be a corresponding '''info_landmark''' entity in the next map. Entities will be transitioned to the next level relative to the info_landmark entities. | ||
==Keyvalues== | ==Keyvalues== |
Revision as of 19:03, 23 January 2023


info_landmark | |
---|---|
![]() | |
Type | Point entity |
Engine | ![]() |
Availability | In all games |
![]() |
---|
CPointEntity |
![]() |
info_landmark It acts as a landmark for Level Transitions. There should be a corresponding info_landmark entity in the next map. Entities will be transitioned to the next level relative to the info_landmark entities.
Keyvalues
- Name (targetname) <string>[ Edit ]
- The name that other entities refer to this entity by, via Inputs/Outputs or other keyvalues (e.g.
parentname
ortarget
).
Also displayed in Hammer's 2D views and Entity Report.See also: Generic Keyvalues, Inputs and Outputs available to all entities
See also
- Level Transitions
- info_landmark
- trigger_changelevel
- trigger_transition
- point_changelevel (only in
)
- info_changelevel (only in
)