[UNSUPPORTED][MISC] Tombstone v1.3.6 - A deadmans chest plugin for Bukkit [1317]

Tombstone - A deadman's chest plugin
Version: 1.3.6
CraftBukkit: 1317
This plugin support SuperPerms. Please do not ask about setting up SuperPerms in this topic, ask here: http://forums.bukkit.org/threads/permissions-faq.25080/

Plugin Dependencies:
Permissions (Optional)
LWC (2 or 3) (Optional)

If you want help, post the output of the "version" command, and make sure you're running atleast the version specified in the topic title.
Please post your server log when asking for help with tombstones not spawning
Do not bother asking for help if you killed the player using anything other than basic attacks. I do not guarantee support for any plugin-based attacks or deaths such as /kill!

=============
Description
=============
Save your players' inventory from disappearing when they die.
I used Deadmans Chest in hMod and thought it was a great plugin, so I started my own version for Bukkit.

Download: http://thedgtl.net/bukkit/Tombstone.jar
Source: https://github.com/TheDgtl/Tombstone

=============
Features
=============
If the player is carrying a chest when they die, place that chest and fill it with as much of their inventory as possible
If the player is allowed, and is carrying two chests, a large chest will spawn to catch all of their inventory
Possible for specific groups/players to be given free chests with no need to carry one with them
Any items that won't fit in the chest will still drop to the ground!
Supports the Permissions plugin, will default to allowing everyone to use basic tombstone if not available
Supports LWC for chest AND sign protection if it is installed
Configurable timeout for LWC unprotection
Configurable timeout for destruction of tombstones, works in unloaded chunks as well
Quickloot support, right click the sign on a tombstone to loot all items in it (Your tombstone only!)
Place a sign on top of the chest with a configurable template
The ability to point your compass at your tombstones!
Supports "SuperPerms"

=============
Config Notes
=============
If you are going to be giving your players a free chest/sign, but don't want them to be able to retrieve those as extra items, you can now set the noDestroy option in the Tombstone config file.
If you do set the noDestroy option, it is highly recommended that you set a timeout for Tombstone removal, because even once LWC is disabled the chest is still not destroyable by any means other than quicklooting it.
With noDestroy enabled, if a player dies without a sign, then their chest will be indestructible until it is removed by Tombstone itself.
It is not recommended to use the noDestroy option without the destroyQuickLoot option

=============
KNOWN BUGS
=============
None?

=============
Config
=============
lwcEnable - Whether to use LWC if available
lwcRemove - Whether to remove LWC after a specific timeout
lwcPublic - Set to true to set LWC protection to Public instead or removing
lwcTimeout - How long to wait before disabling LWC on a tombstone (in Seconds)
tombSign - Whether to place a sign on the tombstone
removeTime - How long to wait before destroying a tombstone (in Seconds)
tombRemove - Whether or not to destroy a tombstone after a timeout
playerMessage - Whether or not to show messages to the player
saveTombList - Whether to save a list of tombstones between server reloads
destroyQuickLoot - Set to true to destroy the chest/sign on quickloot
noDestroy - Set to true to disallow any player from destroying a tombstone (Other than quickloot)
noInterfere - Set to true to stop tombstones from being created next to other chests (Items are dropped to ground instead)
logEvents - Whether to print some "useful" information to the server terminal.
skipBuildCheck - Set whether to skip the blockPlace check (True to bypass region protection) (Default false)

=============
Sign Template
=============
The sign template is stored in plugins/Tombstone/sign.tpl
The following variables are able to be used in the sign template:
{name} - The players name
{cause} - The cause of their death, or their killers name if it was a player
{date} - The date of their death
{time} - The time of their death

The sign template is 4 lines correlating to the 4 lines of the sign. The maximum length
of a line is 15 characters. The default sign template is as follows:
{name}
Killed By
{cause}
{time}

=============
Permissions (Either via SuperPerms, or Permissions 2.x/3.x)
=============
tombstone.use - (Default) Allow the player/group to use the tombstone mod
tombstone.freechest - Allow the player to get a chest whether they are carrying a chest or not
tombstone.large - Allow the player to spawn a large chest if carrying two chests and if one will fit
tombstone.lwc - (Default) Protect the placed chest if LWC is enabled
tombstone.sign - (Default) Whether the player gets a sign on their tombstone chest
tombstone.freesign - Allow the player to get a free sign whether they are carrying one or not.
tombstone.quickloot - (Default) Whether to allow a player/group to quickloot by right clicking the tombstone sign.
tombstone.admin - Allow this user to destroy other players tombstones.
tombstone.cmd.tomblist - Allow this user to use /tomblist
tombstone.cmd.tombfind - Allow this user to use /tombfind
tombstone.cmd.tombreset - Allow this user to use /tombreset

