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

# Configuration & Logic

Daddy GPS is designed to be highly flexible. While the core UI is optimized, the server and client logic are partially open (cl\_editable.lua / sv\_editable.lua) to allow for deep integration with your server.

***

### ⚙️ Main Configuration

The `config.lua` file is the central hub for customizing the GPS experience.

* **Unlimited Departments:** Add any number of departments (LSPD, BCSO, SAHP, etc.) with custom labels, map colors, and hex-based UI accents.
* **Job Whitelisting:** Use `Config.AllowedJobs` to map your server's job grades directly to departments.
* **Item Requirement:** Toggle whether the GPS requires a specific item (like `police_gps`) to be in the player's inventory.
* **Water Damage:** Enable or disable the `H2O_FATAL` glitch system globally.
* **Channel Mode:** Switch between "Private" (department only) or "Inter-agency" (everyone sees everyone) modes.

***

### 🔓 Open Logic (Editable Files)

We believe in full control. The following files are **fully unencrypted**:

#### `cl_editable.lua`

* Custom logic for fetching player names and callsigns.
* Integration with external radio scripts (e.g., pma-voice).
* Custom logic for when the GPS window should be hidden (during cinematics, death, etc.).

#### `sv_editable.lua`

* Server-side validation for department data.
* Integration with database saving (if you wish to store permanent callsigns outside of KVP).
* Whitelist and permission checks.

***

### 🌍 Localization (Multi-Language)

Daddy GPS comes pre-translated into **8 languages**. You can easily add your own or modify existing strings in the `locales/` folder:

* English, Turkish, French, German, Spanish, Portuguese, Italian, and Polish.

***

> \[!IMPORTANT] **No Encryption:** Our logic files are 100% open. We do not use Tebex encryption on configuration or integration files, allowing you to tailor the script to your specific framework needs.