> For the complete documentation index, see [llms.txt](https://fivem.lvsoft.com.ar/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fivem.lvsoft.com.ar/qb-esx/lvs-playerlist/installation.md).

# Installation

## Step 1. Download lvs\_playerlist package

Download the lvs\_playerlist package from your keymaster. \
The best way to place the downloaded files is by creating a folder `[lvs]` in `resources`, where you can put all the scripts related to this <mark style="color:blue;">**LVS Store.**</mark>

***

## Step 2. Install dependencies <a href="#install-dependencies" id="install-dependencies"></a>

Install the dependencies if they are not installed.

| ox\_lib     | <https://github.com/overextended/ox_lib> |
| ----------- | ---------------------------------------- |
| lvs\_bridge | Included in the package                  |

***

## Step 3. Config <a href="#step-5" id="step-5"></a>

Now configure and translate your resources.

<details>

<summary>Config files</summary>

`config/config.lua`\
`config/translation.lua`\
`server/sv_config.lua`

</details>

{% hint style="warning" %}
**Important**: don't forget to edit the `server/sv_config.lua` file. In it, you must enter the details of the Discord or Steam keys according to the identification method you have on your server.
{% endhint %}

***

## Step 4. Start the script (server.cfg) <a href="#add-it-to-your-server" id="add-it-to-your-server"></a>

In the `server.cfg` file, you need to start or ensure the scripts

```editorconfig
ensure qb-core
# ... some others
# lvs_bridge should go right after ensure the framework resource and before any other LVS scripts
start lvs_bridge
# ... some others
start lvs_playerlist

```

***


---

# 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://fivem.lvsoft.com.ar/qb-esx/lvs-playerlist/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.