=============
Commands
=============
/tomblist - List all your tombstones
/tombfind - Gives you a direction from your current location to your tombstone. Use with /compass (Sync'd to CommandBooks /compass)
/tombreset - Doesn't do anything.

=============
FAQ
=============
Q) Can you add support for {PluginX}?
A) No.

Q) Player items are being duplicated, and I'm using SlowHealth, whatsup?
A) http://forums.bukkit.org/threads/mi...ugin-for-bukkit-1000.3923/page-18#post-550275

=============
Changes
=============
[Version 1.3.6]
- Added 'skipBuildCheck' option
[Version 1.3.5]
- Fixed accidental clearing of /tomblist on quickloot
- Added SuperPerms support
- Do a build permission check so we don't spawn a chest in protected areas
[Version 1.3.2]
- Apparently LWC 3.30 had a change in API that wasn't documented, yay
[Version 1.3.1]
- Recompiled with LWC 3.30
[Version 1.3.0]
- Added sign template
- Tombstone no longer created in void death
- Re-enabled the compass for /tombfind

More Changes (open) More Changes (close)

[Version 1.2.9]
- Fixed free double chests
- Made freechest/freesign default to isOp() without permissions
[Version 1.2.8]
- Added logEvent option for debug purposes.
- Do a 3x3 check for a block to place chest.
[Version 1.2.7]
- Check properly if we're placing a big chest for interference
[Version 1.2.6]
- Fixed issue with name length
[Version 1.2.5]
- Option to bail on tombstone creation if it will interfere with another chest.
- Check tombstone stuff more often (Every 100 ticks (5 seconds))
[Version 1.2.4]
- Fixed sign drop bug when destroying with timeout.
[Version 1.2.3]
- Fixed a bug in /tombfind with invalid input
[Version 1.2.2]
- Moved playerInteract to Highest priority since we remove a block.
- Added check to make sure the tombstone is a chest before we doing anything.
- Other general checks
[Version 1.2.1]
- Made /tombfind a bit more useful, will give a NESW direction.
[Version 1.2.0]
- Added compass commands.
[Version 1.1.8]
- Right-clicking a chest will quickloot/destroy if you have noDestroy/destroyQuickLoot enabled
[Version 1.1.7]
- Fixed quicklooting in RB670
[Version 1.1.6]
- Fixed some owner comparisons.
[Version 1.1.5]
- Moved setting "plugin" to onEnable
- Moved setLine() outside of scheduler
[Version 1.1.4]
- Added more LWC checks
[Version 1.1.3]
- Added tombstone.admin
[Version 1.1.2]
- Fixed loading tombstone list after server restart
- Check if player is online before sending tombstone messages
[Version 1.1.1]
- Updated to latest RB
[Version 1.1.0] - Only updating for LWC2 from here on
- Changed versioning scheme
- Changed loading of permissions/LWC
[Version 1.09]
- Updated sign update code, should work better
- Updated for LWC2, there is now an LWC1 build, and an LWC2 build
[Version 1.08]
- Configurable tombstone list storage
- Allow LWC to be set to Public instead of disabled
- Allow destroy on quickloot
- Allow tombstones to be "invincible" besides quickloot
[Version 1.07]
- Fixed a bug in which protected chests could be destroyed.
- Messages to players can be turned off.
[Version 1.06]
- Item-dupe fix broke plugin, fixed
[Version 1.05]
- Re-compiled for b522 to fix ItemStack.equals error
[Version 1.04]
- Small permissions handling update
- Inform player if we run into a casting problem.
[Version 1.03]
- No longer treat GM as a special case, just load it as Permissions 2.0 like the author intended
[Version 1.02]
- Support Permissions 2.0/2.1
- Support GroupManager
[Version 1.01]
- Fixed a Null Pointer Exception when chests are destroyed
[Version 1.00]
- Added ability to remove chests without needing LWC
- LWC and remove thread are now a sync task
- Right-click sign to quickloot. Permission added.
- Better Permissions handling
- LWC protects sign
- Only create a large chest if needed
- Deactivate LWC protection when sign or chest is destroyed
[Version 0.06]
- Implemented tombstone signs
- Changed message if LWC is enabled to say how long before unprotect/destruction
- lwcTime of 0 now indicates that LWC protection never expires
[Version 0.05]
- Added config file
- Implemented chest removal
- Configurable timeout
- Toggle LWC usage via config
[Version 0.04]
- Added LWC timeout
[Version 0.03]
- Added LWC support
- Made Permissions optional instead of required. Default without Permissions is allow all to use
[Version 0.02]
- Initial Public Release

 

