> 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-pausemenu/changelog.md).

# Changelog

## 0.0.1

Public beta.

* Esc, P and pad Start open a custom pause menu instead of GTA's, with the player card, server time and online count
* Five menu styles: Signature, Classic, Vice, Tactical and Luxe
* GTA's own map with a places list, real blip names and icons, waypoint and route
* Every GTA setting in GTA's own order in one searchable screen; graphics applied through GTA's own settings screen; the server's key bindings listed with their resource
* Stats per character: skills, career, crime, vehicles, money and combat
* Photo mode, rules screen and a leave confirmation
* Qbox, QBCore and ESX through daddy\_lib; English and Turkish


---

# 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-pausemenu/changelog.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.
