> For the complete documentation index, see [llms.txt](https://headhunter-1.gitbook.io/headhunter/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://headhunter-1.gitbook.io/headhunter/configurations/head-storage-blocks-config-head-storage-blocks.yml.md).

# Head Storage Blocks Config (head-storage-blocks.yml)

### File Location

```
plugins/HeadHunter/head-storage-blocks.yml
```

***

{% hint style="warning" %}
**Auto-Managed File** - This file is automatically updated by the plugin. Manual edits may be overwritten and can cause block corruption.
{% endhint %}

### How It Works

{% stepper %}
{% step %}

### Block Placement

Admin places a Head Storage Block using <mark style="color:$success;">/hh headstorageblock</mark>
{% endstep %}

{% step %}

### Auto-Save

Plugin saves the block location to this config
{% endstep %}

{% step %}

### Block Usage

Players interact with the block to store heads
{% endstep %}

{% step %}

### Block Removal

When block is broken, location is removed from config
{% endstep %}
{% endstepper %}

***

### File Structure

```yaml
HeadStorageBlocks:
  1: 'world,100,64,200'
  2: 'world_nether,50,70,150'
  3: 'world_the_end,-100,50,300'
```

Format: <mark style="color:$success;">world\_name,x,y,z</mark>

### When To Edit Manually

<details>

<summary><strong>World Name Change</strong></summary>

If you rename a world, you'll need to update the world name in each entry.

</details>

<details>

<summary>Block Recovery</summary>

If a block disappeared but still exists in config, you can manually remove the entry.

</details>

<details>

<summary>Server Migration</summary>

When moving to a new server, you may need to adjust coordinates.

</details>

{% hint style="danger" %}
Making incorrect manual edits can cause blocks to stop working or create ghost blocks. Always backup before editing!
{% 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 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://headhunter-1.gitbook.io/headhunter/configurations/head-storage-blocks-config-head-storage-blocks.yml.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.