Replies: 4 comments
-
The event is deprecated because it duplicates an existing paper event, if the paper events are missing a case, an issue should be filed for that so that can be mitigated, there's no point having multiple events for the same thing |
Beta Was this translation helpful? Give feedback.
-
If so, then it occurs to me to create an event that covers explosions with and without a source that includes a EDIT: But I suppose this would cause a deprecation of the already existing paper event |
Beta Was this translation helpful? Give feedback.
-
It might be useful to create an event that is invoked during an explosion, regardless of where it came from. Mainly, because although I know that there are currently events that are called on similar occasions, however, these events such as |
Beta Was this translation helpful? Give feedback.
-
We added our own event, called in the same places with same reasons in #10831. |
Beta Was this translation helpful? Give feedback.
-
Is your feature request related to a problem?
Actually Paper API has two events that are called when an entity is pushed or receives knockback from another entity.
This is good because EntityKnockbackByEntity of spigot doesn't allow non living entities. So I think that may be the reason why this event is marked as deprecated, it's just my idea.
EntityKnockbackEvent is very usefull to handle explosion that doesn't have a source, like an explosion by a Respawn Anchor or artificial explosions created by World#createExplosion.
The deprecation on EntityKnockbackEvent was introduced in this commit: f172155
Describe the solution you'd like.
Just remove the @deprecated annotation.
Describe alternatives you've considered.
No other.
Other
No response
Beta Was this translation helpful? Give feedback.
All reactions