> For the complete documentation index, see [llms.txt](https://5scripts-1.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://5scripts-1.gitbook.io/docs/assets/5s_hitmarker.md).

# 5s\_hitmarker

### 📖 Documentation Sections

* **🖥️** [**Install**](/docs/assets/5s_hitmarker/install.md) - File installation and server.cfg setup
* **🔧** [**Configuration**](/docs/assets/5s_hitmarker/config.md) - Colors, scaling, fonts and sound packs
* **📝** [**Editable Files**](https://gitlab.d2qube.com/5scripts/5s_docs/-/blob/main/assets/5s_hitmarker/editable.md) - Files you can safely modify
* **💻** [**Available exports**](/docs/assets/5s_hitmarker/exports.md) - Exports to use in your code
* **❓** [**Frequently asked questions**](/docs/assets/5s_hitmarker/faq.md) - Answers to questions asked frequently

### 🚀 Quick Start

1. Place the script in your `resources` folder
2. Add `ensure 5s_hitmarker` to your server.cfg
3. Configure dependencies: `ox_lib`, `5s_lib`

### 📦 Dependencies

* **ox\_lib** (required)
* **5s\_lib** (required)

### ✨ Features

* Color-coded markers based on remaining health, armor, kills and headshots
* Two marker styles: floating 3D damage numbers **or** a 2D crosshair (X) marker
* Distance-based scaling and fade-out for the 3D numbers
* Multiple built-in sound packs (Rust, CS2, Casual, Minecraft) - fully extendable
* In-game player menu (`/hitmarker`) with persistent per-player settings
* Export / import settings to share builds between players
* Standalone - no framework required, runs purely client-side


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://5scripts-1.gitbook.io/docs/assets/5s_hitmarker.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.