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.
Bone008, please fix this:
When using MultiVerse plugins group
(http://forums.bukkit.org/threads/edit-misc-tp-fun-multiverse-2-3-world-management-bukkitdev.3707/)
and Essentials plugin group (Essentials\spawn.yml) :
spawns:
default:
world: SandBox
x: -106.0
y: 226.0
z: 236.0
yaw: -15.681152
pitch: 74.09972
vip:
world: Private-VIP
x: -252.0
y: 212.0
z: 240.0
yaw: 295.0
pitch: 73.0
it is possible to die in SandBox world and respawn in Private-VIP world with restored inventory. (On our server SandBox world and Private-VIP world have different inventories and spawns).
@Bone008 Thank you for your reply, it makes a lot of sense. I understand now how to use this feature and will try to make sure exploitative situations caused by other players are reduced to a minimum. :-)
@Katorone
That FIFO solution could be possible, but it would require lots of work compared to the benefit of it. On most servers, that situation almost never happens (that the player dies unintentionally again before he can get the inventory back).
And I don't think doing it intentionally can be considered "abuse". With the command method, money is only charged when they actually perform the back-command. That's more or less the point of the command method: a player can decide whether he wants to pay to get back his inventory, or just let it drop where he died if it's not worth it.
If he intentionally kills himself to avoid cost, there is no benefit because it will still drop where he died previously (that would be the same as if he just let the timer expire or disconnected). The advantage that he would actually pay for (having the lost items back in his inventory) is not really there.
@Beatkidz That's more or less what happens with the
loss-percentage
option (at the moment). Assuming you set it to 50% and the player has 10 different stacks of items, 5 of them will be randomly chosen and dropped, the rest will be kept.Request: I'm looking for a way to make random things drop out of your inventory. So you Might only drop 3 things but they are completely random.
The problem is that people were getting killed at the spawn point. I'm aware that this is an issue I could have prevented by disabling pvp in that region. However, players spawned, got killed, respawned, got killed, etc. The solution I'm proposing is that the inventories become some sort of FIFO, and players have to do the /death back command for as many times as they died with a non empty inventory. Or allow a total inventory to be filled up and drop all items that flow over. This way, people that are stuck in a dying loop don't get punished.
The way it is now also opens up the system for abuse. People can die, get their items stored, but instead of paying to get their items back they suicide some way and reclaim the items without paying.
@Katorone
No. But what else should be done? If they die again while they still have stored items, they would have to have 2 different inventories stored at the same time. So the consequence is to drop the old inventory and store the new one. If you can't live with that, the only option is to switch to the automatic method where you don't have to type a command at all.
I'm sorry if this is in the explanation somewhere. When people get killed before they had the chance to do /death back, all their items drop on the floor. Is there a way to make the plugin not do this?
I just released v1.6, it mainly fixes the issues with experience and adds a new command!
@KnightsOfTables Uh, seems like an appropiate feature, but I have no idea how to implement it into the configuration system. It is only an option for the PVP cause, so it wouldn't fit as a general setting.
Maybe I'll find a place when I finally overhaul the whole system, but I don't know when this is going to happen.
@kozzy68 I wanted to combine it with the suggested feature that the position of the items are kept again, because it is about the exact same piece of code. But both of it takes up lots of work that I couldn't afford for this update (I had to fix the severe experience issue first). But will be there soon!
Hi how are things with percentage item split formula going ? It seemd you nearly got up to it. (suggestions section)
@KnightsOfTables
I fully support that feature request :)
Is it possible, if when a player is killed by another player, if he chooses to keep his stuff in exchange for some money, if that money could go to the player who killed him? Would be super useful in our case.
Great plugin else-wise :)
@Bone008
I'm using essentials
@richboos
You can set the option "method" to "command" for the respective death cause and player's will have to perform
/death back
to get back their items & pay the money for it. You can configure a timeout as well. More info in the Configuration section.@Photonlance
I have a couple of concepts (somewhat similar to yours), but as I mentioned earlier it takes time which I don't have right now:
Possible to implement either a player /death on sort of toggle?
Or instead let them /accept or /reject upon death? This way with economy tied in players can avoid paying when they died with nothing worthwhile anyway.
add 2-nd configuration for another group of users and permissions for it like deathcontrol.use2 or deathcontrol.use.2
@DjBuRnOuTQc
It is compatible with all Permissions plugins that make use of SuperPerms (bukkit's permissions API). See here. I don't know if bPermissions does that, but I think it does.
Anyway, as Vault is already an optional dependency now, I might as well use its Permissions features as an option. Not very reasonable in my eyes, though.
@drdeft That's something that takes a lot of work and restructuring of the code. My spare time is not much right now so new features can possibly take their time. But there isn't much left on the To-Do list, so it will very likely be the next (bigger) thing to add.
Does this plugin is compatible with other permissions plugins? I'm using bPermissions 2.9.1 and permission nodes doesn't work.
make cause settings able to be mapped to different permisson nodes (per-group and per-world settings)
please do this feature first =)))
@rhinez0r I am using bukkit's native permissions API ("SuperPerms"). I've heard that PEX kind of doesn't fully support that. I just tested it with PEX, seems to work for me when I enable the "superperms" thing in PEX's config. If you set "use-bukkit-permissions" to false in DeathControl's config, it gives all players
deathcontrol.use
, and all ops the rest (bypassing cost, administrating, ...).When having the option enabled, you have to give the permission
deathcontrol.use
to evreyone who should be able to use the plugin.Would LOVE to use this on my server.. but I can't seem to get it working with PEX. Any hints? I've tried toggling use Bukkit Perms on and off. It either gives ALL players the benefits or NONE of them. Doesn't seem to support pex permissions.. What am I doing wrong?