ВЕРСИИ (5)

### Added - Tab completion on Spigot, BungeeCord and Velocity: online players, and the IDs from ids.yml for /ban and /mute. Only IDs the sender is allowed to use are suggested. - Tab completion for /bansystem subcommands, IDs and punishment types. ### Fixed - Players with bansys.ban.bypass (e.g. operators with all permissions) were saved as banned but never kicked. The ban is now refused with "This player cannot be banned!". - Player names are no longer case-sensitive on BungeeCord/Velocity and for offline players on Spigot. - IDs from ids.yml are no longer case-sensitive. - New message keys are added to existing messages files automatically. ### Untested This is a beta: the changes are built and unit-tested, but not yet tested in-game.

### Added - Discord webhook. Every ban, mute, kick, unban and unmute can be posted to a Discord channel as an embed with the target, the staff member, the reason and, for IDs, the level. Set `discord-webhook.enabled` and `url` in `config.yml`; `actions` limits it to e.g. `[BAN, MUTE]`. Sending happens off the server thread, a dead webhook only costs a console line. - German messages. `messages_german.yml` ships with the plugin, `language: german` uses it. ### Changed - First stable release since 1.1. Servers on the default `release` update channel now get the 1.2 fixes as well. Existing servers: the new `discord-webhook` section is not added to an existing `config.yml` automatically. Copy it from the default config if you want it.

- The backend plugin runs on Folia. Kicks, messages and bans go through the entity and global schedulers there, and bStats stays off on Folia. - The Velocity plugin is described by velocity-plugin.json now, so Velocity reports the real version instead of 1.0.0. - Tested on Folia, Paper, Spigot, Velocity and BungeeCord.

Mutes now hold outside of chat, and `/ban` and `/mute` report the punishment they actually applied. - Muted players can no longer bypass their mute with `/me` or the private message commands. The blocked commands are configurable under `mute-command-blacklist` in `config.yml` and are matched on the command name alone, so `/minecraft:msg` is caught as well. Contributed for Velocity by [NTMFanSolidius](https://codeberg.org/NTMFanSolidius) in [pull request #1](https://codeberg.org/LucasTHCR/EmpireBan/pulls/1) and ported to Spigot and BungeeCord from there. - `/mute <player> <id>` applied the ID's escalation level but always announced a mute: an ID whose level is a ban stored a ban, left the player online and talking, and `/check` then reported a ban nobody had handed out. Both commands now resolve the level first, report the type that was applied and kick when it is a ban. - `/mute` now honours only-admins IDs, which so far only `/ban` checked. - New `punishments.require-id` option: with it on, `/ban` and `/mute` only accept IDs from `ids.yml`. Staff with `bansys.ban.admin` keep free durations unless `punishments.admin-bypass` is turned off.

Initial release.