[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


    Lockette support would be nice.
  3. Offline


    Guys stop asking for Lockette support, it's not going to happen, LWC is supported and I was told that is all the support that will be given when I asked for Lockette

    @ Drakia
    Can the tombstone sign be configured to be placed side on to the chest with custom text, if so then we could cause Lockette to kick in that way as it doesn't use a database, it just checks for a sign with [Private] or the server set alternative, no support offered/required from you if we try to Lockette using that config
  4. Offline


  5. Offline


    @Drakia Would it be possible to add in an option to not drop a death chest if killed by PvP?
  6. Offline


    Until I decide otherwise, I will no longer be offering any support for any of my plugins. I'm tired of the way users on this forum act, yes, I'm a dick, but it's mainly as a result of people who can't follow basic instructions, or who don't even take the time to read the first post of my topics.
    My plugins will still be kept up to date with the RBs, however I will not be answering any stupid questions, nor adding any requested features.
  7. Offline


    I haven't read all the posts but just wanted to say that I appreciate all the time and effort you have put into your plugins. Tombstone is a great plugin and has been a valuable addition to my server for some time now.
  8. Offline


    'Tis a shame. It's a great plugin!

    In terms of you thinking you're a dick. I disagree. I've watched Doku start remaking his pack from the get go and everytime someone says "I don't like this" or "can you do that" he just answers with:

    Well I do. And no.

    I think if you adopt that attitude and ignore all but the most serious of plugin bugs, you'll be good. -crosses fingers that Notch doesn't start mini-patching in between now and 1.6-
  9. Offline


    I had a similar issue with BoundaryKill - I think it's because the way that those plugins kill the player isn't currently detected by this plugin (could be possible to make it work, don't know).
  10. Offline


    Well your retarded then. You would be BETTER off making this plugin work with boundarykill AND gastronomic because people use them.
  11. Offline


    Er... no. I think that you may be better off noticing that I'm not the developer and demanding that random people "fix" the plugin probably isn't productive.

    I agree with BlackPandemic - it's unfortunate that it's people with complaints that are the most vocal and the people who most appreciate your plugins often have no need to post as it's working fine for them. The trick is to not let it get to you and ignore them or reply "read first post". Whilst it's a shame to see you stop, I understand your decision and thank you for the great plugins and for the fact that you posted them on GitHub.
  12. Offline


    See, it's douches like that. I should just MAKE the plugin compatible? Because it's that easy? Yeah, go learn how Bukkit works then get back to me @Jessicadawn. Maybe you should let your fiance handle the bug reporting side of things, since you obviously don't know what you're talking about.

    I'm aware that there's a large portion of users who use the plugins that don't have any issues. The problem is I'm stuck dealing with all the idiots on these forums. I may keep releasing patches to make my plugins work with RBs, I may not. It depends how I feel when an RB comes that actually breaks something. As it is, all of my plugins work with 766.
  13. Offline



    Just try and remember that for each troublesome user there are many more happy and grateful users :) Also, I'd forgotten about Jessicadawn already and plan to ignore her future comments if they are of a similar nature (there is also a "report" button there if comments get abusive).
  14. Offline


    Would be kinda hypocritical if I reported users for being rude ;) lol.
    I may still update to the latest RB (I do work for a server) i am not doing support or feature requests though.
  15. Offline


    Drakia, just wanted to tell you that I really appreciate you developing plug-ins. It's a shame there are many dicks around on this forum which keep trolling. I guess that's how the world is, looking on the positive side: I love this add-on and thanks again for making it public!
  16. Offline


    Not rude... abusive, there is a difference :)

    If someone hasn't read the big bold text at the top of the first post being rude is fine :D
  17. Offline


    Drakia, for now on just refuse support to those people when they demand something from you (if you want to take a page from the books of Afforess and Sk89q) as what right have they to demand that your plugin that you work in your spare time on while receiving silent praise (I counted a few hundred "Thank god for tombstones" on my old server) and loud complaints (See Jessicadawn)
  18. Offline


    I wasnt aiming that at YOU. I know who is the plugin developer and hes an asshole. If you cant stand working with people who use his plugin to make it more adaptable to everyone then why do it. I have met AMAZING plugin developers (gastronomic, essentials[who is the guy who hosts my server], regio,) who accept critizism listen to people and keep their calm. You have to realize HOW many complaints i get a day because hunger killed them and their tombstone did work and they lost all their items. Now i deal with complaints on forums because my fiance has a huge problem with keeping his calm. I simply told drakia what was wrong. Told him bukkit build (if im correct) and told him that no errors were spitting out just something actually in game and at the time i couldnt remember because we took it out and i couldnt repeat the error. He got mad at me not the other way around then i got pissed. Plugin developers should be thankful that their plugins are getting used. They should be thankful they get donations (which i know alot do. I made over 1200$ on my server and 10% of every 20$ go to essentials and regio is getting paid to and fulwall from gastronmic.) Yes server owners should be thankful too but i mean plugins are options if it wasnt there it would just be regular minecraft. Also if you read up a bit i said if its possible to make the 2 plguins compataible that would be great. I also said I am not sure if its your end or his end. What you COULD of said was that it was (if it is) your end but you do not support other plugins or w.e it says in your first post which i read but like i said dont know which end theres a problem. And it would be better because people with those 2 plugins i mentioned would use tombstone more likely because its supported. The more supported plugins the more likely people are going to use your plugin. It is a great plugin my players love it (we only made it for vip vipprem and moderators and admins tho) and i mean people donate exactly for tombstone. But like i said i get about 20 complaitns a day from peopel stating that they died by hunger and no tombstone and they lost their shit and QQs all the way

    Excuse my spelling kinda in a rush getting ready for lunch break @ work :p

    Now @Zarius im sorry if you took offense but NOTHING was aimed at you. Not once.
  19. Offline


    OK now look at it from HIS point of view

    Every time one of the integrated plugins updates anyone hooking that plugin for compat has to go check it to see if it broke

    Now lets add in support for Lockette and the hunger mod
    Now Drakia has 3 plugins to monitor besides his own

    Player X asks for support with another plugin
    Drakia either gives them a no and maintains his current work load or he gives a yes, adds to his workload and delays the updates or causes an update storm as conflicts occur or shit breaks

    Donations are just that, donations
    To donate is optional, it can't be considered a paycheck as it's not fixed or definitely going to come through

    So now this is how Drakia has to ballence his day
    Work, Sleep, Eat, Program and Freetime
    Every plugin either delays updates or removes freetime, so someone is going to lose out

    Have you asked the hunger mod group to change their method of killing their users, I know for a fact that all minecraft deaths AND /kill work with Tombstone so have them look in to alternatives to their current kill method as in the long run if they make their kill compatible then not only tombstone but other plugins will be able to catch on to the death event

    How about you turn around to those people that are complaining and direct them to the bukkit forums so they can register, complain here and be told the same thing you are being told
    Tombstone will ONLY support LWC and the minecraft kill events, hell it says in the OP
    Can you give support for X plugin
    Answer: No, and now you know why
    Jeyge likes this.
  20. Offline



    Seems fair enough to me. Keep it updated but that's it. From what I can tell most 'support' is due to plugin incompatibilities and that's not really your responsibility.
  21. Offline


    Just because I'm the curious type, I crawled thru their code (I'm not a Java or plugin dev) and saw that they both use setHealth. I then found this post that says that setHealth won't trigger a death event (also found in this post but I won't push any hatred). Looking thru the API docs, I found another Player API called damage which I think is what they really should use instead of trying to use setHealth.

    Feel free to copy/paste this to those threads if you want or point them back here.

    Having really tried to help some people on this forum, I think the underlying problem comes down to some users thinking that asking for something like a server.log is like an attack on the persons intelligence. I've seen so many responses along the lines of "Why do you need this. It shouldn't matter.". It is like we are attacking them by just trying to help. But yet that server.log might just identify the exact problem they are having. And then again, it might just be a waste of 1's and 0's.

    I really wish there was a way to get the users of these plugins to understand that there are a lot of people out here who are just trying to help and more information never hurt anyone.

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


    @Zarius yes my spelling always in correct my phone retarded makes mistakes as well when I type at work see last post.
    @The guy with rlly long post I've contacted the other pluginlike I stated I posted on both because I wasn't aware of which plugin it was that caused it.

    @ jeyge would you happen to private msg me that and explaining it id appreciate it
  23. Offline


    I'm sorry but I think you handled all of this wrong. And understand that I'm not saying that Drakia is a saint, but he is one of those plugin devs that really does support his plugins. I know you listed a few devs who also support their plugins but we also both know there are a lot out there who don't, so attacking one who does just probably isn't the best thing to do. And for something so simple too.

    You must see all of the posts on here that just go "It broke. Fix it.". Then 15 posts later, someone finally says what the problem is and the solution was really easy. He isn't attacking when he asks for a server log or the full error message. It is just what might be needed to determine what the problem is. Sometimes it just comes down to the way the message is worded that makes it hard to tell what the problem is so users are asked to provide more information. He just does it up front.

    As for what I posted, I didn't do it because it was required or anything like that but because I wanted to show what might happen if a question was asked nicely. He could have done what I did much easier than what I went thru to find it and may have if he was treated nicer. And this isn't even something that should be posted in his thread or just for you. I'm just putting it here because I have a feeling out of most of the people causing these problems, you might just understand it best.

    As I said above, feel free to post it in their threads if you wish or don't if you don't. I don't use their plugins so I'm probably not the best person to let them know but at the same time would love to see all plugins improved.

    PS - Don't take most of what is said on these forums personally. It isn't meant to be that way.

    More information is always better.

    Edit - funny, some guy named @all was just tagged in this post. :)
  24. Offline



    Cool - I was going actually going to check out the code too, just haven't had time.

    I also receive some "concerns" (wouldn't call them complaints) that people have lost stuff from crossing the boundary of my world but that's my decision to continue to use those two plugins together. I tell players that it's just of the dangers of my world :) I can understand this would be more annoying for your players with the hunger mod.

    @Drakia - I also have many more thanks from players that love your mod.

    Actually, players should be grateful that plugins are being written. Whilst some developers may have a lot of time on their hands others slot a little development time into already busy life schedules because they enjoy it. When that turns into "work" because people have expectations it takes some of that enjoyment away.

    Nothing wrong with an initial request (although it's courtesy to read through the first post and see that he already doesn't want to work on supporting other plugins) but if a developer adamantly says no, accept and move on.

    Donations are great, but they are just that - a gift in thanks for work already done and should never be given with expectations of future work.
  25. Offline


    There quoted it for you <3
  26. Offline


    New plan - if you aren't supporting Drakia in his efforts to provide for us a great plugin kindly take your internet argument elsewhere.
    Montag and Zarius like this.
  27. Offline


    New plan - Dont butt in where its not needed. No one EVER said anything about not supporting.
  28. Offline


    @Jessicadawn stop using my plugins, stop asking for help, and go bug somebody else. I am seriously sick of seeing you in my topics.
    Montag likes this.
  29. Offline


    Ignore it then :p Could of ALL been avoided with a simple. "Its my end but i am not supporting any kind of plugins sorry"
  30. Offline


    Except it's not my end, those plugin don't trigger death events. Now kindly gtfo.
  31. Offline


    Then THATS what you should of said the first time i posted and it would of ALL been avoided. Good job =D
Thread Status:
Not open for further replies.

Share This Page