The bug
A less recent attacker than the one that actually caused a player's death can be credited as the killer, appearing in death messages and affecting scoreboards and statistics as mentioned in this comment.
Steps to Reproduce
1) Take one hit from a zombie
2) Take one hit from a husk afterwards
3) Run /kill
Observed result
"Player didn't want to live in the same world as Zombie"
Expected result
"Player didn't want to live in the same world as Husk" since the Husk dealt the most recent damage to the player.
Linked issues
is duplicated by 3
MC-261406
Previous attacker is credited for kill despite being overridden by new attacker
Resolved
MC-261587
playerkills Scoreboard objective and player killed entity advancement do not track correctly
Resolved
MC-261727
Incorrect player kill credit using /effect and /kill from command block after player gets attacked
Resolved
relates to 2
Attachments
Comments
InQuognito
ampolive
@unknown Updated ticket with this information.
InQuognito
This issue is also identifiable in 1.19.3:
https://discord.com/channels/154777837382008833/1073164131026337812
InQuognito
Also, our team has extensively tested this bug and it isn’t just on /kill, it’s any death whatsoever. It also seems to be extremely consistent. It isn’t a chance to happen, this seems to happen every single time (within the 5 second memory limit for attackers)
I've run into the same issue. The first player to hit an other player seems to get the killcredit (till the killcredit cooldown is over) and if a new player hits the same player it doesn't overwrite the previous hitter. This issue only occurs when you use you leftclick/hit a player. When you hit someone with an arrow or with tnt that carries your UUID it does overwrite it properly and gives the last hitter the killcredit.
boq
hey Mojang, you marked my ticket as Duplicate when in fact, this bug runs much deeper than death messages. It affects scoreboards and advancements at their core; It doesn't look like it's the wrong attacker, it is the wrong attacker. This is game breaking for combat maps in 1.19.4. Here are some common examples of issues that can occur because of this:
Monster Hunter achievement could be granted to the wrong player
PvP maps where kills are tracked as the main determining factor for the winner
Maps that run commands at a killer; for instance, a sword with a kill effect such as "Gives player strength I for 3 seconds on kill"
Maps that take advantage of the new death message system
Statistics that track player kill, both in survival and mapmaking alike