@Jessicadawn You're aware I didn't even reply to your post, right?

Now, as for my plugins, I will keep them updated to the latest RBs, but I will not be taking suggestions, nor offering support besides the first post, as that outlines everything you need to know for any of my plugins.

 

Sounds solid. Tombstone has been a lifesaver for my girlfriend. Not sure what she'd do without it

 

Same here. My partner would not have allowed me to turn mobs on without this plugin

 

Your plugin helps me not flood the economy with ill-gotten admin diamonds. Hope to see updates in the future. We're not all ungrateful children! :]

 

You aware I said thats whats you SHOULD of said. I understand you didnt say anything.

 

Since you have ceased all updates (except bukkit compatibility) and support I doubt you would be willing to add in MySQL support (Tombstone is holding me back on updates as I'm dammed if I'm removing it)

I have no way to program java besides guess work as I have no idea how to set-up eclipse else I would try this myself


...just looked over the source code, would I be correct in assuming that you do not use the bukkit.yml?

 

Tweaked the BoundaryKill sourcecode and I can confirm that using player.damage(x) rather than .setHealth(x) works fine with Tombstone (ie. previously tomb chests were not created and now they are) and I'm now running this tweaked code on my server (have also suggested this fix in the BoundaryKill thread).

 

No MySQL will not be added.

 

Is Tombstone dependant on the bukkit.yml, as in can I cahnge bukkit.yml to MySQL without breaking tombstone

 

Tombstone uses it's own flatfile database, it doesn't use bukkit.yml.

 

Thank you for confirming that for me, now I can upgrade everything without worrying about losing Tombstone

 

Just one more user adding a big "Thank You!" for taking the time to make this plugin public so that other people have the chance to use it on their server. Unlike some folks, I understand that my use of your hard work is a privilege, not a right.

 

I just saw a little bit of good news for those who use Tombstone with BoundaryKill or any other plugin that uses setHealth. With the 785 build of CB, setHealth(0) will trigger EntityDeathEvent so those changes to the plugins won't need to be made for Tombstone to trigger the death event.

 

Nice (just after I made my changes too ). Will let Boundarykill know.

 

Awww... you developed this one too... Now I am starting to really hate those an... those people... Mehh... it's good enough that it currently works so thanks for another great plugin...

 

Yeah - Drakia is a prolific plugin writer, many great plugins.

@Drakia

Thanks

 

Drakia,

Love this plugin as do my players. Thank you so much for taking the time to supply it to everyone. Would it be possible for you to add an "updated date" in your OP so we know if a new version comes out since we last one? Or maybe have a some comments in the config file with the version number so we can cross reference it with the ones listed here? If this information is already provided somewhere then I apologize, I looked around and couldn't find it.

Thanks,
Minirova

 

Working great, although some minor gripes with the messages (I can't tell if this is LWC doing this or TS, so I thought I'd ask in here first).

As the owner of the tombstone, when quicklooting:
"Notice: That Private Chest is locked by %owner."
"[Tombstone] Tombstone quicklooted!"

As any other player (when attempting to access the chest):
"Notice: That Private Chest is locked by %player."
This Chest is locked with a magical spell

How do I go about killing off the first message in the first instance (it seems redundant, as the player is already aware that it is their tombstone by the sign) and killing the second message in the second instance?

 

Love the concept of this plugin - dont stop rocking.

 

when you die, tombstone does not appear and all items are scattered ad invisible. running 803 with no errors popping up in console

 

Did you give your users permissions to the following?

Code:

tombstone.freechest - Allow the player to get a chest whether they are carrying a chest or not
 tombstone.large - Allow the player to spawn a large chest if carrying two chests and if one will fit
 

If not, they will have to carry the chests on them.

 

Good for you. Does it say it supports 812?

 

i keep gettting this on 812


