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
@Tobiyas
What about all the errors that comes with java7?
@Ordush This is the usual Error when you are running Java 6 or even Java 5. You need to upgrade to Java 7 (Should not break any other of your Plugins). If you use a hoster, just send him a mail. He knows, what to do. If you are running it on your personal computer, just download java 7 jre from oracle.com It will work afterwards.
I am running with the latest build of Craftbukkit (latest recommended build #2203 1.2.5-R3) Hey man, for some reason i get this error:
2012-06-08 00:26:11 [SEVERE] Could not load 'plugins/DeathChest.jar' in folder 'plugins' org.bukkit.plugin.InvalidPluginException: java.lang.UnsupportedClassVersionError: de/tobiyas/deathchest/DeathChest : Unsupported major.minor version 51.0 at org.bukkit.plugin.java.JavaPluginLoader.loadPlugin(JavaPluginLoader.java:151) at org.bukkit.plugin.SimplePluginManager.loadPlugin(SimplePluginManager.java:305) at org.bukkit.plugin.SimplePluginManager.loadPlugins(SimplePluginManager.java:230) at org.bukkit.craftbukkit.CraftServer.loadPlugins(CraftServer.java:213) at org.bukkit.craftbukkit.CraftServer.<init>(CraftServer.java:189) at net.minecraft.server.ServerConfigurationManager.<init>(ServerConfigurationManager.java:53) at net.minecraft.server.MinecraftServer.init(MinecraftServer.java:166) at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:432) at net.minecraft.server.ThreadServerApplication.run(SourceFile:492) Caused by: java.lang.UnsupportedClassVersionError: de/tobiyas/deathchest/DeathChest : Unsupported major.minor version 51.0 at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:634) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) at java.net.URLClassLoader.defineClass(URLClassLoader.java:277) at java.net.URLClassLoader.access$000(URLClassLoader.java:73) at java.net.URLClassLoader$1.run(URLClassLoader.java:212) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:205) at org.bukkit.plugin.java.PluginClassLoader.findClass(PluginClassLoader.java:41) at org.bukkit.plugin.java.PluginClassLoader.findClass(PluginClassLoader.java:29) at java.lang.ClassLoader.loadClass(ClassLoader.java:321) at java.lang.ClassLoader.loadClass(ClassLoader.java:266) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:264) at org.bukkit.plugin.java.JavaPluginLoader.loadPlugin(JavaPluginLoader.java:140) ... 8 more
@watarimon That's a very good Idea. I'll add this in the next Version :)
Is it possible to add a automatic removal of spawnchests/gravesigns after X hours?
Alot of my players doesn't seem to care about their stuff and just leave the chests all over
@rockosxerxes What does it tell you, when you do /dcpermcheck ? Do you have the Permissions set correctly?
I made my deathchest exactly as it says to, and it works, but when I die my stuff doesn't go into the chest. Why is this?
@Tobiyas
Hero
@beimeith Is on the way :) Will be finished today I guess. There will be a config option to use Secure-Chests instead of lwc. (Done and uploaded as 1.07. Will be available soon)
Hi, I have a request.
I don't use LWC for chest protection, but this instead. Do you think you could contact them and maybe hook into that to automatically secure the chests?
Thanks for a great plugin!
Upgraded to 1.06: working like a charm again :)
@watarimon
Found the Error... *Facepalm of death...*
(copy of my code): public static String createDeathChestOwn = pluginPre + "signchest.create.other"; public static String createDeathChestOther = pluginPre + "signchest.create.own";
Very embarrassing.... Temporary fix would be to switch create.own and create.other permission.
@Meloncraft set in your config: plugin.General.useDeathSpawnType : chest
Don't give Permissions to: deathchest.spawnchest.spawn
This says you use chest on death, but noone has the permission -> not usable. (I guess I will add an to the next Version)
How do you disable graves?
After upgrading to 1.04 and 1.05 my players can't create deathchests anymore. I've checked and doublechecked the permissions but it only says Build Deathchest: false on everyone but me (admin/op). I can create own and others chests...
I'm using pEX with the following permissions on the players:
- deathchest.signchest.create.own
- deathchest.signchest.saveto
- deathchest.spawnchest.spawn
Any ideas?
@Ninjatac0
I ran into some ugly problems. BPermissions does not work with world wide groups. This won't work with the plugin, as long as you don't configure everything yourself. :(
@Ninjatac0
Sure. No Problem. Should be in the next update. (Hopefully I get it done today)
Great plugin, but a quick request being if you'd be able to add compatibility for bPermissions.
@west12345
I compiled the jar with java 1.7 sdk. I guess this will be the problem :)
java version "1.6.0_26"
I wait of the Debian Repository und give you Feedback.