Bukkit

As some questions / error reports reoccur frequently, here is a general summary of the most popular ones.

When are you going to update to craftbukkit XXX?

This plugin should be upwards compatible with new bukkit builds. If I can confirm compatibility with a new recommended build, I usually mark the latest version file like that.

Issues may occur if causes of dying are added or modified through new Minecraft versions, though I might not always notice the breakage.
If you happen to notice it before me, please post the issue on the appropiate forum.

I'm not charged money even though I configured a cost.

1: You are testing with the deathcontrol.use permission node. This makes you bypass the cost parameter. Note that you have this permission by default if you set use-bukkit-permissions to false.

2: Your economy managing plugin isn't set up correctly. You need to have either Register or Vault installed so the cost aspect of this plugin works correctly. If that's not the case and the plugin tries to charge a player, a respective error message is shown in the console. If you see it, make sure one of the mentioned plugins are installed!

When player has full inventory + armor, the armor is lost when items are restored.

Right now, the slots where items were in before death are not saved, and stuff is given back without order. Any overflowing items that no longer fit into the player's inventory are dropped at his feet. This means that the armor should drop as an item when the player respawns.

This was changed in v1.8. Item slot positions are now saved again. Make sure you update to the latest version!

I am getting an exception like this one:

[SEVERE] Could not pass event ENTITY_DEATH to DeathControl
    java.lang.IncompatibleClassChangeError: Expected static method com.nijikokun.register.payment.Methods.getMethod()Lcom/nijikokun/register/payment/Method;
    at bone008.bukkit.deathcontrol.DeathControl.getRegisterMethod(DeathControl.java:229)
    at bone008.bukkit.deathcontrol.DeathManager.pay(DeathManager.java:298)
    at bone008.bukkit.deathcontrol.DeathManager.handle(DeathManager.java:117)
    at bone008.bukkit.deathcontrol.DeathControlEntityListener.onEntityDeath(DeathControlEntityListener.java:37)
    at org.bukkit.plugin.java.JavaPluginLoader$64.execute(JavaPluginLoader.java:691)
    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:303)
    at net.minecraft.server.EntityPlayer.die(EntityPlayer.java:160)
    at net.minecraft.server.EntityLiving.damageEntity(EntityLiving.java:469)
    at net.minecraft.server.EntityHuman.damageEntity(EntityHuman.java:584)
    at net.minecraft.server.EntityPlayer.damageEntity(EntityPlayer.java:202)
    at net.minecraft.server.Entity.aa(Entity.java:271)
    at net.minecraft.server.EntityLiving.aa(EntityLiving.java:124)
    at net.minecraft.server.Entity.s_(Entity.java:192)
    at net.minecraft.server.EntityLiving.s_(EntityLiving.java:268)
    at net.minecraft.server.EntityHuman.s_(EntityHuman.java:153)
    at net.minecraft.server.EntityPlayer.b(EntityPlayer.java:215)
    at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:305)
    at net.minecraft.server.Packet10Flying.a(SourceFile:126)
    at net.minecraft.server.NetworkManager.b(NetworkManager.java:226)
    at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:92)
    at net.minecraft.server.NetworkListenThread.a(SourceFile:108)
    at net.minecraft.server.MinecraftServer.h(MinecraftServer.java:471)
    at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:374)
    at net.minecraft.server.ThreadServerApplication.run(SourceFile:417)

This is happening because another plugin on your server uses an outdated (wrong) way to add the Register library.

At least one of your installed plugins have Register bundled within their plugin jar without having changed its namespace. That way, an old version of Register is loaded instead of the appropiate one, which this plugins expects to be there. Because some methods were changed in the newer versions of Register, they can't be found, causing the error above.

What does this mean?

Basically that means that I am not responsible for that issue and can't fix it, as another plugin is loading Register in a stupid defective way.
Make sure your other plugins are updated, in case that was already changed.

A little help for finding the responsible plugin: Register is an economy API, so it can only be a plugin that makes use of some sort of economy system (for example iConomy).