From Valve Developer Community
Jump to: navigation, search
English (en)Deutsch (de)
... Icon-Important.png
Counter-Strike: Source Terrorist model.
Counter-Strike: Source Counter-Terrorist model.
Counter-Strike: Global Offensive Counter-Terrorist model mit der Bounding Box eines players.
Creating a Classic Counter-Strike Map

info_player_terrorist und info_player_counterterrorist sind Punkt-Objekte, die in den folgenden Source Engine-Spielen verfügbar sind:

Counter-Strike: Source Counter-Strike: Source , Counter-Strike: Global Offensive Counter-Strike: Global Offensive .


Diese Objekte sind die Einstiegspunkte für Terroristen (terrorists - T), bzw. Antiterroristen (counterterrorists - CT). Für jedes Teammitglied sollte mindestens ein solches Objekt platziert werden.

Wie jedes andere player spawn entity (Einstiegspunkt-Objekt), sollte dessen Ursprung...

  • mindestens 16 Einheiten über dem Boden,
  • mehr als 32 Einheiten voneinander entfernt,
  • mehr als 16 Einheiten von Wänden entfernt und
  • nicht innherhalb anderer fester Objekte platziert werden.

ansonsten kann ein Einstiegspunkt ungültig werden, d.h. für das Spiel unbrauchbar.

Die offiziellen Maps haben 16 bis 32 Einstiegspunkte.

Warning.png Achtung:  Die Anzahl dieser Objekte begrenzt die Anzahl an Spielern im jeweiligen Team! Gibt es nur 5 info_player_terrorists, dann können nicht mehr als 5 Spieler den Terroristen beitreten! Dies ist eine mögliche Ursache für den Fehler "Das Team der Terroristen ist voll." bzw. "Das Antiterrorteam ist komplett!".
Warning.png Achtung:  Zu diesen Objekten werden Spieler teleportiert, welche in Counter-Strike: Source und Counter-Strike: Global Offensive eine Breite von 32 Einheiten haben. Hammer zeigt allerdings stets die Bounding box eines Spielermodells, dessen Breite kleiner als 32 Einheiten ist! Siehe Dimensions.
Tip.pngTip: Ungültige Einstiegspunkte werden in der Konsole gemeldet, wenn die Map geladen wird. Beispiel: Invalid terrorist spawnpoint at (<x>,<y>,<z>). Diese Zeilen lassen sich einfach finden mithilfe von con_filter_enable 2 und con_filter_text spawnpoint vor dem Laden der Map.
Tip.pngTip: Counter-Strike: Global Offensive Wenn nur ein paar der Einstiegspunkte für z.B. 5 gegen 5 genutzt werden sollen, erhöhe den Wert von Spawn Priority (int) für alle anderen Einstiegspunkte. Erstere werden dann zuerst genutzt, letztere nur wenn nötig.
Note.pngNote:This is a preserved entity in .
  • On a new round, its properties including its position will intentionally not reset. You can use logic_auto to emulate resetting it.
  • Killing it removes it forever, as it is not respawned on a new round.
  • It cannot be spawned with a point_template.
  • Parenting this with non preserved entities may have undesirable effects.


Spawn priority (priority) <integer> (only in Counter-Strike: Global Offensive)
Bestimmt, welcher Einstiegspunkt zuerst genutzt wird. Kleinere Werte werden vor größeren genutzt.
Enabled by default? (enabled) <boolean> (only in Counter-Strike: Global Offensive)
Soll dieser Einstiegspunkt standardmäßig aktiv sein?

Name (targetname) <string>
The name that other entities use to refer to this entity.
Parent (parentname) <targetname>
Maintain the same initial offset to this entity. An attachment point can also be used if separated by a comma at the end. (parentname [targetname],[attachment])
Tip.pngTip:Entities transition to the next map with their parents
Tip.pngTip:phys_constraint can be used as a workaround if parenting fails.
Origin (X Y Z) (origin) <coordinates>
The position of this entity's center in the world. Rotating entities typically rotate around their origin.
Note.pngNote:Hammer does not move the entities accordingly only in the editor.
Pitch Yaw Roll (X Y Z) (angles) <angle>
This entity's orientation in the world. Pitch is rotation around the Y axis, yaw is the rotation around the Z axis, roll is the rotation around the X axis.
Note.pngNote:This works on brush entities, although Hammer doesn't show the new angles.
Classname (classname) <string> !FGD
Determines the characteristics of the entity before it spawns.
Tip.pngTip:Changing this on runtime still has use, like making matching an entry in S_PreserveEnts will persist the entity on new rounds!
Spawnflags (spawnflags) <flags> !FGD
Toggles exclusive features of an entity, its specific number is determined by the combination of flags added.
Effects (effects) <flags> !FGD
Combination of effect flags to use.
Entity Scripts (vscripts) <scriptlist> (in all games since Left 4 Dead 2) (also in Team Fortress 2)
Space delimited list of VScript files (without file extension) that are executed after all entities have spawned. The scripts are all executed in the same script scope, later ones overwriting any identical variables and functions. Scripts executed on the worldspawn entity will be placed in root scope.
Think function (thinkfunction) <string> (in all games since Left 4 Dead 2) (also in Team Fortress 2)
Name of the function within this entity's script that'll be called automatically every 100 milliseconds, or a user-defined interval if the function returns a number. Avoid expensive operations in this function, as it may cause performance problems.
Lag Compensation (LagCompensate) <boolean> (in all games since Left 4 Dead 2) !FGD
Set to Yes to lag compensate this entity. Should be used very sparingly!
Is Automatic-Aim Target (is_autoaim_target) <boolean> (in all games since Counter-Strike: Global Offensive) !FGD
If set to 1, this entity will slow down aiming movement for consoles and joystick controllers when the entity is under the crosshairs.


