> 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-gps/installation-guide.md).

# Installation Guide

Installing Daddy GPS is a simple process. Follow these steps to get your unit tracking system live in minutes.

***

### 📥 Downloading the Script

1. **Keymaster:** Log in to your [FiveM Keymaster](https://keymaster.fivem.net/assets).
2. **Asset:** Find `daddy-gps` in your "Granted Assets" list.
3. **Deploy:** Download the latest version and unzip the folder.

***

### 🚀 Setup Steps

#### 1. Resource Placement

Move the `daddy-gps` folder into your server's `resources` directory. Do not rename it, the escrow protection depends on the folder name.

#### 2. Configuration

Open `shared/config.lua` and adjust the following settings to match your server:

* `Config.ItemName` and `Config.RequireItem`: the item players need to open the GPS (see [Opening the GPS](/daddy-studios-docs/scripts/daddy-gps/configuration-and-logic.md#opening-the-gps)).
* `Config.AllowedJobs`: map the names of your police and EMS jobs to a department.
* `Config.Departments`: set your department names, map colors and UI accents.
* `Config.Locale`: the default language.

The framework and inventory are detected automatically, there is nothing to switch.

#### 3. The GPS Item

If `Config.RequireItem` is `true`, create an item named like `Config.ItemName` (default `gps`) in your inventory. The script registers it as a usable item, so using the item opens the GPS. If your inventory does not trigger the framework's usable items (for example `ox_inventory` on some setups), add the export to the item:

```lua
['gps'] = {
    label = 'GPS',
    weight = 200,
    stack = false,
    client = { export = 'daddy-gps.open' },
},
```

#### 4. Server Start

Add the resource to your `server.cfg`, after `ox_lib` and your framework:

```bash
ensure ox_lib
ensure daddy-gps
```

***

### 📋 Requirements

To ensure the best experience, Daddy GPS requires the following:

* **Server Artifacts:** Version 6500 or higher.
* **Dependency:** [`ox_lib`](https://github.com/overextended/ox_lib).
* **Framework:** one of **QBCore**, **Qbox** or **ESX**.
* **Inventory (optional):** `ox_inventory`, `qs-inventory`, `ps-inventory`, `lj-inventory`, `qb-inventory` or `core_inventory`, only needed for the item requirement.

{% hint style="warning" %}
**Performance Tip:** If you are using a custom map with very high texture usage, ensure your players have their "Texture Quality" set to High or Normal to prevent UI flickering on the NUI layer.
{% endhint %}

***

#### 🤝 Support

Encountering issues?

1. Check the [Troubleshooting](/daddy-studios-docs/scripts/daddy-gps/troubleshooting.md) page.
2. Join our [Discord](https://discord.gg/NFKjbN9s2q) and provide your Tebex ID and server console logs.


---

# 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-gps/installation-guide.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.