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

# Installation

1. Download the resource from your [Keymaster](https://keymaster.fivem.net) and put the `daddy-lstour` folder in your `resources` folder. Do not rename it.
2. Add the `lstour_board` item to your inventory, see [Board Item](/daddy-studios-docs/scripts/daddy-lstour/items.md).
3. Start it after its dependencies in `server.cfg`:

```cfg
ensure oxmysql
ensure qbx_core          # or qb-core / es_extended
ensure ox_inventory      # your inventory
ensure ox_target         # or qb-target
ensure daddy-lstour
```

4. Restart the server. The database table `daddy_lstour` is created on the first start, the console shows:

```
[daddy-lstour] sql imported: daddy_lstour.sql (1 stmt)
[daddy-lstour] sql verify: table daddy_lstour ok
```

`sql/daddy_lstour.sql` is only needed by hand when your database user is not allowed to create tables.

5. Give yourself the item and use it, the place mode starts. See [Commands & Permissions](/daddy-studios-docs/scripts/daddy-lstour/commands-and-permissions.md) for staff access.

{% hint style="info" %}
Inventory, target and notifications are detected automatically. Force one in `config.lua` (`Config.Inventory`, `Config.Target`, `Config.NotifySystem`) only when the detection picks the wrong resource.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://daddy-studios.gitbook.io/daddy-studios-docs/scripts/daddy-lstour/installation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.