This plugin stores a player's inventory in a chest on death for later retrieval. It has many options, but configuration and use has been kept as simple as possible.
- Places a single or double chest at player's death location containing the player's inventory
- Optional sign placement on chest, showing player name and death date
- Configurable list of block types that chests can replace
- WorldGuard, GriefPrevention, PreciousStones and Towny aware, will not place a chest where the player does not have access. Enabled individually.
- Option to check protection plugins on chest access. Enabled individually, disabled by default.
- added WorldGuard 7.0 compatibility.
- Searches a configurable distance from death location to find a suitable chest location
- Optionally require players to have chest(s) in inventory
- Chest protection allows only owners access. Also makes chests explosion proof!
- Optionally allow player's killer to access their chest, for pvp looting.
- Prevent concurrent access to chests when killer looting is enabled.
- Optional quick-loot feature allows one click (sneak-punch) chest looting
- Configurable expiration time for death chests, at which point they will break and drop their contents
- Custom messages and language localization
- Per world enabled in configuration
- Uses sqlite for persistent storage
- Prevents creative mode players from opening death chests
- Optionally prevent players from placing items in death chests
- Optional sound effects!
- A perfect compliment to SavageDeathCompass and SavageGraveyards
||Default player permissions||true|
||Enable death chests for player.||true|
||Allows player to quick-loot death chests by sneak-punching.||true|
||Allows placement of double chests if necessary.||true|
||Default administrator permissions||op|
||Overrides creative mode chest opening restriction.||op|
||Allow player to loot other player's chests.||op|
||Allows use of plugin reload command.||op|
||Allows a user to view a list of their death chests and locations.||op|
||Allows a user to view a list of other players death chests and locations.||op|
/deathchest list [username]
Displays a list of player's death chest locations. Requires deathchest.list permission. If a player has permission deathchest.list.other, they can supply a username to list another player's deathchests, or type an asterisk (*) to list all deathchests.
Reloads configuration file and messages. Requires deathchest.reload permission, which is child node of deathchest.admin.
Displays version info and some config settings. Requires deathchest.status permission, which is child node of deathchest.admin.
/deathchest help [command]
Displays a brief help message and command usage.
Put the jar in your plugins folder and restart your server. Edit the generated configuration file to your liking, then reload the plugin settings with the
/deathchest reload command. No server restart necessary!
All configuration changes can be made without needing to restart your server. Just issue the reload command when you are satisfied with your settings in config.yml.
Source code for this plugin is hosted on github and distributed under the GPLv3 license.
Hello! How to name the worlds in which we want death chests enabled?
I've seen in previous comments that the Nether should be named world_nether but for other dimensions, added by other mods?
For example, with the LOTR mod, i get a world/DIM100 (MiddleEarth) and world/DIM101 (Utumno). Would i need to use DIM101, world_DIM101, Utumno (the name i gave it in MultiverseCore), world_utumno?
Thanks in advance for your guidance.
The plugin was made for use in survival worlds. In survival worlds, It is usually important to keep players with access to creative mode from giving away items to survival players. Therefore, items in a player's creative inventory are not placed in chests in the unusual event of a creative player dying, and creative players are also prevented from opening chests so they can't use them as a means of bypass to give items to survival players.
Since players with creative mode can use the creative inventory to easily replace lost items, there really is no need for death chests for these players. Also, creative players don't usually die, except by the /kill or /suicide commands.
Thank you!! I like your plugin, but I have a problem ... I want it to work when I'm playing in game mode 1 and I can not. Why? :c
That's a lot more complicated than it sounds, and I'm not sure that it is a feature that could be easily added to this plugin as it stands. I will consider the possibly for a future version. Before I wrote this plugin, I used one that had this feature, but I found it inconsistent in how it placed the gravestones, and sometimes destructive and potentially a tool for grief.
It's possible, but it runs counter to the original goal of the plugin, which was to allow players to be able to retrieve their loot, even if it took longer than the five minutes before items despawn, but not make it so easy that dying had no repercussions. I wanted them to have to expend some effort to retrieve their inventory, rather than just using the /back on death command.
A better option for this functionality would be a separate plugin that manages the home chests, and removes items from a players death drops when they die and places them in the home chest. In the latest version (beta-3), I changed the priority of the player death listener so that other plugins can manipulate player death drops before the death chests get stocked. This was a request to make this plugin work with DropProtect.
Also it should be noted that this plugin is open source, licensed under the GPL, and the source code is available on github. So it's possible and I encourage anyone to fork the project if they would like to implement their own features, as long as they follow the GPL and make their changes available if they distribute it.
hello, very excited by this, i've being hoping for a good deathchest plugin for 1.8,
but could you add a perm to create a "home" deathchest? where your items will end if you die in that world and only spawn a chest if that home chest is full?
that was my players' favorite feature of the old deathchest plugin we use
Could you please add an option to place a gravestone where the player died and place chest under the ground if option is enabled? Would be even more awesome if I could use my own schematic as gravestone.
My server crashes mainly when I goto leave the nether. So I can enter but not leave
Will add world_nether
You only need to add the nether (world_nether) if you'd like death chests to deploy there. The 'another_world' entry is just an example, you can safely remove it without effect. It shouldn't cause issues in the nether either way, but just out of curiosity, what sort of issues are you having?
Do I need to add the nether to the following
As I am having nether issues and the last plugin that was installed was this one. I am just wondering and asking as I am lost as to what might cause this issue. trying to eliminate one by one. Thank you
That's exactly right. It lets you grab the entire contents of a chest with a simple sneak-punch.
Anything is possible, but I think this would over complicate the plugin. For example, how would one decide what items to allow the killer to take?
The best bet would be a separate plugin to accomplish this.Other plugins can detect my death chests by checking for block metadata on chests (or signs) with the key 'deathchest-owner'. The value stored is the owner's uuid. If they were killed by another player, another key/value pair is assigned with the key 'deathchest-killer' and the killer's uuid.
With quick-loot one can get all chest's contents with a sneak-punch (click), so that you no longer have to drag (or shift+click) every single item to your inventory.
What does quick loot actually do? I'm confused by it.
Also, I'd like the killer to be able to open the victims chest but only take X amount of items so the killer gets reward, but the player doesn't lose everything. Something you can do?
I've just uploaded a new version, 1.3.1-beta2. Can you download and try that once it's approved by bukkit staff? I had included the sqlite library in my project, but bukkit/spigot already provides one, and this can cause version conflicts. I removed the sqlite library from my plugin. Hopefully this will solve your issue.
Nope nothing was changed. It happens if I restart or reload the server. It happens literally every single time unless I completely stop the server and delete the sqllite database each and every server restart.
This is the error I get during a complete server restart with a proper shut down.
This is the error I get when I try and do any command.
These are the current plugins I have installed.
I really hope this issue can be resolved, this plugin is really great for the type of server I am using it on and I can't find anything like it any where else.
I have uploaded a new version, which
will be available for download as soon as it is approved by bukkit staffis now available for download. It's not as thoroughly tested as I would have liked, due to being unable to coordinate with my main tester, so it is marked as beta. The WorldGuard bug is definitely fixed, and chest protection should now be working properly.
If you find an issue, post it here, and I'll get a fix out asap. I want to squash any and all bugs in the current version before implementing any new features, so your help in testing is appreciated.
Is it possible that file permissions on the data file or directory were changed? I'll keep an eye out for another possible cause of this issue.
When is the update being uploaded :(
This plugin is AMAZING! But I am now having an issue. It was working fine for me today when I first installed it but for some reason it is no longer working. Here is the error I am getting: Your text to link here.... I recently updated to the latest bPermissions, I don't know if that is the problem but switching back to check is a bit of a hassle because of the UUID conversion.
Edit: I was able to fix the problem by deleting the sqllite file. I will leave this here though just in case it is some sort of bug but I don't know so I didn't change anything besides restarting the server a few times and updating and converting permission files and plugin.
Edit: The plugin doesn't load the sqlite or yaml files if the server is reloaded. Not to sure if it is meant to be like that so I am just informing you.
Oh sorry, i'm not a native english speaker, what i wanted to say is that YOU deserve a big