Global actors

This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these template messages)

This article needs more  links to other articles to help  integrate it into the encyclopedia. Please help improve this article by adding links  that are relevant to the context within the existing text.
January 2024

This article is an orphan, meaning that few or no articles link to it.
You can help by  adding links to this article from other relevant articles.
January 2024

In some of Valve's games where the Source Engine is used, they do not use entity names for playermodels as it would cause problems having to specify every name of the actors from map editors. Valve solved this problem up by using global actors that is capable of "detecting" models for the specific actor.

This is used in features like Response Rules, for example, the Citizens have their genders specified in the global_actors.txt to make them play their responses specific to the gender ($gender is used here for the soundscripts, it can detect the models if they are marked as either "male" or "female", restricting the specified model to only play the sounds and responses specific to that gender). When done, it prevents having to make seperate soundscripts for both genders.

However, if, for example, a model that has no name specified (no "female" or male"), when used as the entity npc_citizen, they will randomly play the responses of the two genders because they lack it.

Stub

This article or section is a stub. You can help by expanding it.

This article has not been added to any content  categories. Please help out by  adding categories.
January 2024