> For the complete documentation index, see [llms.txt](https://x1studios.gitbook.io/x1studios-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://x1studios.gitbook.io/x1studios-docs/whos-talking/installation.md).

# Installation

## X1Studios Whos Talking?

### Requirements

The only required dependency is:

#### PMA-Voice

PMA-Voice must already be installed and functioning on your FiveM server.

No framework is required.

The script works with:

* Standalone
* QBCore
* QBox
* ESX
* vMenu
* Custom frameworks

***

## Step 1 — Install PMA-Voice

If PMA-Voice is not already installed on your server, install it first.

The Talking Indicator relies on PMA-Voice to determine when players are speaking.

Make sure PMA-Voice is working correctly before continuing.

***

## Step 2 — Download The Script

Download the latest version of the **X1Studios Whos Talking?**.

Extract the resource using:

* 7-Zip
* WinRAR
* Windows File Explorer

Keep the resource's original folder structure intact.

***

## Step 3 — Add The Resource To Your Server

Place the Talking Indicator resource inside your server's resources directory.

For example:

```
resources/
├── [voice]/
│   └── pma-voice/
│
└── X1S-Talking/
```

The exact folder name may differ depending on the version of the resource.

***

## Step 4 — Verify PMA-Voice

Before starting the Talking Indicator, verify that PMA-Voice is running.

Your server configuration should start PMA-Voice before the Talking Indicator.

For example:

```cfg
ensure pma-voice
ensure X1S-Talking
```

If your PMA-Voice resource is located inside a category folder, use the appropriate resource name for your server.

***

## Step 5 — Add The Resource To server.cfg

Open your:

```
server.cfg
```

Add:

```cfg
ensure X1S-Talking
```

Make sure the resource name matches the actual folder name.

***

## Step 6 — Restart The Server

Restart your FiveM server after adding the resource.

You can also start the resource manually from the server console:

```
ensure X1S-Talking
```

Check the server console for any errors.

***

## Step 7 — Test The Talking Indicator

Connect to your server with at least one other player.

Have the player speak using PMA-Voice.

The Talking Indicator should display something similar to:

```
------------
Talking:
[12] John Doe
------------
```

When multiple players are talking:

```
------------
Talking:
[12] John Doe
[27] Havoc Sheriff
------------
```

When the player stops speaking, their name should disappear from the list.

***

## Step 8 — Verify Player Information

Confirm that the display correctly shows:

* Player server ID
* Player name
* Talking status

The information should update automatically as players begin and stop speaking.

***

## Troubleshooting

### Talking Indicator Does Not Appear

If the UI does not appear:

* Verify the resource is running.
* Verify PMA-Voice is running.
* Check the server console for errors.
* Check the client console for errors.
* Verify the resource name in `server.cfg`.
* Restart the resource.

***

### Players Are Not Appearing When Speaking

If players can speak but are not appearing in the Talking list:

* Verify PMA-Voice is functioning correctly.
* Confirm the player is actually transmitting through PMA-Voice.
* Verify PMA-Voice starts before the Talking Indicator.
* Restart both resources.
* Check for client-side errors.

***

### Names Are Not Displaying Correctly

If the server ID appears but the player name does not:

* Check the client console for errors.
* Verify the resource is running the correct version.
* Restart the resource.
* Have the affected player reconnect to the server.

***

### PMA-Voice Works But The Indicator Does Not

If voice communication works normally but the Talking Indicator does not respond:

1. Verify PMA-Voice starts before the Talking Indicator.
2. Restart the Talking Indicator.
3. Restart the FiveM client.
4. Check both client and server consoles for errors.
5. Verify that you are running the latest version of both resources.

***

## Resource Order

PMA-Voice should start before the Talking Indicator.

Recommended order:

```cfg
ensure pma-voice
ensure X1S-Talking
```

The Talking Indicator relies on PMA-Voice being available.

***

## Updating The Script

When installing a new version:

1. Stop the Talking Indicator resource.
2. Back up your existing files if you have made configuration changes.
3. Download the latest version.
4. Replace the old resource files.
5. Start the resource again.
6. Test voice communication.
7. Test the Talking Indicator with multiple players.

***

## Installation Complete

The **X1Studios Whos Talking?** is now installed.

Once players begin speaking through PMA-Voice, their server ID and name will automatically appear in the talking list.

The default layout is:

```
------------
Talking:
[ID] NAME
[ID] NAME
------------
```

For support, open a ticket in the official X1Studios Discord.

**X1Studios Discord**

<https://discord.gg/TqcPD9Xee3>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://x1studios.gitbook.io/x1studios-docs/whos-talking/installation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
