[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


    I speak from much experience here...

    you will see a hole in the lava with a sign inside. Below the sign is the chest. If (if) IF you can find a way out to the sign in the lava (you just died, so you have nothing, remember?) then you can quickloot your chest. I've had some very anxious 'running naked through the dark in the Nether and tiptoeing around lava with ghasts hovering overhead' experiences *shudder*.
  3. Offline


    OMG, lol.... @Drakia, very sorry to be cluttering up your thread with this, but that's hilarious to me :D

    Also, I think the recurse spell, using air, would be a great way to "dig out" a chest if that's the case- you just need a wand and a wooden shovel ;) (And, you know, Wand/Spells installed, permissions, etc...)

    Also, @Drakia, I am totally wanting to support this when I start making spells PvP.

    I'm assuming that if I just call setHealth, and then they die, that things will be hunky dorey- so hopefully I won't have to bug you about it when the time comes.

    This should be fixed as of CB552, by the way! God, I hated this bug (I think the bukkit devs called it "chunk ghosting")- it's been around since 1.3, kills Spells, kills NetherGate, sucks overall.

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
    Last edited by a moderator: May 8, 2016
  4. Offline


    I'm leaving that warning up until they mark a post-522 build as an RB.
    And I'm nit worried about clutter. in regards to sethealth, it will only work if that triggers the death hook.
  5. Offline


    download link isnt working for me.
  6. Offline


    Can you make it destroy the chest and sign on quickloot/after looted? I want free chest but don't want people picking them up.
  7. Offline


    May add destroy on quickloot as an option, but you may want to look up the definition of free.
  8. Offline


    I run a RP/PVP server. I dont want them being able to lock it for themselves. If LWC is set to public, they can take the items, but they can't lock the chest. Which means, If their inventory is full and they can't carry all the loot, they have to pick most valuable things and leave the rest there hoping someone else dont pass by.
    Also, while in battle, they can't use other player tombstone to store their items if they're afraid of dying.
  9. Offline


    And I don't run an RP/PVP server. The plugin is open source, and as such, if you want this functionality you can add it yourself, then make a pull request if you have the desire to do so.
  10. Offline


    Wow What a jerk...
    Why are you making plugins if yon don't accept any suggestions from the people who use it?!?

    Keep going your own way, I will not make you lose your precious time anymore. Guess you're too important to consider other people suggestions/questions.
  11. Offline


    this is HIS plugin, if you dont like it WRITE YOUR OWN, if you like it and want something changed CHANGE IT YOURSELF
    its opensource so that everyone can contribute and implement things he doesnt. he even told you that you can do a pull request, so why get upset? no reason for him to implement something he does not need at all

    *sigh* dont just rely on others and then call them a "jerk" because that makes you a "jerk" or rahter a troll and nobody needs trolls
  12. Offline


    Are you planning database, or something like this?

    When server restart (every 8 hours on my server) all timers (lwcRemove, tombRemove) reset and disabled, so I cant use this plugin :(
  13. Offline


    @MrCamping Why am I making plugins? Because I run a server. What you really want to ask if why do I RELEASE plugins, and the reason is so that OTHER PEOPLE can use them. I do take suggestions into account, but I don't take EVERY suggestion into account. It's MY plugin, which means I get to pick what gets put in and what doesn't. I choose what I spend my time doing. Nobody else. AS I said, you want the feature, add it yourself. In my opinion NOBODY should run a server without a programmer.

    @Dreadreaver Thanks for standing up for me :) I am a jerk though, but that's just how I have to handle people like him ;)

    @ksevelyar I'm actually thinking about it, cause my server has the same thing where there are time I need to update Bukkit to fix a bug and it loses the counter. If I do I'll have it pushed sometime in the next few days :) Just moved into a new house, so things are kinda hectic atm, mainly doing support and not coding at the moment.
  14. Offline


    You should add that chest dont create when players burn in lava.
  15. Offline


    I actually like that it creates tombstones in lava. You can still access them _most_ of the time as long as it's only a few blocks down.
  16. Offline


    Is there a way to see, what player died, if i check the chest without sign? Player keep asking me "who's chest is this in front of my house". If i could check who's inventory is in the chest, i could tell the People to get there stuff.
  17. If someone die close to a tomb, the two chest will make just one big and the last dead player will access all the loots...

    So it's easy to die close to a tomb to steal the loots...

    Any idea ?
  18. Offline


    Make two-chest tombs?
  19. Offline


    Thanks - works great for me :)
  20. Offline


    There is no way to see what chest belongs to who without a sign.
    There's also no way to solve the chests beside eachother messing with the LWC locks. It's a Minecraft gameplay mechanic at work, two chests placed beside eachother become one chest.
  21. Offline


    one of my members died with a TNT mishap..... the chest and sign didn't get made (could it be destroyed by the TNT as well?).
    In the console log, i saw this
    "CONSOLE: Got position 89.89977215620836, 49.54890339745907, 1067.1092249697163
    CONSOLE: Expected 90.30000001192093, 49.54890339745907, 1067.1092249697163"

    Is that related in some way to the chest not being created?

    edit: I did confirm the chest gets made when this user dies via just falling and not TNT
  22. Offline


    If you die via explosion then the chest/sign are destroyed by the explosion. In regards to the moved wrong, that has nothing to do with Tombstone, I don't adjust users position.
  23. Hello Drakia, i tried to recompile your sourcecode in eclipse for last 5 hrs. I really don't know what to do. So i hope, you can do something for me (for us).
    I want to try one thing: change position of sign to aside of chest with "[private]" on line 0, for use TombStone with Lockette together. I do not expect you will teach me how to put your code to eclipse, change it and compile plugin, which will work. Only, could you think about option to link Lockette and TombStone together? Hello and thanks for almost perfect plugin!
  24. Offline


    To import into eclipse:
    1) Download the source/extract
    2) Create a new Java Project in Eclipse, include the required .jar files (Bukkit, CraftBukkit, LWC, Permissions)
    3) Select File->Import->File System, select the extracted directory, Click "Select All" and set the Destination folder to your project root
    4) Compile

    Now, if any of that is beyond you, then you're not a plugin dev and shouldn't be trying to compile my plugin until you learn how to actually make plugins.

    Just uploaded v1.08 with some nifty new features:
    [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

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
    Last edited by a moderator: May 8, 2016
  25. this will help me a lot, i think, that was my problem, i didnt know i can import directories... many thanks...
  26. Just tested this plugin with craftbukkit updated a couple of days ago and:
    - Large chests don't create (room wasn't the problem), it just drops everything including my extra chest
    - I don't see any signs, it would be usefull to support lockette with [private] headed signs
    - Chests should be allowed to be destroyed by their owners
  27. Offline


    @Digi Your post gives me zero information on why it's not working. Was there any console output? Did Tombstone enable properly? Do you have permissions to use it? If Permissions is not installed large chests are never created, and considering your other posts bitching about dependencies you probably aren't running Permissions.
    I support LWC for chest protection.
    A sign is only created if you are carrying a sign.
    Did you even bother reading the first post? Cause from the looks of it you didn't. Owners can destroy their tombstone, anybody can destroy any tombstone if you configure it as such. Where did you get that owner can't? Unless you changed an option the default is that LWC will protect a chest from other people, but the owner can destroy their tombstones.
  28. Yeah great, at least that guy said it clearly he required permissions, you didn't specify which options *require* permissions to work.
    I don't want to use permissions since I don't need it.

    Anyway, no console output, it was enabled and it placed one chest.
    I read the topic, but what I said is from what I tested, I died, I got to my chest and I tried to destroy it, it didn't let me, then I emptied it and I still couldn't destroy it... but still, no LWC, I use lockette for chest protection since it gives a better and easier visual information.

    Well anyway, I just wanted a simple way for people to not have their equipament scattered across the map, it seems I have to complicate it with permissions, I'll try with that then.
  29. Offline


    "that guy" is me, genius. And obviously you didn't read the first post, as I said.
    "Supports the Permissions plugin, will default to allowing everyone to use basic tombstone if not available"
    Basic tombstone being a single chest with a sign if available.
    When you try to destroy the chest does it give an error? (Whether to the player themself or in the console?) Because I just tested with the default config and it lets you destroy tombstones perfectly fine.
    There are no plans to add support for Lockette.
    And if you keep bitching about Permissions and refusing to install it, a lot of plugins aren't going to work how you want them to. A large majority of plugins "support" permissions in that most of their functionality is determined by either Permissions, or isOp()

    You did however make me think of an issue that people are going to run into, so thanks for that I guess.
  30. Offline


    Any plans on adding directional help to the tombstone? such as a command that gives a compass direction (degrees) to a tombstone, or something that lets the users loookup the coords?
  31. Offline


    There is always DeathTP+ in the mean time for that. Its a fast way of getting there..although not "true survival" its definitely a solution in the interim.
Thread Status:
Not open for further replies.

Share This Page