When using the minecraft:behavior.delayed_attackcomponent, if the pushable target under attack has a collision box larger than that of the attacker, it triggers a pathfinding blockage that prevents the attacking entity from executing normal attacks.minecraft:behavior.delayed_attack。
The severity of this bug lies in the fact that it effectively breaks the combat AI for any custom or vanilla entity utilizing the minecraft:behavior.delayed_attack component. This pathfinding loop prevents the entity from fulfilling its core function, rendering it passive and unresponsive in combat scenarios against larger targets. This significantly limits the utility of data-driven entity behaviors in the Bedrock Edition.
这个漏洞的严重性在于它实际上会破坏任何使用该 minecraft:behavior.delayed_attack 组件的自定义或原版实体的战斗 AI。这种寻路循环阻止了实体完成其核心功能，使其在面对大型目标的战斗场景中变得被动且无反应。这大大限制了基于数据的实体行为在 Bedrock 版中的应用。
While I could switch to minecraft:behavior.melee_box_attack or minecraft:behavior.melee_attack as a workaround, the trade-off is unacceptable: I would lose access to the hit_delay_pct feature from minecraft:behavior.delayed_attack. This is a critical parameter that allows precise control over the timing of damage within an attack animation, a functionality that cannot be replicated with other components.
虽然我可以切换到 minecraft:behavior.melee_box_attack 或 minecraft:behavior.melee_attack 作为变通方法，但这种权衡是不可接受的：我将失去 hit_delay_pct 功能的访问权限 minecraft:behavior.delayed_attack 。这是一个关键参数，允许对攻击动画中伤害的时机进行精确控制，这一功能是其他组件无法复制的。
Therefore, I propose the following solutions: either fix the bug where minecraft:behavior.delayed_attack fails to trigger attacks due to hitbox collisions, or implement hit_delay_pct (or an equivalent function) into the minecraft:behavior.melee_box_attack component.
因此，我提出以下解决方案：要么修复因碰撞 minecraft:behavior.delayed_attack 判定导致无法触发攻击的 bug，要么在组件中 minecraft:behavior.melee_box_attack 实现 hit_delay_pct（或类似函数）。
Linked issues
is duplicated by 2
Attachments
Comments 6
I understand the policy regarding duplicate reports. However, I am submitting this because the issue remains unresolved in the current version of the game, despite previous reports being marked as "resolved."
The reason I am providing this new, more detailed report is that the previous ones did not lead to an actual fix. I have included a specific reproduction world and a sample Addon that clearly demonstrate the pathfinding failure.
Please review the attached evidence, as this is a critical regression (or persistent bug) that severely impacts Addon development. I am not trying to spam, but to ensure this functional break in minecraft:delayed_attack is accurately addressed.
Please delete this duplicate ticket. I’ve already supplemented the original report (MCPE-222718) with all necessary files and repro steps. Since this issue is still reproducible, please also reopen MCPE-222718 (change status from Resolved to Open). Thanks!
I have now supplemented this original report with all necessary reproduction files and detailed steps as requested. Please note that this issue still persists in the latest version!
Since the core evidence is now fully provided here, could you please REOPEN this ticket and change the status from 'Resolved' back to 'Open'? This is a critical bug for Add-on development, and I've consolidated all data to this single thread. Thank you.
My apologies, sent to the wrong ticket. Please refer to the primary report MCPE-222718 for all updated evidence. You can proceed with deleting this duplicate. Thank you!
Please stop duplicating this report. Your previous reports have been resolved as duplicates of this one.