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.
@kozzy68
I replied in the thread I mentioned ...
@Bone008
60% we can say its 6/10 = 0.6 * 30 = 18 diamonds to keep and 12 to drop.So there is no complication here result is integer. Tts not best example. Complcation is when you get results like keep 0.3 diamods or 1.7 diamond. We dont like to simply round it. Instead we play dice with last item in stack if we keep it or not and odds are given by reminder 0.5 is 50% 0.3 is 30% ... . so fair formula is: [%] * [items in stack] / 100 = X.y (1.33 x=1 y=0.33 ) X is integer part and y is rest. keep = X+Radom(y) result of random function is either 0 or 1 and odds are given by y
@kalez238
Can't reproduce that with thing with the whitelists. If you added the list "diamondtools", you did also have diamondtools in your inventory when dying, didn't you?
If the issue keeps occuring, please open a thread in the issues forum and provide the following information:
Bukkit version (build number), plugin version, server log when the plugin loads as well as when you are dying, the relevant part of your
config.yml
andlists.txt
.Also, make sure you set "logging-level" in the config to 2 before you take the logs.
@kozzy68
I actually check the forums quite frequently (thanks to the non-existent notification system on BukkitDev ...), I must have missed your post (and I can't even locate it now o.O).
Anyway, your suggestion looks ... interesting.
I don't really understand the logics behind it yet, but I think it is quite what I am looking for as a replacement for the current loss system. Mind explaining it a bit more? Maybe a general forumla? And ... what would for example happen if you had a stack of 30 diamonds, and the loss-percentage would be let's say 60% (3/5) ?
Please reply in the forums, I already created a topic for it.
:) seems you have moved from forums so I just post my comment also here. Its about item droping percentage formula. Hi, use this formula it will be much better. Lets say you keep 33% (1/3) of items and you have 2 diamonds that is 2/3=0.666 = you have 66% chance to keep that one diamond. Scenario 2 when you have 4 diamonds 4/3 = 1.33 you keep one diamond always and have 33% chance to keep also second one. Its elegant fast solution and spliting diamonds would not give you any adventage. I hope its clear how I explained it might sound bit geeky but its simple. Another idea would be not bad to have option to keep items that you are wearig.
ok not sure what happened but i was editting the configuration shortly after installing it, and after about my 10th test (jumping off a cliff) the plugin just stops working all together. nothing in chat, nothing in the log. i tried reinstalling, deleting the config and the list, restarting the server, nothing fixed it. not sure what happened.
EDIT: ok so the problem seems to be the whitelist (not sure about the blacklist). i added a whitelist: -diamondtools to one of my things and then when you died nothing happened. you could still use commands but it wouldnt say anything in chat or give you any items. once i removed the whitelist part it started working again.
@zeroinfinity2
Pleas take a look at the To-Do list, I am already intending to add support for Vault.
@Negikun12
Please set "logging-level" in the config file to 2, then recreate the situation and post the server logs.
But please use the issues forum for that, it is far more easy to provide support over there than here in the comments.
It might be a known bug with v1.4, though. I just released a hotfix (v1.41) that might as well fix the problem.
doesent work with bukkit 1.1 (build #1774), on death items drop and when u type /death back, ur money is taken but it sais u have no items toget back... cause they dropped. please updated for 1.1
add support for Vault as an economy managing alternative
Please. Vault and Register don't seem to want to play nicely.
@mag0ca
Yup, was already suggested here. It is on the To-Do list at the very top, just a bit differently expressed ;)
Thanks anyway, it's encouraging to hear that the demand is high for that feature.
Just a suggestion but I think it would be handy to have this plugin save the XP as well as the items. I didn't see that in the TODO list so I figured I would just suggest it :)
@Robert107 I wanted to do that for a long time, but I never figured out a good configuration structure for it. I'll change the To-Do list to state such a functionality more specifically, so when I happen to come by it, I can think more about it and maybe find a good way ;)
@TehLampshade Unfortunately, bukkit didn't add a DamageCause for potions (even though there is one in the native server code). The issue is the same as once with the /kill command (until SUICIDE was added): when dying from a potion, no new damage cause is set, so the plugin will only see the reason for the last "normal" damage before that and use that to get the death cause. I can't do anything against that ...
@Brock_Blocking You can already separate creepers from other mobs. Set stuff in cause "MOB" to what you want, then override everything in "MOB|creeper" back to default (basically keep-inventory -> false and cost to 0 if you changed that). I'm eventually going to add separate support for all other mobs ...
Thank you all for your positive feedback :)
Very useful. The ideal plugin, no need to explain it to users, just let them play and 'ahh.'
Request: Creeper get it's own category separate from mob. Perhaps enderdragon as well. I want my creeper deaths to be punishing, I play on hard.
great plugin! could you include options for when people die from magic? (potions)
Hey! This is a great plugin, i just got a petition / idea for you!:
Could you make groups of death causes linked to permissions nodes?
I'll like to have diferent manage of deaths for different players.
For ie. i could have a group named default, that only prevent items for falling in cases of lava, falling, and creep. Then i would have a permission node named deathcontrol.group.default.
And another group named vip that prevents items for falling at all causes. And the permission node will be named deathcontrol.group.vip.
Hope you like it!
A great plugin for non-spout users! Taking this to take a look!
@Royalgamer06 Register does support it, so it should be working.
To everyone who reported an issue in the comments:\ I created a FAQ page, please check if your issue is listed there.
Otherwise please look at the new section "Reporting an issue" in the main page. Everyone with a problem or a suggestion, please post it in the forums, it is far more organized there.
Thank you
I have some suggestion.
Here is like this.
Dying with fire.
Gold nuget -> 30% loss
Wood -> 100% loss
Wool -> 100% loss
Dying with water.
Wool -> 30% loss
Map -> 100% loss
How about this? : )
Sorry my poor english : - o
06:52:37 [WARNING] [DeathControl] lists.txt: data value '1029' must be a number!
1029 isnt a valid number ? 318:1029 is the item id of an obsidian sword ... would like members with that weapon to keep it upon death :)
What's about a possibilty to define cause-groups, like
So you don't need to mess the config up with tons of duplications?
And I would love it when the items wouldn't be dropped as stacks, but as percentages. So if you have a single stack of diamonds you would just lose some single diamonds, instead of all or none.