> 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/detailed-features.md).

# Detailed Features

Daddy GPS is packed with high-end features designed for competitive and immersive roleplay. Below is a deep dive into the systems that make this tracking tool unique.

***

### 📍 Live Blip System

The heart of the GPS system is its dynamic map tracking.

* **Dynamic Iconography:** The blip icon changes automatically based on your vehicle type (On Foot, Car, Motorcycle, Helicopter, Plane, or Boat).
* **Department Visuals:** Each department has its own custom map color and UI accent, so players can tell units apart at a glance.
* **Heading Indicator:** The blip rotates to show the direction the unit is traveling.
* **Smooth Interpolation:** Blips move smoothly between updates to prevent "teleporting" or "laggy" map icons, even during high-speed chases.
* **Chase Blip:** When a unit runs its siren in an emergency vehicle, its blip switches to a dedicated chase blip.
* **Signal Strength:** Every unit shows signal bars that depend on the distance between you and them.

***

### 🖥️ Sophisticated GPS Interface

The UI is a modern, standalone application built with high-fidelity animations.

#### 🔐 Login & Auth

* **Biometric Login:** Features a custom fingerprint scan animation.
* **Prefilled Profile:** Remembers your last name, callsign, and department for faster deployment.

#### 🏠 Unit Hub

* **Live Directory:** View all connected units with their department, callsign and signal strength.
* **Advanced Navigation:** Search for a unit by name or callsign, or set a waypoint to any unit with one click.
* **Unit Following:** Track a unit, and your map follows its movement until you stop.
* **Tactical View:** Optional visual cone projection for allied units on the tactical map.

#### 📡 Communication Channels

* **Secure Networks:** Switch between private department channels or one global inter-agency network.
* **Unit Counts:** Real-time indicator of how many units are active on each channel.

#### 👤 Profile & Customization

* **On-the-Fly Editing:** Update your callsign and name directly within the app.
* **System Theme & Color:** 8 theme colors, changed live.
* **Display Scale:** Scale the UI from 70% to 150%.
* **Draggable UI:** Position the GPS device anywhere on your screen.
* **Self Blip:** Optionally show your own unit on the map.
* **Language:** Switch between 8 languages inside the app.

***

### 🌊 Water Damage & Glitch System

To prevent unrealistic gameplay, Daddy GPS includes a built-in "Technical Failure" system.

* **Submersion Fail:** If an officer swims or goes underwater while on foot, the GPS takes water damage.
* **Glitch UI:** A broken screen with a glitch animation and `ERR_CODE: H2O_FATAL` blocks usage.
* **Repair Sequence:** Units run a timed repair sequence with status updates before the hardware reconnects.

Turn it off globally with `Config.WaterDamage.Enabled = false`.

***

{% hint style="success" %}
**Every officer decides.** Theme color, display scale, device position, self blip and blip sizes are saved on the player's own client, so nobody has to ask the server owner to change them.
{% 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-gps/detailed-features.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.