Get an Epic Experience with Premium

HeroicDeath

Informational Login to Add Favorites
  • 0 Likes
  • Minecraft
  • 336 Monthly Downloads
  • Supports: 1.1
  • 113,733 Total Downloads
  • Updated 01/26/2012
  • Created 09/23/2011
  • 4 Favorites
  • Project Site
  • Comments
  • Release Type: Release
  • License: GNU General Public License version 3 (GPLv3)
  • Newest File: HeroicDeath 1.11.3
or

About HeroicDeath

HeroicDeath - Player Death Notification Plugin (v1.11.2)
Download HeroicDeath v1.11.2 [CraftBukkit 1174+]
Download HeroicDeath v1.9.0 [CraftBukkit 10351173]
Download HeroicDeath v1.8.2 [CraftBukkit 5611034]
Download HeroicDeath v1.6.1 [CraftBukkit 349560]
Download HeroicDeath v1.3.1 [CraftBukkit 348-]
Latest Jar Only | In Development Jar

HeroicDeath provides functionality to CraftBukkit server administrators to broadcast player deaths on a per-world or whole-server basis and finely customize the messages that are displayed based on the type of death (or damaging entity). The project has no external dependencies and does not add any features not directly associated with its primary purpose; this makes the plugin easy to install and maintain andgenerally speakingremain compatible with future changes.

COMPATIBILITY WARNING 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.

https://github.com/Xon/HeroicDeathToCraftIRC/downloads

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!

https://github.com/downloads/Xon/HeroicDeathToJSONAPI/HeroicDeathToJSONAPI.jar

Features


  • 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):

                           :Drown
                          :Cactus
                          :Fire
                          :Explosion
                          :Creeper
                          :Ghast
                          :Slime
                          :Zombie
                          :PigZombie
                          :Spider
                          :Skeleton
                          :Giant
                          :Wolf
                          :Enderman
                          :CaveSpider
                          :Silverfish
                          :Chicken
                          :Cow
                          :Pig
                          :Sheep
                          :Squid
                          :Fall
                          :PVP
                          :Void
                          :Lava
                          :Other
                          :Suffocation
                          :Dispenser
                          :Lightning
                          :Suicide
                          :Starvation
    

Screenshot

http://dl.dropbox.com/u/1131502/HeroicDeath/heroicdeath_screenshot.png

Installation


  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
    Configuration

config.yml
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:

[SPOILER]<<code>># HeroicDeath Configuration

  1. Messages are defined in heroicdeath.messages
  2. Items (for PvP kills) are defined in heroicdeath.items
  3. This file is for configuration of colors, log preferences and localized mob names
    1. Color options
    2. message: Text color of death notifications, wrapped around names/item.
    3. name: Color for the name of victim and killer.
    4. item: Color for the name of the item used in a PvP death.
  4. Color is defined according to the Bukkit enum ChatColor
  5. Acceptable entries:
    1. BLACK
    2. DARK_BLUE
    3. DARK_GREEN
    4. DARK_AQUA
    5. DARK_RED
    6. DARK_PURPLE
    7. GOLD
    8. GRAY
    9. DARK_GRAY
    10. BLUE
    11. GREEN
    12. AQUA
    13. RED
    14. LIGHT_PURPLE
    15. YELLOW
    16. WHITE
  6. If color entered is inappropriate, HeroicDeath will default to the following values:
    1. message: RED
    2. name: DARK_AQUA
    3. item: GOLD colors: message: RED name: DARK_AQUA item: GOLD
  1. Logging Preferences:
    1. data: true to log a serialized object representing all the relevant information associated with a death
    2. messages: true to log death messages (as output to the server) to a separate file
    3. time: Whether or not to timestamp messages (if logging messages), and what timestamp format to use for data/messages
      1. stamp: true to timestamp messages
      2. format: Uses format strings from Java SimpleDateFormat. Read all here: http://download.oracle.com/javase/1.4.2/docs/api/java/text/SimpleDateFormat.html
    4. files: Filenames to store data/messages in. A server admin could ostensibly change this value daily/weekly/monthly for collection of timed logs
      1. data: Data storage filename
      2. messages: Messages storage filename log: data: true messages: true time: stamp: true format: MM/dd/yyyy HH:mm:ss z files: data: death_data.log messages: death_messages.log
  1. Event Support:
    1. 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. events: only: false
  1. Localized monster names:
    1. If you would like to specify custom localization for the mob names, edit the defaults below monsters: ghast: Ghast slime: Slime monster: Monster zombie: Zombie pigzombie: PigZombie spider: Spider creeper: Creeper skeleton: Skeleton wolf: Wolf unknown: Unknown giant: Giant
  2. Options
    1. useDisplayName: Set to true if you want HeroicDeath to display the player's display name instead of their fixed character name.
    2. serverBroadcast: Set to FALSE if you want HeroicDeath to only broadcast its messages in the world they belong to.
    3. worlds: Lists of quiet/loud worlds for broadcast targeting. NOTE: World names are case-sensitive.
      1. quiet: Worlds listed here will NEVER receive ANY HeroicDeath broadcasts.
      2. loud: Worlds listed here will ALWAYS receive ALL HeroicDeath broadcasts. options: useDisplayName: false serverBroadcast: true worlds: quiet: [peacefulworld, noobworld] loud: [pvpworld, nether] <</code>>[/SPOILER]

