This repository has been archived by the owner on Nov 9, 2017. It is now read-only.
Add an EntityDespawnEvent. Fixes BUKKIT-5645 #36
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Split from GlowstoneMC/Glowkit#3
Original Bukkit PR: Bukkit#1070
Additional changes: None
Glowstone implementation: Not done
Previously it was not possible to determine when an entity despawns for
reasons other than death. This made it difficult for plugins to determine
things like despawning due to distance or other causes, and therefore may
still track those now-missing entities.
This commit allows plugin authors to determine what happened to entities
when they despawn for their various reasons, therefore making plugin
developer's lives a little bit easier.