# New Features:
<br>
**Added new variable "plugin=pluginname" to add all commands from a plugin**
> **Warning:** This only works on **standalone Spigot (+Fork)** servers!
>
> You can now add all commands from a plugin by simply adding `plugin=<pluginname>`
> to your storage.yml.
>
> You can then use the negation operator (`!`) to block a few of these commands.
> Here an example:
```yaml
# Adds all Essentials commands and blocks off these few commands.
# It does not matter if the plugin name is written with big or small letters.
- "plugin=essentials"
- "!about"
- "!anvil"
```
<br>
**Added new option for block-namespace-commands**
> A new option called ``always-block-command`` has been added.
>
> It's enabled by default and basically means that commands are still not executable,
> even though the cancellation for command executions has been disabled inside
> ``cancel-blocked-commands`` for example.
```yaml
block-namespace-commands:
enabled: false
# Basically blocks the command execution no matter if
# 'cancel-blocked-commands' is enabled or not.
always-block-command: true
```
<br>
**Added new option "allow-group-overruling"**
> Allows to block commands inside a PAT group, if the commands were
> considered **allowed** according to the ``global`` section before.
>
> Blocking commands inside a PAT group works by using the negation
> operator (`!`) afront of a command.
```yaml
# (!) Warning:
# Enabling this could lead to performance issues depending on
# the amount of players and commands. (> 1100)
#
# This allows PAT groups to block commands, which have been allowed
# inside the global section. This can be achieved by negating commands
# inside a PAT group.
allow-group-overruling: false
```
<br>
**Added negation of PAT group commands!** _(Basically blocking commands via PAT groups)_
> Allows to block commands inside a PAT group using the negation operator (`!`)
> afront of a command.
>
> **Warning**: It only blocks the command, if it's not been allowed
> inside the ``global`` section before. But this can be bypassed by enabling
> the new option **allow-group-overruling**. (above)
<br> <br>
# New Commands:
<br>
**Command to convert another plugin/command hider plugin into PAT**
> **Usage:** ``/(b)pat convert (plugin)``
> **Description:**
> Converts the config.yml from another "plugin/command hider" plugin into PAT's format of the storage.yml.
> For example, converting the ``config.yml`` of AdvancedPlHider into a PAT storage.yml.
> This should simplify the process of switching to PAT. ^^
>
> **Example:**
> ``/pat convert AdvancedPlHider``
>
> **Supported plugins:**
> ``AdvancedPlHide, CommandWhitelist, PlHide(Pro), PluginHiderPlus``
<br>
**Command to extract ALL commands from a plugin**
> **Usage:** ``/pat extract (plugin) <use-colon>`` or ``/pat extract (plugin) <group> <use-colon>``
> **Description:**
> Extracts all commands from a plugin and writes them directly into the storage.yml.
>
> **Parts explanation:**
> ``<use-colon>`` = Includes ``plugin:command`` commands. (e.g: ``essentials:feed``)
> ``<group>`` = PAT group if you want to extract the commands in there.
>
> **Example:**
> ``/pat extract essentials true``
> = Writes all Essentials commands in the global section of PAT with and without colon commands.
> = So it includes both ``essentials:feed`` and ``feed`` etc.
>
> ``/pat extract fastasyncworldedit builder false``
> = Writes all FAWE commands into the PAT group called ``builder`` without any colon commands.
> = So it only includes commands such as ``//wand`` but not ``/fastasyncworldedit:/wand``
>
<br> <br>
# Fixes:
- Improved "missing-parts" warning
- Fixed TOKEN not updating after PAT reload
- Fixed auto-config-updater option
- Fixed wrong size of PAT group commands
- Fixed potential error message for proxies
- Fixed issue filtering colon commands with PAT in BLACKLIST mode
- Fixed in-code wrong data type for "load-from-env.name"
- Fixed tab-completion issue with Bungeecord commands while having bypass permissions (sub-arguments)
- Fixed tab-completion issue with Bungeecord commands on 1.8.8 servers (player-names and commands)
- Fixed wrong filtering process of custom-plugins & custom-version commands for legacy servers
- Fixed wrong tab-completion of available commands (``/(b)pat add <...>``)
- Fixed wrong last-sync time in post-debug
- Disabled custom-plugins and custom-version feature on backend servers if ``handle-through-proxy`` is enabled
- Fixed missing server-name using bpat-serv commands with an unknown group-name
Optional dependencies
PlaceholderAPI
Any compatible version
LuckPerms
Any compatible version
PAPIProxyBridge
Any compatible version
Developer information
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle.
maven { name = "Modrinth"; url = "https://api.modrinth.com/maven" }