Logic director query

Template:L4d2 point It is used to output the AI Director's 'anger' value, where the director is angered by players that are performing well. This provides an opportunity for map elements to be adjusted in an attempt to appease the AI Director. Some examples include adjusting the goal distance and increasing/decreasing obscuring weather effects.

Any number of logic_director_query entities can exist in the same map, each with their own value range and noise settings.

KeyValues

Name (targetname) <string>[ Edit ]

The name that other entities refer to this entity by, via Inputs/Outputs or other keyvalues (e.g. parentname or target).
Also displayed in Hammer's 2D views and Entity Report.

See also:  Generic Keyvalues, Inputs and Outputs available to all entities

Min Anger Range (minAngerRange) <integer>

Max Anger Range (maxAngerRange) <integer>

The range of integers used to represent the director's anger. The value will be mapped within it. Choosing a wider range of numbers allows finer "anger management".

Noise (noise) <choices>

Randomises the entity's output slightly. “No noise” will cause the output being the exact remapped value of the director's anger, while “complete noise” will result in a random number within the anger range. There are various other levels in between.

Inputs

HowAngry

Asks the director: “On a scale of <Min Anger Range> to <Max Anger Range>, how angry are you?”

Outputs

OutAnger <integerRedirectInput/integer>

Director is this much angry (expressed as an integer), fired in response to HowAngry. Sends the current remapped value of the director's anger to an entity of your choice (logic_case is generally the most useful).

On20SecondsToMob

Fires 20 seconds before mob spawns

See also

• L4D2 Level Design/Director Queries