heroicdeath.messages 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

heroicdeath.items 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"

Localization
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 - http://dl.dropbox.com/u/40701071/heroicdeath.messages

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.

HeroicDeath Changelog

Version 1.11.3


  • Added 1.0 mobs
  • fix some old code and cleanup
  • rewrite structure of config file

    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.

    Version 1.9.1

  • Added support for world names in death messages. Use %w in your messages and it'll get replaced with the world.

    Version 1.9.0

  • Now supports per-world messaging! Set options.serverBroadcast to FALSE to force HeroicDeath to only send its messages to the world in which the death occurred.
  • Add the name of a world to options.worlds.quiet to prevent ANY HeroicDeath message from being sent to that world (even if options.serverBroadcast is true!)
  • Add the name of a world to options.worlds.loud to send ALL HeroicDeath messages to that world (even if options.serverBroadcast is false and the death didn't occur on that world)
  • Fixed yet another projectile bug, this should be the last time for now!
  • Added 1.7 items to the default-generated heroicdeath.items file (took long enough!)

    Version 1.8.4

  • Fixed a bug with projectile detection.

    Version 1.8.3

  • Added config option "options.useDisplayName" to allow admins to choose whether or not to display a player's set display name.
  • Removed references to deprecated event EntityDamageByProjectileEvent

    Version 1.8.2

  • Made HeroicDeathEvent cancellable; cancelling the event prevents broadcast of the message. This is important if another plugin wants to selectively disable death messages.
  • Made DeathCertificate in HeroicDeathEvent modifiable via a setter. This is important if another plugin wants to selectively change the death message.

    Version 1.8.1

  • Improved damage type detection. This is kind of advanced; basically I only record a damage type if it would put your health at or under 0. Now I additionally throw it out after 20 server ticks (1 seconds) as stale data, allowing a new damage type to be overwritten, and I further won't allow a damage type to be written if it has a pending record, UNLESS that pending record is for Lava or Lightning (whose readings are frequently thrown off by fire).

    Version 1.8.0

  • Added Lightning messages.
  • Removed explicit references to ISO-8851-1

    Version 1.7.3

  • Added world to data log.
  • Removed death dupe bugfix (long-since implemented in CraftBukkit)

    Version 1.7.2

  • Bugfix: Fixed TNT showing up as Creeper death.

    Version 1.7.1

  • Added Wolf messages.
  • Added author to plugin.yml

    Version 1.7.0

  • Updated to RB 602 - WON'T WORK ON CB 560-
  • Added DamageType.VOID; use the ":void" label in "heroicdeath.messages" to customize your void deaths.

    Version 1.6.1

  • Bugfix: Changed HashMap in HeroicDeathItems to use the item as a key and not its name, thanks MadJawa.

    Version 1.6.0

  • Added support for mob-specific death messages, like the creeper already has
  • If a monster does not have any specific death messages defined, it will use a random "Monsters" message
  • To add mob-specific messages, edit your "heroicdeath.messages" file and add a new label with the mob's default name. If you changed the mob names in your config.yml, use its default name for your label, and use %a to insert your localized mob names! Example:
    [SPOILER]
    :Skeleton %d got boned by %a :Spider %d was wrapped in silk by %a :Zombie %d's brains tasted good to %a :Creeper %d was %a bombed %d hugged a %a
    [/SPOILER]
    [*]Valid labels are :Ghast, :Slime, :Zombie, :PigZombie, :Spider, :Skeleton, :Giant, :Creeper (you should already have :Creeper)
    [*]Bugfix: Fixed creeper messages for users who changed the default name of the creeper mob.
    [*]Added the new 1.3 items to the heroicdeath.items file. If you want these to be added to your items file, just delete it and it'll be recreated from default. Keep in mind that the heroicdeath.items file only specifies *custom* item names; if it encounters an item that isn't in the file, it'll use that item's default name.
    [/LIST]
    Version 1.5.1

  • Fixed duping bug for admins who are running CB <521

    Version 1.5.0

  • Added support for customizing monster names. Upon next reload, your config file will be extended with the default monster names, which you can then edit as desired.

    Version 1.4.4

  • Bugfix: Fixed creepers returning the generic monster message.
  • Changed name of custom event thrown by HeroicDeath to "HeroicDeathEvent"

    Version 1.4.3

  • Added an "events.only" configuration option for plugins that use HeroicDeathEvent: set this option "true" to disable HeroicDeath messages (and send only events on death). Again, not a required update for server admins unless you want to run a plugin that supports this.

    Version 1.4.2

  • Added Dutchy's implementation of a custom "HeroicDeathEvent" event that is called when a player dies, containing the DeathCertificate. Other plugin developers can use this to easily receive more detailed information about a player death than is provided in ENTITY_DEATH alone.

    Version 1.4.1

  • Bugfix: Removed Stupidly Long Constructor to fix WARNING logs in CB Jenkins build 45+ (Bamboo 400+ I believe)

    Version 1.4.0

  • Updated for compatibility with new CraftBukkit event handling in 349+
  • DO NOT download this version if you are using a CraftBukkit bamboo build of 348 or below!

    Version 1.3.1

  • Bugfix: Fixed an unhandled null in death reporting, only reachable when a user dies with no known cause.
  • No config changes, download JAR only to upgrade. Tested against bamboo builds 211, 231, 254, and 302.

    Version 1.3.0

  • Added support for logging. Death data and death messages can be logged.
  • Death data log stores Victim, Killer, Murder Weapon, Cause of Death, Location, Timestamp, and Death Message
  • Death messages log just stores death messages (intended for ease of reading), but can optionally be timestamped
  • As always, users upgrading only need the .JAR and defaults will be chosen, but it is recommended to add the following block to your config.yml to configure logging options:
    [SPOILER]<<code>>
  1. Logging Preferences:
    1. data: true to log a serialized object representing all the relevant information associated with a death
    2. messages: true to log death messages (as output to the server) to a separate file
    3. time: Whether or not to timestamp messages (if logging messages), and what timestamp format to use for data/messages
      1. stamp: true to timestamp messages
      2. format: Uses format strings from Java SimpleDateFormat. Read all here: http://download.oracle.com/javase/1.4.2/docs/api/java/text/SimpleDateFormat.html
    4. files: Filenames to store data/messages in. A server admin could ostensibly change this value daily/weekly/monthly for collection of timed logs
      1. data: Data storage filename
      2. messages: Messages storage filename log: data: true messages: true time: stamp: true format: MM/dd/yyyy HH:mm:ss z files: data: death_data.log messages: death_messages.log<</code>>[/SPOILER]

[*]Example Data Log output:

[SPOILER]<<code>>#HeroicDeath Data Log - This file stores serialized data on player deaths in the following order:

  1. Victim|Killer|Murder Weapon|Cause of Death|Location|Timestamp|Death Message
  2. Murder weapon is in the format TypeIDxData, so Red Wool would be 35x14
  3. Location is in the format (x, y, z), and represents where the victim died. SquallSeeD31|Monster||ENTITY_ATTACK|(-112.0,66.0,184.0)|02/09/2011 22:18:09 PST|SquallSeeD31 got shot by a dispenser. SquallSeeD31|Monster||ENTITY_ATTACK|(-112.0,66.0,184.0)|02/10/2011 02:55:18 PST|SquallSeeD31 got shot by a dispenser. SquallSeeD31|null||BLOCK_EXPLOSION|(-112.0,57.0,190.0)|02/10/2011 02:55:38 PST|SquallSeeD31 apparently has an explosive personality SquallSeeD31|Monster||ENTITY_ATTACK|(-113.0,66.0,184.0)|02/10/2011 02:56:25 PST|SquallSeeD31 got shot by a dispenser. SquallSeeD31|SquallSeeD31|331x0|ENTITY_ATTACK|(-116.0,67.0,184.0)|02/10/2011 02:56:51 PST|SquallSeeD31 killed SquallSeeD31 wielding redstone dust SquallSeeD31|SquallSeeD31|35x14|ENTITY_ATTACK|(-115.0,67.0,183.0)|02/10/2011 03:04:07 PST|SquallSeeD31 killed SquallSeeD31 wielding red wool SquallSeeD31|CACTUS||CONTACT|(-133.0,66.0,187.0)|02/10/2011 03:32:28 PST|SquallSeeD31 poked a cactus, but the cactus poked back SquallSeeD31|Dispenser||ENTITY_ATTACK|(-112.0,66.0,185.0)|02/10/2011 03:32:55 PST|SquallSeeD31 got shot by a dispenser. <</code>>[/SPOILER]
    [/LIST]
    Version 1.2.0

  • Added support for Dispensers! As always, a default message will be used if you do not supply custom messages.
  • Use the ":Dispenser" label to add dispenser messages in your heroicdeath.messages file.
  • Due to Bukkit limitations, it is not possible to know who triggered the dispenser, so the only usable token is %d
  • Format Example:
    :Dispenser %d got shot by a dispenser. %d did not need a dispenser there. %d was dispensed of.

    [/LIST]
    Version 1.1.2

  • Bugfix: Creeper deaths will now always use Creeper-specific messages.

    Version 1.1.1

  • Bugfix: Added support for Slime/Giant monster types

    Version 1.1.0

  • Added support for items with durability (wood, coal, wool, dye)
  • Fixed display of "fists" (entry needs to be NAME:0:-0x1 to work properly)

    Version 1.0.0

  • Initial public release!

Comments

Login to Curse

Don't have an account? Create One.

Get an epic experience with Curse Premium
  • Faster addon downloads
  • Premium-Only Beta Giveaways
  • Ad-Free Curse experience
  • Premium Curse Client
  • and many More Features
  • Learn More »

Infinite Crisis NA

Get Your Preferred Access Code!