01:33:31 [SEVERE] Could not pass event PLAYER_INTERACT to Tombstone
java.lang.IllegalArgumentException: Listener already listening
at net.minecraft.server.Container.a(SourceFile:28)
at net.minecraft.server.EntityPlayer.syncInventory(EntityPlayer.java:70)
at org.bukkit.craftbukkit.entity.CraftPlayer.updateInventory(CraftPlayer.java:215)
at net.TheDgtl.Tombstone.Tombstone$pListener.onPlayerInteract(Tombstone.java:567)
at org.bukkit.plugin.java.JavaPluginLoader$9.execute(JavaPluginLoader.java:299)
at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:58)
at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:310)
at org.bukkit.craftbukkit.event.CraftEventFactory.callPlayerInteractEvent(CraftEventFactory.java:162)
at net.minecraft.server.ItemInWorldManager.interact(ItemInWorldManager.java:209)
at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:544)
at net.minecraft.server.Packet15Place.a(SourceFile:57)
at net.minecraft.server.NetworkManager.b(NetworkManager.java:214)
at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:75)
at net.minecraft.server.NetworkListenThread.a(SourceFile:105)
at net.minecraft.server.MinecraftServer.h(MinecraftServer.java:394)
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:308)
at net.minecraft.server.ThreadServerApplication.run(SourceFile:422)
01:33:35 [INFO] Honorfull: Rofl -.- I took shelter in a house next to my house >.>
01:33:39 [INFO] svenska142: !!!!!!!!!!!!!!!!!!!!!!!1
01:33:41 [SEVERE] Could not pass event PLAYER_INTERACT to Tombstone
java.lang.IllegalArgumentException: Listener already listening
at net.minecraft.server.Container.a(SourceFile:28)
at net.minecraft.server.EntityPlayer.syncInventory(EntityPlayer.java:70)
at org.bukkit.craftbukkit.entity.CraftPlayer.updateInventory(CraftPlayer.java:215)
at net.TheDgtl.Tombstone.Tombstone$pListener.onPlayerInteract(Tombstone.java:567)
at org.bukkit.plugin.java.JavaPluginLoader$9.execute(JavaPluginLoader.java:299)
at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:58)
at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:310)
at org.bukkit.craftbukkit.event.CraftEventFactory.callPlayerInteractEvent(CraftEventFactory.java:162)
at net.minecraft.server.ItemInWorldManager.interact(ItemInWorldManager.java:209)
at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:544)
at net.minecraft.server.Packet15Place.a(SourceFile:57)
at net.minecraft.server.NetworkManager.b(NetworkManager.java:214)
at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:75)
at net.minecraft.server.NetworkListenThread.a(SourceFile:105)
at net.minecraft.server.MinecraftServer.h(MinecraftServer.java:394)
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:308)
at net.minecraft.server.ThreadServerApplication.run(SourceFile:422)

 

See previous post

 

Working mostly ok for me in 814 Quickloot requires me to rightclick on the sign then open the chest before I get all the loot but I didn't expect it to work at all, yet - so it's all good

Edit: Working fine in 818 - quickloot has no problems now.

 

Quick question/problem/bug: one of the maps on my server does not have bedrock (or the like). IE if you were to 'jump off the edge' you will fall into the void and die. Now this wouldn't normally be an issue except that when this happens it seems that tombstone still stores the information.

Here is how I found this; I jumped into the void and died. Later, after a server restart, a user was asking me why their was a chest floating in the sky (pretty high up as well). Upon closer inspection I discovered that it was my tombstone.

This isn't really a huge issue but it kind of breaks the feel of the plugin if chests end up floating in the sky after a death from the void. I can't really think of a way to fix this or a feature that would 'make sense' so just count this as me rambling >.>

I guess maybe a feature request to be able to select the mode-of-death in which the tombstone is spawned?

 

small bug:
if I am protecting an area with WorldGuard, someone dies in that area, they leave a chest, which is fine, but the chest isn't being removed after the specified time.

 

Great plugin!

Is there a way to make chest that cant spawn to be created in some kind of grave yard? Or maybe an option to always move chests to o set location when someone dies? If you have some plugin bugs that spawn someone in the ground they wont get a chest, maybe a /summon chest command?

Anyway its a great plugin, im just giving you some ideas if you want to add more features

 

Those are not options I will be adding. If a person suffocates (In a block) there's no reliable way to determine where to place a chest. Just as with in 1.3.0 I'm removing chest spawning on void deaths (As it spawns the chest at a random Y location)

 

Is this plugin also work fine with b935?

Thx for your help!