ВЕРСИИ (5)

## Cleaner Hijacking Removed PvP mode hijacking of the original WG's protection listener. Overall, this should improve stability of non-default `pvpmode` setting. The unfortunate part, the `deny-message` message is no longer configurable through WGExtender, so consider either setting up the `deny-message` flag on a `__global__` region, or using a translation WG plugin/fork of your liking. Added an option for less hijacked `/rg claim` command flow - it disables translatability too, but should be more stable with the future WG updates. Disabled by default for the time being, feel free to test it. Also made hijacked flow more inline with the current WG behavior. `/rg claim` now supports the polygonal selection type - as WG intended. ## `/wgex` Command Migrated commands to Mojang's Brigadier API, which should improve the usage experience. I've also added permission checks for each of plugin's subcommand - `wgextender.admin.<subcommand>`, e.g. `wgextender.admin.update` for `/wgex update`. ## Update Checker Implemented update checker. You can disable it in the config at `updater.enabled`. The notifications are shown to the admins with `wgextender.admin` permission. ## Messages Major messages updates: - `claim.too-many`: Now has the `{count}` and `{limit}` placeholders - `claim.too-big`: Replaced `{maxVolume}` placeholder with `{limit}` - `claim.only-cuboid` > `claim.wrong-shape`: Remade the message to better reflect the behavior. For the new messages, see the [diff](https://github.com/imDaniX/WGExtender/compare/v3.5.0...v3.6.0#diff-4d9b55e143253b0c5ad748d7f1c85b4c9afe466a8c6ba5e4111688898df3b652). ## Metrics Integration Added bStats metrics integration. As always with bStats, you can opt-out in `./plugins/bStats/config.yml` config file. Generally speaking, I'm just collecting data on which features of the plugin are used.

## LuckPerms Integrating LuckPerms with two new custom contexts: - **`wgex:context-helper`**: A context that works alongside the `context-helper` WG string flag, allowing you to specify additional region information (also works with PAPI `%wgex_context_helper%`). - **`wgex:in-region`** - A context that simply marks whether a player is currently inside any non-`__global__` region > E.g. if you want to disallow /tp command on a PvP arena, add `context-helper` flag with `deny-tp` value, and negate the permission using `wgex:context-helper=deny-tp` context ## Restrict Commands Refactored and optimized restrict commands feature functionality. Added two new options under the `restrictcommands` config section: - `aliased-search`: Match commands by their aliases, e.g. `tp` also matches `teleport`; default `true`. - `prefixed-search`: Match commands that are a prefix of the input, split by spaces, e.g. `home bed` matches `home bed here`; default `true`.

Plugin now supports multiple languages using `messages/messages_<locale>.yml` files. Configurable via `messages.locale` config option, like so: ```yaml messages: locale: ru ``` The default/supported ones: `en` for English and `ru` for Russian. The default is `en`.

**Notable changes**: - PlaceholderAPI support with block limit caching: - `%wgextender_blocklimit_refresh%` - refresh and get the current blocks limit - `%wgextender_blocklimit_cached%` - get cached blocks limit - `%wgextender_blocklimit_calc%` - calculate blocks limit without caching it - `%wgextender_blocklimit_group_<group>%` - get configured blocks limit - PAPI introduction comes with commands to control blocks limits cache: - `/wgex limits refresh <player>` - refresh player's blocks limit (use with `-s` at the end to make no messages) - `/wgex limits clear` - fully clear the cache > Caches are updated upon claiming a region. If you don't use the introduced placeholder, you don't need to care about it. - Allowed explosion triggers are now configurable in `regionprotect.explosion.source-detection`, see the default config - Vault is no longer required - using the same groups methods, as WG/WE.