func_respawnroom
func_respawnroom
is a brush entity available in Team Fortress 2.
Entity description
Designates a respawn room for a team.
Respawn rooms have the following properties:
- Gives players instant respawns when they change class or loadout.
- Blocks engineers from being able to build, similar to a
func_nobuild
entity. - Forces players to drop carried
item_teamflag
entities. - Forces players to drop active powerups.
- Grants MvM bots their spawn protection.
Keyvalues
TeamNum:
- Initial Team
(TeamNum)
<choices> - Which Team the entity belongs / is assigned to on spawn
- 0: None
- 1: Spectator/Halloween Souls
- 2: RED
- 3: BLU/Robots
- 5: Halloween Bosses (only in ) !FGD
BaseTrigger:
- Filter Name
(filtername)
<filter> - A filter entity to test potential activators against.
- Start Disabled
(StartDisabled)
<boolean> - Stay dormant until activated (with the
Enable
input).
Base:
- Collisions
(solid)
<choices> - Method of collision for this entity.
Values:
- 0: None
- 1: BSP (QPhysics) !FGD Bug:In , if an entity using QPhysics collisions is hit by Gel, the game will crash!
- 2: Bounding Box
- 3: Oriented Bounding Box (Use for runtime spawned brush entities meant to be rotated) !FGD
- 4: Oriented Bounding Box but constrained to Yaw only !FGD
- 5: Custom/Test (Usually no collision with anything) !FGD
- 6: VPhysics
- 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:Entities transition to the next map with their parentsTip: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: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: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: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.
Flags
TFTeam:
SetTeam
<integer>- Changes the entity's Team keyvalue.
Inputs
Todo: Describe custom inputs.
SetActive
SetInactive
ToggleActive
RoundActivate
BaseTrigger:
Toggle
- Toggles this trigger between enabled and disabled states.
Enable
- Enable trigger
Disable
- Disable trigger
TouchTest
(in all games since )- Triggers either the OnTouching or OnNotTouching outputs for whether anything is touching this entity.
StartTouch
(in all games since ) !FGD- Behave as if the
!caller
entity had just entered the trigger volume. Accepts non-physical entities.
EndTouch
(in all games since ) !FGD- Behave as if !caller had just exited the trigger volume.
Toggle:
Toggle
- Toggle the enabled/disabled status of this entity.
EnableDisable:
Enable
Disable
- Enable/disable this entity from performing its task. It might also disappear from view.
Base:
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"
|
ClearContext
- Removes all contexts from this entity's list.
ClearParent
- Removes this entity from the the movement hierarchy, leaving it free to move independently.
FireUser1
toFireUser4
- Fires the respective
OnUser
outputs; see User Inputs and Outputs.
Kill
- Removes this entity and any entities parented to it from the world.
KillHierarchy
- Functions the same as
Kill
, although this entity and any entities parented to it are killed on the same frame, being marginally faster thanKill
input.
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.
Outputs
BaseTrigger:
OnStartTouch
- Fired when a valid entity starts touching this trigger.
!activator
is whatever touches the trigger.
OnStartTouchAll
- Fired when a valid entity starts touching this trigger, and no other entities are touching it. If there are any other entities touching the trigger when a new one begins to touch, only
OnStartTouch
will fire.
OnEndTouch
- Fired when a valid entity stops touching this trigger.
Warning:This includes entities which are deleted while inside the trigger. In this case !activator will be invalid.
OnEndTouchAll
- Fired when all valid entities stop touching this trigger.
OnTouching
(in all games since )- Fired if something is currently touching this trigger when
TouchTest
is fired.
OnNotTouching
(in all games since )- Fired if nothing is currently touching this trigger when
TouchTest
is fired.
Base:
OnUser1
toOnUser4
- These outputs each fire in response to the firing of the like-numbered
FireUser1
toFireUser4
Input; see User Inputs and Outputs.