> For the complete documentation index, see [llms.txt](https://ney.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://ney.gitbook.io/docs/betterhud-extension.md).

# BetterHud Extension

BetterHud Extension connects Typewriter dialogues and quest navigation to\
BetterHud popups and pointers.

Before using the extension, familiarize yourself with the plugins it builds\
upon.

### Prerequisites

#### Understanding Typewriter

BetterHud Extension builds upon Typewriter's powerful system. You should understand:

* **Pages**: How Typewriter organizes content into Sequence and Manifest pages
* **Entries**: The building blocks - Events, Actions, and Manifest entries
* **Facts System**: Typewriter's variables that track player data and progression

**Learn Typewriter**: [Typewriter Documentation](https://docs.typewritermc.com/beta/docs/getting-started)

Take time to explore the documentation and understand Typewriter's core mechanics before proceeding.

#### Understanding BetterHud

Since BetterHud Extension operates on top of BetterHud, you need to be comfortable with:

* **Layouts**: Creating and managing HUD layouts
* **Popups**: Displaying temporary HUD elements
* **Placeholders**: Using dynamic text and variables in HUD elements

**Learn BetterHud**: [BetterHud Wiki](https://github.com/toxicity188/BetterHud/wiki)

Make sure you understand how to create layouts, work with popups, use placeholders, and configure basic HUD elements.

***

**Ready to start?** Now that you're familiar with the basics, let's explore what BetterHud Extension can do!


---

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

```
GET https://ney.gitbook.io/docs/betterhud-extension.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.