It was requested that this be reopened for normal triage. I will rewrite the report shortly. I hope Mojang makes the right call…
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.
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 couldn’t reproduce the issue where it drops you in the void while you’re standing still, so I assumed you were moving when you did it. Could you upload a video recording of the issue with the debug overlay (F3) enabled and showing the game version and system specs?
You can record your screen using:
On Windows, the built-in Snipping Tool app (shift+win+S)
On macOS, the the built-in Screenshot app (shift+cmd+5)
Third-party software such as OBS
It is recommended that you trim, convert and/or reduce the quality of your recording so that it is under 10MB, as this will make the upload much quicker.
The gateway will always put you in the middle of a block (except in the case of MC-155800, which may no longer exist.) It will not necessarily put the player in a safe location, but if the player is standing still when they teleport they are guaranteed to survive unless that bug occurs. To ask for the gateway to choose a “better” location is a feature request, so I will resolve this as Invalid. You can post this feedback to the Feedback site or Feedback Discord instead, but most likely someone has already made a post regarding this issue, so search for existing posts and upvote them if they exist, and only if no substantially similar post exists should you make your own.
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.
Changed the link to point to the main report to avoid a chain of duplicates.
This report is invalid; game string errors for languages other than US English should be reported on Crowdin, not Mojira.
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.
Please upload a video recording of the issue. Enable the debug overlay (F3) for at least part of the recording, and ensure that the game version and system specs are visible in it.
You can record your screen using:
On Windows, the built-in Snipping Tool app (shift+win+S)
On macOS, the the built-in Screenshot app (shift+cmd+5)
Third-party software such as OBS
It is recommended that you trim, convert and/or reduce the quality of your recording so that it is under 10MB, as this will make the upload much quicker.
You’re absolutely right. I thought I had tested this myself and failed to repro, but I must have forgotten. I have now marked it as Confirmed and will ask internally for a priority reassessment.
If it’s not a hardware problem then this may be due to a system keyboard shortcut, possibly a hardcoded one, as was the case with MC-278386. Try playing Minecraft Classic. You should be able to build with both B and Fn + B. If the latter does not work, then unless your browser is intercepting the key combo, your OS must be, and would do the same for regular Minecraft. Let me know how it goes. (Not sure if it’s possible to test the full Fn + F3 + B in Minecraft Classic, on Firefox the F3 input brings up the search field, but perhaps it would work on another browser.)
Confirmed is for when Mojang or a mod or helper can reproduce the issue, which often is not possible for issues like this.
Me neither. Can you upload a video recording showcasing the bug, with the debug overlay (F3) enabled and showing the game version for at least part of the recording?
You can record your screen using:
On Windows, the built-in Snipping Tool app (shift+win+S)
On macOS, the the built-in Screenshot app (shift+cmd+5)
Third-party software such as OBS
It is recommended that you trim, convert and/or reduce the quality of your recording so that it is under 10MB, as this will make the upload much quicker.
Thanks for responding, I have marked this as Plausible.
Please upload a video recording of the issue with the debug overlay (F3) enabled and showing the game version and system specs.
You can record your screen using the built-in Snipping Tool app (shift+win+S) or third-party software such as OBS. It is recommended that you trim, convert and/or reduce the quality of your recording so that it is under 10MB, as this will make the upload much quicker.
Only reports in English are accepted, since English is the common language used on Mojira. This report will be resolved as Invalid.
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.