backwards compability will be removed in 3.2, should give people enough time to update

Because the currency item is stored in the deathchest upon death, my users have no use for the currency option unless they return all the way home (which is a long way because we don't allow other forms of TP), so an option to keep only their currency item in their inventory upon respawn would be very nice.

I tried out the DeathControl plugin for this purpose, but its far more extensive than what I need, and may cause conflicts later down the road. Also, having two separate plugins for the same thing is confusing to users.

Another option (I don't require this but I predict other admins might):
Allow to set a limit on how many of the currency item is retained.

should that be configurable? pvp, monster, both?
different messages for different modes?

Possible incompatibility with CombatTag plugin.

11:44:53 [SEVERE] Could not pass event ENTITY_DEATH to DeathTpPlus
java.lang.ClassCastException: org.bukkit.craftbukkit.CraftOfflinePlayer cannot be cast to org.bukkit.entity.Player
        at org.simiancage.DeathTpPlus.models.DeathDetail.<init>(DeathDetail.java:51)
        at org.simiancage.DeathTpPlus.listeners.DTPEntityListener.onEntityDeath(DTPEntityListener.java:31)
        at org.bukkit.plugin.java.JavaPluginLoader$65.execute(JavaPluginLoader.java:718)
        at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:58)
        at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:339)
        at org.bukkit.craftbukkit.event.CraftEventFactory.callPlayerDeathEvent(CraftEventFactory.java:320)
        at net.minecraft.server.EntityPlayer.die(EntityPlayer.java:168)
        at net.minecraft.server.EntityLiving.damageEntity(EntityLiving.java:502)
        at net.minecraft.server.EntityHuman.damageEntity(EntityHuman.java:609)
        at net.minecraft.server.EntityPlayer.damageEntity(EntityPlayer.java:210)
        at net.minecraft.server.EntityWolf.a(EntityWolf.java:352)
        at net.minecraft.server.EntityCreature.m_(EntityCreature.java:70)
        at net.minecraft.server.EntityWolf.m_(EntityWolf.java:96)
        at net.minecraft.server.EntityLiving.d(EntityLiving.java:887)
        at net.minecraft.server.EntityAnimal.d(SourceFile:43)
        at net.minecraft.server.EntityWolf.d(EntityWolf.java:137)
        at net.minecraft.server.EntityLiving.w_(EntityLiving.java:297)
        at net.minecraft.server.EntityWolf.w_(EntityWolf.java:165)
        at net.minecraft.server.World.entityJoinedWorld(World.java:1253)
        at net.minecraft.server.WorldServer.entityJoinedWorld(WorldServer.java:107)
        at net.minecraft.server.World.playerJoinedWorld(World.java:1235)
        at net.minecraft.server.World.tickEntities(World.java:1142)
        at net.minecraft.server.MinecraftServer.w(MinecraftServer.java:518)
        at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:425)
        at net.minecraft.server.ThreadServerApplication.run(SourceFile:457)

Mainly need to look at the Tomb and Tombstone implementation and if the packages are really worthwhile.
I don't know if the splitting of the events and listeners really makes sense.
Moving the methods and codes of Tomb and TombStone into helper classes would probably make more sense.

well, I changed the permissions which are assigned by default a little bit, but I haven't implemented anything similar to AllowDeathtp which overrules permissions.

Moving this to 3.1 as this could probably done together with refactoring and other bigger changes

see http://dev.bukkit.org/server-mods/deathtpplus/tickets/15-new-feature-ragequit-announcement/

Can you add support for Deadbolt? http://dev.bukkit.org/server-mods/deadbolt/

It is based on Lockette and is better in my opinion. It was created after the dev of Lockette disappeared from the forums for a while.

also create a warning in the logs if still the old ones are used so we need support both permissions till 3.2

Allow deathtp only when a TombStone was created otherwise not.

Instead of creating the chest in the exact location of the players death...

If the player died in a 'non-air' block (liquids usually, or solids for suffocation), calculate the nearest air block directly above the location of death. (preferably check for 2 air blocks so the chest can be opened if the terrain is protected from modification)

Similarly, if the player died in 'air', check below vertically to place the chest above the first non-air block.

If processor usage becomes a problem (probably not, since it should find the nearest block pretty quickly in MOST circumstances), the distance-to-chest can be limited to a reasonable number.

Searching sideways is too difficult, only search vertically. For large chests, when an air block is detected, search the adjacent 4 blocks for 1 more air block.

Config Option: If a suitable space for the chest(s) cannot be found...
A) Create the block at the location of death, over writing the blocks there. (Default, current behavior)
B) Do not create a chest, destroy the contents (This option is good for servers who do not want chests overwriting special terrain/buildings/features)

I have it set so my users get a free chest and sign on death but when they don't come back for the tombstone it just stays there and never goes away. I have the time to the default 3600 seconds but the chest is still there days later. Is there something I can do to make the chests go away ? Right now my world is getting littered by tombstones all over the place and I'm the only one that can remove them. Love the plugin

