AntiCommandTab
Description
AntiCommandTab protects your server from Layer 1 CoPY-Cat attacks. Users will not be able to figure out your server plugins and through commands or [TAB].
Features
- Blocks / [TAB]
- Blocks /ver [TAB]
- Blocks /version [TAB]
- Blocks /about [TAB]
- Blocks /pl and /plugins
- Blocks /about
- Blocks /version and /ver
- Blocks /?
- In the config.yml you can customize the deny message (chat format supported!)
Permissions
- lib.commandtab.bypass - bypasses /[TAB] and commands
Requirements
- This plugin requires ProtocolLib.
Support
Comments are disabled to keep the project page clean. Please report issues on the Github issues tab for this project. For feature requests, feel free to private message them!
Comments
-
_ForgeUser6852435 Owner
-
_ForgeUser9938598 Author
-
View User Profile
-
Send Message
Posted Aug 4, 2013@darkness1999
Greetings, one thing to note about that code, is that it doesn't ignore case. Therefore someone can do /PL and see the plugins. The method I used is .equalsIgnoreCase to distinguish that from .startsWith(). I left out /help because a plugin like essentials uses that.
:o I'll upload a new version soon.
-
View User Profile
-
Send Message
Posted Aug 4, 2013@sgtcaze
I think you did the same fault as I...I forgot to say that I want to block everything that starts with /pl for example
The change would be very easy: (probably)
@EventHandler(priority = EventPriority.NORMAL
public void onPlayerCommandPreprocess(PlayerCommandPreprocessEvent event) {
if(!(e.getPlayer().hasPermission("messages.blocked-cmds") || p.isOp())) {
if (event.getMessage().equalsIgnoreCase("/plugins")
|| event.getMessage().startsWith("/pl")
|| event.getMessage().startsWith("/?")
|| event.getMessage().startsWith("/about")
|| event.getMessage().startsWith("/ver")
|| event.getMessage().startsWith("/help")
|| event.getMessage().startsWith("/version")) {
}
}
}
I have also added the command /help, /ver because they were missing.
Please upload a new version today :D because Im on holiday tomorrow and could need this.
-
View User Profile
-
Send Message
Posted Aug 3, 2013@LaFong
This is true. Hmm, I'll work on a fix when I can. I'm developing a lot of plugins right now. I'd recommend negating the permission "bukkit.command.help" for now.
-
View User Profile
-
Send Message
Posted Aug 1, 2013I've noticed that you can easily bypass being able to see the plugin list by doing:
/? <#>
The command /? is blocked, but if you put a number after it (which shows the help pages), players can look through all the help pages and see what plugins we have.
-
View User Profile
-
Send Message
Posted Jul 27, 2013Wow great Plugin, thanks for this.
-
View User Profile
-
Send Message
Posted Jul 23, 2013@sgtcaze
WOW!! Thx! Amazing! THXTHX :DDD
Best Plugin Hide Plugin!!
-
View User Profile
-
Send Message
Posted Jul 23, 2013@NoHoPeLess
Allow the permission "bukkit.command.plugin". Don't worry, if you allow the permission they won't be able to see the plugins. This plugins message takes priority. :)
-
View User Profile
-
Send Message
Posted Jul 22, 2013Yes, ok it works i dont know why??
But when i type /pl result:
-
View User Profile
-
Send Message
Posted Jul 20, 2013@NoHoPeLess
1) This plugin is guaranteed to not break across versions (just tested works fine) 2) Verify you have the required dependency "ProtocolLib" 3) Verify you have reloaded your permissions file or that you are in the necessary group
The error you have encountered is a fault of your own. I just tested it on a private server. (See attached image)
-
View User Profile
-
Send Message
Posted Jul 20, 2013Can u pls update to 1.6.2 ? the message from the config is not displayed...
and the permissions are not working...
-
View User Profile
-
Send Message
Posted Jul 7, 2013@sgtcaze
Oh yes sry, I downloaded this already but forgot to restart!
-
View User Profile
-
Send Message
Posted Jul 7, 2013@darkness1999
The latest bukkit build hasn't even been approved yet. Click on "development builds" button above and use build #7 if you want it early.
-
View User Profile
-
Send Message
Posted Jul 7, 2013@sgtcaze
I tested this with the latest build but it does not work
-
View User Profile
-
Send Message
Posted Jul 7, 2013@darkness1999
Thanks for the suggestion. I have uploaded a new version now applying the following:
Check my Jenkins (build #7) or wait for Bukkit to approve the file.
-
View User Profile
-
Send Message
Posted Jul 6, 2013Please make it so that only people without permission X will get the deny message.
Because it should be possible for admins to review the plugins...
-
View User Profile
-
Send Message
Posted Jul 6, 2013Great to see some activity again and a new author :D
I had to patch it for 1.5 myself ;)
-
View User Profile
-
Send Message
Posted Jul 5, 2013Uploading version 2.1 with the following changes:
As always, early builds can be acquired at my Jenkins server (link above). If you want to wait for the official release, please allow bukkitdev some time to review the file.
-
View User Profile
-
Send Message
Posted Jun 30, 2013@jaime29010
Deny "bukkit.command.version" but allow the other permissions. I will work on a fix for that now.
-
View User Profile
-
Send Message
Posted Jun 29, 2013The plugin is fine but if you put / version and tab, they can see the plugins. Not only that, if you put /PL , /PLUGINS or /VERSION in capitals also can see, would be nice to be able to fix this please. :D
-
View User Profile
-
Send Message
Posted Jun 22, 2013Love it! :) +1