mojira.dev

InQuognito

Assigned

No issues.

Reported

MC-276937 Elytra performs a weird hop not present in past versions when jumping right on touching ground Awaiting Response MC-275980 Food will not get eaten if animation begins immediately out of shield break Awaiting Response MC-271736 Eating animation is not cancelled when the food component is removed mid-animation Cannot Reproduce MC-270494 Items with modified components can be used in recipes, but won't jump to the crafting UI when clicked in the recipe book Duplicate MC-266987 Inconsistent behavior with dead entities Duplicate MC-266023 [Invalid/WAI] scoreboards of type "health" cannot be used as source in /scoreboard players operation Invalid MC-261406 Previous attacker is credited for kill despite being overridden by new attacker Duplicate MC-258392 Projectiles that have their Owner tag modified mid-flight cannot hurt the original Owner Duplicate MC-234860 Passing through Light Blocks in the air make walking noise Duplicate

Comments

Can confirm this is still an issue on the latest release.

Updated. Let me know if this is sufficient data, I didn't really have much else to add because it's pretty straightforward.

This footage was taken on a vanilla server; I'm running Fabric with some client side mods. But I will re-record the footage in a vanilla client when I get home from work.

@tryashtar I have attached a video showing the effect.

https://streamable.com/29un6n

Regardless of its intended behavior, it is still inconsistent behavior.

oh I see, I suppose that makes sense. This is a good catch, thanks for pointing that out!

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)

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