BuildSystem [1.8-1.21]

• Add permissions to each world type creation
  » Allows server owners to restrict which world types can be created
  » Permissions can be found here
  
• Allow admins to bypass a world's permission
  » Use the admin permission: buildsystem.admin

• Fix NoSuchMethodError thrown in legacy versions

+ Don't use StringUtils from apache commons lang3
+ Switch from Spigot 1.19 to 1.19.1 as API version

+ Fix "Double Stone Slab" block being placed incorrectly (Minecraft 1.14+)
+ Show archived private worlds in world archive

+ Added piston head block to /blocks
+ When editing gamerules in a world (/worlds edit), the next page button should now work as intended in versions <1.13

+ Fix updater showing incorrect version

+ Add support for Minecraft 1.19

+ Bug fixes:
» Don't import a world twice if already existent (/worlds importAll)

+ Default world permissions
» Added 2 new config options: world.default.permission.public and world.default.permission.public
» Each option sets the default permission the respected world type will have when created
» Use %world% as a placeholder for the world's name

+ Restrict commands to world creator
» All commands defaults to .self when no suffix (.self, .other) is provided. For example: buildsystem.day = buildsystem.day.self
» With the permission suffix .self, a player can only modify worlds that belong to the player (player is creator)
» With the permission suffix .other, a player can only modify worlds that don't belong to the player (player is not creator)

+ More permission checks when using /worlds edit
» Each task found in /worlds edit now has an extra sub-permission to restrict tasks to certain players.
» A list of all permissions can be found here: https://buildsystem.eintosti.com/worlds/edit/

+ Correctly allow multiple private worlds to be created

+ Fixes a bug where creators could not add builders to their world with /worlds addBuilder

+ From now on, only the creator of a world can delete it (or players with the admin permission: buildsystem.admin)

+ Players are no longer limited to one private world. Use the permission buildsystem.create.private.<amount> to the maximum amount a player can create