pma-voice is running, HumaLike only observes its radio and phone state to
avoid transmitting to NPCs during those conversations. Player voice remains
owned by the server’s normal voice resource.
Push to talk
Players speak to AI NPCs using HumaLike’s push-to-talk binding. They can change the binding in FiveM key settings. The HUD indicates whether HumaLike is currently transmitting. A custom HUD can subscribe on the client:Which NPC hears the player
The resource continuously maintains a small set of direct conversation targets so the HUD reflects the current routing before the player presses PTT. It prioritizes:- An NPC following that player.
- NPCs sharing the player’s vehicle.
- A nearby NPC the player’s ped and gameplay camera are directed toward.
Proximity and muted indicators
HumaLike limits how many NPC conversations are active around each player. The label shows when an NPC is not currently in that player’s listening set. Direct target selection updates that state so the NPC the player is addressing is not presented as unavailable while other nearby NPCs are temporarily muted. Muting is per player. Two players in the same area can have different active NPCs without changing the NPC globally.Vehicles
Players and NPCs in the same vehicle cabin remain voice-connected. An NPC that is following a player is prioritized for that player, including after entering a vehicle. Other players keep their own routing and priorities.Diagnose voice
Run/voice in the FiveM client to inspect the local connection. Also check:
- the browser/NUI microphone permission;
- the configured HumaLike PTT key;
- that the server license is valid;
- that the registered callback still points at this FXServer;
- that OneSync is enabled.
humalike_debug only while diagnosing a problem. Do not publish logs
that contain connection URLs or credentials.

