> 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-hud/changelog.md). # Changelog ## 1.0.0 — first public release ### HUD * Body map style and ECG monitor style * Status row with values: health, armor, hunger, thirst, stamina, oxygen, radiation and voice range * Three status row designs: Urban, Outline and Diamond; each item can be hidden or shown only when low * Injury icons with four severity levels, hunger and thirst warnings * Noise indicator with radius in meters for movement, voice, gunshots, horn, crashes and vehicles * Vehicle display: speed in km/h or mph, gear, RPM, fuel, engine health and seatbelt * Round minimap, compass strip, cinematic bars, optional server logo * Settings menu with live preview, accent color, HUD size and opacity, performance profiles and effects * Edit mode: drag, scale, hide and lock modules with grid and snap, saved per player ### Health system * Built-in tracker: hit zone from the bone, wound type from the weapon, bleeding, fractures from falls and vehicle hits * Optional effects: limp, arm shake, head hit blur, bleeding damage * `ml_healthsystem`, plain GTA health or an external medical script through exports * Clears injuries on revive and heal events of common ambulance scripts and txAdmin ### Setup * Qbox, QBCore, ESX (with `esx_status`) or standalone, detected automatically * pma-voice, SaltyChat, mumble-voip and TokoVOIP voice ranges * ox\_fuel, LegacyFuel, cdn-fuel, ps-fuel and lc\_fuel; qbx\_smallresources or event based seatbelt, or the built-in seatbelt * Client and server exports for visibility, modules, noise and injuries * English and Turkish, language files in `locales/` * Fonts bundled (SIL OFL), no external requests --- # 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-hud/changelog.md?ask=&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.