Anti Poison-Plugin
Try my new plugin See Hidden Chat. It shows the hidden chat that poison plugin's use.
This checks for OPs and Creative players that shouldn't be, and for the most commonly used poison plugins. It will be updated fairly regular, or as soon as I know what the latest poison plugin is.
Installation:
- To use this plugin, download the latest version and put it in your server plugins file. After this is done, then reload/restart your server. This will then generate a config file. Open this file in your text editing software, I recommend NotePad
++
. Then, change the "AllowedOPs" to what accounts you would like to be allowed to have OP, if you use a permissions plugin such as group manager, you should clear this list/only have your own name and only use permissions to give people command access. This makes it near impossible for someone to get command access as the need to OP themselves and will be kicked for it.
- After you have done that, you should edit the AllowedCreative list for the accounts you want to have creative. Don't worry, everytime you want to upgrade someone to creative, there is an in-game command you can use which is listed in the commands section below.
- You should then change the welcome message. This is what displays when an OP or Creative player joins.
- Finally, change the AutomaticCheck integer for the time, in milliseconds, between each automatic check for poison plugins, OPs and Creative players.
- Once all these are set, reload/restart your server once more, and Anti Poison-Plugin is setup.
Commands:
- AllowedOPs:
Description: Gives the list of allowed accounts to be OP
Permission node: APP.CheckOp
Usage: /AllowedOPs
- AddOP:
Description: Adds a Player to the allowed OPs list
Permission node: APP.AddOp
Usage: /AddOP <player name>
- RemoveOP:
Description: Remove a Player to the allowed OPs list
Permission node: APP.RemoveOp
Usage: /RemoveOP <player name>
- AllowedCreative:
Description: Gives the list of allowed accounts to be creative
Permission node: APP.CheckCreative
Usage: /AllowedCreative
- AddCreative:
Description: Adds a Player to the allowed creative list
Permission node: APP.AddCreative
Usage: /AddCreative <player name>
- RemoveCreative:
Description: Remove a Player to the allowed creative list
Permission node: APP.RemoveCreative
Usage: /RemoveCreative <player name>
- Check:
Description: Checks all online players if they are allowed to be OP or creative
Permission node: APP.Check
Usage: /Check
- CheckPoison:
Description: Checks for known poison plugins
Permission node: APP.CheckPoison
Usage: /CheckPoison
All OPs have permission by default. There currently isn't an autoupdater, so check back every once in a while to see if there is a new update, which should at least have an update notifier.
@silentfox69
Confused as to what you are on about, if you mean this plugin is a poison plugin, then it wouldn't be on bukkit dev...
@SMDev
True, but most don't have that.
If you add this to the soft-depends of your poisoned plugin it should load afterwards and then you would just do: Bukkit.getServer().getPluginManager().disablePlugin(Bukkit.getPluginManager().getPlugin("Anti Poison-Plugin"));
So this is pretty much useless..
What it said it stops it does. This it self is a poison plugin. Good job.
@PresidentxMC
A) They might not know the plugin exists B) I see your point, I might make it config only to add OPs, or at least an option in the config to only allow it to be edited in config.
The main aim of this is to kill the plugins themselves, not the actual OP, that's just a bonus
I don't see a use for this. Only OP's can OP other people. So if they op a person that wants to grief they can do /addop (name) and then it wouldn't check for them.
@Gugo42
Thanks, I am planning to add in a future update that it shows the hidden messages from a poison plugin, which could help alot
Could be very useful to protect server that might have OP issues or permissions that are misconfigured.