Inactive [INACTIVE][INFO] HeroicDeath v1.11.2: Customizable server broadcasts on player death [1185]

Discussion in 'Inactive/Unsupported Plugins' started by SquallSeeD31, Feb 2, 2011.

  1. Offline


    HeroicDeath - Player Death Notification Plugin (v1.11.2)
    Download HeroicDeath v1.11.2 [CraftBukkit 1174+]
    Download HeroicDeath v1.9.1 [CraftBukkit 1035~1173]
    Download HeroicDeath v1.8.2 [CraftBukkit 561~1034]
    Download HeroicDeath v1.6.1 [CraftBukkit 349~560]
    Download HeroicDeath v1.3.1 [CraftBukkit 348-]
    Latest Jar Only | In Development Jar

    Due to API changes, if you are not using the latest Recommended Build of CraftBukkit, DO NOT download the latest build of HeroicDeath. I have provided links to all legacy versions of HeroicDeath based on which CraftBukkit versions they support.

    CraftIRC Integration
    Do you use CraftIRC? Do you want HeroicDeath to send its death messages to your IRC channel? Xon has developed a helper plugin to do just that! I do not maintain or test this plugin, but I am happy to endorse it and link it for any CraftIRC/HeroicDeath users who want to use both together.

    JSONAPI Integration
    Xon has ALSO developed a helper plugin that pushes HeroicDeath messages to JSONAPI, allowing server admins to easily procure deaths via anything capable of reading a JSON string. Thanks, Xon!

    • Broadcast cause of death when a player dies
    • Shows who killed whom in PvP and with what item
    • Shows which kind of monster was responsible for eating a player
    • Optionally shows which world they were killed in!
    • Define an unlimited (within reason) number of custom messages based on cause of death, and a random message will be chosen
    • Log deaths to a configurable file, including timestamp and location of death!
    • Send messages on a per-world basis or to the whole server, configure which worlds should get messages and which shouldn't!
    • Define the text color to be used for the message, the player(s) involved, and the "murder weapon" (for PvP deaths)
    • Customize item names to be displayed for PvP deaths (Ex. "Excalibur" instead of "Gold Sword")
    • Supports items with durability! (wood, coal, dye, wool)
    • Item list doesn't need to be updated for future Minecraft patches! (If an item is not defined in the items file, the name of its Material will be prettified and used by default)
    • Supports following causes of death (all lines below the :Tag will be treated as messages for that type of death):


    1. FAST INSTALL: Drop the JAR in your plugins directory and reload plugins; HeroicDeath will automatically create default files. If you want to edit them before your first run:
    2. Download latest .ZIP archive from the link at the top
    3. Extract the archive into your main server directory (archive contains directory mapping)
    4. Open /plugins/HeroicDeath/config.yml and configure to taste
    5. Open /plugins/HeroicDeath/heroicdeath.messages and add/remove/edit death messages
    6. Open /plugins/HeroicDeath/heroicdeath.items and add/remove/edit item names
    7. Save all configuration files and reload your server

    The config file contains default text colors and logging preferences. You can specify the chat colors that will be used for broadcasting a death message, displaying the name of the dead (and their killer if applicable), and displaying the name of the item used to kill the player (for PvP deaths). You can now also choose whether or not to log death data, death messages, and a few formatting choices for your logs.

    This file is saved in the YAML format, so please be sure to maintain the formatting and change only the element values.
    Default configuration:

    Show Spoiler
    # HeroicDeath Configuration
    # Messages are defined in heroicdeath.messages
    # Items (for PvP kills) are defined in heroicdeath.items
    # This file is for configuration of colors, log preferences and localized mob names
    ## Color options
    ## message: Text color of death notifications, wrapped around names/item.
    ## name: Color for the name of victim and killer.
    ## item: Color for the name of the item used in a PvP death.
    #Color is defined according to the Bukkit enum ChatColor
    #Acceptable entries:
    #If color entered is inappropriate, HeroicDeath will default to the following values:
    ##message: RED
    ##name: DARK_AQUA
    ##item: GOLD
        message: RED
        name: DARK_AQUA
        item: GOLD
    #Logging Preferences:
    ##data: true to log a serialized object representing all the relevant information associated with a death
    ##messages: true to log death messages (as output to the server) to a separate file
    ##time: Whether or not to timestamp messages (if logging messages), and what timestamp format to use for data/messages
    ###stamp: true to timestamp messages
    ###format: Uses format strings from Java SimpleDateFormat.  Read all here:
    ##files: Filenames to store data/messages in.  A server admin could ostensibly change this value daily/weekly/monthly for collection of timed logs
    ###data: Data storage filename
    ###messages: Messages storage filename
        data: true
        messages: true
            stamp: true
            format: MM/dd/yyyy HH:mm:ss z
            data: death_data.log
            messages: death_messages.log
    #Event Support:
    ##If you only want HeroicDeath to send its custom event for other plugins to pick up, and NOT send the death message, set this to true.
        only: false
    #Localized monster names:
    ##If you would like to specify custom localization for the mob names, edit the defaults below
        ghast: Ghast
        slime: Slime
        monster: Monster
        zombie: Zombie
        pigzombie: PigZombie
        spider: Spider
        creeper: Creeper
        skeleton: Skeleton
        wolf: Wolf
        unknown: Unknown
        giant: Giant
    ##useDisplayName: Set to true if you want HeroicDeath to display the player's display name instead of their fixed character name.
    ##serverBroadcast: Set to FALSE if you want HeroicDeath to only broadcast its messages in the world they belong to.
    ##worlds: Lists of quiet/loud worlds for broadcast targeting. NOTE: World names are case-sensitive.
    ###quiet: Worlds listed here will NEVER receive ANY HeroicDeath broadcasts.
    ###loud: Worlds listed here will ALWAYS receive ALL HeroicDeath broadcasts.
        useDisplayName: false
        serverBroadcast: true
            quiet: [peacefulworld, noobworld]
            loud: [pvpworld, nether]

    Contains all the possible messages that can be displayed, sorted by type of death. Every line under a death type label is treated as a message for that death type, until the next label is reached. Labels are prefixed with the colon ":" and are self-explanatory.
    Variables accepted in messages:

    %d holds the name of the dead player.
    %a holds the name of the attacking entity (player or monster) for PVP and Monster deaths.
    %i holds the name of the attacking player's current item for PVP deaths.
    %w holds the world the death occurred in
    This file contains custom names for the item a PvP killer is holding. The names here will be replaced in the %i marker for PvP deaths. If a mapping is not provided for an item in this file, a default name will be used automatically.
    Item Format: NAME:ID:<Optional>DATA
    Item IDs and Data Values may be found on the Minecraft Wiki
    Optional DATA parameter uses hex notation, so purple wool would be "purple wool:35:0xa"

    If you have translated heroicdeath.messages into another language and would like to share your translation with the community, let me know! I'd be happy to share it here in the OP for those looking.

    German - By Keav -

    Changelog (Download Full Changelog)
    Version 1.11.2
    • Added 1.8 mobs Enderman, Cave Spider, Silverfish
    • Added passive mobs Chicken, Cow, Pig, Sheep, Squid
    Version 1.11.1
    • Fixed an exception that would occur if the player dies without being damaged first (such as by a rogue plugin)
    Version 1.11.0
    • Added support for MC 1.8.1 death messages (by removing them)
    • Added new MC 1.8.1 items
    • Added support for STARVATION DamageCause
    Version 1.10.0
    • Added support for SUICIDE DamageCause, mainly for the /suicide and /kill default commands.
    kahlilnc, Chike, SmartyGeek and 20 others like this.
  2. Offline


    im new to been a server owner and iv just installed this but it doesnt show up in game chat log that someone died.
    it shows up in the web administration console's chat log, can anyone tell me what is happening here
  3. Offline


    Hi, i'm loving the mod as it gives us a great way to mock peoples failure.

    I was wondering if in the next revision you could add different messages for every mob, like the creeper has? It would make this awesome mod even more awesome.
  4. Offline


    Can you pastebin your config.yml? If events.only is true, HeroicDeath will only send out its custom event, instead of also notifying the world.

    @Ragepyro: A couple people have asked for it, I'd consider it a "to-do"
  5. Offline


    Awesome. Someone suggested while I was adding more messages that I put 'Got boned' as a skeleton one, but I had to say I couldn't D:
  6. Offline


    i suggest in config separate death messages for each monster. so i can make specific messages for example killed by spider: "was enwrapped in silk by a spider"
  7. Offline


    Okay, alright already, I'll add per-mob death messages. :p

    Okay, support for per-mob death messages is added in 1.6.0. Read the changelog/OP for details and feel free to ask questions.

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


    yo, i may be retarded and couldnt see this in your post but how do i add colors to the death.messages file?
  9. Offline


    How is this supposed to work? Do the messages come automatically after death, just by putting the plugin in?

    When I die nothing happens =/
  10. Offline


    You can specify the color of names (attacker, victim), of items (used to kill when it's a PvP death), and of messages (in general) in the config.yml, but I do not have an easy way for the time being to add any other color at custom points in the messages. In theory, a \u00A7 character (section symbol, '§') followed by the appropriate color number should parse appropriately, but I haven't explicitly tested that.

    Yes, if you have not set the node events.only to "true" in the config.yml, HeroicDeath will broadcast a message to the server whenever a player dies. You can see if it's working, even if you *do* have events.only set to true, by checking the server console; the death message should go to the server console regardless.

    If that's not working, please post your CraftBukkit version, HeroicDeath version, and any errors you may see in the console when HeroicDeath is enabled.

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


    thanks, ive got it working now :) awesome plugin
  12. Offline


    Thank You. Turns out I thought an outside command /kill would work with this plugin. Its fixed. ;)
  13. Offline


    Ah, sorry. I only listen for ENTITY_DEATH, which doesn't typically get called with the way some plugins effect their kill commands. Glad to hear it works fine otherwise. =)
  14. Offline


    Using CraftBukkit v.531

  15. Offline


    So the error you posted is an error in the config.yml, most likely caused by a manual edit that malformed the structure of the YAML (or used a tab character). If you pastie/pastebin your config.yml I can take a look at it and see if I can figure out what the issue is.

    It's definitely unrelated to your CraftBukkit version though.
  16. Offline


    Here it is...

  17. Offline


    I wonder if it's possible to add a prefix to the messages for console only so that the log is a bit clearer and seperates the death messages from regular chat.
  18. Offline


    Awesome plugin. Just added about 20 of my own death messages to the defaults, I have my friends LOLing every time we get snuffed for whatever reason. :)
  19. Offline


    I noticed something in this file: you use a HashMap<String, MaterialData> but I think you should use HashMap<MaterialData, String> instead because right now two items can't have the same custom name.

    I was the item names and I noticed that some of them didn't work at all in game because I was using the same name for some similar items, and so they couldn't be added to the hashmap[​IMG]
  20. Offline


    Hy !
    I found a bug
    Heroic Death made conflict with War (and the problem where Died player don't have new stuff)
    Only whith the lastest version of Heroic Death
    With previously version, no problem, but with lastest version, WAR don't give new stuff after death.

    Sorry for my english, i'm french
  21. Offline


    Awesome plugin!
    I've noticed a few errors. They do not interupt the functionality but just giving you a heads up.
    These occur both on server start and when a player dies.

    CraftBukkit: 544
    HeroicDeath: 1.6.0
    Plugins: WorldEdit, JumpBlock, CraftBookCircuits, MyWarp, ChatBukkit, Permissions, MyHome, CraftBookMechanisms, ScrapBukkit, GroupManager, CraftBookCommon, HeroicDeath, LoginMessage, CraftBookVehicles, WorldGuard, HeroChat

    15:37:17 [SEVERE] [HeroicDeath] Error writing message log:
    15:37:17 [SEVERE] plugins/HeroicDeath/death_messages.log (Permission denied)
    15:37:17 [SEVERE]      at Method)
    15:37:17 [SEVERE]      at<init>(
    15:37:17 [SEVERE]      at<init>(
    15:37:17 [SEVERE]      at com.herocraftonline.squallseed31.heroicdeath.HeroicDeath.recordDeath(
    15:37:17 [SEVERE]      at com.herocraftonline.squallseed31.heroicdeath.HeroicDeathListener.onEntityDeath(
    15:37:17 [SEVERE]      at$39.execute(
    15:37:17 [SEVERE]      at org.bukkit.plugin.RegisteredListener.callEvent(
    15:37:17 [SEVERE]      at org.bukkit.plugin.SimplePluginManager.callEvent(
    15:37:17 [SEVERE]      at net.minecraft.server.EntityPlayer.a(
    15:37:17 [SEVERE]      at net.minecraft.server.EntityLiving.a(
    15:37:17 [SEVERE]      at net.minecraft.server.EntityHuman.a(
    15:37:17 [SEVERE]      at net.minecraft.server.EntityPlayer.a(
    15:37:17 [SEVERE]      at net.minecraft.server.EntityLiving.a(
    15:37:17 [SEVERE]      at net.minecraft.server.Entity.a(
    15:37:17 [SEVERE]      at net.minecraft.server.EntityPlayer.b(
    15:37:17 [SEVERE]      at net.minecraft.server.NetServerHandler.a(
    15:37:17 [SEVERE]      at net.minecraft.server.Packet10Flying.a(SourceFile:126)
    15:37:17 [SEVERE]      at net.minecraft.server.NetworkManager.a(SourceFile:230)
    15:37:17 [SEVERE]      at net.minecraft.server.NetServerHandler.a(
    15:37:17 [SEVERE]      at net.minecraft.server.NetworkListenThread.a(SourceFile:100)
    15:37:17 [SEVERE]      at net.minecraft.server.MinecraftServer.h(
    15:37:17 [SEVERE]      at
    15:37:17 [SEVERE]      at
    I noticed the "Permissions Denied" so re-chmod'd the plugin folder with 775. Created the 'death_messages.log' & 'death_data.log' with 775 permissions as well. When the server starts the error message is gone, but upon player death the above error still reoccurs. Humph. It's all default settings from install.
  22. Offline


    This worked! thanks!

    Essentially i just cut and paste the § symbol then a color number into the messages file. Thanks!
  23. Offline


    That's a good catch! I kept the Items and Messages classes as similar as I possibly could to the original DeathNotify hey0 plugin to maintain backwards-compatibility with its files, but that comes with the added baggage of not being inside the original author's mind. If I had to guess, I'd say it was originally written that way so that--at least in the future--support could be added for pulling a random custom name for the item as well as a random death message.

    Anyway, I'm not using it for that purpose, so having it *work* intuitively is the better goal, and as such I've made that change in all the relevant places in code and tested it, along with CraftBukkit 556 to ensure nothing else broke.

    Download version 1.6.1 to fix your woes =)

    I'm not sure I understand what exactly the problem is. Certainly WAR has a lot to do with players dying, so I understand the potential for a conflict to exist, but I don't know what exactly the conflict is. I mean, are there any error messages? What's "new stuff after death"?

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


    Don't worry too much about it. I'm looking into it. The "new stuff after death" is the player's respawn inventory.

    I verified that you're using the MONITOR event priority, so a conflict shouldn't happen, technically - i.e. it's probably my fault (I always got lucky in that players cheat death and tp automatically to their team's spawn even though there's no event.setCancelled(true) for ENTITY_DEATH). I'll install HeroicDeath and tease the problem out. I'll let you know when I've closed the issue. Thanks!

    Done. War v1.3.1 fixes the conflict between our plugins.

    Edit: By the way, thanks for the awesome plugin. This is the perfect match for War (provided you don't have too many games going on at once). I can't believe I didn't install it before.

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


    Thanks to both of you ;)
  26. Offline

    Ryan Fuller

    Im having trouble getting this mod to work with my server i have build 556 its giving this error
    i am on a mac btw

    22:25:10 [INFO] This server is running Craftbukkit version git-Bukkit-0.0.0-544-g6c6c30a-b556jnks (MC: 1.3)
    22:25:10 [INFO] Preparing level "world"
    22:25:10 [INFO] Preparing start region
    22:25:11 [INFO] Preparing spawn area: 40%
    22:25:12 [SEVERE] Could not load plugins/HeroicDeath.jar in plugins: null
    at org.bukkit.plugin.SimplePluginManager.loadPlugin(
    at org.bukkit.plugin.SimplePluginManager.loadPlugins(
    at org.bukkit.craftbukkit.CraftServer.loadPlugins(
    at net.minecraft.server.MinecraftServer.e(
    at net.minecraft.server.MinecraftServer.a(
    at net.minecraft.server.MinecraftServer.d(
    Caused by: java.lang.UnsupportedClassVersionError: Bad version number in .class file
    at java.lang.ClassLoader.defineClass1(Native Method)
    at java.lang.ClassLoader.defineClass(
    at Method)
    at java.lang.ClassLoader.loadClass(
    at java.lang.ClassLoader.loadClass(
    at java.lang.ClassLoader.loadClassInternal(
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(
    ... 8 more
    22:25:12 [INFO] ChatBukkit v0.0.1 is enabled!
    22:25:12 [INFO] ScrapBukkit version 0.2.1 is enabled!
    22:25:12 [INFO] Done (0.207s)! For help, type "help" or "?"
  27. Offline


    Thank you very much, I couldn't figure out what he was talking about, sadly. =(

    I love War as well, and hope to install it on my PvP server in due time.

    Since you're of the wargames mind, you might appreciate the logging feature of HeroicDeath; it saves data in a marshallable format so that you could ostensibly parse the log into a database and then run statistics about the most frequently used "murder weapon", who has the best Kill/Death Ratio, etc.

    Now is this only with the latest version of HeroicDeath, or have you tried other versions in the past? What JVM are you running (vendor and version please)? Does this happen with any other plugin?

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


    new CB 561:
    2011-03-23 17:35:06 [SEVERE] ENTITY_DAMAGED loading HeroicDeath v1.6.1.145 (Is it up to date?)
    java.lang.NoSuchFieldError: ENTITY_DAMAGED
        at com.herocraftonline.squallseed31.heroicdeath.HeroicDeath.onEnable(
        at org.bukkit.plugin.SimplePluginManager.enablePlugin(
        at org.bukkit.craftbukkit.CraftServer.loadPlugin(
        at org.bukkit.craftbukkit.CraftServer.loadPlugins(
        at net.minecraft.server.MinecraftServer.e(
        at net.minecraft.server.MinecraftServer.a(
        at net.minecraft.server.MinecraftServer.d(
  29. Offline


    I don't support non-recommended builds of CraftBukkit specifically for reasons like this: they decided to change most of the event names, which breaks every plugin that uses those events until they rename them. In *my* particular case, it's a fairly easy fix. Change ENTITY_DAMAGED to ENTITY_DAMAGE and everyone's happy. I just don't want to release that until it's part of a Recommended Build, because I'll have to support three versions of HeroicDeath at that point.

    If you promise not to hold me responsible for it, you can have this indev build of HeroicDeath that implements that change, and see if it works for you:
  30. Offline

    Ryan Fuller

    I believe that it is the latest version of heroic death and this happens with basically every plugin i do i am new to bukkit
    The java version that i think i am running is 12.7
    could i be doing something wrong?
  31. Offline


    Well, basically the error you described occurs when I compile code with a version of the Java compiler that's newer than the Java virtual machine you run it on. Most plugin developers are using Java 6 (1.6.0_23 or 24, usually) in my experience. I unfortunately don't know enough about the Mac Java environment to comment on the version numbering you're reporting, but you may want to look into updating Java and see if that fixes your problem. =)

Share This Page