> For the complete documentation index, see [llms.txt](https://alchelvly.gitbook.io/inarius-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://alchelvly.gitbook.io/inarius-documentation/master/how-to-set-up-blizztracker-notifications.md).

# How-to: set up BlizzTracker notifications

Setting up BlizzTracker notifications with Inarius.

Inarius can listen in on the blizztracker feed provided by the will2code API and send notifications to a notifications channel saved in the clients configuration. This setting can be saved with or without a role ID for optional pings.

## Setup

In order to start receiving notifications when a new blizztracker post is made, you need to update the setting in the client configuration. Diablo II & Diablo IV blizz tracker settings have been split into separate settings. Optional is the notification role to ping when a new post is made.

#### Configuration (Blizz Tracker Channel)

```bash
Usage: configuration update d2_blizz_tracker <channel> (role)
Usage: configuration update d4_blizz_tracker <channel> (role)
```

<figure><img src="https://706327511-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUVsjEmpyynDPHE8PUwZm%2Fuploads%2F2JoAuCugu5ZsU8Mhxmb0%2Fconfig_add_blizz_tracker2.png?alt=media&amp;token=f682fc80-42e0-4f91-aa76-511ad9c7226b" alt=""><figcaption><p>Saving a blizztracker notification channel</p></figcaption></figure>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://alchelvly.gitbook.io/inarius-documentation/master/how-to-set-up-blizztracker-notifications.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.