Bedrock Player Managment for Floodgate (Geyser)

This is a major update. · Backward compatibility has been implemented for Minecraft servers 1.8.8, 1.9.x, 1.10.x, 1.11.x, 1.12.x, 1.13.x, 1.14.x and 1.15.x. · Complete Vault support has been added to the permission module, so all permission plugins can be used that are supported by the Vault API. For example: Permissions 3, bPermissions, PEX, GroupManager, PermissionsBukkit, zPermission, SimplyPerms, Privileges, DroxPerms, xPerms – for more information, visit the Vault resource page. · Vault permissions can be applied per world or globally. · Command execution (upon joining) for all players can now be performed in solo mode. Floodgate is a soft dependency now. If 'commands.java.enabled', 'commands.bedrock.enabled' and 'permissions.enabled' have been deactivated with 'false', commands can be executed for all players without Floodgate. This update has been tested since server version 1.8.8 via Java and Bedrock client with Vault and Luckperms in all major server versions. It should work without any issues. If you still discover a bug, please report via issue tracker or via Discord. New config options have been implemented All defaults for new options are designed to not damage old configurations. You can add the new options to your configuration or generate a new one if you want to customize them. New default config.yml Code (YAML): ### ofunnys BedrockPlayerManager for Floodgate ### # This plugin is listening on the PlayerJoinEvent what gets triggered when a player joins a server. # Basic commands can normally be applied directly without delay. Some commands (like Teleport) # have to be processed after the player finally joined, therefore I give you the option to delay the execution # in server ticks. If 0 delay cause proplems with some commands you can set it to 1 or 2 ticks for example. execution_delay : 1 # # Command modul. commands: java : # If true -> the following commands will be executed when a java player joins. enabled : false # Execute commands as server/console. # The placeholder {player} will be replaced with the joining players name. # # One command per line or {} if empty # Example: # - say hi {player} # - say How are you today? # - give {player} dirt 1 server : { } # Execute commands as the joining player. # The placeholder {player} will be replaced with the joining players name. player : { } # bedrock : # If true -> the following commands will be executed when a bedrock player joins. enabled : false # Execute commands as server/console. # The placeholder {player} will be replaced with the joining players name. # # One command per line or {} if empty # Example: # - say hi {player} # - say How are you today? # - give {player} dirt 1 server : { } # Execute commands as the joining player. # The placeholder {player} will be replaced with the joining players name. player : { } # all : # If true -> the following commands will be executed for all player joins unrelated to the client enabled : false # Execute commands as server/console. # The placeholder {player} will be replaced with the joining players name. # # One command per line or {} if empty # Example: # - say hi {player} # - say How are you today? # - give {player} dirt 1 server : { } # Execute commands as the joining player. # The placeholder {player} will be replaced with the joining players name. player : { } # # Permission modul. permissions : # If true, the following permission group will be added / removed depending on the client version (Bedrock / Java) when a player joins / leaves. enabled : false # Supported permission plugins. # Choose: # plugin: "luckperms" if you use Luckperms or # plugin: "vault" for Vault compatible permission plugins like Permissions 3, bPermissions, PEX, GroupManager, # PermissionsBukkit, zPermission, SimplyPerms, Privileges, DroxPerms, xPerms # You can use the command function for any unsupported permission plugin and apply perms/groups via command. plugin : "luckperms" # # Vault specific settings # Leave the following option set to "false" if your permission plugin supports global groups (recommended if available). # Check carefully that your plugin really supports global groups and use them if available. # >> In case of 'plugin: Luckperms' this option has no affect, it will always use global groups. << vault : # If your permission plugin supports per world permission groups only, activate "per_world_permissions" by setting it to true. per_world_permissions : false # You can define a list of worlds in which the groups will be apllied or leave it empty for all worlds on your server. # WARNING: the following 'bedrock_group_name' must exist as permission group for each defined world otherwise # you might get an error each time the plugin trys to set or remove this group. So create it in your permission plugin first! worlds : { } # # The permission group to add for bedrock users or to remove for java users. # If a user joins via Floodgate, the group gets applied otherwise removed (if previously inherited by the joining / leaving user). # Make sure to add the group in Luckperms first. I check if the group exist before it will be applied! bedrock_group_name : "bedrock_user" # # Activate advanced debug messages. debug : false # # Do not touch the following lines! version : 1

The exception in the Luckperms module has been fixed what occured in the rare case if the message service got deactivated in the Luckperms plugin configuration. This bug did not cause any malfunction but it spammed a warning into the console whenever a player joined and the Luckperms module has been activated.

New option added to delay execution of commands and group assignment in x server ticks! Code (YAML): execution_delay : 1 The default value is 1. You may add it to your config if you wanna adjust it. This plugin is listening on the PlayerJoinEvent what gets triggered when a player joins the server. Basic commands can normally be applied directly without delay. Some commands (like Teleport) have to be processed after the player joined, therefore I give you the option to delay the execution in server ticks. If zero delay cause problems with some commands you can set it to 1 or 2 ticks for example. Complete default config Code (YAML): ### ofunnys BedrockPlayerManager for Floodgate ### # This plugin is listening on the PlayerJoinEvent what gets triggered when a player joins a server. # Basic commands can normally be applied directly without delay. Some commands (like Teleport) # have to be processed after the player finally joined, therefore I give you the option to delay the execution # in server ticks. If 0 delay cause proplems with some commands you can set it to 1 or 2 ticks for example. execution_delay : 1 # # Command modul. commands: java : # If true -> the following commands will be executed when a java player joins. enabled : false # Execute commands as server/console. # The placeholder {player} will be replaced with the joining players name. # # One command per line or {} if empty # Example: # - say hi {player} # - say How are you today? # - give {player} dirt 1 server : { } # Execute commands as the joining player. # The placeholder {player} will be replaced with the joining players name. player : { } bedrock : # If true -> the following commands will be executed when a bedrock player joins. enabled : false # Execute commands as server/console. # The placeholder {player} will be replaced with the joining players name. # # One command per line or {} if empty # Example: # - say hi {player} # - say How are you today? # - give {player} dirt 1 server : { } # Execute commands as the joining player. # The placeholder {player} will be replaced with the joining players name. player : { } all : # If true -> the following commands will be executed for all player joins unrelated to the client enabled : false # Execute commands as server/console. # The placeholder {player} will be replaced with the joining players name. # # One command per line or {} if empty # Example: # - say hi {player} # - say How are you today? # - give {player} dirt 1 server : { } # Execute commands as the joining player. # The placeholder {player} will be replaced with the joining players name. player : { } # Permission modul. permissions : # If true, the following permission group will be added / removed depending on the client version (Bedrock / Java) when a player joins / leaves. enabled : false # Supported permission plugin. # Only luckperms is supported at the moment. The option "plugin" has no effect at the moment. More permission plugins may follow in the future. # You can use the command function for any unsupported permission plugin and apply perms/groups via command. plugin : "luckperms" # The permission group to add for bedrock users or to remove for java users. # If a user joins via Floodgate, the group gets applied otherwise removed (if previously inherited by the joining / leaving user). # Make sure to add the group in Luckperms first. I check if the group exist before it will be applied! bedrock_group_name : "bedrock_user" # Activate advanced debug messages. debug : false # Do not touch the following lines! version : 1