> For the complete documentation index, see [llms.txt](https://wiki.chrisgraph.fr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.chrisgraph.fr/how-to-install/behaviorwatch/getting-start.md).

# Getting start

### Requirements

* **Paper/Purpur:** 1.21.4+
* **Java:** 21

### Installation

1. **Install**
   * Drop **BehaviorWatch-\<version>.jar** into /plugins/.
   * Restart the server.
2. **First start**
   * config.yml is created automatically.
   * Data is stored in /plugins/BehaviorWatch/data/ (one file per player).
3. **Permissions**
   * Only staff with behaviorwatch.admin can use commands or GUIs.
   * Optional: give behaviorwatch.ignore to exclude a player from tracking.
4. **Use**
   * Run /behavior to open the main GUI.
   * Click a player to open their profile.
5. **PlaceholderAPI (optional)**
   * If PlaceholderAPI is installed, BehaviorWatch registers its placeholders automatically.
6. **Reload config**
   * Use /behavior reload after editing config.yml.\
     Missing keys are merged without overwriting your values.

### Generated files

```
plugins/BehaviorWatch/
config.yml
data/
bStats/
```

**Details**

* config.yml → main configuration (auto‑created on first start)
* data/ → one YAML file per player (behavior data)
* bStats/ → bStats configuration (can be opted out)


---

# 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://wiki.chrisgraph.fr/how-to-install/behaviorwatch/getting-start.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.