# Installation

## Step 1. Download package

Download the lvs\_shops package from your portal.&#x20;

* lvs\_shops
* lvs\_bridge
* lvs\_interact
* lvs\_npcdialog

\
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                  |
| lvs\_interact  | Included in the package                  |
| lvs\_npcdialog | Included in the package                  |

{% hint style="info" %}
**lvs\_interact** is optional; you can use a target system such as **ox\_target** or **qb-target**.
{% endhint %}

***

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

Now configure and translate your resources.

* `lvs_shops/config/*.lua`
* `lvs_shops/server/editable.lua`

{% hint style="warning" %}
If this is your first time using **lvs\_bridge** or **lvs\_npcdialog**, you will need to adjust them to your needs in their respective **config.lua** files.
{% 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
start ox_lib
start ox_target
start lvs_bridge
start lvs_lib

start lvs_interact
start lvs_shops
# ensure [lvs]

```

***


---

# Agent Instructions: 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:

```
GET https://fivem.lvsoft.com.ar/qb-esx/lvs-shops/installation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
