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.
nice plugin. :)
Will there be an update to 1.9 soon? Currently experiencing an issue where all players keep their inventory even those without the permission (it is set for a certain rank). Look forward to hearing from you.
Players dying while mounted on horses are dropping all their items :( I am running DeathControl 2.1.1 on Spigot 1.8.8
Awesome plugin. Dont suppose you could easily add a variable for the players coordinates when they die
Seems that death control doesn't like death by NPC's in 1.9 using Sentry for Citizens which are both fully updated for 1.9 http://hastebin.com/demalenune.avrasm
Looks like it's something to do with arrows and stuff? only seems to happen with the Sentries that wield bows
Edit: seems like its with any deaths, falling, lava etc... same working setup from 1.8....guess your plugin needs a 1.9 update
Hi there, fantastic plugin, and it works flawlessly, but would you ever consider adding a variable for the item used to kill a player in pvp? That is the one problem that's keeping me from switching completely over to deathcontrol. Much thanks for such a great plugin!
Regards, Neo
Im having an issue if another plugin kills the player. I dont see a condition for that and a way to make it so the player keeps their items/exp.
Thanks
Im using this on spigot 1.8.7, it works perfectly. Thanks for an amazing plugin. :D
Hi Bone,
If you can, please have a look at this: http://dev.bukkit.org/bukkit-plugins/deathcontrol/forum/issues/83796-death-control-not-effective-for-mod-slots/?unread
Thanks,
Alte
Anyone know if are compatible with 1.8.X ?
Thanks.
It seems like player can get killed from fire-aspect and drop their stuff?
Any way to keep items from this way?
Does this support all 1.8 versions?
Through this plugin, can you have it so only the player keeps their "HELD" item and armor?
Would also be nice if we could damage said armor.
@drexel_levante
I don't think "player" is a valid death cause any more (it used to be an alias). Try using "pvp" instead, which mean the same thing. If I recall correctly, I renamed that at some point in the past.
@Noobsbeard
I am not sure what you mean ...
Hi there i have been usign the plugin and just notice in my console that im getting an error. says "error in conditions "cause" invalid death cause: player" every other condition plus player seems fine in the other files. Any ideas?
0.34% 1,415.01% 21.93 s 707.51 ms 0.0 0.0k Task: BukkitDeathHandler$1(Single)
1.8.6
@ZwingGX
I don't make use of the full feature set, but it has been running fine for me with Spigot 1.8.3/4.
It is works 1.8.3?
I have released v2.1.1 - a bugfix release. Only the changes noted in the changelog were made, if you were not affected by them, feel free to skip this release.
Please let me know if there are any issues. I could not test it as thoroughly as I would have liked.
@Bajads
I see, I looked at the code and it seems that I limited the data value at a maximum of 127, which was the range that all items used back in the day (written in 2011, holy shit this plugin is old).
But now for potions that is no longer enough. So that is actually an error in the plugin, sorry. However, I seem to allow higher numbers in advanced lists, so you can try writing this as your list item instead: