Add a dedicated event for Wind Burst effects

未关闭
#14,483 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

@Doc94 已经在做这个了。

开始于 2024年12月27日。

  • #11840 来自 @Doc94 —— 未关闭

评估

难度
5/5
预计耗时
一周以上
新手友好度
12/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
java
领域
api

调研方向

The payload names no files. Start from the existing EntityAttemptSmashAttackEvent and EntityPushedByEntityAttackEvent in the Paper API, and check how Wind Burst's knockback is currently triggered and whether it has a player source. The design is not settled: the event's fields, whether it can cancel the whole effect, and how it relates to the existing events all need a maintainer decision first. Done means an agreed event shape, with the event firing when Wind Burst triggers and tests showing it can be cancelled.

由索引模型根据 Issue 内容生成。

描述

status: accepted
Is your feature request related to a problem?

When a player attacks a block-containing Sulfur Cube with a mace, the Sulfur Cube is immune to damage, so EntityDamageByEntityEvent is not triggered. However, the mace attack can still trigger Smash Attacks and the Wind Burst enchantment.

Although EntityAttemptSmashAttackEvent allows plugins to deny the Smash Attack using Result.DENY, this does not prevent the Wind Burst effect from activating.

Additionally, now Wind Burst appears to have a player source and can trigger EntityPushedByEntityAttackEvent. However, even when this event is cancelled, Wind Burst can still apply knockback to nearby entities within a limited range.

Describe the solution you'd like.

I would like Paper to introduce a dedicated EntityWindBurstEvent that is fired whenever the Wind Burst enchantment is triggered.

The event should provide:

Access to the player or entity that triggered Wind Burst.

Access to the original target of the mace attack.

Access to entities affected by the Wind Burst effect.

The ability to modify or cancel the resulting knockback.

The ability to cancel the entire Wind Burst effect, preventing it from affecting nearby entities.

This would allow protection plugins to properly identify the source of Wind Burst and enforce region protection rules consistently, without relying on indirect knockback events or temporary tracking mechanisms.

Describe alternatives you've considered.

Perhaps allowing left-click attacks against block-holding Sulfur Cubes to still trigger EntityDamageByEntityEvent could solve this issue?

Other

No response

主要语言
Java
星标
12.8k
派生
3.6k
平均合并
3 天 7 小时
30 天内合并 PR
19

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

PaperMC/Paper 的其他 Issue

查看 PaperMC/Paper 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。