PvPToggle by sleelin & updated by AlexDGr8r
Allows PvP enabling or disabling on a per-user basis, or allows for global PvP to be enabled or disabled.
Supports multiple worlds when defined in the config file.

Supports Permission plugin. Permissions nodes:

- pvptoggle.use
	Enable usage of the pvptoggle plugin (i.e. status check when hit)
- pvptoggle.command.toggle
	/pvp [on|off]: individual pvp toggling
- pvptoggle.command.status
	/pvp status: check individual pvp status
- pvptoggle.admin
	/pvp [on|off|status] [player]: modify or check status of specific player in sender's current world
	/pvp [on|off|status] [player] [world]: modify or check status of specific player in specified world
	/pvp [on|off] *: modify status of all players in sender's current world
	/pvp [on|off] * [world]: modify status of all players in specified world
	
- pvptoggle.gcommand.status
	/gpvp status: checks global pvp status
	/gpvp status [world]: checks pvp status in specified world
- pvptoggle.gadmin
	/gpvp [on|off]: toggles global pvp status
	/gpvp [on|off] [world]: toggles pvp status in specified world

Changelog:
v0.4.0:
- Updated to new permissions
- Added support for forced PvP in a specific world
v0.3.0:
- Added option for cooldown between last conflict and disabling PvP
- Added console support for toggling PvP status of specific players, or all players in a specific world, or across all worlds
v0.2.5:
- Updated multiworld support to use bukkit-dependent world detection (fixes issues with misconfiguration)
- Swapped to YAML config file format for ease of use 
v0.2.3:
- Added persistence across player sessions
- Fixed bug in /pvp with no arguments
v0.2.1:
- Fixed severe errors on reload (to do with initialising players)
- Fixed /pvp status [player] [world] - it actually works now
v0.2.0:
- Added multiworld support
- Tidied up command handling
v0.1.0:
- Initial release
 