DeathChest
DeathChest v1.13
Features
DeathChest is a Plugin for controlling the death of a Player. Each Player can set his DeathChest somewhere in a world. If he dies, his inventory will be transferred to this chest. You can also set packages of worlds for which the Inventory will be transferred to. A Player can therefore only place one DeathChest in one World-Package.
For example: Player a has the save inventory in world c and world d. His DeathChest is located in world c. He dies in world d. His inventory will be transferred to the DeathChest in World c.
There is also the possibility to place a chest at the death of a Player. The DeathChest created by the player will always be preferred to the SpawnChest on his death location. The SpawnChest can be activated by giving the Player the Permission: deathchest.spawnchest
There is an alternative to the SpawnChest: The Grave Yard signs. When a player dies, a sign is spawned at his death location. If the player destroys it again, his Items and part of his exp will be dropped. It can be changed between Grave Yard Signs and SpawnChests, changeing the option in the config.yml.
If you want weather SpawnChests nor Grave Yard Signs, just set the Config option to: plugin.General.useDeathSpawnType: 'none'
There are also several config-options to limit the transfer to the DeathChest.
HOWTO:
How do I actually create a DeathChest?
This is simple. You just have to create a Sign above a Chest or a DoubleChest with the Letters: "deathchest" (not case sensitive) in any line of a Chest. After placing this sign, the DeathChest will be created and the first line will be filled with your name, the third line will be filled with the worldname the chest is in. (creating a DeathChest needs the Permission: deathchest.signedchest.create, saving your Inventory after you died to this chest needs the Permission: deathchest.signchest.saveto or just simply: deathchest.signchest.use (includes the permission to build, too))
With the Permission: deathchest.signchest.create.other a player can create a DeathChest of another person. Therefore line 0 has to be: "deathchest", line 1 has to be the Name of the Player.
A little guide is located at the Images: link
Commands
Detailed information can be found under Pages -> Commands link
- /dchelp: a short overview over the commands in DeathChest
- /dcreload: reloads the configuration of DeathChest
- /dcversion: displays the Version of DeathChest
- /dcpermcheck: checks all permissions of you and display them
- /dcport: ports to your DeathChest (Still Experimental)
- /dcgravelist [PlayerName]: lists all your GraveYard Signs and the time till witter
- /dcgraveport [Number] [PlayerName]: ports yourself to the GraveStone of Player with the given number
- /dcremove [WorldName] [PlayerName]: removes the DeathChest of 'Player' From 'World'
Config
Config help can be found under: Pages -> Config link
Permissions
Description for Permissions in Pages -> Permissions link ATTENTION! PERMISSIONS CHANGE WITH 1.04
Dependencies (Plugins)
Hard Dependencies:
- none
Soft Dependencies:
- one of the following PermissionPlugins: Vault, PermissionsEx, GroupManager, PermissionsBukkit
- WorldGuard: for Config-Option to check if player may place Chest on this position
- LWC : for Config-Options to check and set Player-Protection to Chests
- SecureChests : for alternate use instead of LWC
- Lockette: for alternate use instead of LWC
- BattleNight: for checking if player is in battle
Other
- If someone finds a Bug or requests a new Feature, just write it in the comments or create a ticket. I will then try to answer and fix / implement it if it seems usefull
Known Bugs
- none to know
Planed for next Version (1.14)
- Nothing new yet
- Bugfixes if found
Feature Requests:
I love the ideas ursak mentioned below and would like to see them as option in the next release as I plan on using DeathChest on my server as well.
Additionally, can you please API GriefPrevention into your next release. GriefPrevention is the next best thing for MineCraft and controls things WorldGuard and other protection suites can and won't be able to, including containers, levers, buttons, etc... not just land.... everything and is totally the choice for any Server Owner to use over WorldGuard.
Thanks
If you could add so that admin could place the chests and let players "activate" one for themselfs. even better if they have to pay for them as well.
Im looking for a way to make players able to retrieve thier stuff but to force them to have to travel to a place of my choise.
The "ultimate" way would be with a vault filled with chests placed in the main town of the server. A player buys one of the chests there and when they die they have to get to the vault in the city to get thir things. This is to make the players have to work some to get things back, not just respawn and click.
Even better still would be to also charge them for each retrieval.
So, by short: Player buys a deatchest in town, dies and have to travel to town, click their deathchest and are charged a sum to retrieve their stuff.
Anyway to turn off the fact the XP gets stored in the deathchest? I can confirm it works with 1.4.5
It even works as expected in 1.4.5 as far as I could see it. So yay. I still have the issue I mentioned in october though, since it's by design. (The GraveSign turns to death trap in lava thing.)
Just wondering if that is on purpose or an oversight in the block swapping function. ^^
Really nice plugin!
Were going to use it.
Any chance you can provide a way to change the message on the sign?
IE we would like it to say:
- The Corpse of - <displayname> - lays on the ground. -*Click to inspect*
Any chance we can get access to source so we can edit it ourselves? Save you the work?
Cheers!
When they die the signs create but when they right clic the sign doesnt give the items. Here are the permissions that my users have:
Awesome Plugin! Been looking for this for awhile now. Not sure why I never discovered it before. Awesome!!!!!
I am running 1.4.2 server and this plugin works great. I tested it and I a very happy with it. Great plugin
@TrentADoodle Yes. But I think it already runs on 1.4.2. Haven't tested it yet.
@GintaSama Well I guess I can explane this. The stacktrace you posted is not my plugin. I have no class named: "com.Belkar.DeathChests.Tombstone". If you see in a StackTrace something like: "de.tobiyas.deathchest" then you can blame me. ;)
If I saw this correct, blame him here: DeathChests (By Belkar)
are you going to update it for 1.4.2? or no?
Please explain
31.10 20:19:07 [Server] INFO at net.minecraft.server.ThreadServerApplication.run(SourceFile:539) 31.10 20:19:07 [Server] INFO at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:418) 31.10 20:19:07 [Server] INFO at net.minecraft.server.MinecraftServer.p(MinecraftServer.java:500) 31.10 20:19:07 [Server] INFO at net.minecraft.server.DedicatedServer.q(DedicatedServer.java:245) 31.10 20:19:07 [Server] INFO at net.minecraft.server.MinecraftServer.q(MinecraftServer.java:536) 31.10 20:19:07 [Server] INFO at org.bukkit.craftbukkit.scheduler.CraftScheduler.mainThreadHeartbeat(CraftScheduler.java:321) 31.10 20:19:07 [Server] INFO at org.bukkit.craftbukkit.scheduler.CraftTask.run(CraftTask.java:52) 31.10 20:19:07 [Server] INFO at com.Belkar.DeathChests.Tombstone$2.run(Tombstone.java:88) 31.10 20:19:07 [Server] INFO at com.Belkar.DeathChests.DeathChests.playerPickupTombstone(DeathChests.java:563) 31.10 20:19:07 [Server] INFO at com.Belkar.DeathChests.Tombstone.getInventory(Tombstone.java:270) 31.10 20:19:07 [Server] INFO java.lang.ClassCastException: org.bukkit.craftbukkit.block.CraftBlockState cannot be cast to org.bukkit.block.Chest 31.10 20:19:07 [Server] WARNING [DeathChests] Task #22 for DeathChests v1.2.2 generated an exception
I noticed one behaviour of which I'm not sure if it was intentional. (Running 1.3.2 R1.0) We are using the GraveYardSign function on our servers and the grave consists of a bedrock block with a sign on top, as I assume is intentional to make it otherwise indestructible and stand out to players. Funny thing is the replacement function swaps the block of death (or the one beneath, not sure) for the bedrock and on reclaiming of the Sign, swaps it back to it's former block. Under most circumstances that would be no problem, but when someone died in lava... it turns the Grave Yard Sign into a pretty mean deathtrap. We went through length to remove the lava around the Sign, so we could savely reclaim the saved items and XP. But once we destroyed the sign, the bedrock (and possibly the sign too) turns into lava, killing you all over again AND destroying all items that weren't yet reclaimed.
While this was funny at the time I noticed that, I think it could be pretty annoying to anyone else, loosing their hard earned stuff all over again. XD
Soo what I would suggest, is an option to make the plugin check, if the swapped out blocks are lava, and if they are, return obsidian instead, or just air.
Thanks for listening!
Dukey
P.S.: Also, to make the little graves more grave like, maybe swap one block in front of the sign into dirt with a flower on top, too. Nothing functional, just for the eye really. :)
@Tobiyas
I did a little bit of testing and it seems to work correctly.
Hi, why is it not avilable for the 1.3.1 CB R2?
Could you add a Death-Counter Sign? I'm currently using DeathTpPlus, which is not very compatible with Griefprevention and thinking of switching to yout plugin. Hoewever lots of my users really like the Tombstone feature where they can see their deathcount and reason of last death. Would be really great! Besides of that I personally really like your plugin - especially when you enable XP-Orbs with a high percentage and level... really funny lighningshow :D
Making a video if you want it, PM me!
Version 1.11 coming soon. (already uploaded!) Total rewrite of the transferring stuff. (hopefully bugfree now).
Getting this error: http://pastebin.com/zV49qb52
@greedseed
Yep, same here. Players are reporting that sometimes they lose all their stuff and sometimes it dupes it.