# Fixed Ban Reason

You can configure custom ban reasons. This will enforce the staff members to use your reasons.

{% hint style="info" %}
The entire **reasons** section is optional and **not** present in the default config
{% endhint %}

### Configuration

```yaml
ban-module:
  enabled: true
  permban-template: default
  tempban-template: default
  reasons: 
    - name: GRIEFING
      reason: No griefing allowed on this server
    - name: BULLYING
      reason: bullying will not be tolerated
      template: bullying
    - name: CURSING
      reason: Consistent cursing. Temporarily banned.
      template: cursing
      ban-type: TEMP_BAN
```

In the above config we have defined 3 ban reasons. GRIEFING, BULLYING and CURSING.\
\
Every reason configuration must have at least a `name` and a `reason` . Optionally you can also define a `template` . When you define a template you overwrite any other configured template. However staff members can still [provide a template in their command](/features/banning/templates.md#overwriting-the-default-template).&#x20;

By default ban reasons are applicable to both permanent and temporary ban. You can however define another optional configuration option`ban-type` . The ban type can be configured with **TEMP\_BAN** or  **PERM\_BAN.** When the type is configured, this ban reason will only apply for these types of bans. \
\
If no ban reasons are configured, the staff members can provide a custom reason. As soon as at least one ban reason is configured they are obligated to use ban reasons and can no longer fill in a custom message


---

# 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://wiki.staffplusplus.org/features/banning/fixed-ban-reason.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.
