BetterSecurity v1.6 | New additions + new major changes!
NEW SECURITY PATCH (BungeeCord)
┃Added in the bungeecord section "Prevent_Command_Spam", it is able to fix an exploit that is able to crash the bungeecord! Currently plugins like LPX do not take advantage of this feature, so I recommend you to activate it.
┃Added "bettersecuritybungee.bypass.cmdspam" permission to bypass this new prevention.
# This feature allows you to fix an exploit that crashes your proxy! # You can customize it as you like according to your needs. enabled: true
# If it is on "true" the execution attempt warning will be sent to chat. warning: true
# This option determines how often you can run the command (In seconds) delay: 3
# This function determines how many commands based on the delay, the player is punished. # (If set to 0, this function will be ignored) command_limit: 10
# If this is set to "true", you will not be able to execute the command during the cooldown. block_command: false
# (If you have set the command limit, along with the kick, this section will be ignored. # You can also ignore it by simply putting -> message: '') # This message will be shown during a cooldown. # # You can use the following placeholders: # - %seconds% | (Seconds left) # - %commands% | (Number of commands executed) # < ? > You can find more information about the executors in the header. executors: - '
[KICK
] &cYou performed
%commands% commands in 3 seconds!\n&cPlease rejoin and don''t make commands too fast.'
# Here you can enter the type of method you want to use to set the command cooldown: # - BLACKLIST | (The commands in the list will have the cooldown) # - WHITELIST | (Commands in the list will have no cooldowns) method: 'BLACKLIST'
commands: - 'alert'
- 'alertraw'
- 'bungee'
- 'end'
- 'find'
- 'glist'
- 'greload'
- 'ip'
- 'perms'
- 'send'
- 'server'
- 'lpb'
- 'luckpermsbungee'
NEW CHANGES (BungeeCord)
┃Added executors to the bungeecord as well! The same ones that are in the spigot version have been added, except 2: BossBar and Sound. Also added was the "[KICK] reason" executor.
┃In the "Blocks_Commands" section, the messages have been replaced with executors.
# In this field you can decide whether to activate the logs also via the console. log_console: true
# This message will be sent to those with permission: bettersecuritybungee.broadcast.warnings # < ? > You can find more information about the executors in the header. # ATTENTION! Do not use the "@" in front of the broadcast, there is already the automatic one via the above permission. formats:
commands: # You can use the following placeholders: # - %command% | (The command that was blocked) format: - '
[MESSAGE
] &e&l⚠ &e
%server% ┃ &b%player% &7attempted to execute the command: &c%command%' console: '
%player% attempted to execute the command: %command%' prevent_command_spam: # You can use the following placeholders: # - %command% | (The command executed too many times) format: - '
[MESSAGE
] &e&l⚠ ┃ &b
%player% &7has executed the command too many times: &c%command%' console: '
%player% has executed the command too many times: %command%'
# If it is on "true" the execution attempt warning will be sent to chat. warning: true
# Here you can enter the type of method you want to use to block commands: # - BLACKLIST | (The commands in the list will be blocked) # - WHITELIST | (The commands in the list will be able to execute) method: 'BLACKLIST'
# Forced checking if enabled can cause problems with other plugins. # For example AuthMeBungee (If you execute a blocked command before login, the plugin will overwrite it) force_check: false
# This message will be shown as soon as the command is blocked. # < ? > You can find more information about the executors in the header. executors: - '
[MESSAGE
]%prefix%&cYou cannot execute this command!'
# List of blocked or enabled commands according to the selected method. # If you want to block commands only through "server mode", just put "commands: []" commands: - 'bungee'
- 'waterfall'
- 'pl'
- 'plugins'
- 'ver'
- 'version'
- 'about'
- '?'
- 'help'
- 'bukkit:pl'
- 'bukkit:plugins'
- 'bukkit:ver'
- 'bukkit:version'
- 'bukkit:about'
- 'bukkit:?'
- 'bukkit:help'
- 'minecraft:?'
- 'minecraft:help'
# Server mode allows you to block commands based on the server the player is on. server_mode: enabled: false
# This is the list of servers where commands are blocked. servers: # This is an example server. lobby: # < ? > The methods are the same that are located above. method: 'BLACKLIST'
# Instead these are the commands blocked on that server. commands: - 'examplecommand1'
- 'examplecommand2'
# In this example you can use another message. survival: # < ? > The methods are the same that are located above. method: 'BLACKLIST'
# This executor will only be sent to this server. # < ? > You can find more information about the executors in the header. executors: - '
[MESSAGE
] &a&lSURVIVAL ┃ &cYou cannot execute this command!'
# Instead these are the commands blocked on that server. commands: - 'examplecommand1'
- 'examplecommand2'
NEW CHANGES (Spigot/Bukkit)
┃Added placeholder "%center%", to be usable for all messages. (Included in executors)
┃Added event priorities! You can change their priority for the various sections. They have been added for the following sections: Unknown_Command, Block_Syntax, Blocks_Commands, Commands_Only_Console, Commands_Only_Players, Block_Custom_Commands.
# --------- < ⚠ > --------- # This feature is only recommended for versions 1.19+! # This is because spigot does not currently edit the unknown command via spigot.yml, # but remains the default one. If you have a version lower than 1.19, you can leave it to false. # If you use PlugMan, it can cause problems if the plugin it loads registers commands for the first time. enabled: false
# Here you can set the priority of the event. You can find the priority list with this link # --> https://hub.spigotmc.org/javadocs/spigot/org/bukkit/event/EventPriority.html priority: HIGHEST
# To ignore this section put "exempt_commands: []" # This function allows you, in case of problems, to be able to insert a # list of commands that the plugin will ignore. # The command set by default was put as an example for those who use ChatControl-Red, # who when running /tell also execute a command that is not registered on Bukkit. exempt_commands: - '
#flp'
# If set to "true", it will fetch the unknown message directly from spigot.yml. # If it's false, then it will use the executor below. use_spigot_message: true
# If "use_spigot_message" is true, ignore this section. # < ? > You can find more information about the executors in the header. executors: - '
[MESSAGE
]%prefix%The "&b%command%&7" command was not found.'
# Here you can set the priority of the event. You can find the priority list with this link # --> https://hub.spigotmc.org/javadocs/spigot/org/bukkit/event/EventPriority.html priority: HIGHEST
# If it is on "true" the execution attempt warning will be sent to chat. warning: true
# Message that is sent if one tries to do: <plugin>:<command>. # Tip. It is useful to avoid being in situations where you can bypass blocked commands, # or commands known as minecraft:me, minecraft:tell, etc... # < ? > You can find more information about the executors in the header. executors: - '
[MESSAGE
]%prefix%&cYou can''t do /<plugin>:<command>' - '
[TITLE
] &e&lBETTER SECURITY;&c&l┃ &cYou can''t do /<plugin>:<command>;20;40;20'
# Here you can set the priority of the event. You can find the priority list with this link # --> https://hub.spigotmc.org/javadocs/spigot/org/bukkit/event/EventPriority.html priority: HIGHEST
# If it is on "true" the execution attempt warning will be sent to chat. warning: true
# Here you can enter the type of method you want to use to block commands: # - BLACKLIST | (The commands in the list will be blocked) # - WHITELIST | (The commands in the list will be able to execute) method: 'BLACKLIST'
# This message will be shown as soon as the command is blocked. # < ? > You can find more information about the executors in the header. executors: - '
[MESSAGE
]%prefix%&cYou cannot execute this command!'
# List of blocked or enabled commands according to the selected method. commands: - 'pl'
- 'plugins'
- 'ver'
- 'version'
- 'about'
- '?'
- 'help'
- 'icanhasbukkit'
# Here you can set the priority of the event. You can find the priority list with this link # --> https://hub.spigotmc.org/javadocs/spigot/org/bukkit/event/EventPriority.html priority: HIGHEST
# If it is on "true" the execution attempt warning will be sent to chat. warning: true
# This message will be shown as soon as the command is blocked. # < ? > You can find more information about the executors in the header. executors: - '
[MESSAGE
]%prefix%&cYou cannot execute this command!'
# List of commands that can only be executed from the console. commands: - 'op'
- 'minecraft:op'
- 'deop'
- 'minecraft:deop'
- 'reload'
- 'minecraft:reload'
- 'rl'
- 'minecraft:rl'
- 'execute'
- 'minecraft:execute'
# Here you can set the priority of the event. You can find the priority list with this link # --> https://hub.spigotmc.org/javadocs/spigot/org/bukkit/event/EventPriority.html priority: HIGHEST
# If it is on "true" the execution attempt warning will be sent to chat. warning: true
# This message will be shown as soon as the command is blocked. # < ? > You can find more information about the executors in the header. executors: - '
[MESSAGE
]%prefix%&cYou cannot execute this command!'
# List of players authorized to execute the commands below. # Tip. You can put both the player's name and his UUID. bypass_players: - 'playerName1'
- '8667ba71-b85a-4004-af54-457a9734eed7'
# List of commands that players in the list above can perform. commands: - 'pl'
- 'plugins'
- 'bukkit:pl'
- 'bukkit:plugins'
# 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'
priority: HIGHEST
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'
priority: HIGHEST
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'
priority: HIGHEST
# 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!' # In this example, he shows you how you can block multiple commands with the same executor. example_Command4:
commands: - 'examplecommand4'
- 'examplecommand5'
priority: HIGHEST
warning: true
permission_required: 'bettersecurity.bypass.exampleCommands'
executors: - '
[MESSAGE
]%prefix%&cYou cannot execute this command!'
FOR SUPPORT ┃Write to me
here in private,
Telegram, or by
Discord ⚠️ After the update, reset or add the new changes, to the config.yml