will need some cleaning up though as that can cause NPE... probably best to only use it during chat messages

What steps will reproduce the problem?
1.in config, ensure "enableLockette: false"
also ensure "enableLWC: true"
NOTE: LWC settings are all default / using OP native privelages
2.Start server
3.Login to server with OP privelages (not required, but used in testing, anyone with appropriate LWC & DeathTpPlus permissions is able to do so)
4. die by any means
5. approach chest, and right click in hopes to quickloot

What is the expected output? What do you see instead?
What is expected: chest quickloots and empties contents into inventory
What do I see instead:Error log posted below

What version of the product are you using?
CraftBukkit: Recommended Build 1.0.1-R1
LWC: Alpha 4 (build 515)
DeathTpPlus: 3.1

Do you have an error log of what happened?

02:03:40 [SEVERE] Could not pass event PLAYER_INTERACT to DeathTpPlus
java.lang.NoSuchMethodError com.griefcraft.sql.PhysDB.unregisterProtection(I)V
at org.simiancage.DeathTpPlus.helpers.TombStoneHelperDTP.deactivateLWC(T
ombStoneHelperDTP.java:156
at org.simiancage.DeathTpPlus.helpers.TombStoneHelperDTP.destroyTombSton
e(TombStoneHelperDTP.java:481
at org.simiancage.DeathTpPlus.listeners.PlayerListenerDTP.onPlayerIntera
ct(PlayerListenerDTP.java:141
at org.bukkit.plugin.java.JavaPluginLoader$11.execute(JavaPluginLoader.j
ava:335)
at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.jav
a:58)
at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.j
ava:339)
at org.bukkit.craftbukkit.event.CraftEventFactory.callPlayerInteractEven
t(CraftEventFactory.java:178
at net.minecraft.server.ItemInWorldManager.interact(ItemInWorldManager.j
ava:266)
at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:593)
at net.minecraft.server.Packet15Place.a(SourceFile:39)
at net.minecraft.server.NetworkManager.b(NetworkManager.java:226)
at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:93)
at net.minecraft.server.NetworkListenThread.a(SourceFile:108)
at net.minecraft.server.MinecraftServer.w(MinecraftServer.java:527)
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:425)

at net.minecraft.server.ThreadServerApplication.run(SourceFile:457)

Please provide any additional information below.

regressed since Hidendra posted an updated RB for the new Recommended CraftBukkit. LWC 3.54 works as intended, only the new way it's working in 4.x is providing this error.

http://dev.bukkit.org/server-mods/deathtpplus/tickets/19-updated-lwc-incompatibility/

The message reads:

Player1 was victimized by Player2's Org.bukkit.craftbukkit.entity.craftarrow

neither DeathMessages or TombMessages are reading the config files correctly.

looks like getList isn't the correct way to read the structure as the deathmessages will always contain the default messages.

Haven't found a solution yet :-(

Allow an option to have the Sign & Chest disappear when destroyed, rather then going into the players inventory. The user does not get them back after they have been used for a tomb/tombstone.

This is particularly helpful for users who have the free sign & chest permission enabled, because they will accumulate a stack of signs and chests over time.

Rather than deleting all chests every X number of deaths, this option would allow free creation of new chests as long as a limit has not been reached. When the limit is reached, the oldest chest is destroyed. Each chest has a death timestamp (at least at time of creation), so calculating oldest should not be difficult.

I do not currently need an option that allows different user groups to have different amounts, although with the future in mind, some users may enjoy this feature. I'm not sure if the permissions you supports allows for info nodes (I use PermissionsBukkit, and will be transitioning to PEX at a later time)

was Check Teleport behaviour for not placing you at the right coordinates

see http://dev.bukkit.org/server-mods/deathtpplus/tickets/18-new-config-use-new-north/

looks like people use craftirc 3.0 now.. http://ensifera.com:8080/job/CraftIRC%203/

trying for if it works fine support till the official release is out, also dropping 2.0 in that case

no config options, just disable creating them as player don't have anything with them

for example add map diamond sword to sparkling dagger and Creeper to walking bomb via an alias file

2011-12-27 09:55:28 [SEVERE] Error occurred while enabling DeathTpPlus v3.3.1597 (Is it up to date?): while parsing a block collection; expected , but found Scalar

http://pastebin.com/VbKqCeQD

Also, I don't know if this is related or not but I can't get ANY DTP features to work in-game.

perhaps integrate a command to remove last deathtp location?

I'm still getting the default MC death messages coming through even though I have enableDeathtp: true and showDeathNotify: true

I'm not seeing DeathTp's messages at all

version 3.3.1597 , CB 1597

I have a feeling that this is a compatibility problem with other plugins rather than an issue with DTP, but I could be wrong.