jail_team_master entity
The jail_team_master entity is used as a master to provide a method of testing for a player's jail and armory status. It is used just like the game_team_master entity, but will only trigger if the player's status matches what is being tested.
Masters are utilized in two manners. When they are specified as the master of another entity, the entity will check the master to see if the activator can utilize the entity. This is how team specific buttons are done. Masters can also be triggered just like any other entity. However, if a master is triggered, it will not actually fire unless the master's criteria is met.
Specifics
| Name | Description | ||||||
|---|---|---|---|---|---|---|---|
| targetname | Name assigned to the master.
Use this name as the value of the master specific for other entities. |
||||||
| target | Name of the targets to be triggered when the master is triggered. | ||||||
| killtarget | Name of the targets to be removed when the master is triggered. | ||||||
| delay | If the master is triggered, the delay specifies the amount of time the master will wait prior to triggering the target and the killtarget. | ||||||
| triggerstate | Specifies the manner that a target
will be triggered.
|
||||||
| teamindex | The index of the team that will match the master. The index is zero based, so to match team 1, set the teamindex to 0. To allow any team to match the master, specify a teamindex of -1. |
Spawnflags
| Value | Description |
|---|---|
1 |
Remove this entity after the entity fires |
1024 |
Player can be free * |
2048 |
Player can be in jail * |
4096 |
Player can be on death row * |
8192 |
Player can be in an armory * |
16384 |
Player can be not in an armory * |
* Multiple player statuses can be tested for in the same entity. Setting all five status spawnflags will cause the jail_team_master entity to act like a game_team_master entity.