Info landmark: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
mNo edit summary |
||
| Line 7: | Line 7: | ||
|engine=2 | |engine=2 | ||
|in=0 | |in=0 | ||
}} {{point ent|this=0}} | }} {{point ent|type=e0|this=0}} | ||
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. | ||
Revision as of 10:54, 14 December 2022
| info_landmark | |
|---|---|
 | |
| Type | Point entity |
| Engine |  Source |
| Availability | In all games |
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.
 Class hierarchy
|
|---|
| CPointEntity |
| subs.cpp
|
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
See also
- Level Transitions
- info_landmark
- trigger_changelevel
- trigger_transition
- point_changelevel (only in
) - info_changelevel (only in
)