[ADMN/SEC] PvPable v0.3.2 - Comprehensive PvP Control; Now with Proximity-Command-Restrictions [953]

PvPable - Control who can and can't PvP with a single permission node!
Version: v0.3.2
Download: PvPable v0.3.2 (JAR)
Requested by @Monkz

IMPORTANT: v0.3+ IN ORDER TO USE THE NEW COMMAND RESTRICTION FEATURE, YOU MUST SET THE USE-COMMAND-RESTRICTION NODE IN THE CONFIG TO TRUE! IT WILL NOT WORK OTHERWISE!

This plugin started out very simple. It allowed you to control who could and could not take part in PvP with one simple permission node 'PvPable.enable'
However, it now boasts a full CUSTOM command-restriction interface (based on how close a player is to the command sender), and in due time, it's sure to have more features!

THIS PLUGIN REQUIRES PERMISSIONS.

Features:

• Allows people to set permission nodes for players who can/can not take part in PvP(For example, a Merchant Group on an RPG server without PvP.enable wouldn't be able to attack players, or BE attacked by players)
• Sends notifications to tell players why they can't attack others.
• (NEW) Full-Featured Configuration! (Notifications, as well as command restrictions info)
• (NEW) CUSTOM Command Restrictions based on how close a player is to the command sender (customizable radius, of course! )

Permissions:

• 'PvPable.enable' - Any player with this node is allowed to PvP, but they can't attack players without this node
• (NEW) 'PvPable.override' - Any player with this node will ignore CommandRestriction (if its set to true in the config)

(NEW) Configuration:

Show Spoiler Hide Spoiler

CommandRestriction:
Restriction-Range: 20.0
If a player is within this range, any commands defined in Restricted-Commands will be disabled.
Restricted-Commands:
- command1
List of restricted commands. Loads 'command1' by default, you can change (and add) accordingly.
DO NOT USE THE / in the command name!
Use-Command-Restriction: false
This must be turned to true in order for the command restriction to work!
Custom-Messages:
These are pretty self explanitory, let me know if you get lost, however!
Attacker-PvP-Disabled: You can't attack a player if you have PvP disabled!
Attacked-PvP-Disabled: You can't attack a player that has PvP disabled!
OP-Attacking-Disabled: Careful, the person you're attacking has PvP disabled!

Bug Reports:

You know the drill, people!
Bukkit Build # AND Error in console.

Known Issues:

Show Spoiler Hide Spoiler

• None yet, but as I did 0 bug testing (didn't have time, and wanted to release this to the guy who needed it) there's bound to be some

TODO:

Show Spoiler Hide Spoiler

• Dunno, made this as a request. You tell me.

Changelog:
Version 0.3.2

• CmdRestriction now prevents any command that contains a restricted command
• Example: - 'party tp' Will deny any command with "party tp" in it (so /party tp <playername>)

Version 0.3.1

• Added permission node 'PvPable.override' to allow players to bypass CmdRestriction, even if its on
• CmdRestriction now has OP support (Ops override by default, now)

Older Changelogs

Show Spoiler Hide Spoiler

Version 0.3
MAJOR UPDATE!

• Added the new Command-Restriction (based on player proximity) feature!
• Added a comprehensive configuration file!
• IMPORTANT: To use the new Command-Restriction feature, you MUST set the Use-Command-Restriction to true in the config, as it defaults to false (to minimize plugin weight on the server, if people dont want to use this feature)

Enjoy!

Version 0.2

• Changed the core permission node to 'PvP.enable' (for inheritance purposes)
• Added alerts to players who were denied PvP (tells them why they can't attack the other player)

Version 0.1.1

• Now allows OPs to attack players, regardless of the target's PvPable status

Version 0.1

• Releasing PvPable

 

@DrBoweNur
Well, Permissions fucked it over.. I switched to group manager and it works wonderfully. TY for the quick reply.

 

@Olat
No problem. Just as a heads up though, you mentioned you wanted it so your guests couldnt PvP. You realize that this plugin makes it so that they themselves are immune to attack as well, though...right?

 

@DrBoweNur
Ya my guest acct is liek a greylist you can connect and talk but cant build, pvp, or do anything until you apply on the forums and are accepted. This allows people to view the cities and pvp and the attitude of the server before joining. Them not being killed is a good thing as my players are viscious and would prey upon the clue less at times. Hardcore PVP at its best.

Thanks again!

 

Could you make it possible to enable PVP (but mostly command restrictions) in a certain area? I mean, that PVP is always enabled in that area, and people who enter that area always have command restrictions.

 

Something like Niels,

It would be cool to have PVP areas and Non-PVP areas.

 

Source Code?

 

You're welcome to decompile it, you have full permission from me

I'm on a bit of a coding hiatus--rather I'm busy with Python and Blender--so I'm a bit busy.
I think the source is pretty neat, but lacks comments...so decompile at your own demise

 

Mmh... I've already this problem with an else plugin...
It's because you use Permissions 3x or else who don't are compatible with this plugin!
Me, i use GroupManager now....

 

Actually, despite the thread being changed, this now uses SuperPerms. So anything that supports Bukkit's built-in permissions (Such as PEX/GroupManager/bPermissions) will work with it.

 

Long time no see DrBowe. You will notice that this thread has now been placed into the Inactive Plugin subforum.
If you wish to revive this plugin, please ensure that you update and test compatibility with the latest recommended Bukkit build before reporting your original post, asking for it to be moved back to the release forum.

Thanks for your time.
md_5