LoliColleen

Is the new one added right now? The following is the reason of deprecated: @deprecated use {@link com.destroystokyo.paper.event.entity.EntityKnockbackByEntityEvent} or {@link io.papermc.paper.event.entity.EntityPushedByEntityAttackEvent} I havent seen any cause from neither EntityPushedByEntityAttackEvent nor...

I see. However, the new one has causes but is deprecated(forRemoval=true) so that the building of plugin cant work correctly. I tried @SuppressWarnings("deprecation") to use the new one but the...

Do you mind if I send a Pull Request to join causes to solve the problem as soon as possible? I really need this feature

By the way, shield item has two bugs caused by Vanilla and Spigot's code. Both of these bugs I think can be fixed together. But I'm not sure if this...

Do I need to remove the previous "cause"? Like the method: public void knockback(double d0, double d1, double d2, @Nullable Entity attacker, EntityKnockbackEvent.KnockbackCause cause) Also I m not sure which...

The video was missing. But you can still reproduce this bug easily.

The option to modify the behavior seems feasible. But I personally don't agree. The reason for this is that version 1.20.4 and before that can produce this behavior is essentially...

In addition, plugins can reproduce this behavior. Can monitor EntityDamageByEntityEvent if damage source be blocked when cancel this event. Then make some changes to the contents such as the item...

> About this issue, there is still deviation from Vanilla > > In Vanilla, even if the second attack of a stun does no knockback - which I reported as...

> #10877 created a PR for this, the option will have to live in unsupported, given it introduces a bug we are _technically_ trying to solve. > > It would...