Fire Aspect can nullify the effect of Looting

What do you really mean?

Hey there!

Did you happen to be using any mods or datapacks at the time of when you were experiencing this issue?

@Avoma Hello, nono, its just vanilla, if you want test that "glitch" or "bug",

What he means is that if you hit the mob and Looting activates first, you get more items and Fire Aspect doesn't activate. But if Fire Aspect activates first, Looting won't activate and you won't get more items, only cooked ones.

Is there any possible chance that you could attach a video of this occurring with the F3 debug screen enabled?

 Duplicate of MC-163573

what

This might have the same underlying issue as MC-163573, but the behavior is quite different, so I marked them as related instead.

I also updated the description of this ticket to make it clearer. Hope you're fine with that.

Yes!! No problem, sorry and thanks!

Verified a minimal fix for this on 26.2 with a Fabric mixin. The root cause is that two paths only consult the killing blow's direct attacker, which is null when the fatal tick is the fire your own Fire Aspect lit: the ATTACKING_ENTITY loot parameter in LivingEntity.dropFromLootTable (that's the Looting loss) and the source.getEntity() read in LivingEntity.die (that's the missing per-mob kill statistic). Falling back to lastHurtByPlayer in exactly those two null cases restores Looting drops and the kill stat, while deaths with a real direct attacker are untouched. Vanilla already keeps lastHurtByPlayer with its own memory window and already uses it for advancements and the generic mob_kills counter via getKillCredit(), so those work today; only these two paths forget the player. For comparison, TNT ignited by your flame arrow does credit you, because the TNT inherits the arrow's owner as direct attacker. This does not touch MC-163573, which is the mirror case: there the direct attacker is present and the issue is the killing blow's damage type not counting as fire.