DeathControl
Overview
This plugin is a powerful tool to control what happens when players die. Its primary feature is to allow players to keep their inventory, but by now it offers plenty of more possibilities about what to do. You can set conditions that have to be met and actions that will be executed.
Flexibility is one of the main objectives of the plugin. Whether you want a simple way to keep inventories, you want enchanted pickaxes named "Pink Elephant" to be destroyed upon death or you just want to change PVP deaths - this plugin makes it all possible.
Main Features
- provides a powerful way to set up handlings for player deaths
- create different behaviors depending on how and where the player died
- able to save a player's inventory, experience and/or food level upon death
- destroy or damage items upon death
- allows item filters to affect only certain items
- economy support: charge them money for it!
- waiting for the player to perform a command can give them the choice of what to do
- disconnecting players are treated with a timeout
- supports every major economy-plugin through Vault or Register
- uses regular permissions system or the OP system
- flexible messaging system that allows localization and customization
- hooks into the API of MobArena and BattleArena to fix deaths in an arena
Donate
If you want to support the development of the plugin, feel free to drop a donation! It really helps to keep this plugin alive. Thank you :)
Pages
- Configuration
- Commands
- Permissions
- Changelog
- FAQ (Frequently Asked Questions)
- Source code
Setup
- If you want to use economy plugins, you need to have Register or Vault installed as a plugin.
Just download the jar from the linked page and put it in yourplugins/
folder, if you haven't yet. - Drop the plugin's jar in the
plugins/
-directory of your server (just like every plugin, eh?). - Start/Reload the server once to generate the configuration files at
plugins/DeathControl/
. - Read the instructions on the Configuration page for config information!
- Make your adjustments to
config.yml
andlists.txt
as you wish - Reload the config files either through reloading the server or, easier, with the command "
/death reload
" - Enjoy the plugin!
Dependencies
The plugin is functional without any other plugins.
To be able to use the "charge" action (and thus make players pay money), you need one of those plugin libraries so this plugin can make use of your installed economy plugin:
One of them needs to be installed as a plugin on your server.
Reporting an issue
If you think you found an error with the plugin:
- Read the FAQ. It might be a common incompatibility.
- Go to the Issues forum and check if the issue was already posted/answered by another user.
- If not, create a new topic in that same forum and describe your issue precisely. Always post your craftbukkit version, plugin version and if relevant your config file(s).
Please do not report issues in the comments! Only use the forums!
To-Do
This section is now represented by the Tickets tab.
@Mayhem777
If it still occurs in 1.3.2-R2.0, please open a forum thread with steps how to reproduce it. I can't find any reason why this could suddenly happen. Is it basically ANYTIME you die (and the plugin keeps something)?!
Also, your stack trace (error message) looks a bit cut off, do you have a complete one?
@adenslayer
Not right now, been on the Todo list for quite some time, but it's lots of refactoring work in the plugin. I'll eventually rewrite it, but not too soon. The config structure needs to be complete changed to allow high flexibility, the challenge is to still make it simple to understand.
@Robert107
It should actually be up to date. I just pushed another recent small change. DeathControlEntityListener is wayy outdated, though. It was removed (renamed) about 4 months ago in this commit. Shouldn't be there anymore.
Are you talking about the vanilla death messages? I think there's plugins out there dedicated to that aspect, but if you want to add it, sure ;) If you make a pull request, please make sure you keep the diff as low as possible, though. No unnecessary refactorings, please :). (just pointing that out, I've seen too much of that)
@Bone008
Hey, the github repo it's updated? I cloned it and it have some things that dosen't have much sense, for ie: in some part of DeathControlEntityListener it calls getActualExp but it dosent exists, instead getCurrentExp does.
Can you update it? I'm going to modify it to send the death messanges to the involved players in the deaths instead to the whole server! I can make a pull if you want to.
is there a way to set this up so that different groups get different ways of saving for causes of death?
No one, when i have problems like that i put all my plugins in a invalid fonder and then load only the one with problems, and i get the same problem only with deathcontrol, only to players with permission "deathcontrol.use"
@Mayhem777 I can't find anything why this plugin could cause that. The stack trace looks like a plugin is digging pretty deeply in native code, which I am not doing here. It looks like it's doing something with custom entities or nasty death hooks. What other plugins are on your server?
I get this with 1.3.2 R1 when a player with permissions die:
http://pastebin.com/Z12mPts0
And of course server crashes...
@kalvin807 I know, sorry. The current system in the code doesn't really allow that right now, and I don't have time to recode it. Writing down all of them separated with a comma is only work you do once, though, then you never need to worry about it again (see Configuration page)
@Plumeex Glad to hear that :D
@Valon750 I might do that, but considering that I can't really develop new features at all right now, it probably won't happen soon. Sorry.
@fatalerror0x00 First of all, I'm only one guy, and I tend to overlook PMs quite frequently. I read them once and then forget to get back to them, since they are not actively throwing themselves at me. Your issue also didn't sound very "huge".
Since you did at least post in the forums now, I'll respond there.
I feel like somethings is wrong as I PMed these guys over a month ago with a huge issue with this plugin that really needs to be fixed and I haven't heard from anyone at all in return. It's getting frustrating and wanted to know if anyone had luck getting in contact.
It works perfectly with Essentials Economy. My players are very happy ! :D
Can you add a option that for all death causes? It is very annoying to set them one by one :P anyway , very useful
edit: (oops i was being a noob deleted earlier post) good useful plugin :)
@VietNg Update to the latest version, you are still on v1.81 ...
[SEVERE] Error occurred while disabling DeathControl v1.81 (Is it up to date?) java.lang.NullPointerException at bone008.bukkit.deathcontrol.DeathManager.expire(DeathManager.java:54) at bone008.bukkit.deathcontrol.DeathControl.onDisable(DeathControl.java:60) at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:219) at org.bukkit.plugin.java.JavaPluginLoader.disablePlugin(JavaPluginLoader.java:400) at org.bukkit.plugin.SimplePluginManager.disablePlugin(SimplePluginManager.java:400) at org.bukkit.plugin.SimplePluginManager.disablePlugins(SimplePluginManager.java:393) at org.bukkit.craftbukkit.CraftServer.disablePlugins(CraftServer.java:278) at net.minecraft.server.MinecraftServer.stop(MinecraftServer.java:329) at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:438) at net.minecraft.server.ThreadServerApplication.run(SourceFile:539)
@Bone008
Alright, cool. Craftbukkit's other dev releases suck, so I've been staying behind on their good one.
The beta build is the worst release ever, and I've been watching some of the complaints being made, but I guess the staff is not seeing it, or they say it's a plugin issue.
Have you come accross the issues such as: Not being able to teleport, use commands, or chat? Also claim you're in a different location, yet you're still in the same location that you logged in, or started at?
@MasterGabeMOD
There's no reason that it should not. It only has potential to break between major Minecraft updates, if the way damage causes or experience works changes. It should almost always be fine between craftbukkit builds for the same MC version (1.3.1 and 1.3.2 is really a difference as well).
@Bone008
Awesome, and could this also be compatible for craftbukkitdev build #2351?
That's the only one I've been using, since all the rest are crap.
Thanks
@MasterGabeMOD
The first and third stack traces happen when the plugin disables while there is more than one stored inventory left to be given back. I missed a stupid error of mine there, causing this exception. I apparently need ANOTHER bug fix update for 1.8x, never needed that many for one version :/
The second and last stack traces occur because a player on your server apparently has more than 100000 levels of experience (126325 and 131093, to be precise). That number seems pretty insane to me. 100k is a built-in limit of the experience manager I am using so its array doesn't grow infinitely. Someone with a level above that just didn't seem reasonable.
But it's technically possible like your example shows, so I might have to find a solution to that ...
Thanks for reporting!
Hello,
A few days ago, my headadmin sent me some errors that we were having on my server. I was not sure what was going on, but DeathControl has been lagging, and crashing the server with errors.
Click: http://pastie.org/4609018
@netraameht
Yup:
If you die (any reason) you will drop all your items, exept emeralds. You will lose just 50% of the emeralds. Is this possible?