Info player counterterrorist: Difference between revisions
Jump to navigation
Jump to search
Placement Tip:like every player spawn entity, its origin should be placed...
Warning: The number of these entities limits the number of players on the corresponding team! If there are 5 info_player_terrorists, there cannot be more than 5 players on the Terrorist's team! This is a possible cause for Team is full! errors.
Warning: These entites spawn players, which have a width of 32 units in 
and 
. However, Hammer displays the bounding box of a player model, whose width is less than 32 units! See also: Dimensions.
Tip: Invalid spawn points are reported in the console when the map is loaded, for example:
Tip: If only some of the spawn points shall be used for say 5v5, increase the
Important:This is a preserved entity in.
If the game has round restart mechanics this entity may not behave as expected:
Porting from
mNo edit summary |
|||
| Line 12: | Line 12: | ||
This entities is also available on {{cs2|4}}. | This entities is also available on {{cs2|4}}. | ||
These entities are spawn points for either [[Terrorists]] or [[Counter-Terrorists]]. | |||
These entities are spawn points for either Terrorists or Counter-Terrorists | |||
At least one of each should be placed for each team member. This may result in the ''Both Teams are Full'' error. | |||
* at least 16 | |||
{{Placement Tip|like every [[:Category: Player spawn entities|player spawn entity]], its origin should be placed... | |||
* at least 16 [[unit]]s above the ground, | |||
* more than 32 units away from each other, | * more than 32 units away from each other, | ||
* more than 16 units away from surrounding walls and | * more than 16 units away from surrounding walls and | ||
* not intersecting with any solid geometry, | * not intersecting with any [[solid geometry]], | ||
}} | |||
otherwise the spawn point can become invalid, effectively behaving as if it didn't exist. | otherwise the spawn point can become invalid, effectively behaving as if it didn't exist. | ||
Standard maps use between 16 and 32 spawn points. | Standard maps use between 16 and 32 spawn points.{{Why}} | ||
{{Warning | The number of these entities limits the number of players on the corresponding team! If there are 5 '''info_player_terrorist'''s, there cannot be more than 5 players on the Terrorist's team! This is a possible cause for ''Team is full!'' errors.}} | {{Warning | The number of these entities limits the number of players on the corresponding team! If there are 5 '''info_player_terrorist'''s, there cannot be more than 5 players on the Terrorist's team! This is a possible cause for ''Team is full!'' errors.}} | ||
{{Warning | These entites spawn [[player]]s, which have a width of 32 units in {{css}} and {{csgo}}. However, [[Hammer]] displays the [[bounding box]] of a player [[model]], whose width is less than 32 units! ''See also: [[Dimensions]].''}} | {{Warning | These entites spawn [[player]]s, which have a width of 32 units in {{css}} and {{csgo}}. However, [[Hammer]] displays the [[bounding box]] of a player [[model]], whose width is less than 32 units! ''See also: [[Dimensions]].''}} | ||
| Line 28: | Line 30: | ||
{{Tip | {{csgo}} If only some of the spawn points shall be used for say 5v5, increase the <code>Spawn Priority (int)</code> keyvalue for all other spawn points. The former are used first, latter are ''only'' used if needed.}} | {{Tip | {{csgo}} If only some of the spawn points shall be used for say 5v5, increase the <code>Spawn Priority (int)</code> keyvalue for all other spawn points. The former are used first, latter are ''only'' used if needed.}} | ||
{{PreservedEnt|0}} | {{PreservedEnt|0}} | ||
== Porting from {{hl2|4}} and {{hl2dm|4}} == | |||
Unlike {{hl2|4}} and {{hl2dm|4}} spawn point entities, {{css|4}} spawn point entities will intersect the ground if not placed a couple of units above it. | |||
== Keyvalues == | == Keyvalues == | ||
Revision as of 19:25, 3 July 2023
 |
info_player_terrorist and info_player_counterterrorist are point entities available in the following Source engine games:
Counter-Strike: Source, Counter-Strike: Global Offensive.
This entities is also available on 
Counter-Strike 2.
These entities are spawn points for either Terrorists or Counter-Terrorists.
At least one of each should be placed for each team member. This may result in the Both Teams are Full error.
Placement Tip:like every player spawn entity, its origin should be placed...
- at least 16 units above the ground,
- more than 32 units away from each other,
- more than 16 units away from surrounding walls and
- not intersecting with any solid geometry,
otherwise the spawn point can become invalid, effectively behaving as if it didn't exist.
Standard maps use between 16 and 32 spawn points.[Why?]
Warning: The number of these entities limits the number of players on the corresponding team! If there are 5 info_player_terrorists, there cannot be more than 5 players on the Terrorist's team! This is a possible cause for Team is full! errors.Warning: These entites spawn players, which have a width of 32 units in and . However, Hammer displays the bounding box of a player model, whose width is less than 32 units! See also: Dimensions.Tip: Invalid spawn points are reported in the console when the map is loaded, for example: Invalid terrorist spawnpoint at (<x>,<y>,<z>). These lines can easily be found in the console using con_filter_enable 2 and con_filter_text spawnpoint.Tip: If only some of the spawn points shall be used for say 5v5, increase the Spawn Priority (int) keyvalue for all other spawn points. The former are used first, latter are only used if needed.Important:This is a preserved entity in.If the game has round restart mechanics this entity may not behave as expected:
|
Porting from 
Half-Life 2 and 
Half-Life 2: Deathmatch
Unlike Half-Life 2 and Half-Life 2: Deathmatch spawn point entities, Counter-Strike: Source spawn point entities will intersect the ground if not placed a couple of units above it.
Keyvalues
- Spawn priority (priority) <integer> (only in )
- Determines which spawn points get used first. Smaller numbers are used before larger numbers.
- Enabled by default? (enabled) <boolean> (only in )
- Should this spawn be enabled by default?
Inputs
- SetEnabled (only in )
- Sets this spawn point as enabled.
- SetDisabled (only in )
- Sets this spawn point as disabled.
- ToggleEnabled (only in )
- Toggle the enabled/disabled state of this spawn point.