activator Last edited 3 months ago2024-08-06 09:23:25 UTC

In GoldSrc entity system, the activator is one of the entity references passed to an entity's targets when it gets activated, the other being the caller i.e. the immediate entity firing the target.

Examples of activation that passes an activator include a player touching a trigger, or pressing a button. The targets of these entities receive references to both the caller (trigger or button), and the activator (the player). In case of solid triggers, checking the "Monsters" (1) flag makes monsters activators too.

An entity getting triggered can, in turn, fire its own targets. This is called a trigger chain. For some entities, it will pass along the activator as it receives it to its targets, perpetuating the activator reference. Then, an entity somewhere along the trigger chain can act on the original activator (e.g. game_text or env_fade, depending on how they're set up) even if it's many levels removed from the original triggering event.

Suppose this chain of triggers:

player → trigger_multiple → multi_manager → game_text

the game_text entity at the end of this trigger chain will be able to display its text to the player who activated the trigger_multiple entity at the start of the chain, because these entities pass along the activator when they trigger each other, in this case the player.

Another example:

player → func_button → func_healthcharger
player → trigger_multiple → func_healthcharger

The first line will give the player exactly 1HP no matter how long the USE key is pressed on the button, because unlike a func_healthcharger a func_button only sends an impulse USE, and the charger only sends 1HP to the activator.
The second line, with a trigger_multiple with reset value of 0.1s, now turns the trigger into a healing forcefield that respects the func_healthcharger per-skill juice amount.

Do note however that not all entities will pass along their activator reference. Some send none, others will send itself. This means that an activator reference can be a non-player, or none at all, and when they trigger entities that directly affect their activators like func_healthcharger or game_text it may fail, or even cause a crash.

Some scenarios where activator is used:

• Some entities such as func_healthcharger and game_text acts on the activator by principle or by default. Others like env_fade can be set to affect activators instead of globally.
• In multiplayer, it is used to award points to players who uses environmental traps, provided the trigger chain is carefully crafted to carry the activator reference. This excludes func_tank & co. though.
• Some special entity names are automatically triggered on certain game events e.g. spawning or getting a kill/killed, with the affected player as activator.

The activator chain however will be broken (i.e. the original activator reference lost) in the following entities:

• trigger_relay - sends itself as activator (however in Spirit of Half-Life it does forward the activator). Use multi_manager instead.
• scripted_sequence and scripted_sentence - sends no activator
• func_breakable - sends no activator
• monstermaker - sends itself as activator