# Ban

## config.yml

### Prefix

The prefix is used by default for each message. It can be set in the message files at the beginning of each message. To set it simply write `%prefix%` (placeholder). This will then be replaced by the system with the prefix entered in `config.yml`.

```yaml
prefix: "&7[&6BanSystem&7]&r"
```

### permanent

Here you can enter how many Ban Points a player needs to be permanently banned.

```yaml
# how many points for permanent ban
permanent: 100
```

### autoBanOperatorName

Here you specify the name that will be displayed on the ban screen when the player is banned for having too many ban points.

```yaml
autoBanOperatorName: "AutoBanSystem"
```

### autoBanOperatorUUID

Here you specify the UUID of the [above operator name](#autobanoperatorname).

```yaml
autoBanOperatorUUID: "00000001-0001-0001-0001-000000000001"
```

### autoBanReason

Here you specify the reason when the player is automatically banned from the system.

```yaml
autoBanReason: "auto ban"
```

### banReasons

Here you enter how many ban reasons you want to define. You can change these in the[ message files](https://wiki-en.herrtechniker.eu/bungeesystem/messages-files).

```yaml
banReasons: 6
```

### infoMessageOther

Here you can choose whether the team members of your network should receive a message when a player is banned.

```yaml
infoMessageOther: true
```

### Aliases

You can also define so-called aliases that you can enter instead of /ban. For this you simply add further points under the point `aliases`.

```yaml
aliases: []
```

### Default configuration

```yaml
punishment:
  ban:
    prefix: "&7[&6BanSystem&7]&r"
    # how many points for permanent ban
    permanent: 100
    autoBanOperatorName: "AutoBanSystem"
    autoBanOperatorUUID: "00000001-0001-0001-0001-000000000001"
    autoBanReason: "auto ban"
    banReasons: 6
    infoMessageOther: true
    webhook: false
    aliases: []
```

## Command

### Syntax

```
/ban <player> <id>
```