When a Channeling trident hits a mob under the right conditions, it summons lightning at that location. The immediate tick of lightning damage is skipped due to damage invulnerability from the trident itself, but the mob sometimes takes a tick of damage later due to MC-72028. This results in very inconsistent damage output.
See the comments for further discussion of this issue.
Linked issues
is caused by 1
Attachments
Comments 9
I see what you mean that the damage from the lightning bolt can be entirely skipped due to this issue. I will leave it as a duplicate for now but will make a note about it internally so that Mojang can decide how they want to track these issues.
Why moderators not affiliated with Mojang like yourself are allowed to freely make these decisions before they ever reach developers is beyond me.
MC-72028 being triaged and left open establishes that lightning dealing damage twice is unintended. If the same were done here, which given how things have gone in the past seems entirely possible, there would be two mutually exclusive reports left open, making it difficult to say with certainty what is a bug and what isn’t. While I am usually content to confirm issues and trust in the triage process, in this case I would rather ask about things internally to ensure that things are wrapped up quickly. Please be assured that in the worst case I will make sure that this report can be changed to “Damage from Channeling lightning is sometimes skipped on the hit entity” and linked as caused by MC-72028.
I have, give them a couple of days to respond. If they do not I will rewrite this report to be about Channeling hits dealing inconsistent damage and reopen it with a caused by link already added.
It was requested that this be reopened for normal triage. I will rewrite the report shortly. I hope Mojang makes the right call…
Recap for Mojang: OP assumed lightning always dealing damage twice was intended (MC-72028 being open implies that it isn’t), and that therefore a stationary target should always take damage from the trident and then a tick of lightning damage later. Since this assumption is false I do not know that this issue needs to be tracked in its own report, and think it would make sense to resolve this into MC-72028.
My own thoughts: The way to enforce consistency is to fix MC-72028 and then remove damage invulnerability while making it so attackers track their own attack cooldown (either one single cooldown, for mobs which swing their arms, or a per-target cooldown, for mobs and entities which deal continuous damage like lightning, slimes and the ender dragon). I have always seen damage invulnerability as something that was just added in a hurry to prevent players from killing their enemies quickly by spam-clicking, it cannot compete on merit with an attacker-cooldown system, which is why basically every other game uses the latter. Furthermore, the current system makes bugs like MC-107856, MC-169167 and MC-191642 basically inevitable, with more sure to come in future updates. In this and other areas I would like to see the game evolve to match the needs of the players rather than remain bound by decisions that were made with haste a long time ago.
For lack of a better alternative, I will resolve this as a duplicate of MC-72028 even though the assumed intended behavior is the opposite.