# Head Locations

Head locations are stored inside each hunt's YAML file, under the `locations` section. When you place a head in the world, it is automatically saved in the corresponding hunt file (e.g., `hunts/default.yml`).

There is no separate `locations.yml` file — each hunt manages its own heads.

## Example

In `hunts/default.yml`:

```yaml
id: default
displayName: "Default"
state: ACTIVE
# ... hunt config ...

locations:
  4848fbff-3002-46e6-98c2-14145ccb4ecb:
    name: ''
    location:
      x: -12
      y: 34
      z: 56
      world: default
    rewards:
      - type: MESSAGE
        value: '&aThis is a test message'
      - type: COMMAND
        value: give %player% gold_ingot
      - type: BROADCAST
        value: '&e%player% &afound one head!'
    orderIndex: 1
    hitCount: 12
```

## Properties

Each head has a UUID as its key identifier.

| Property       | Description                                                                            | Auto-generated |
| -------------- | -------------------------------------------------------------------------------------- | -------------- |
| **name**       | Display name in GUIs and chat. Supports hex colors. Rename with `/hb rename`           | No             |
| **location**   | X, Y, Z coordinates and world                                                          | Yes            |
| **rewards**    | Per-head rewards (MESSAGE, COMMAND, BROADCAST). Configurable via `/hb options rewards` | No             |
| **orderIndex** | Click order index, defined with `/hb options`                                          | Yes            |
| **hitCount**   | Maximum clicks allowed on the head (global), defined with `/hb options`                | Yes            |

{% hint style="warning" %}
Properties marked as auto-generated should not be changed manually unless you know what you're doing.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://aerwyn81.gitbook.io/headblocks/headblocks3/other-files/locations.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.