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

    SquallSeeD31

    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

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






    [​IMG]

    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:

    Show Spoiler
    Code:
    # 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:
    ##BLACK
    ##DARK_BLUE
    ##DARK_GREEN
    ##DARK_AQUA
    ##DARK_RED
    ##DARK_PURPLE
    ##GOLD
    ##GRAY
    ##DARK_GRAY
    ##BLUE
    ##GREEN
    ##AQUA
    ##RED
    ##LIGHT_PURPLE
    ##YELLOW
    ##WHITE
    #
    #If color entered is inappropriate, HeroicDeath will default to the following values:
    ##message: RED
    ##name: DARK_AQUA
    ##item: GOLD
    colors:
        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: http://download.oracle.com/javase/1.4.2/docs/api/java/text/SimpleDateFormat.html
    ##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
    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
    
    #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.
    events:
        only: false
    
    #Localized monster names:
    ##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
    #Options
    ##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.
    options:
        useDisplayName: false
        serverBroadcast: true
        worlds:
            quiet: [peacefulworld, noobworld]
            loud: [pvpworld, nether]
    



    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:

    Code:
    %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.
     
    kahlilnc, Chike, SmartyGeek and 20 others like this.
  2. Offline

    netraameht

    You are the best :D
     
  3. Offline

    andrewkm

    @SquallSeeD31
    Im just doing some testing with the newer cbs.
    Using #1087 -> every death message is broadcasted twice. Just a little headsup :)
     
  4. Offline

    SquallSeeD31

    Three possibilities for that:
    1) You have another plugin that's broadcasting death messages. That'd be trivially easy to figure out, just look and see if it's exactly the same message or not.
    2) HeroicDeath is reporting the same death twice. Check death_data.log and see if there are two entries for every death.
    3) Two EntityDeathEvents are being sent for every death. HeroicDeath can't do anything about this. This would be an erroneous situation caused most likely by another plugin, as I don't see any changes from 1060 to 1087 that could cause that.
     
  5. Offline

    andrewkm

    @SquallSeeD31
    Code:
    2011-09-03 17:32:16 [SEVERE] Could not pass event ENTITY_DEATH to HeroicDeath
    java.lang.NullPointerException
     at org.bukkit.craftbukkit.entity.CraftPlayer.sendRawMessage(CraftPlayer.java:105)
     at org.bukkit.craftbukkit.entity.CraftPlayer.sendMessage(CraftPlayer.java:109)
     at org.bukkit.craftbukkit.CraftServer.broadcast(CraftServer.java:763)
     at org.bukkit.craftbukkit.CraftServer.broadcastMessage(CraftServer.java:238)
     at com.herocraftonline.squallseed31.heroicdeath.HeroicDeathListener.onEntityDeath(HeroicDeathListener.java:131)
     at org.bukkit.plugin.java.JavaPluginLoader$60.execute(JavaPluginLoader.java:663)
     at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:58)
     at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:338)
     at net.minecraft.server.EntityPlayer.die(EntityPlayer.java:142)
     at net.minecraft.server.EntityLiving.damageEntity(EntityLiving.java:391)
     at net.minecraft.server.EntityHuman.damageEntity(EntityHuman.java:438)
     at net.minecraft.server.EntityPlayer.damageEntity(EntityPlayer.java:180)
     at net.minecraft.server.EntityLiving.a(EntityLiving.java:489)
     at net.minecraft.server.EntityHuman.a(EntityHuman.java:868)
     at net.minecraft.server.Entity.a(Entity.java:635)
     at net.minecraft.server.EntityPlayer.b(EntityPlayer.java:360)
     at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:363)
     at org.getspout.spout.SpoutNetServerHandler.a(SpoutNetServerHandler.java:596)
     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:89)
     at org.getspout.spout.SpoutNetServerHandler.a(SpoutNetServerHandler.java:478)
     at net.minecraft.server.NetworkListenThread.a(SourceFile:105)
     at net.minecraft.server.MinecraftServer.h(MinecraftServer.java:453)
     at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:363)
     at net.minecraft.server.ThreadServerApplication.run(SourceFile:422)
    2011-09-03 17:32:31 [INFO] [G] [Owner] andrewkm: woah ... nowherodeath doesnt even work
    2011-09-03 17:32:52 [SEVERE] Could not pass event ENTITY_DEATH to HeroicDeath
    java.lang.NullPointerException
     at org.bukkit.craftbukkit.entity.CraftPlayer.sendRawMessage(CraftPlayer.java:105)
     at org.bukkit.craftbukkit.entity.CraftPlayer.sendMessage(CraftPlayer.java:109)
     at org.bukkit.craftbukkit.CraftServer.broadcast(CraftServer.java:763)
     at org.bukkit.craftbukkit.CraftServer.broadcastMessage(CraftServer.java:238)
     at com.herocraftonline.squallseed31.heroicdeath.HeroicDeathListener.onEntityDeath(HeroicDeathListener.java:131)
     at org.bukkit.plugin.java.JavaPluginLoader$60.execute(JavaPluginLoader.java:663)
     at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:58)
     at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:338)
     at net.minecraft.server.EntityPlayer.die(EntityPlayer.java:142)
     at net.minecraft.server.EntityLiving.damageEntity(EntityLiving.java:391)
     at net.minecraft.server.EntityHuman.damageEntity(EntityHuman.java:438)
     at net.minecraft.server.EntityPlayer.damageEntity(EntityPlayer.java:180)
     at net.minecraft.server.EntityLiving.a(EntityLiving.java:489)
     at net.minecraft.server.EntityHuman.a(EntityHuman.java:868)
     at net.minecraft.server.Entity.a(Entity.java:635)
     at net.minecraft.server.EntityPlayer.b(EntityPlayer.java:360)
     at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:363)
     at org.getspout.spout.SpoutNetServerHandler.a(SpoutNetServerHandler.java:596)
     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:89)
     at org.getspout.spout.SpoutNetServerHandler.a(SpoutNetServerHandler.java:478)
     at net.minecraft.server.NetworkListenThread.a(SourceFile:105)
     at net.minecraft.server.MinecraftServer.h(MinecraftServer.java:453)
     at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:363)
     at net.minecraft.server.ThreadServerApplication.run(SourceFile:422)
    2011-09-03 17:33:00 [SEVERE] Could not pass event ENTITY_DEATH to HeroicDeath
    java.lang.NullPointerException
     at org.bukkit.craftbukkit.entity.CraftPlayer.sendRawMessage(CraftPlayer.java:105)
     at org.bukkit.craftbukkit.entity.CraftPlayer.sendMessage(CraftPlayer.java:109)
     at org.bukkit.craftbukkit.CraftServer.broadcast(CraftServer.java:763)
     at org.bukkit.craftbukkit.CraftServer.broadcastMessage(CraftServer.java:238)
     at com.herocraftonline.squallseed31.heroicdeath.HeroicDeathListener.onEntityDeath(HeroicDeathListener.java:131)
     at org.bukkit.plugin.java.JavaPluginLoader$60.execute(JavaPluginLoader.java:663)
     at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:58)
     at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:338)
     at net.minecraft.server.EntityPlayer.die(EntityPlayer.java:142)
     at net.minecraft.server.EntityLiving.damageEntity(EntityLiving.java:391)
     at net.minecraft.server.EntityHuman.damageEntity(EntityHuman.java:438)
     at net.minecraft.server.EntityPlayer.damageEntity(EntityPlayer.java:180)
     at org.bukkit.craftbukkit.entity.CraftLivingEntity.damage(CraftLivingEntity.java:177)
     at org.bukkit.command.defaults.KillCommand.execute(KillCommand.java:27)
     at org.bukkit.command.SimpleCommandMap.dispatch(SimpleCommandMap.java:162)
     at org.bukkit.craftbukkit.CraftServer.dispatchCommand(CraftServer.java:346)
     at net.minecraft.server.NetServerHandler.handleCommand(NetServerHandler.java:737)
     at net.minecraft.server.NetServerHandler.chat(NetServerHandler.java:701)
     at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:694)
     at net.minecraft.server.Packet3Chat.a(Packet3Chat.java:33)
     at net.minecraft.server.NetworkManager.b(NetworkManager.java:226)
     at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:89)
     at org.getspout.spout.SpoutNetServerHandler.a(SpoutNetServerHandler.java:478)
     at net.minecraft.server.NetworkListenThread.a(SourceFile:105)
     at net.minecraft.server.MinecraftServer.h(MinecraftServer.java:453)
     at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:363)
     at net.minecraft.server.ThreadServerApplication.run(SourceFile:422)
    Its not just you i realized infact everything is double. Joining, leaving broadcasted double, automessages going double, ect... :p
    Must be bukkit. Going back to 1067#
    edit: Yes heroicdeath is broadcasting them twice in log/console

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

    SquallSeeD31

    Okay, what version of HeroicDeath is this? Can you try using this indev build: http://dl.dropbox.com/u/1131502/HeroicDeath/plugins/DEV/HeroicDeath.jar

    Can you post an excerpt of your death_data.log (in the HeroicDeath folder)

    Just trying to understand what's going on.
     
  7. Offline

    andrewkm

    [​IMG]
    Code:
    #HeroicDeath Message Log - This file stores player death messages as reported to the server
    [09/03/2011 18:24:22 EDT] D0rc fell to their death
    [09/03/2011 18:24:25 EDT] andrewkm fell to their death
    This is using the dev you just gave.
    Only once in console, and death log, but twice in game.
    -
    It must be bukkit as EVERYTHING is showing up twice. Logins/logouts, lotteyr plugin messages, automessages, save-all messages, :p

    @SquallSeeD31
    Just went through all the CB versions. The problem is NON-existant on CB 1074 -> however making the jump to 1078 (All the builds inbetween are red = unstable) the problem shows up.
    Something in bukkit.
    Implemented new broadcast method (commit: 620ec206cae91c60e300fcef0348d2468a2fbea7) — Dinnerbone / githubweb

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

    SquallSeeD31

    Thanks for the research andrew, I'm at the football game right now but I'll try to check out that build later. Either way, as you noted, if it only logs once the only thing I could do is change the broadcast message
     
  9. Offline

    GarretSidzaka

    im pretty sure this is a bukkit issue
     
  10. Offline

    andrewkm

    @SquallSeeD31
    @GarretSidzaka
    It is actually a spout confliction with 1075 :p Nothing for heroicdeath to worry about, after messing around a bit more with stuff.
    PS: Hope you had a good football game :D
     
  11. Offline

    SquallSeeD31

    Thank you once again for the followup. ... And yes I did, Aztecs 49-21 =)
     
  12. Offline

    GarretSidzaka

    wrong! i dont use spout anymore brotha so thats not it!

    we were noticing death lag from this plugin

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

    SquallSeeD31

    I'm not sure what that means, could you elaborate?
     
  14. Offline

    andrewkm

    Removing spout stops the double messages for me completely.
     
  15. Offline

    Armaxxx

  16. Offline

    SquallSeeD31

  17. Offline

    Armaxxx

    i really dunno whats bukkit dev for, but what i know is that the page i sent you is for automatic "updates" of the plugins but thanks anyway ^_^
     
  18. Offline

    hexagonlux

    how hard would it be to have the players dropped items also logged?
     
  19. Offline

    SquallSeeD31

    Not terribly, but how exactly would you want that data to be displayed? I'd have to see if that's the sort of feature that really belongs in HeroicDeath.
     
  20. Offline

    hexagonlux

    I have been looking for a plugin that gives me a list of things that people lose on death in case my server hiccups and causes someone to die. I dont know if it would go best in the log that is already detailing how/ where they died or in a new file all together. I definitely don't think this information needs to be broadcasted.

    Thanks for the reply :)
     
  21. Offline

    McLovn

    Can you add HeroicDeath to BukkitDev Please?
     
  22. Offline

    SovereigN_

    How do I make it to where it shows who killed who? I installed the plugin and tested it to see if it displays who killed who but it says Herobrine or unknown causes. Help please? :<
     
  23. Offline

    SquallSeeD31

    Which version of HeroicDeath, which version of CraftBukkit?
     
  24. Offline

    SovereigN_

    HeroicDeath version is whatever you had in the 'Latest Jar Only' and as for the Bukkit version I have no idea... (Fairly new to this) but I know all my plugins work. Is there a way to verify my Bukkit version?
     
  25. Offline

    SquallSeeD31

    If you type "/version" in game or from your server console, then "/version HeroicDeath" and post the output of both, I'll be able to get what I need.
     
  26. Offline

    Ocram

    Funny plugin :)
    It's possible, in a future release, you add fully customizable formatting messages taking color codes(&0-f) directly from "heroicdeath.messages" file?
    Would be great .
     
  27. Offline

    SquallSeeD31

    I suppose; no harm in adding it.
     
  28. Offline

    beanpastebunn

    I am experiencing problems with heroric death. I added custom death messages but when people die, it uses default death messages like Nickname1 was killed by lava
     
  29. Offline

    SquallSeeD31

    Paste your heroicdeath.messages and I can see if it's a parsing issue.
     
  30. Offline

    beanpastebunn

    Code:
    :Drown
    %d blocked their snorkel
    %d forgot their air tank
    %d shipwrecked
    :Cactus
    %d ate the wrong green food
    %d took the catcus as his teddy
    %d poked the catcus, the catus poked back
    %d loved the catcus too much
    :Fire
    %d danced in the campfire
    %d forgot about his mashmollows
    :Explosion
    %d's guts splattered across the room
    %d found a good way to propell his head to the moon
    :Creeper
    %d found out he wasn't punching a catcus
    %d found a... *HISS* *BOOMmm*
    :Ghast
    %d had a snowball fight with a %a
    %d realised the jellyfish in the sky wasn't a cat
    :Slime
    %d got smothered with slime
    :Zombie
    %d got raped by a %a
    :PigZombie
    %d punched a pigzombie. They all punched back.
    :Spider
    %d played SAW with a spider
    :Skeleton
    %d didn't know where the arrows came from. A %a
    :Giant
    %d got squashed by a %a
    :Wolf
    %d shouldn't buy %a from guys in a van anymore
    :Fall
    %d forgot his parachute
    %d proved Newton right
    %d realised why skydiving is a dangerous sport
    %d didn't learn gravity
    :PVP
    %d got slashed by %a and his %i
    %d had a mining accident with %a
    :Void
    %d fell off the world
    :Lava
    %a overheated his hot tub
    %a became hot soup
    %a became the inside of a volcano
    :Other
    %a got attacked by Herobrine
    %a got attacked by Israphel
    %a got attacked by an Unknown object
    :Suffocation
    %a got crushed by falling gravel and sand
    %a ate some sand
    :Dispenser
    %a was attacked by hidden arrows
    :Lightning
    %a will remember not to wear tin foil clothes in a storm
    %a realised playing golf in the rain is a bad idea
    %a became a zombie pig
    %a was fishing in the rain[09/11/2011 17:25:37 BST] krafting became obsidian
    [09/11/2011 17:26:33 BST] krafting became obsidian
    [09/11/2011 17:26:43 BST] krafting was killed by Herobrine
    [09/11/2011 17:28:18 BST] krafting was killed by lava
    [09/11/2011 18:06:31 BST] megagary18 took a bath in a lake of fire
    [09/11/2011 18:14:24 BST] krafting was killed by an angry Neighbour
    [09/11/2011 18:14:34 BST] megagary18 was killed by an angry Neighbour
    
     
  31. Offline

    SquallSeeD31

    Well, for starters, all your messages from Lava down use %a instead of %d, and there's no "attacker" for most of those messages. However, what's curious to me is the monster message; that's default too even though it looks like you have some custom entries. What is "Neighbour" in your config.yml?

    Also, to check, which version of HeroicDeath, which version of CraftBukkit, and is this file named heroicdeath.messages and stored in plugins/HeroicDeath?

    One more question real quick: Do ANY of your custom messages work?
     

Share This Page