Patbox
- Patbox
- patbox
- Europe/Stockholm
- Yes
- No
REALMS-1625![[Mojang] Gegy](../../../data/avatars/users/10122.svg){kind=small}
![[Mojang] slicedlime](../../../data/assets/gravatar/slicedlime.jpeg){kind=small}
![[Mojang] Panda](../../../data/avatars/users/41658.png){kind=small}
Normal
MC-261798MC-277545
The text goes beyond the designated place
Realms menu in polish:
The text goes beyond the designated place
Realms menu in polish:
The text goes beyond the designated place
Realms menu in polish:
When server/singleplayer world makes client load invalid resource pack (for example one from [MC-258457|https:/bugs.mojang.com/browse/MC-258457]
), client will be stuck in infinite resource reload loop (since it can't remove it from being loaded).When server/singleplayer world makes client load invalid resource pack (for example one from
MC-258457, client will be stuck in infinite resource reload loop (since it can't remove it from being loaded).
When server/singleplayer world makes client load invalid resource pack (for example one from
MC-258457), client will be stuck in infinite resource reload loop (since it can't remove it from being loaded).
Stonecutter no longer uses custom nbt in item selection
Before 1.20.2 (Pre-1), if custom/modded server sent Stonecutter recipe, that contained custom nbt in the output item, Vanilla client would display it without issues. Since this pre-release (or likely earlier snapshot), it is no longer the case.
After checking the serialization code with Fabric, it looks like recipe constructed from packet doesn't copy nbt into new/recipe-bound ItemStack, while still writing it to the packet. While it doesn't affect vanilla servers, it still breaks functionality from previous versions. See attached images for comparition between 1.20.2 and 1.20.1.
image-2023-09-07-12-44-07-473.png
If you create `minecraft:item_display` entity with item set to a clock or compass, it won't display current time / direction correctly, which is inconsistent with other entities such as armor stands or item frames.
Command to summon the entity.
/summon minecraft:item_display ~ ~ ~ {item:{id:"clock",Count:1}}
Clocks and compasses in Item Display Entities don't show correct time/direction
Clocks andcompasses in Item Display Entities don't show correct time/directionClocks and Compasses in Item Display Entities don't show correct time/direction
Pitch of display entities can no longer be set totovalues above 90
In 1.21.1 and
before, setting pitch of display entities to 180 (or any value above 90) allowed creation "upside down" displays, that could share animation / transformation with other display entities without requiring to compute separate transforms. In current 1.21.2 pre-release it's no longer possible, as it is limited to values between -90 and 90.Example command:
/summon minecraft:item_display ~ ~ ~ {Rotation:[0f,180f],item:{id:"tnt"}}In 1.21.1 and earlier, setting pitch of display entities to 180 (or any value above 90) allowed creation "upside down" displays, that could share animation / transformation with other display entities without requiring to compute separate transforms. In current 1.21.2 pre-release it's no longer possible, as it is limited to values between -90 and 90.
Example command:
/summon minecraft:item_display ~ ~ ~ {Rotation:[0f,180f],item:{id:"tnt"}}
In 1.21.1 and earlier, setting pitch of display entities to 180 (or any value above 90) allowed creation of "upside down" displays, that could share animation / transformation with other display entities without requiring to compute separate transforms. In current 1.21.2 pre-release it's no longer possible, as it is limited to values between -90 and 90.
Example command:
/summon minecraft:item_display ~ ~ ~ {Rotation:[0f,180f],item:{id:"tnt"}}
In 1.21.1 and earlier, setting pitch of display entities to 180 (or any value above 90) allowed creation of "upside down" displays, that could share animation / transformation with other display entities without requiring to compute separate transforms. In current 1.21.2 pre-release it's no longer possible, as it is limited to values between -90 and 90. Rotation of existing display entities is also affected, which can be seen as breaking change.
Example command:
/summon minecraft:item_display ~ ~ ~ {Rotation:[0f,180f],item:{id:"tnt"}}
You need mod like optifine. In vanilla minecraft this don't work.
Still an issue in pre3
After checking for myself, can confirm it's the case for datapack ones
Compared to original loottable
As I wrote on the issue you need modded/custom server for that (like fabric or bukkit). The issue itself is a bug purely on the vanilla client not using nbt even when it's written/read from packet.
Yes, on vanilla server, you can't do that with a datapack. But it's still useful functionality for custom servers (can be used for uis or just more specific crafting). Through even with that being the case, it will be fixed on client.
The issue got fixed in 1.20.2-Pre3!
This issue seems to be caused by player heads, that only provide texture value without the signature, which wasn't required before 1.20.2. Technically it's still not required, as player heads display correct texture, aside of creating log spam.
Example command to create a head block, requires usage of command block.
setblock ~ ~1 ~ minecraft:player_head{SkullOwner:{Properties:{textures:[{Value:"eyJ0ZXh0dXJlcyI6eyJTS0lOIjp7InVybCI6Imh0dHA6Ly90ZXh0dXJlcy5taW5lY3JhZnQubmV0L3RleHR1cmUvMTRiMmNiZmUxZmQ0ZDMxMjM0NjEwODFhZDQ2MGFjYjZjMDM0NWJlZDNmM2NlOTZkNDc1YjVmNThmN2I5MDMwYiJ9fX0="}]}}}After first usage, it requires different player head to log the error (or alternatively reloading the game) or having a lot of different ones and reloading them on client.
There are cases of Mojang fixing issues that didn't have impact in vanilla game (yet), so this issue report is fine tbf, let the devs decide™
This feature isn's available for commands or datapacks, as it was introduced in a way only accessible for server side mods (as it's part of packet specification, similar to other tablist features like header/footer overrides or displayed player name replacement), see Network Protocol section in https://www.minecraft.net/en-us/article/minecraft-java-edition-1-19-3 I consider this as bug as:
This requires a custom/modified server, you can't access this on vanilla server with a datapack or resource pack. Only vanilla context here is the client (and it's networking protocol).