SetEnabled  (only in Counter-Strike: Global Offensive)
Aktiviert diesen Einstiegspunkt.
SetDisabled  (only in Counter-Strike: Global Offensive)
Deaktiviert diesen Einstiegspunkt.
ToggleEnabled  (only in Counter-Strike: Global Offensive)
Wechselt zwischen aktiviertem und deaktiviertem Zustand dieses Einstiegspunktes.

AddContext <string>
Adds to the entity's list of response contexts. See Context.
AddOutput <string>
Assigns a new keyvalue/output on this entity. For keyvalues, some rely on extra necessary code to be ran and won't work if its simply just changed through this input. There is a strict format that must be followed:
// Format of changing KeyValues: "AddOutput [key] [value]"
//// Raw text:
"OnUser1" "!self,AddOutput,targetname new_name"

// Format of adding an Output: "AddOutput {targetname}:{inputname}:{parameter}:{delay}:{max times to fire, -1 means infinite}"
//// Raw text:
"OnUser1" "!self,AddOutput,OnUser1:SetParent:!activator:0.0:-1"
// Arguments can be left blank, but the empty blank should still be contained.
//// Raw text:
"OnUser1" "!self,AddOutput,OnUser1:ClearParent::0.0:-1"
Removes all contexts from this entity's list.
Removes this entity from the the movement hierarchy, leaving it free to move independently.
FireUser1 to FireUser4
Fires the respectiveOnUseroutputs; see User Inputs and Outputs.
Removes this entity and any entities parented to it from the world.
Functions the same as Kill, although this entity and any entities parented to it are killed on the same frame, being marginally faster thanKillinput.
RemoveContext <string>
Remove a context from this entity's list. The name should match the key of an existing context.
SetParent <string>
Move with this entity. See Entity Hierarchy (parenting).
SetParentAttachment <string>
Change this entity to attach to a specific attachment point on its parent. The entity will teleport so that the position of its root bone matches that of the attachment. Entities must be parented before being sent this input.
SetParentAttachmentMaintainOffset <string>
As above, but without teleporting. The entity retains its position relative to the attachment at the time of the input being received.
Use  !FGD
Same as a player invoking +use; no effect in most cases.
DispatchResponse <string> !FGD
Dispatches a response to the entity. See Response and Concept.
DispatchEffect <string> (removed since Left 4 Dead) !FGD
Dispatches a special effect from the entity's origin; See also List of Client Effects. Replaced by the particle system since Left 4 Dead.
RunScriptFile <script> (in all games since Left 4 Dead 2) (also in Team Fortress 2)
Execute a VScript file from disk, without file extension. The script contents are merged with the script scope of the receiving entity.
RunScriptCode <string> (in all games since Left 4 Dead 2) (also in Team Fortress 2)
Execute a string of VScript source code in the scope of the entity receiving the input. String quotation may be needed when fired via console.
Icon-Bug.pngBug:In Hammer, using string arguments will corrupt the VMF file's structure, making the file unviewable for the next Hammer session.
Note.pngFix:Remove the string argument manually with a text editor.
Note.pngNote:Team Fortress 2 Backtick characters ` are replaced with quotation marks at runtime, allowing quotation marks to be used when normally not possible.
CallScriptFunction <string> (in all games since Left 4 Dead 2) (also in Team Fortress 2) !FGD
Calls a VScript function defined in the scope of the receiving entity.
TerminateScriptScope  (only in Team Fortress 2) !FGD
Destroys the script scope of the receving entity.
SetLocalOrigin <coordinates> (in all games since Alien Swarm) !FGD
Send this entity to a spot in the map. If the entity is parented to something, it will be offset from the parent by this amount.
SetLocalAngles <angles> (in all games since Alien Swarm) !FGD
Set this entity's angles.



OnUser1 to OnUser4
These outputs each fire in response to the firing of the like-numbered FireUser1 to FireUser4 Input; see User Inputs and Outputs.

See also