Arctico
- Arctico
- JIRAUSER769626
- Europe/Stockholm
- Yes
- No
MC-267795Description:
If the generic.jump_strength of a player or an entity is set to a value high enough, to make them jump above their generic.safe_fall_distance, they are capable of taking fall damage on, or if the generic.jump_strength is set high enough, even above the y-level, they took off at.
Expected behaviour:
Players and entities can't take fall damage above the y-level they took off at.
Steps to replicate:
- Create a new world, set "Allow Commands" to "ON".
- Open the chat.
- Type / paste the following command:
/attribute @s minecraft:generic.jump_strength base set 1
- Press your jump key and wait until you reach the ground.
- You just took fall damage.
If the generic.jump_strength of a player or an entity is set to a value high enough, to make them jump above their generic.safe_fall_distance, they are capable of taking fall damage on, or if the generic.jump_strength is set high enough, even above the y-level, they took off at.
Expected behaviour:
Players and entities can't take fall damage above the y-level they took off at.
Steps to replicate:
- Create a new world, set "Allow Commands" to "ON".
- Open the chat.
- Type / paste the following command:
/attribute @s minecraft:generic.jump_strength base set 1
- Press your jump key and wait until you reach the ground.
- You just took fall damage.
If the generic.jump_strength of a player or an entity is set to a value high enough, to make them jump above their generic.safe_fall_distance, they are capable of taking fall damage on, or if the generic.jump_strength is set high enough, even above the y-level, they took off at.
Expected behaviour:
Players and entities can't take fall damage above the y-level they took off at.
Steps to replicate:
- Create a new world, set "Allow Commands" to "ON".
- Open the chat.
- Type / paste the following command: "/attribute @s minecraft:generic.jump_strength base set 1"
- Press your jump key and wait until you reach the ground.
- You just took fall damage.
This refers to an older report, opened by myself (
MC-267795).This bug was introduced with the 1.20.3 update, and has not been patched since.
Whenever a player dies in any version, from 1.20.3, upon respawning, there's a "Loading terrain..." screen, being thrown in their face. From what I was told, this has been added to prevent players from falling into the void, whenever a world isn't loading correctly (
MC-228420).However, this screen is being displayed every time a player goes through the process of respawning, even if the spawn chunk is already being loaded.
This can be extremely annoying whilst playing mini-game maps, especially if the gamerule "doImmediateRespawn" and "kill" commands are used a lot.
From my experience, using mods, which most players do nowadays, makes the "Loading terrain..." screen display exponentially longer, depending on the mods in use (Comparison at 60hz: No mods / a few mods).
Expected behaviour:
Loading terrain screen won't be displayed, if involved chunks are already being loaded.
Steps to replicate:
- Create a new world, set "Allow Commands" to "ON".
- Open the chat and paste the following commands:
/setworldspawn ~ ~ ~ (Sets the default spawnpoint to your current position) /gamerulegamerulespawnRadius 0 (Prevents you from respawning in nearby chunks) /gamerule doImmediateRespawn true (Enables immediate respawning, skipping the death screen) /forceload add ~ ~ (Permanently loads the chunk, you're positioned in)
- Kill your character by opening the chat and pasting:
/kill @s
- Repeat step 3, if you didn't notice the "loading terrain" screen (This might not be as noticable if your monitor uses a higher-end refresh rate).
This refers to an older report, opened by myself (
MC-267795).This bug was introduced with the 1.20.3 update, and has not been patched since.
Whenever a player dies in any version, from 1.20.3, upon respawning, there's a "Loading terrain..." screen, being thrown in their face. From what I was told, this has been added to prevent players from falling into the void, whenever a world isn't loading correctly (
MC-228420).However, this screen is being displayed every time a player goes through the process of respawning, even if the spawn chunk is already being loaded.
This can be extremely annoying whilst playing mini-game maps, especially if the gamerule "doImmediateRespawn" and "kill" commands are used a lot.
From my experience, using mods, which most players do nowadays, makes the "Loading terrain..." screen display exponentially longer, depending on the mods in use (Comparison at 60hz: No mods / a few mods).
Expected behaviour:
Loading terrain screen won't be displayed, if involved chunks are already being loaded.
Steps to replicate:
- Create a new world, set "Allow Commands" to "ON".
- Open the chat and paste the following commands:
/setworldspawn ~ ~ ~ (Sets the default spawnpoint to your current position) /gamerule spawnRadius 0 (Prevents you from respawning in nearby chunks) /gamerule doImmediateRespawn true (Enables immediate respawning, skipping the death screen) /forceload add ~ ~ (Permanently loads the chunk, you're positioned in)
- Kill your character by opening the chat and pasting:
/kill @s
- Repeat step 3, if you didn't notice the "loading terrain" screen (This might not be as noticable if your monitor uses a higher-end refresh rate).
This refers to an older report, opened by myself (
MC-267795).This bug was introduced with the 1.20.3 update, and has not been patched since.
Whenever a player dies in any version, from 1.20.3, upon respawning, there's a "Loading terrain..." screen, being thrown in their face. From what I was told, this has been added to prevent players from falling into the void, whenever a world isn't loading correctly (
MC-228420).However, this screen is being displayed every time a player goes through the process of respawning, even if the spawn chunk is already being loaded.
This can be extremely annoying whilst playing mini-game maps, especially if the gamerule "doImmediateRespawn" and "kill" commands are used a lot.
From my experience, using mods, which most players do nowadays, makes the "Loading terrain..." screen display exponentially longer, depending on the mods in use (Comparison at 60hz: No mods / a few mods).
Expected behaviour:
Loading terrain screen won't be displayed, if involved chunks are already being loaded.
Steps to replicate:
- Create a new world, set "Allow Commands" to "ON".
- Open the chat and paste the following commands:
/setworldspawn ~ ~ ~ (Sets the default spawnpoint to your current position) /gamerule spawnRadius 0 (Prevents you from respawning in nearby chunks) /gamerule doImmediateRespawn true (Enables immediate respawning, skipping the death screen) /forceload add ~ ~ (Permanently loads the chunk, you're positioned in)
- (Step 3, formatting is buggy) Kill your character by opening the chat and pasting:
/kill @s
- (Step 4, formatting is buggy) Repeat step 3, if you didn't notice the "loading terrain" screen (This might not be as noticable if your monitor uses a higher-end refresh rate).
How is this marked as "works as intended", I think getting rid of the loading screen upon respawning is a must...
@Dhranios I see, definitely a nice feature, if used right. I think a good solution would be to only display the "loading terrain" screen, if the spawn-chunk actually isn't loaded.
Honestly, I think they aren't supposed to give you an effect, when attacking you with melee weapons, as they are clearly using tipped arrows to give certain effects to entities.
Can confirm
Can confirm. This may be caused because of differences between minecraft:wind_charge and minecraft:breeze_wind_charge
I think it's a nice idea, but that's rather a suggestion, not a bug. Usually, you'd post suggestions right here: https://feedback.minecraft.net/ . However I currently can't login at the site, so that'd might have to wait. (Not sure if that's a me-problem)
This is the case because with the snapshot from two weeks ago, Item NBT data has been replaced by components.
I recommend reading through this article or watching this very well made video by a mojang employee, to clear up confusion.
Can confirm 24w11a
Can confirm,
this is the case for a lot of items, not just custom spawn eggs, taking use of custom nbt data, as they aren't compatible with the new component system.
EliteHog, yea, thanks.
Affects 24w12a
Affects 24w12a
can confirm 1.21