Info player start: Difference between revisions

From Valve Developer Community
Jump to navigation Jump to search
(TF2 spawnpoint classname)
mNo edit summary
Line 8: Line 8:
* To prevent the player from spawning into geometry, the entity cannot reside halfway through a solid object.
* To prevent the player from spawning into geometry, the entity cannot reside halfway through a solid object.
* In [[Counter-Strike: Source]], this entity represents the initial origin for a player that has just joined the game.
* In [[Counter-Strike: Source]], this entity represents the initial origin for a player that has just joined the game.
* If there isn't atleast one spawn entity, most mods will usually spawn the player at 0, 0, 0.
* If there isn't at least one spawn entity, most mods will usually spawn the player at 0, 0, 0.
{{note|While normally a problem, any number of <code>info_player_start</code> entities can be placed in a map when working in cordoned areas (see [[Hammer Cordon Usage#Localized starting points|Localized starting points]] for more information).}}
{{note|While normally a problem, any number of <code>info_player_start</code> entities can be placed in a map when working in cordoned areas (see [[Hammer Cordon Usage#Localized starting points|Localized starting points]] for more information).}}



Revision as of 10:55, 10 September 2008

Template:Wrongtitle Template:Base point

Entity description

Info player start.png
  • This entity indicates the position and facing direction at which the player will spawn.
  • In Single Player games: Template:Map properties
  • To prevent the player from spawning into geometry, the entity cannot reside halfway through a solid object.
  • In Counter-Strike: Source, this entity represents the initial origin for a player that has just joined the game.
  • If there isn't at least one spawn entity, most mods will usually spawn the player at 0, 0, 0.
Note.pngNote:While normally a problem, any number of info_player_start entities can be placed in a map when working in cordoned areas (see Localized starting points for more information).

Keyvalues

Flags

  • Master (Has priority if multiple info_player_start entities exist)