# Features

### What makes InHouseQueue unique and different from other bots out there?

* **Seasons System**: Manage competitive seasons with leaderboards, stats, and automated notifications. Perfect for structured, long-term competition.
* **Captain Queue**: Introduces strategic gameplay by allowing captains to draft teams, with multiple selection modes like highest MMR, randomized captains, or admin-decided.
* **MMR Decay System**: Keeps rankings fair by reducing inactive players' MMR over time, with customizable decay intervals, amounts, and notifications.
* **Suspend Players**: Temporarily or permanently ban disruptive players from queues, ensuring a fair and enjoyable environment.
* **Map Selection**: Choose how maps are picked each game with three modes: Random for quick games, Vote to let all players have a say, or Ban for strategic pick-and-ban between team representatives.
* **Per-Queue Customization**: Customize colors, banners, and game modes independently for each queue channel.
* **Admin Logs**: Keep track of important events with private log channels for server owners and moderators.
* **Custom Leaderboards**: Support for global and unique leaderboards, giving flexibility in how stats are tracked and displayed.
* **Webhook Integration**: Send leaderboard data to a Webhook URL after each game, enabling advanced integrations with your own website or API for custom leaderboards and analytics.
* **Website Queue**: Join, leave, and ready up in queues directly from the InHouseQueue website. Everything stays in sync with Discord in real time.

Read on to find out more!


---

# Agent Instructions: 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://docs.inhousequeue.xyz/docs/features.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.
