💯Block Custom Commands

Lock the commands individually, setting different messages, titles, etc. ..

Enabled

You can decide whether or not to enable this features.

# ------------------
# Block Custom Commands Settings
Block_Custom_Commands:

  enabled: false

Commands

From here you can configure the commands individually. You can set requirements like in the examples, type permission or via player. If you don't set a requirement like the first example, it will only be executable from the console.

  # This allows you to run an executor for each command.
  # < ? > You can find more information about the executors in the header.
  commands:
    # In this example the command will be blocked for everyone.
    example_Command1:
      command: 'exampleCommand1'
      warning: true
      executors:
        - '[MESSAGE] %prefix%&cYou cannot execute this command!'
        - '[ACTION] &c&l⚠ &7You tried to run the command: &c%command%'
    # In this example, however, it requires permission to execute the command.
    example_Command2:
      command: 'exampleCommand2'
      warning: true
      permission_required: 'bettersecurity.bypass.exampleCommand2'
      executors:
        - '[MESSAGE] %prefix%&cYou cannot execute this command!'
    # In this other example, only the players on the list will be able to perform it.
    example_Command3:
      command: 'exampleCommand3'
      # Tip. You can put both the player's name and his UUID.
      required_players:
        - 'playerName1'
        - '8667ba71-b85a-4004-af54-457a9734eed7'
      executors:
        - '[MESSAGE] %prefix%&cYou cannot execute this command!'

How to set it up?

This is the structure of the command.

  commands:
    <commandName>:
      command: <commandName>
      warning: <true/false>
      # * = Optional
      # * permission_required: <permission>
      # * required_players: <list_players>
      executors: <list_executors>

Command

Here you just need to enter the name of the command that the player will have to execute.

Example: "command: examplecommand1"; as soon as the player types /examplecommand1 the block will occur.

  commands:
    <commandName>:
      command: <commandName>

Warning

Here you can activate or deactivate the warning that will be broadcast if the player who executes the command does not meet the requirements.

  commands:
    <commandName>:
      command: <commandName>
      warning: <true/false>

For more information on Warnings click HERE.

Requirements

Here you can optionally set the requirements to be able to execute the command.

  commands:
    <commandName>:
      command: <commandName>
      warning: <true/false>
      # * = Optional
      # * permission_required: <permission>
      # * required_players: <list_players>

If you do not set any requirements, the command will be blocked for all players, including operators.

Requirement list:

• permission_required: <permission>; You can set a permission to be able to execute the command. | Example: "permission_required: bettersecurity.bypass.examplecommand"

• requiredplayers: <list_players>; You can set one or more players in the list who can execute the command. (In the list you can put both the nick and the UUID) | Example: "required_players: ["playerName1", "8667ba71-b85a-4004-af54-457a9734eed7"]"

Executors

Here you can set the action that will execute as soon as the player who does not qualify, will go to execute the command.

  commands:
    <commandName>:
      command: <commandName>
      warning: <true/false>
      # * = Optional
      # * permission_required: <permission>
      # * required_players: <list_players>
      executors: <list_executors>

You can find all the information about the executors HERE.