I don't have time anymore sorry
No, it happens even when the wind charge collides with the hitbox obviously why else would I make this bug report then?
Just throw it at them like normal don't use command blocks
No players take less vertical/upward knockback than mobs. Maybe they take more horizontal knockback I'm not sure. I'll edit this bug report to make it more clear on what the bug is about. After editing it does anyone wanna get rid of the "Duplicate" label, as that is incorrect? Thank you.
No blast protection is what causes players to take less knockback than mobs. Should I still make a new report?
Grey, I don't see what else there is to explain sorry. The reason why the bug that you showed is labeled as "Works As Intended" is because the term "blast" in "blast protection" is used correctly, therefore it's intentional that blast protection lowers knockback from wind charges.
But this bug that I wrote states that players take less knockback than mobs, therefore it has nothing to do with the term "blast" or anything like that. Maybe this bug is from a coding issue. Does that make sense or is there anything else you're wondering about, Grey?
I think I should've written my other comment a little bit better, sorry about that.
The reason why MC-268411 is labeled "Works As Intended" is because the reporter didn't know that the term "blast" can also be used to call a "strong gust of wind or air". Therefore they thought that Blast Protection lowering knockback from wind charges was unintentional. But this bug report that I made has nothing to do with any of this at all. That's why I made this bug report.
It's not a duplicate. The bug report says that players take more knockback from wind charges than mobs. It doesn't say that knockback is lowered by blast protection, that's when it would be a duplicate.
No, but to make this easier to understand I've split this bug between this one and MC-268515
Syarumi, is this something you would want to record?
It's gonna be annoying whenever you're fighting someone and your pearl lands on your opponent's wind charge or your own wind charge. That's why it's not worth keeping the bug if I think about what you've just said Ruukoto
That fixed it, thank you for the help Turbo
Sorry about the weird command, I'm not sure how to fix it. I tried editing it to fix it and I tried to post it in the comments but none of them worked.
Oh by invul timer you mean damage tick (red phase of the player's skin). What you just explained happens in older versions but not in the newer versions anymore, you would have to hit them manually.
I hope that is not the case. If it is true then I think that something that should be thought about is to whether help players who play with hitbox ON or not anything to save resources like cost or time. But that is up to Mojang to decide because they know their own priorities the best.
In case if people are wondering "Why keep the hitbox on?" I will say it again JUST to be extra, extra sure. Basically the point is that a fully armored player is still clearly visible with invisibility on even if their hitbox is not on. So you might as well make it easier for people who regularly use hitboxes so people cannot abuse against that.
I rewrote the bug report below but since I don't know anything about coding I'm not sure if this is good or not. The most important part is the steps to reproduce. The text below was written by ChatGPT so it may not be fully accurate, but it should give a clearer picture of what this bug is about:
1. The Bug: The cursor position in the game window does not reset correctly when opening a GUI after the window loses and regains focus. The bug occurs even when the game window does not lose focus externally. It is triggered when the cursor is locked, and a GUI is opened, resulting in an incorrect cursor position.
2. Steps to Reproduce: To reproduce the bug, follow these steps:
Launch the game and ensure the game window has focus.
Within the game, lock the cursor (using the game's input system or a specific key combination).
Open a GUI (e.g., inventory, settings) within the game.
Observe the cursor's position in the GUI.
3. Intended Behavior: The intended behavior is that when the cursor is locked and a GUI is subsequently opened, the cursor should appear from the position where it was locked. This behavior should occur consistently, regardless of whether the cursor was locked before opening the GUI or not.
4. Actual Behavior: The actual behavior is that when the cursor is locked and a GUI is opened, the cursor does not appear from the correct position. This issue is related to a discrepancy in the documentation of GLFW's GLFW.glfwSetCursorPos()
method. According to the method's Javadoc, it is stated that glfwSetCursorPos()
only works when the cursor mode is set to CURSOR_DISABLED. However, through experimentation, it has been found that the method only takes effect when the cursor mode is set to CURSOR_RELEASED.
In the case of Minecraft, the game attempts to center the cursor when opening a GUI. However, since the GLFW.glfwSetCursorPos()
method is invoked by Minecraft while the cursor mode is CURSOR_DISABLED, the action fails to correctly reset the cursor position. As a workaround, a mod has been developed to manually set the cursor mode to CURSOR_RELEASED before invoking Minecraft's cursor centering method.
Please note that this bug report is based on the provided information, and further investigation or clarification may be required from the development team to fully address the issue.
Nope, there wasn't anything that you missed. It's nice to know that it's a feature since it balances end crystals, long story short.
No, the bug happens even if you aren't crouched which is why it also affects End Crystal PvP especially with slow falling. You just need to throw the ender pearl on the ground.
I don't have time for this anymore sorry