-
Bug
-
Resolution: Unresolved
-
None
-
23w06a, 23w07a, 1.19.4 Pre-release 1, 1.19.4 Pre-release 2, 1.19.4 Pre-release 3, 1.19.4 Release Candidate 1, 1.19.4 Release Candidate 2, 1.19.4, 23w12a, 23w13a, 23w14a, 23w16a, 23w17a, 23w18a, 1.20 Pre-release 2, 1.20 Pre-release 3, 1.20 Pre-release 4, 1.20 Pre-release 5, 1.20 Pre-release 6, 1.20 Pre-release 7, 1.20 Release Candidate 1, 1.20, 1.20.1, 23w43b, 23w44a, 1.20.4, 24w14a, 1.21.1, 24w36a
-
Confirmed
-
Commands, Text
-
Normal
-
Platform
The bug:
Some damage type death messages expect two variables for the translation: one for the victim and one for the killer. In vanilla, this always works fine, but with /damage, it's possible to deal damage of this type without a killer. In this case, due to the recent changes to out of bounds variables, the message is printed without any variable substitution.
How to reproduce:
/damage @s 30 fireball
- Prints "%1$s was fireballed by %2$s"
Expected result:
- The message should output either: "[username] was fireballed by a command" or "[username] was fireballed by %2$s"
- is duplicated by
-
MC-259807 /damage with specific types of damage without an attacker gives wrong death message
- Resolved
-
MC-259840 uses of /damage with certain damage type and damage source cause death message with broken translation
- Resolved
-
MC-259857 %1$s was killed by %2$s
- Resolved
-
MC-259924 /damage arrow damage without "by" will cause undefine death message
- Resolved
-
MC-260674 New /damage command
- Resolved
-
MC-261659 Bug at /damage command: Unresolved references
- Resolved
-
MC-261702 When using command /damage @p mob_attack_no_aggro it says "%1$s was slain by %2$s"
- Resolved
-
MC-264050 Error using the command /damage
- Resolved
-
MC-270449 The "damage" command shows an error in the death message
- Resolved
- relates to
-
MC-259813 /damage can print untranslated "player" and "item" variants of some death messages
- Reopened