# Configuration

The `config.yml` file is the heart of QuantumPunish. It allows you to automate moderation and customize the plugin's behavior.

#### 📊 Database & Cleanup

* **`cleanup-days`**: To prevent the database from becoming too large, set the number of days after which expired punishments are deleted.
  * *Example:* `30` means any record older than 30 days that has expired will be wiped. Set to `0` to keep history forever.

#### 🆔 ID System

Enable this to use shortcuts for common reasons.

* If enabled, you can run `/ban <player> 1` instead of typing the whole reason. The plugin will automatically use "Hacking/Cheating".

#### 🤖 Auto Punishments

Create a progression of punishments based on warning points.

* **`points`**: The threshold to trigger the action.
* **`action`**: `MUTE`, `KICK`, or `BAN`.
* **`duration`**: Set a timed duration (e.g., `1h`, `1d`) or `0` for permanent.

#### 🤬 Chat Filter Settings

* **`action`**:
  * `REPLACE`: Swaps bad words with `****`.
  * `BLOCK`: Prevents the message from being sent entirely.
  * `WARN`: Allows the message but automatically assigns warning points.
* **`detect-evasion`**: Intelligent engine that catches bypassed words (e.g., `@pples` instead of `apples`).
* **`max-repeated-letters`**: Limits spammy letters (e.g., `haaaaack` is treated as `haack`).

#### 🔗 Discord Webhook

* **`url`**: Your unique Discord Webhook URL.
* **`enabled`**: Set to `true` to start receiving real-time logs in Discord.

***


---

# 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://quantum-14.gitbook.io/quantum-docs/free-product/quantumpunish/configuration.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.