RoyaleProtectionBlocks v1.18.0 Alpha R

Additions

• Added new filter on the admin protection list inventory, which can be used to filter protections by their protection block.
• Added support to CoreProtect, which can be enabled through the Config.yml file.
• Added support to PlaceholderAPI on inventory titles.

Fixes

• Fixed issue with new SQL field for invitations, which wasn't setting a default value.
• Added missing fields which weren't exported when using /pb files export blocks.

Additions

• Added new Discord message system which allows the customization of Discord messages which are available on the plugin. You'll have to move the configuration from the Config.yml file to the Discord.yml file.

Changes

• Enabled /pb settings command, which was unavailable from previous developments.

Fixes

• Fixed issue with message customization, which was sharing improperly the same object in memory, causing other protections to have the same message setting.
• Fixed issue with protections being removed, which previously had configured settings, as it caused problems with the settings table not removing the data from the removed protection.

Fixes

• Included missing checking on message controller, which wasn't considering the fact that the messages setting on protections may be disabled on the configuration.

Additions

• Added new menu in the protections, Settings, which allows to modify the settings of the prections.
• Added new setting Greeting/Farewell messages, which replaces the actual message system from the plugin and WorldGuard with a new one which can be customized per group, and allows to use multiple output types: Chat, Action bar, Title or Boss bar.
• Added new setting TNT, which allows players to define if TNT can explode or not. This only affects to TNT and minecart TNTs. TNTs can still explode if the TNT is primed outside the protection, but won't break blocks from the protection.

Changes

• Included new checking on the PvP setting which will consider the current PvP status of the player from third party plugins. This will prevent players from having vulnerability if they are already on a PvP, managed by PvPManager or others.

Fixes

• Fixed issue with PvPManager due last update, which renamed certain packages and classes, and the plugin was unable to work properly. This forces to use the last PvPManager update to work.
• Fixed issue with the PvP setting, which wasn't treating properly the status of each player, and would allow PvP on certain cases.

Hello everyone,

The BBB account was blocked due some new policies, but after some chatting, I was able to get the account again. Now I'll be able to upload the updates on BBB together with Spigot.

Fixes

• Fixed issue with blocks duplication, where, on laggy servers or with lot of protections, protections were able to be deleted twice.
• Fixed issue with blocks duplication (vanilla items), where fast tools were able to duplicate blocks using the small amount of time where the block was visible again.
• Fixed issue with guard system, where the values in the guard system weren't loaded, leaving the protection unguarded. Values for the guard system on specific protections may have been resetted due this issue. If you've used the guard system, check protections that were guarded to see if they are still guarded or not.
• Fixed issue where players were able to place protections over other protections due missing checkings after the API implementation.
• Fixed issue on players' search list inventory, where staff in vanish were shown on the inventory. Now they aren't shown based on if the player can or not see, value returned by the internal API from Spigot.

Additions

• Added compatibility for player placeholders on inventory_protections_manage.yml, which will show the information of the user looking through the inventory.
• Now it's possible to leave single-line lore fragments from inventory_protectionblocks_list.yml empty, the plugin will ignore this lines.

Fixes

• Fixed issue with loverpa checkings, which was by default disabled due API changes, leading to protections being over other protections or WorldGuard regions.
• Fixed issue with items lore on inventory_protectionblocks_shop.yml inventory, showing the same lore twice if the block had an empty lore.
• Now showing the actual command path of the /pb setspawn command in the startup message which tells you that there's no spawn defined on the plugin.

Additions

• Updated Config.yml file which contains comments for the new sections.
• Added guard system, available through the /pb admin guard command, which allows to guard protections to prevent them from being purged temporary (or permanently) by purges.
• Added /pb admin staffmode command, which is used to bypass certain limitations of the plugin without using a permissions plugin. (Due the lack of time, checking are being moved to this system partially).
• Added compatibility with standard internal placeholders on inventory_protections_manage.yml file.

Changes

• Modified plugin version nomenclature, standing now for {major}.{minor}.{fix} as no huge updates are currently expected to happen.
• Switched value representation on Blocks.yml files for their radius, switching to diamater. Now coordinates will reference the diameter of the blocks and not their radius (2x2x2 is now 5x5x5 for example). This does not modify the current data on the Blocks.yml file, to keep your values updated, you'll have to export the blocks.
  
  This new changes modifies lot of things on the system. This update has been tested on multiple ways and hasn't been an issue. Specific configurations or the quantity of modified and created protections may cause other kind of issues which are unexpected. It's recommended to create a new backup just in case. Any issue can be reported and we'll work on their fixes.
  
  
• Modified internal system to be adapted for the new API-Based services, which are available through RoyaleProtectionBlocksAPI class. A new GitHub with its documentation will come soon.

Fixes

• Fixed issue with recipes, which caused issues with recipes that had some empty slots, like the first or second one, on the upper and lower row.