AntiCommands
Anti Command plugin deny all commands to be used based on a list of players or argumments.
This plugin is ideally for you, server owners is wanting to deny player to use your skin with "/skin set yourNick", or want your adm to not deop you, or deny any type of command with the argumments on lists.
Configuration and How to Use:
You can add more list as you need, and the use "{your-list-name}" followed a command to deny commands with the argumments or name of your custom list.
#The command list is composed as "- command {list-name}:text to show for player" command-list: - deop {player-ops}:&cYou cant deop this player! #Example command to deny deop players - skin set {player-adms}:&cYou cant use the skin of this player! #Example command to deny players to use the admin skins player-ops:[] #List of OPs that cant be deoped player-adms: #List of admins that cant have the skin used - Adm1 - Adm2 #Create as many lists you want with players , entities and arguments, and add {my-custom-list} to the config.
Permissions & Commands:
All permissions default for OPs.
| Command | Comment | Permissions |
|---|---|---|
| /antic reload | Reload the plugin | anticommand.reload |
| Permission to bypass the commands on config | anticommand.bypass |
Other Amazing Plugins
| RedProtect | SedexPet | |
|---|---|---|
| PvPDiffTimer | LoreTag |
|---|---|
| Ultimate Translator |
|---|
-
View User Profile
-
Send Message
Posted Jan 27, 2016@CloudeLecaw
I will fix this soon. Initially does work. The plugin consider only one list/command.
@Formula350
I will try to make like you want ;)
-
View User Profile
-
Send Message
Posted Jan 23, 2016Is there any way to make it conditional based on what Block/Item the player has in hand (whitelist would be ideal in this situation, instead of blacklist, but both being available)? On top of that, the ability to assign a specific permission to each, and a bypass?
For example, I've long wanted just a simple plugin that lets me let players use /hat but not just use any block or item like currently is possible.
In this case it'd be something like how BetterAlias works (or at least how it's config is laid out):
Note1: This is the command.
Note2: This is the permission node. The .1 is to indicate this specific conditional, where .2 would have it's own whitelist or blacklist.
Note3: These are IDs of what must be in hand in order to run the command for the player. If they are holding _anything_ else, it won't execute. If they lack the above permission, it won't execute.
Note4: I'm assuming BANNER.* will allow for any banner to be worn, figuring when customized they are sorta like Potions with their Data Values.
Note5: This specifies where on a player the white/black listed ID/s would need to be, in order to execute the command. "any" would thus mean anywhere on the player, armor, hotbar, or inventory.
Bypass Perm would be, in this instance: anticommand.hat.*.bypass or anticommand.hat.bypass (I understand that hat.*. in this case accomplishes the same thing as hat.bypass, but I'm just anticipating a situation it'd come in handy that I'm not considering right now)
Heck, may not even really need to program any permission function directly, and just hook into Vault instead, which would be completely fine by me :D
I think being able to limit, but specify the conditions that need to be met in order to execute. Which a number of situations I can think of where this could offer me more flexibility on my RPG server. Furthering the above's possible use would be the ability to make the item/block have an NBT conditional... Item name that matches, or lore.
Which in our specific case would need to not be too anal about matching. For example our one weapons plugin outputs names which are a bit stupid. They look fine, but when you look at the NBT is where things show up. We see "&6&lBig Sword", but NBT has "&0&0&0&0&0&0&0&f&b&6&lBig Sword" :\ So the conditional would for instance be to match anywhere in the indicated line (Name, Lore), but still the specific string in the config. Using the Big Sword example, in the config we'd have "&6&lBig Sword", so an anvil named item wouldn't work since it'd be "&b&oBig Sword". However, all those &0s and silliness would be ignored.
(It's an old, abandoned plugin that is core to our server, but otherwise works fine besides a hiccup here and there, such as that)
Thanks :)
-Form
(apologies is this would've been better suited as a Ticket...)
-
View User Profile
-
Send Message
Posted Dec 7, 2015@CloudeLecaw
I can add block only commands. The initial proposit is block player to use my, and admins skins with skinrestorer :)
For "- sumon Enderdragon:'&cYou cant summon the Enderdragon'" you can add create a lista called {deny-entities} and add entityes denied to summon, like Enderdragon.
For "- tp {player-list} {block-player}:'&cYour not allowed to TP this " i dont have tested, but if not work...i will take a look!