Autor Tema: DeathMessagesPrime v1.13.11 → 1.12 + 1.13  (Leído 424 veces)

C4BR3R4

  • SuperAdmin.
  • *
  • País: es
    • Ver Perfil
DeathMessagesPrime v1.12.5 → 1.12
« Respuesta #15 en: 11 de Julio de 2017 a las 08:40 »
1.12.5  Fixed Thorns

    Fixed the Thorns death message and added a new API feature, registerTagPrefix.

C4BR3R4

  • SuperAdmin.
  • *
  • País: es
    • Ver Perfil
DeathMessagesPrime v1.12.7 → 1.12
« Respuesta #16 en: 14 de Julio de 2017 a las 08:45 »
1.12.7  Removed debug message

    Self-explanatory.

1.12.6  Fixed %weapon% with bows

    If show-custom-death-msg-on-all-weapons was true and/or PlayerProjectileCustom message was used, the %weapon% tag would not work properly. This has been fixed.

C4BR3R4

  • SuperAdmin.
  • *
  • País: es
    • Ver Perfil
DeathMessagesPrime v1.12.8 → 1.12
« Respuesta #17 en: 15 de Julio de 2017 a las 09:10 »
1.12.8  Implemented FallKillWeapon & fixed TNTKill

    FallKillWeapon (which should already be in config.yml) should now work, appearing instead of FallKill with the same conditions as PlayerCustom / PlayerMelee. TNTKill has been fixed and should now appear again with primed TNT. No config changes needed.

C4BR3R4

  • SuperAdmin.
  • *
  • País: es
    • Ver Perfil
DeathMessagesPrime v1.12.9 → 1.12
« Respuesta #18 en: 17 de Julio de 2017 a las 20:12 »
1.12.9  FallKillWeapon fix

    Will not error anymore when the killer is not a player.

C4BR3R4

  • SuperAdmin.
  • *
  • País: es
    • Ver Perfil
DeathMessagesPrime v1.12.10 → 1.12
« Respuesta #19 en: 25 de Julio de 2017 a las 08:51 »
1.12.10  Sweep attack fix

    In case that damage from a sweep attack kills the player, the death message should now appear properly. (Not sure if this was ever a concern though)

C4BR3R4

  • SuperAdmin.
  • *
  • País: es
    • Ver Perfil
DeathMessagesPrime v1.12.11 → 1.12
« Respuesta #20 en: 25 de Julio de 2017 a las 20:54 »
1.12.11
1.8 support readded

    This is the initial test of readding 1.8 support, which was removed in DMP version 1.2. If there are any issues (such as errors in console), please report them in the thread.

C4BR3R4

  • SuperAdmin.
  • *
  • País: es
    • Ver Perfil
DeathMessagesPrime v1.12.12 → 1.12
« Respuesta #21 en: 03 de Agosto de 2017 a las 08:53 »
1.12.12  Bed death message & death message cooldown

    Added a bed death message and a death message cooldown system.

    Configs updated, changes (except if you regenerate your config):

    config-version is now 35.

    Added Bed death message:
Código: [Seleccionar]
...
    EnderCrystal:
      - "%plrtag% blew up"
    Bed: # exploding beds
      - "%plrtag% blew up"
    Cactus:
      - "%plrtag% was pricked to death"
...

Added the config flags for the cooldown (between worlds-death-message-radius and debug):
Código: [Seleccionar]
# If a player dies over death-count times within death-interval seconds,
# death messages from that player will be hidden for death-cooldown seconds.
# If death-reset is true, every hidden death message resets the cooldown.
cooldown-death-count: 3
cooldown-death-interval: 10
cooldown-death-cooldown: 10
cooldown-death-reset: false

C4BR3R4

  • SuperAdmin.
  • *
  • País: es
    • Ver Perfil
DeathMessagesPrime v1.12.13 → 1.12
« Respuesta #22 en: 07 de Agosto de 2017 a las 23:00 »
 Conflict & Ender Dragon Breath fixes

    Fixed possible plugin conflicts, the plugin tries its best to display the modified death message now if a plugin interferes, with an option to toggle whether DMP will use the standard Spigot death message broadcasting in that case (false) or broadcast the custom death message provided by some other plugin using its own system (true, default).

    A couple of errors (causing stack traces) relating to deaths caused by Ender Dragon breath are also fixed.

    Config updates:
    - config-version updated to 36.
    - death-message-compat-mode description was changed:
Código: [Seleccionar]
# Death message compatibility: set the message as normal, until HIGHEST,
# when it is emptied.
# Use this if any conflicts arise.
death-message-compat-mode: ...

