🔐Permission Prevention

With this features you can keep under control the users who may have operator permissions. You will be able to whitelist the players who may have the operator, certain permissions, or groups.

Enabled

You can decide whether or not to enable this features.

# ------------------
# Permission Prevention Settings
Permission_Prevention:

  enabled: false

Checks

These are the checks that will be made to see if the player belongs to the list or not, and if he has to apply the punishment.

  # The checks that are made to see if the player has unwanted permissions.
  checks:
    chat: true # When he writes in chat.
    commands: true # When writing a command.
    inventory: true # When he clicks the inventory.
    interact: true # When it interacts with a block.
    movement: true # When the player moves.
    join: true # When the player joins.
    left: true # When the player lefts.

Remove Permission

This is the command it will execute to remove permissions from a player.

  # Removes all permissions the player cannot own.
  # You can use the following placeholders:
  # - %player% | (Name of the player whose permission will be removed)
  # - %permission% | (Permission that it will remove)
  remove_permission: 'lp user %player% permission unset %permission%'

Placeholders

You can use the following placeholders:

• %player% | (Name of the player whose permission will be removed)

• %permission% | (Permission that it will remove)

Remove Group

This is the command he goes to execute to remove the player's group.

  # Removes all groups that the player cannot own.
  # You can use the following placeholders:
  # - %player% | (Name of the player whose group will be removed)
  # - %group% | (Group that will remove)
  remove_group: 'lp user %player% parent remove %group%'

Placeholders

You can use the following placeholders:

• %player% | (Name of the player whose group will be removed)

• %group% | (Group that will remove)

Punishment

This is a list of executors, which is activated as soon as the player has to be punished because he has a group, a permission, or is an operator without being on the list.

  # The punishment that the player who will not be enabled in the list will receive.
  # < ? > You can find more information about the executors in the header.
  punishment:
    - '[CONSOLE] ban %player% You are not authorized to receive certain permissions. Contact the administrators for more information.'

The functioning of the punishments is the same as the executors. For more information click HERE.

Global Bypass

This is the global bypass. The players on this list will not suffer any punishment.

  # Players on this list will bypass the permissions, groups, and operator controls.
  global_bypass:

    enabled: true

    # Tip. You can put both the player's name and his UUID.
    bypass_players:
      - 'playerName1'
      - '8667ba71-b85a-4004-af54-457a9734eed7'

Enabled

You can decide whether or not to activate this bypass.

  # Players on this list will bypass the permissions, groups, and operator controls.
  global_bypass:

    enabled: true

Bypass Players

This is the list of players who will be immune to the plugin's punishments.

    # Tip. You can put both the player's name and his UUID.
    bypass_players:
      - 'playerName1'
      - '8667ba71-b85a-4004-af54-457a9734eed7'

You can use both the player's name and their UUID.

Operators

This is what will be checked against the player list located on "bypass_players". If a player not on the list becomes an operator, he will be punished if he performs an action of THESE.

  # Here you can make sure that only enabled players can be operators.
  operators:

    enabled: true

    # Tip. You can put both the player's name and his UUID.
    bypass_players:
      - 'playerName1'
      - '8667ba71-b85a-4004-af54-457a9734eed7'

Enabled

You can decide whether or not to activate this check.

  # Here you can make sure that only enabled players can be operators.
  operators:

    enabled: true

Bypass Players

This is the list of players who can be operators.

    # Tip. You can put both the player's name and his UUID.
    bypass_players:
      - 'playerName1'
      - '8667ba71-b85a-4004-af54-457a9734eed7'

You can use both the player's name and their UUID.

Groups

This is what will be checked against the player list located on "bypass_players". If a player not on the list has a group located on "list", he will be punished if he performs an action of THESE.

  # Here you can make sure that a group can only have the players enabled below.
  groups:

    enabled: true

    list:
      # Example group with players.
      owner:
        # Tip. You can put both the player's name and his UUID.
        bypass_players:
          - 'playerName1'
          - 'playerName2'
      # Second example group with player's name and uuids.
      admin:
        bypass_players:
          - 'playerName1'
          - '8667ba71-b85a-4004-af54-457a9734eed7'

Enabled

You can decide whether or not to activate this check.

  # Here you can make sure that a group can only have the players enabled below.
  groups:

    enabled: true

Group list

This is the structure of the groups.

    list:
      <groupName>:
        bypass_players: <list_players>

Bypass Players

This is the list of players who will be able to have the group below.

    bypass_players:
      - 'playerName1'
      - '8667ba71-b85a-4004-af54-457a9734eed7'

You can use both the player's name and their UUID.

Permissions

This is what will be checked against the player list located on "bypass_players". If a player not on the list has a permission located on "list", he will be punished if he performs an action of THESE.

  # Here you can make sure that only enabled players can have the permissions on the list.
  permissions:

    enabled: true

    # For permissions, instead of the dot, you must enter '_'. If not, it won't work!
    list:
      '*':
        # Tip. You can put both the player's name and his UUID.
        bypass_players:
          - 'playerName1'
          - '8667ba71-b85a-4004-af54-457a9734eed7'
      'plugin_*':
        bypass_players:
          - 'playerName1'
          - '8667ba71-b85a-4004-af54-457a9734eed7'

Enabled

You can decide whether or not to activate this check.

  # Here you can make sure that only enabled players can have the permissions on the list.
  permissions:

    enabled: true

Permission list

This is the structure of the permissions.

    list:
      <permission>:
        bypass_players: <list_players>

You don't have to use dot in the permissions. Just put an underscore in its place. Example: permission.example.1 -> permission_example_1

Bypass Players

This is the list of players who may have the permission below.

    bypass_players:
      - 'playerName1'
      - '8667ba71-b85a-4004-af54-457a9734eed7'

You can use both the player's name and their UUID.