PvPToggle
PvPToggle
Allows players to decide whether or not they want PvP to be enabled or disabled, and stops PvP attacks when either the attacker or defender has PvP disabled. Also allows admins to toggle global or world-specific PvP, or the PvP status of a specific player, in a specific world. Muti-world compatible, Permissions compatible.
Latest version: v3.0.0
Features:
- Pretty much stated above, but hey, here they are anyway:
- Individual, player-specific enabling or disabling of PvP
- Global PvP control
- World-specific PvP control
- Automatically enable PvP in combat
- Permissions support - only allow certain groups or players access to specific functions
- Multiworld support - configure which world you want the plugin to be active in
- Cooldown timer - set time since last conflict in seconds before users can disable PvP again
- Blocks projectile PvP damage (including damage from Arrows, Snowballs and Fireballs!)
- Block thrown poisonous potion damage
- Warmup timer - set time since enabling PvP in seconds before users can PvP
- Pick between three different commands
- Set your own custom messages on PvP and command events
- WorldGuard PVP flag integration!
Installation:
To install this plugin, all you have to do is place it in your Bukkit plugins folder, and run the server (or reload it) once. This automatically generates a configuration file. That's it! The plugin is now installed.
To read more information about how to set up the configuration, see the Configuration page.
Or, to see what permissions you need to give your users for them to be able to use certain commands, see the Permissions page.
Commands:
PvPToggle now has the functionality to allow you to set the command which it should use! This is settable in the configuration file, and by default, will be set to "/pvp". All command functionality of PvPToggle is accessed via one command.
Basic command overview:
Command | Description |
---|---|
/pvp | Toggle own PvP status |
/pvp [status| on| off] | Set or check own PvP status |
/pvp [status| on| off] <player> [world] | Set, reset or check another players' PvP status. Add [world] argument to work in specific world |
/pvp w:<world> [status| on| off| reset] | Check, set or reset world-wide PvP status of specified world |
/pvp global [status| on| off| reset] | Deals with server-wide plugin operations - used to enable, disable, reset or check status of server-wide global PvP |
/pvp region [add| remove] <region> <world> | Adds or removes a WorldGuard region from PvPToggle's usage |
For more detailed information on usage of each command, see the commands page!
For more detailed information on region management and WorldGuard integration, see the WorldGuard Integration page!
Upcoming:
- Blocking
potion andfire damage - Time-based PvP restrictions
- Announcements
For support, bugs and feature requests, DON'T COMMENT, please start a ticket instead!
I have this error:
2012-10-30 13:08:07 [SEVERE] Could not pass event EntityDamageByEntityEvent to PvPToggle v2.2.1
org.bukkit.event.EventException
at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:341)
at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:62)
at org.bukkit.plugin.SimplePluginManager.fireEvent(SimplePluginManager.java:477)
at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:462)
at org.bukkit.craftbukkit.event.CraftEventFactory.callEvent(CraftEventFactory.java:80)
at org.bukkit.craftbukkit.event.CraftEventFactory.callEntityDamageEvent(CraftEventFactory.java:364)
at org.bukkit.craftbukkit.event.CraftEventFactory.handleEntityDamageEvent(CraftEventFactory.java:386)
at net.minecraft.server.EntityLiving.damageEntity(EntityLiving.java:591)
at net.minecraft.server.EntityHuman.damageEntity(EntityHuman.java:595)
at net.minecraft.server.EntityPlayer.damageEntity(EntityPlayer.java:353)
at net.minecraft.server.EntityHuman.attack(EntityHuman.java:762)
at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:1054)
at net.minecraft.server.Packet7UseEntity.handle(SourceFile:36)
at net.minecraft.server.NetworkManager.b(NetworkManager.java:282)
at net.minecraft.server.NetServerHandler.d(NetServerHandler.java:111)
at net.minecraft.server.ServerConnection.b(SourceFile:35)
at net.minecraft.server.DedicatedServerConnection.b(SourceFile:30)
at net.minecraft.server.MinecraftServer.q(MinecraftServer.java:561)
at net.minecraft.server.DedicatedServer.q(DedicatedServer.java:213)
at net.minecraft.server.MinecraftServer.p(MinecraftServer.java:474)
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:406)
at net.minecraft.server.ThreadServerApplication.run(SourceFile:539)
Caused by: java.lang.NullPointerException
at com.sleelin.pvptoggle.PvPToggle.checkLastAction(PvPToggle.java:356)
at com.sleelin.pvptoggle.listeners.EntityListener.eventMagic(EntityListener.java:97)
at com.sleelin.pvptoggle.listeners.EntityListener.onEntityDamage(EntityListener.java:57)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:339)
... 21 more
Help?
Good day, Great plug-in! Thank you for working on it. Is there a way to turn off the messages, like, "Global PVP is disabled!"?
Thank you.
@Sleelin Okay I think I solved the problem by installing the old good version 2.1.0 :)
Can you add pvp-groups?
Every group can have personal pvp-premission to be pvp-ed, or vice versa.
So It can play role of some simple rpg plugin =)
@AlphaFarer
We're running the latest version of bukkit and about 50 of the most popular plugins and have found PVP Toggle to be solid. Sleelin, thanks again for a great plugin.
@Sleelin Since a few days (doesn't matter if using the newest or an older version) I only getting these messages spamming the console around 10 times per second:
@Sleelin
Reported.
@AlphaFarer
Would you mind providing more information on exactly what the bugs are so that I can fix them, instead of just saying there are bugs?
Edit: preferably through a ticket
[v2.2.1] Is the buggiest version I've ever used of this plugin.
@ZwingGX
What version of Citizens are you using? Must be at least v2.0+
@Digitalink2008
It will cycle through each region a player is currently in, and if any of them have the PVP flag set to either "allow" or "deny", it will force either PvP enabled for allow, or disabled for deny. I have plans to add an ignored regions section to the config though.
so is the idea with the WG integration that we don't have to set any additional flags? PvPToggle will just respect the WG pvp flag?
Hot damn! The WG integration is in! Right on Sleelin.
@Sleelin
Sleelin, thanks for fixing this, looking good now! I'm really happy you were able to fix this, it's an important plugin for our server.
<<reply 1004248>>
v2.2.1 is this error spam message.
http://dev.bukkit.org/paste/6388/
@Sleelin
You happy, me happy :) Thanks! ;)
@ThisUsernameIsMine
Magical WorldEdit custom Vector type dependencies! Hooray! Nobody had reported that yet. Should now be fixed in v2.2.1
Welcome back Sleelin ;)
I'm not sure if there's already a ticket of this, but under 2.2.0 @ CB RB 1.3.2-R1.0
the following happens at server-start: http://dev.bukkit.org/paste/6385/
@paulj1x
Actually I've been on an extended leave of absence from my development environment for health reasons (read: I got sick), and haven't been able to touch this project. The project isn't abandoned, I have just been physically incapable of working on it.
Tickets about the Citizens integration now causing EntityDamagedByEntity Event non-passing errors are due to Citizens changing their API (again, that makes three times in a year), and I literally just fixed it as it was a single line (where previously it was CitizensManager.isNPC(player), it is now CitizensAPI.getNPCRegistry().isNPC(player)).
I am also now working on WorldGuard integration - the WorldGuard API is less extensive than one would hope, but I should be able to release v2.2.0 with WG hooks in the next hour
@jenks1999
There are several tickets with the same problem, all being ignored.
This appears abandoned, the authors haven't been on since May. Mine stopped working and provides no protection.
What are good alternatives to this plugin?