- A new option, death-message-conflict-broadcast, under death-message-compat-mode:
Código: [Seleccionar]
# Whether to use DMP broadcasting if a custom death message is set by
# another plugin.
death-message-conflict-broadcast: true

C4BR3R4

  • SuperAdmin.
  • *
  • País: es
    • Ver Perfil
DeathMessagesPrime v1.12.14 → 1.12
« Respuesta #23 en: 11 de Agosto de 2017 a las 00:52 »
1.12.14 Compatibility & priority changes

    Death messages are now broadcasted at MONITOR, not HIGHEST. compat-mode is now true by default (in the new config.yml, no changes needed however) and handles hidden death messages (e.setDeathMessage(null)) correctly.

C4BR3R4

  • SuperAdmin.
  • *
  • País: es
    • Ver Perfil
DeathMessagesPrime v1.12.16 → 1.12
« Respuesta #24 en: 13 de Agosto de 2017 a las 15:27 »
v1.12.16 https://www.spigotmc.org/resources/deathmessagesprime.3789/update?update=180909
 Fixed %weapon% possibly being empty

    This would only happen with weapons with no custom name. It attempts to use a standard name based on the item's type now, although at some point translation support for it will be added.


v1.12.15 https://www.spigotmc.org/resources/deathmessagesprime.3789/update?update=180790
 PVP prefix/suffix and custom messages for killing players

    Added custom-messages-per-killer-player (custom messages for a killing player) as well as prefix-pvp and suffix-pvp (prefix and suffix for PVP messages only).

    Config changes:

    config-version updated to 37.

    Added under the prefix and suffix under death-messages (yes, the fact that they're comments is intentional):
Código: [Seleccionar]
  # If you want a prefix / suffix only for PVP messages, uncomment these:
  # prefix-pvp: "&a[&eD&a] &c"
  # suffix-pvp: ""

Added under the custom-messages-per-player block:
Código: [Seleccionar]
custom-messages-per-killer-player:
  # Same as above, but for killing players in PVP events.
  # To get the UUID of an online player, use /dmsg uuid player_name
 
  # "123e4567-e89b-12d3-a456-426655440000":
  #   natural:
  #     TNTKill:
  #       - "%plrtag% got blown up by a VIP player, %entity%!" 
(custom-messages-per-player.conflict also controls custom-messages-per-killer-player)

C4BR3R4

  • SuperAdmin.
  • *
  • País: es
    • Ver Perfil
DeathMessagesPrime v1.12.17 → 1.12
« Respuesta #25 en: 03 de Septiembre de 2017 a las 19:55 »
1.12.17  Fixed some mob messages not working with custom-mob-death-messages

    Fairly self-explanatory. This mainly affected the Creeper and WitherSpawnBoom messages, which will now be properly checked through TNTKill.

C4BR3R4

  • SuperAdmin.
  • *
  • País: es
    • Ver Perfil
DeathMessagesPrime v1.12.19 → 1.12
« Respuesta #26 en: 27 de Octubre de 2017 a las 10:29 »
1.12.18  Small bugfixes

    No major changes here. This update tries to fix the possible NPE that might sometimes occur.


1.12.19  Multiline colors fixed

    Fixed some bugs where messages split into multiple lines might lose colors (such as when a weapon name wraps to a second line).

C4BR3R4

  • SuperAdmin.
  • *
  • País: es
    • Ver Perfil
DeathMessagesPrime v1.12.20 → 1.12
« Respuesta #27 en: 02 de Noviembre de 2017 a las 08:13 »
v1.12.20 Fixed 1.8 bug

    When running on 1.8, an occasional error related to AreaEffectCloud could break the plugin. This has now been fixed.

C4BR3R4

  • SuperAdmin.
  • *
  • País: es
    • Ver Perfil
DeathMessagesPrime v1.12.21 → 1.12
« Respuesta #28 en: 13 de Diciembre de 2017 a las 07:58 »
1.12.21  Queue glitch possibly fixed

    The exact circumstances of this glitch are still unknown, but the common factor is that a large number of death messages (that either got delayed or were never supposed to be broadcasted in the first place) will get broadcasted at once on specific configurations. There is now a lock around the queue when it comes to broadcasting messages, and some of the checks for each message have been reordered.

C4BR3R4

  • SuperAdmin.
  • *
  • País: es
    • Ver Perfil
DeathMessagesPrime v1.12.21 → 1.12
« Respuesta #29 en: 13 de Diciembre de 2017 a las 16:04 »
Desinstalado porque el plugin ChatControl Pro realiza la misma función