Info landmark: Difference between revisions
Jump to navigation
Jump to search
In code, it is represented by the
(-added class hierarchy) |
Noruzenchi86 (talk | contribs) Tag: Undo |
||
| Line 5: | Line 5: | ||
{{base point|info_landmark|sprite=1}} | {{base point|info_landmark|sprite=1}} | ||
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. | ||
{{code class|CPointEntity|subs.cpp}} | {{code class|CPointEntity|subs.cpp}} | ||
Revision as of 14:18, 14 November 2022
| Class hierarchy
|
|---|
| CPointEntity |
| subs.cpp
|
Template:Base point 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.
In code, it is represented by theCPointEntityclass, defined in thesubs.cppfile.
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
)