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

Discussion in 'Inactive/Unsupported Plugins' started by Drakia, Feb 10, 2011.

Thread Status:
Not open for further replies.
  1. Offline


    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!

    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

    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


    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:
    Killed By

    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

    /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.

    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

    [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)

    [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
    ray landers, Montag, harakiwi and 9 others like this.
  2. Offline


    When I pick up my tomb, the hp and hunger level raising to the max. Is it normal?
  3. Offline


    Tombstone does not touch either of these.
  4. Offline

    Nick Lozon

    It would be nice to have a feature that would:
    • Remove entries from the tomblist when a chest no longer exists at that location
    • Removes empty chests on the tomb list
    Maybe I'll code my own...
  5. Offline


    PermissionsEx works with this just fine. I recommend you switch over to that.
  6. Offline


    how to i take tombstone.lwc off default? I only want some peopel to have auto locking chests due to my server limits.
  7. Offline


    Learn how your chosen permissions handler negates nodes.
  8. Offline


    I have CraftBukkit Build 1221 and TombStone 1.3.6 and LWC 3.53

    The Chest isnt protected with LWC and the chest dont removes automatically after 3600 seconds.

    lwcRemove: false
    tombRemove: true
    lwcTimeout: 3600
    noDestroy: true
    logEvents: false
    lwcEnable: true
    playerMessage: true
    destroyQuickLoot: true
    noInterfere: true
    lwcPublic: false
    tombSign: true
    removeTime: 3600
    saveTombList: true
  9. Offline


    Yeah it doesn't seem like chests are getting rid of themselves, regardless of what time you set. Dangit! :)
  10. Offline


    I will look into this when I have time.
  11. Offline


    Okay i have deleted the database file and now works all fine again :)
  12. Offline


    @cr0ss Chest removal is working fine for me (Timeout set to 20 seconds).
  13. Offline


    I'll check it out by doing what wassilij did, delete the DB file. Thanks for lookin into it Drakia :)
  14. Offline

    Nick Lozon

    If someone dies on top of a chest, it will not spawn a tombstone chest.
  15. Offline


    Plugin devs put a lot of time and effort into both their plugins and their posts. Next time please read the entire post before saying it's not working right:

    noInterfere - Set to true to stop tombstones from being created next to other chests (Items are dropped to ground instead)
  16. Offline

    Nick Lozon

    I did read the entire post.

    A) I did not say it was broken; this is just a how MC functions by not allowing chests on top of each other and wouldn't expect TombStone to act in any other way. I did not see any comment on the topic, so I wanted to bounce it off the community.
    B) We assumed noInterfere meant on X and Z axis since it says "next to". This feature helps prevents against players gaining access to chests they are not intended to by dying beside a protected chest and then having access to it through the chest that TombStone creates. "next to, above or below" or something along those lines would have been a little clearer, but not a big deal.

    I appreciate the response, but don't appreciate how rude you are.
  17. Offline


    In case anyone else like me is still running a 1.7.3 server, this build works perfectly with the most recent 1.7.3 build of Bukkit.

    Great plugin!
  18. Offline


    Good plugin!
    Its working with CraftBukkit 1240 without errors :)

    When a user is killed by an other user the items drop. (for pvp purposes)
  19. Would it be possible for you to include an option to use the official PermissionSystem. Because when a SuperpermBridge from PermissionsBukkit is installed it always takes the old outdated permissions system instead of PermissionsBikkit here.
  20. Offline



    Plz add multiworld support for disable in some worlds :) thanks !
  21. Offline


    That is all handled by permissions
  22. Offline


    Permissions: bukkit: 1317
    08:19:56 [INFO] [Tombstone] Permissions plugin lost.
    08:19:56 [SEVERE] Error occurred (in the plugin loader) while disabling Tombstone v1.3.6 (Is it up to date?): null
    	at java.lang.Class.isAssignableFrom(Native Method)
    	at org.bukkit.plugin.java.JavaPluginLoader.removeClass(JavaPluginLoader.java:245)
    	at org.bukkit.plugin.java.JavaPluginLoader.disablePlugin(JavaPluginLoader.java:992)
    	at org.bukkit.plugin.SimplePluginManager.disablePlugin(SimplePluginManager.java:296)
    	at org.bukkit.plugin.SimplePluginManager.disablePlugins(SimplePluginManager.java:289)
    	at org.bukkit.plugin.SimplePluginManager.clearPlugins(SimplePluginManager.java:317)
    	at org.bukkit.craftbukkit.CraftServer.reload(CraftServer.java:384)
    	at org.bukkit.Bukkit.reload(Bukkit.java:182)
    	at org.bukkit.command.defaults.ReloadCommand.execute(ReloadCommand.java:22)
    	at org.bukkit.command.SimpleCommandMap.dispatch(SimpleCommandMap.java:163)
    	at org.bukkit.craftbukkit.CraftServer.dispatchCommand(CraftServer.java:355)
    	at org.bukkit.craftbukkit.CraftServer.dispatchCommand(CraftServer.java:351)
    	at net.minecraft.server.MinecraftServer.b(MinecraftServer.java:506)
    	at net.minecraft.server.MinecraftServer.h(MinecraftServer.java:485)
    	at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:374)
    	at net.minecraft.server.ThreadServerApplication.run(SourceFile:417)
    >version 08:24:29 [INFO] This server is running Craftbukkit version git-Bukkit-0.0.0-1126-g35eac7a-b1317jnks (MC: 1.8.1) 08:24:29 [INFO] This server is also sporting some funky dev build of Bukkit! 
  23. Try CB#1318 this could be a known bug in CB#1317
  24. Offline


    same thing.
  25. Offline


    Would love to see the possibility of having more than one tombstone sign message in the config and then picking a random one to place on the tombstone.
    wassilij likes this.
  26. Offline


    Is it possible to give one group lwc protection and not another? I was using it as a donation rank to have it protected...but looks like you can do that.
    Any permission to specifically deny protection (as its default?)
  27. Offline


    ... Learn how to do negation on your chosen Permissions plugin?
    wassilij likes this.
  28. Offline


    Is it possible for another plugin to check if a chest/sign is a tombstone? I have a user request asking me not to destroy chests that are tombstones, so is there a way to hook in? Thanks
  29. Offline


    There is no API and there is no guarantee that the functions will stay the same between versions.
  30. Offline


    Hi, great plugin.
    I have a request : Make a dynmap marker when a tomb is created
  31. Offline


    Is there any plans for an API? If not, that's ok.
Thread Status:
Not open for further replies.

Share This Page