> For the complete documentation index, see [llms.txt](https://hirzigamingyt.gitbook.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hirzigamingyt.gitbook.io/installations/installing-the-pack.md).

# Installing the pack

After configuring the config file, compress the `scripts folder`, `manifest.json`, and `pack_icon.png` into a zip file. Rename the zip file to `pack.mcpack`, then click the file and choose Minecraft to open it.

If you have already added this addon to a world and want to change the config, you need to update the config in the world's behavior pack folder. Alternatively, you can delete the existing pack folder and copy the new one with the updated configuration.

For more information about world behavior packs location:

{% content-ref url="/pages/nbeaa7Qe4hDKSuFqXRqe" %}
[Configuration File](/installations/configuration-file.md)
{% endcontent-ref %}


---

# 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://hirzigamingyt.gitbook.io/installations/installing-the-pack.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.