[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


    *Points to backpack.*
  3. Offline


    *points to my reply*

  4. Offline


    I didn't use backpack. Does it throw out ALL inventory? so it must have hook on death event and might conflict with Tombstone
  5. Offline


    Backpack puts all the inventory slots into the dropped loot list that is in the Entity Death event. It lets other plugins decide how to handle it.
  6. Offline


    It would depend on which is calle first. If it calls tombstone first it'll drop anything other than the basic inventory. If it calls backpack first this plugin is coded in such a way that everything it can fit will be put in the two chests and the rest is left to drop on the ground, no matter the size of the droplist.
  7. Offline


    I intentionally used the lowest priority to get called first.
  8. Offline


    Then it should be completely fine, anything that won't fit into the large chest will just be dropped to the ground.
  9. Offline


    Aw. We couldn't get like 4 or 5 chests instead? ;)
  10. Offline


    Nope, having more than two chests beside eachother leads to client glitches first of all, and the code required to place multiple single/large chests around the player is just too irritating to think about right now ;)
  11. Offline


    for some reason when they die not only does there items drop outside the chest but also go into the chest???

    cb 432
    --- merged: Feb 28, 2011 2:27 PM ---
    anybody know a fizx to this?
  12. Offline


    I can't figure what do you ask. The point is to get your items in the chest, what's the problem?
  13. Offline


    There is an issue in Bukkit currently where a CraftBlockState (getBlockState()) may not be able to be cast into a Chest object, I don't know what causes this as it's sporadic as to when it happens, and currently I know of no way to fix it.
    --- merged: Mar 2, 2011 7:35 AM ---
    @Stephen92 I have never encountered that error, and unless you can give more details (Server errors?) then there's nothing I can do to fix it. There should be absolutely 0 way for that to happen unless another plugin is interfering with the way this plugin operates.
  14. Offline


    Thanks for a great plugin I use for my family's LAN SMP.

    I've two feature requests and one configuration question.

    First feature request:
    Tombstone sign that can be left in place after chest removal.
    Current state - When removing death chest, the tombstone sign located on top is "unplaced" and loses its desired information.
    My thought - Place signs adjacent to chest if space available.
    Alternative - When chest emptied, the chest is destroyed and sign is "replaced" at former chest location retaining its information.
    Alternative - Tie into or replicate the various "trading via a sign" plugins to do without a chest entirely.

    Second feature request:
    Configurable list of chest-authorized items to fine tune death penalty.
    Current state - Everything goes into chest (if space available), removing all death penalty.
    My thought - Permissions or Tombstone list of items excluded from death chest and simply tossed onto the ground, best if capable of group or per-player settings.

    Configuration question:
    Is there a setting where, if chest or sign is unplaced the chest or sign is destroyed?
    Current state - Players are collecting chest and sign, giving them an extra benefit for dying.
    Assume my settings are that players get a free death chest and tombstone sign.
    I've not tried playing with the "Configurable timeout for destruction of tombstones" but suspect it simply extends the total time they have to get back to their death point before everything is lost, and that they can still collect the chest and sign if within the time limit.

    If the answer on my configuration is no, I'll probably revert to no free chest but still give the sign for the humor.

    I see they still have to watch out for creepers...the explosion apparently destroys the chest [evil chuckle].
    With my creeper skin modded to mostly transparent (it's "camocreeper"), all I need now is for WildGrass ported to bukkit and game tension will be amazingly fun.
    Even with just camocreeper, it's like a US Vietnam-war movie.
    "Watch my back as I axe this tree"
    "Wait saw mvmnt"
    [end transmission]
  15. Offline


    I have the same problem, everything drops outside the chest. No error messages in console.
  16. Offline

    Lunar Delta

    I've been getting a lot of :

    15:26:59 [SEVERE] Could not pass event ENTITY_DEATH to Tombstone
    java.lang.NoSuchMethodError: org.anjocaido.groupmanager.GroupManager.getPermissi
            at net.TheDgtl.Tombstone.Tombstone.hasPerm(Tombstone.java:206)
            at net.TheDgtl.Tombstone.Tombstone$eListener.onEntityDeath(Tombstone.jav
            at org.bukkit.plugin.java.JavaPluginLoader$39.execute(JavaPluginLoader.j
            at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.jav
            at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.j
            at net.minecraft.server.EntityPlayer.a(EntityPlayer.java:111)
            at net.minecraft.server.EntityLiving.a(EntityLiving.java:393)
            at net.minecraft.server.EntityHuman.a(EntityHuman.java:378)
            at net.minecraft.server.EntityPlayer.a(EntityPlayer.java:137)
            at net.minecraft.server.EntityLiving.a(EntityLiving.java:491)
            at net.minecraft.server.Entity.a(Entity.java:581)
            at net.minecraft.server.EntityPlayer.b(EntityPlayer.java:253)
            at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:260)
            at net.minecraft.server.Packet10Flying.a(SourceFile:126)
            at net.minecraft.server.NetworkManager.a(SourceFile:230)
            at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:75)
            at net.minecraft.server.NetworkListenThread.a(SourceFile:100)
            at net.minecraft.server.MinecraftServer.h(MinecraftServer.java:357)
            at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:272)
            at net.minecraft.server.ThreadServerApplication.run(SourceFile:366)
    15:26:59 [INFO] strangelob fell to their death
  17. Offline


    Build 493 is now the recommended CB build version. Please kick out an update to let us know it's fully functioning.
  18. Offline


    Pushed an update v1.04:
    - Small permissions handling update
    - Inform player if we run into a casting problem.
  19. Offline


    Any way of suppressing the death messages? Works great but I would like to have only HeroicDeath show up on the event.
    SweetCraft Girl likes this.
  20. Offline


    You'd have to grab a copy of Eclipse and remove them yourself, sorry.
  21. Offline


    still having the dupe issue where it goes inside the chest as well as outside and there is no error in the chat log or anything.
  22. Offline


    And you still haven't answered any of the questions I asked you before.
    There is, programatically, no way that should happen. The items are REMOVED from the drop list when they are put in the chest. They can be one place or another, it is literally impossible for this plugin alone to put them in two places.
    I've seen it "dupe" items on the ground when the chest fails, but those second items are client-side glitches and can't actually be picked up.
    Are you sure it's in the chest and on the ground, and you're not just looking at your inventory as being "in the chest"?
  23. Offline


    How does this fare with Backpack? I've got this and that installed, just wondering if they work together or not.
  24. Offline


    Never tried, should work as was talked about a page back.
  25. Offline

    SweetCraft Girl

    Too bad.

    A person may as well just rewrite everything else they can as well.

    To have one plug-in 'functionally obsolete' because it intereferes with a very popular and fun plugin that reports how each person died is pretty lame - especially considering Tombstone is a simple inventory storage on death and really does not need to interject itself into the existing RolePlay environment of the server with its additional death messages that cannot even be configured to not report.

    Was seriously waiting to use this again for the benefit of my residents will have to ask them what they want now. Heroically Hilarious Death Message reporting or a Chest on dying.... *rolls eyes*.
    Janb likes this.
  26. Offline


    Yes, they may, just like I do when I come across a problem with a plugin.
    There is a VERY small subset of people who would want no messages on death. It doesn't "interfere" with anything, it doesn't make plugins "functionally obsolete", it outputs a message to a SINGLE user on their death reporting that their items were stored instead of dropped. It outputs to ONE user whether there is a timeout on the chest for LWC or whether that chest will be automatically destroyed.
    There are 10 different messages output by this plugin, that is 10 different config values to make it so that everybody is pleased with it, or I could just leave it how I use it on MY server, since I coded it for myself and released it because I'm just that freakin' nice.

    As I said, if you want such a specific change, do it yourself, the plugin is open source for a reason.
  27. Offline


    Haha You guys are lucky he even releases anything. The server he is talking about is the one I own. And I tell him not to release his stuff. Altho thats mainy so I dont have to listen to him bitch about all the support and everything but my point stands.
  28. Offline


    ok i've checked my chatlog and theres nothing happening there, im positive that im looking in the chest, if you want logon my server and ventrilo so you can test it yourself, ip for server
    let me know if you wanna do this so I can be on for you.

  29. does anyone know if this works with multiworld? I just get it throwing the stuff on ground. :(
  30. Offline


    glad more than 2 people are having this problem.
  31. Offline


    Throwing stuff on the ground and duping items are two different things Stephen. Post screenshots and server output if you want help.
Thread Status:
Not open for further replies.

Share This Page