Simple Voice Chat

Four trigger powers and four entity conditions that react to voice activity from Simple Voice Chat.

All of them are behaviour-gated: the types are always registered, so a pack that uses them loads on any server. Without Simple Voice Chat installed the conditions read false and the trigger powers never fire.

Types#

Type	Kind	Fires / passes when
apoli:action_on_speak	Power	The holder starts or stops talking.
apoli:action_on_reply	Power	Someone talks back to the holder shortly after they spoke.
apoli:action_on_speech	Power	The holder says a specific phrase out loud.
apoli:action_on_sending_message	Power	The holder sends a matching chat message.
apoli:voice_speaking	Entity condition	The entity is talking right now.
apoli:voice_disabled	Entity condition	The entity has voice chat off or isn’t connected.
apoli:voice_loudness	Entity condition	The entity’s current loudness passes a comparison.
apoli:voice_listeners	Entity condition	Enough connected players are in earshot.

How loudness is measured#

Loudness is approximated from the size of the encoded voice packet — no audio is decoded. That makes it very cheap, but coarse: it is good for “loud vs. quiet”, not for precise volume. The value is normalised to 0–100.

Where it is evaluated#

Voice state is tracked on the server. A condition evaluated purely client-side — for example inside a client render power — will not see it.

Speech versus chat#

apoli:action_on_speech and apoli:action_on_sending_message both match words, but they are unrelated systems:

• action_on_speech transcribes the player’s microphone on their own machine and sends only text to the server. It does not use Simple Voice Chat at all and works without it.
• action_on_sending_message matches typed chat messages. It is the fallback for setups where speech recognition isn’t available.

Simple Voice Chat itself only carries audio, so it can never provide word matching on its own.