Skip to content

Conversation

@bobthequail
Copy link

Fixes #752 by switching the method of finding the entity killer from last damage source to entity.getKiller().

@Krakenied
Copy link
Collaborator

Krakenied commented Dec 21, 2025

I don't see possibility that it fixes the issue. Have you even tested it? On which server software and version?

@bobthequail
Copy link
Author

I tested this on a 1.21 Spigot server and it did fix the issue. With the plugin as downloaded from GitHub any mobs which died to due to fire from a Fire Aspect sword did not count for the quest, however with this fix they did. LivingEntity.getKiller() gets the player which Minecraft assigns to be the killer of a mob, which in the case of a mob dying by fire is either null or the player who hit it within the last five seconds (See https://minecraft.wiki/w/Experience#Sources).

@Krakenied Krakenied self-assigned this Dec 21, 2025
Still fallback to last damage event damager if null. It doesn't really fix LMBishop#752, however possibly allows for Fire Aspect tracking of entities ignited within last 5 seconds (similarly to different built-in game mechanics).
@Krakenied
Copy link
Collaborator

Krakenied commented Dec 21, 2025

Maybe it's actually okay for mobkilling, however I want it to still fallback to the last damage cause damager - changed it. Thanks!

@Krakenied Krakenied merged commit 0049726 into LMBishop:master Dec 21, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Fire aspect issue

2 participants