JochCool
- JochCool
- jochcool
- Europe/Stockholm
- Yes
- No
![[Mojang] Grum (Erik Broes)](../../../data/assets/gravatar/grum.png){kind=small}
![[Mojang] Nathan Adams](../../../data/assets/gravatar/dinnerbone.png){kind=small}
![[Mojang] Searge (Michael Stoyke)](../../../data/assets/gravatar/searge.png){kind=small}
MCD-1702![[Mojang] slicedlime](../../../data/assets/gravatar/slicedlime.jpeg){kind=small}
![[Mojang] Cory Scheviak](../../../data/avatars/users/92893.png){kind=small}
![[Mojang] Bartosz Bok](../../../data/avatars/users/10122.svg){kind=small}
MC-259373
(scroll down)
I am working on a custom map, and I noticed Minecraft 1.9 is almost out (I saw a video on YouTube about 1.9). I thought those additions could be very useful in my map, especially those new command blocks and the cooldown on weapons. So I started Minecraft on the latest Snapshot (15w38b) and I started working on my world again.
The first thing I noticed is that the shape of my upside down stairs (for decoration I added upside down stone brick stairs) was wrong. It took some time to discover what was wrong with the shape:
shape: inner_rignt should be {{shape: inner_left }},
shape: inner_left }} should be {{shape: inner_right,
shape: outer_right should be {{shape: outer_left }},
shape: outer_left }} should be {{shape: outer_right.Note: this is not the case for stairs with half: bottom (regular stairs), only for stairs with half: top (upside down stairs).
It is the same for other types of stairs.
(scroll down)
I am working on a custom map, and I noticed Minecraft 1.9 is almost out (I saw a video on YouTube about 1.9). I thought those additions could be very useful in my map, especially those new command blocks and the cooldown on weapons. So I started Minecraft on the latest Snapshot (15w38b) and I started working on my world again.
The first thing I noticed is that the shape of my upside down stairs (for decoration I added upside down stone brick stairs) was wrong. It took some time to discover what was wrong with the shape:
shape: inner_rig
nt should be{{shape: inner_left }},
shape: inner_left}} should be {{shape: inner_right,
shape: outer_right should be{{shape: outer_left }},
shape: outer_left }} should be {{shape: outer_right.Note: this is not the case for stairs with half: bottom (regular stairs), only for stairs with half: top (upside down stairs).
It is the same for other types of stairs.(scroll down)
I am working on a custom map, and I noticed Minecraft 1.9 is almost out (I saw a video on YouTube about 1.9). I thought those additions could be very useful in my map, especially those new command blocks and the cooldown on weapons. So I started Minecraft on the latest Snapshot (15w38b) and I started working on my world again.
The first thing I noticed is that the shape of my upside down stairs (for decoration I added upside down stone brick stairs) was wrong. It took some time to discover what was wrong with the shape:
shape: inner_right should be shape: inner_left,
shape: inner_left should be shape: inner_right,
shape: outer_right should be shape: outer_left,
shape: outer_left should be shape: outer_right.Note: this is not the case for stairs with half: bottom (regular stairs), only for stairs with half: top (upside down stairs).
It is the same for other types of stairs.
(scroll down)
I am working on a custom map, and I noticed Minecraft 1.9 is almost out (I saw a video on YouTube about 1.9). I thought those additions could be very useful in my map, especially those new command blocks and the cooldown on weapons. So I started Minecraft on the latest Snapshot (15w38b) and I started working on my world again.
The first thing I noticed is that the shape of my upside down stairs (for decoration I added upside down stone brick stairs) was wrong. It took some time to discover what was wrong with the shape:
shape: inner_right should be shape: inner_left,
shape: inner_left should be shape: inner_right,
shape: outer_right should be shape: outer_left,
shape: outer_left should be shape: outer_right.Note: this is not the case for stairs with half: bottom (regular stairs), only for stairs with half: top (upside down stairs).
It is the same for other types of stairs.(scroll down)
I am working on a custom map, and I noticed Minecraft 1.9 is almost out (I saw a video on YouTube about 1.9). I thought those additions could be very useful in my map, especially those new command blocks and the cooldown on weapons. So I started Minecraft on the latest Snapshot (15w38b) and I started working on my world again.
The first thing I noticed is that the shape of my upside down stairs (for decoration I added upside down stone brick stairs) was wrong. It took some time to discover what was wrong with the shape:
shape: inner_right should be shape: inner_left,
shape: inner_left should be shape: inner_right,
shape: outer_right should be shape: outer_left,
shape: outer_left should be shape: outer_right.Note: this is not the case for stairs with half: bottom (regular stairs), only for stairs with half: top (upside down stairs).
It is the same for other types of stairs.
(scroll down)
I am working on a custom map, and I noticed Minecraft 1.9 is almost out (I saw a video on YouTube about 1.9). I thought those additions could be very useful in my map, especially those new command blocks and the cooldown on weapons. So I started Minecraft on the latest Snapshot (15w38b) and I started working on my world again.
The first thing I noticed is that the shape of my upside down stairs (for decoration I added upside down stone brick stairs) was wrong. It took some time to discover what was wrong with the shape:
shape: inner_right should be shape: inner_left,
shape: inner_left should be shape: inner_right,
shape: outer_right should be shape: outer_left,
shape: outer_left should be shape: outer_right.Note: this is not the case for stairs with half: bottom (regular stairs), only for stairs with half: top (upside down stairs).
It is the same for other types of stairs.(scroll down)
I am working on a custom map, and I noticed Minecraft 1.9 is almost out (I saw a video on YouTube about 1.9). I thought those additions could be very useful in my map, especially those new command blocks and the cooldown on weapons. So I started Minecraft on the latest Snapshot (15w38b) and I started working on my world again.
The first thing I noticed is that the shape of my upside down stairs (for decoration I added upside down stone brick stairs) was wrong. It took some time to discover what was wrong with the shape:
shape: inner_right should be shape: inner_left,
shape: inner_left should be shape: inner_right,
shape: outer_right should be shape: outer_left,
shape: outer_left should be shape: outer_right.Note: this is not the case for stairs with half: bottom (regular stairs), only for stairs with half: top (upside down stairs).
It is the same for other types of stairs.
(scroll down)
I am working on a custom map, and I noticed Minecraft 1.9 is almost out (I saw a video on YouTube about 1.9). I thought those additions could be very useful in my map, especially those new command blocks and the cooldown on weapons. So I started Minecraft on the latest Snapshot (15w38b) and I started working on my world again.
The first thing I noticed is that the shape of my upside down stairs (for decoration I added upside down stone brick stairs) was wrong. It took some time to discover what was wrong with the shape:
shape: inner_right should be shape: inner_left,
shape: inner_left should be shape: inner_right,
shape: outer_right should be shape: outer_left,
shape: outer_left should be shape: outer_right.Note: this is not the case for stairs with half: bottom (regular stairs), only for stairs with half: top (upside down stairs).
It is the same for other types of stairs.
(scroll down)
I am working on a custom map, and I noticed Minecraft 1.9 is almost out (I saw a video on YouTube about 1.9). I thought those additions could be very useful in my map, especially those new command blocks and the cooldown on weapons. So I started Minecraft on the latest Snapshot (15w38b) and I started working on my world again.
The first thing I noticed is that the shape of my upside down stairs (for decoration I added upside down stone brick stairs) was wrong. It took some time to discover what was wrong with the shape:
[{{shape: inner_right}}] should be [{{shape: inner_left}}],
[{{shape: inner_left}}] should be [{{shape: inner_right}}],
[{{shape: outer_right}}] should be [{{shape: outer_left}}],
[{{shape: outer_left}}] should be [{{shape: outer_right}}].Note: this is not the case for stairs with half: bottom (regular stairs), only for stairs with half: top (upside down stairs).
It is the same for other types of stairs.
(scroll down)
I am working on a custom map, and I noticed Minecraft 1.9 is almost out (I saw a video on YouTube about 1.9). I thought those additions could be very useful in my map, especially those new command blocks and the cooldown on weapons. So I started Minecraft on the latest Snapshot (15w38b) and I started working on my world again.
The first thing I noticed is that the shape of my upside down stairs (for decoration I added upside down stone brick stairs) was wrong. It took some time to discover what was wrong with the shape:
[{{shape: inner_right}}] should be [{{shape: inner_left}}],
[{{shape: inner_left}}] should be [{{shape: inner_right}}],
[{{shape: outer_right}}] should be [{{shape: outer_left}}],
[{{shape: outer_left}}] should be [{{shape: outer_right}}].Note: this is not the case for stairs with half: bottom (regular stairs), only for stairs with half: top (upside down stairs).
It is the same for other types of stairs.(scroll down)
I am working on a custom map, and I noticed Minecraft 1.9 is almost out (I saw a video on YouTube about 1.9). I thought those additions could be very useful in my map, especially those new command blocks and the cooldown on weapons. So I started Minecraft on the latest Snapshot (15w38b) and I started working on my world again.
The first thing I noticed is that the shape of my upside down stairs (for decoration I added upside down stone brick stairs) was wrong. It took some time to discover what was wrong with the shape:
[*{{shape: inner_right}}*] should be [*{{shape: inner_left}}*],
[*{{shape: inner_left}}*] should be [*{{shape: inner_right}}*],
[*{{shape: outer_right}}*] should be [*{{shape: outer_left}}*],
[*{{shape: outer_left}}*] should be [*{{shape: outer_right}}*].Note: this is not the case for stairs with half: bottom (regular stairs), only for stairs with half: top (upside down stairs).
It is the same for other types of stairs.
(scroll down)
I am working on a custom map, and I noticed Minecraft 1.9 is almost out (I saw a video on YouTube about 1.9). I thought those additions could be very useful in my map, especially those new command blocks and the cooldown on weapons. So I started Minecraft on the latest Snapshot (15w38b) and I started working on my world again.
The first thing I noticed is that the shape of my upside down stairs (for decoration I added upside down stone brick stairs) was wrong. It took some time to discover what was wrong with the shape:
[*{{shape: inner_right}}*] should be [*{{shape: inner_left}}*],
[*{{shape: inner_left}}*] should be [*{{shape: inner_right}}*],
[*{{shape: outer_right}}*] should be [*{{shape: outer_left}}*],
[*{{shape: outer_left}}*] should be [*{{shape: outer_right}}*].Note: this is not the case for stairs with half: bottom (regular stairs), only for stairs with half: top (upside down stairs).
It is the same for other types of stairs.(scroll down)
I am working on a custom map, and I noticed Minecraft 1.9 is almost out (I saw a video on YouTube about 1.9). I thought those additions could be very useful in my map, especially those new command blocks and the cooldown on weapons. So I started Minecraft on the latest Snapshot (15w38b) and I started working on my world again.
The first thing I noticed is that the shape of my upside down stairs (for decoration I added upside down stone brick stairs) was wrong. It took some time to discover what was wrong with the shape:
shape: inner_right] should be shape: inner_left,
shape: inner_left] should be shape: inner_right,
shape: outer_right] should be shape: outer_left,
shape: outer_left] should be shape: outer_right.Note: this is not the case for stairs with half: bottom (regular stairs), only for stairs with half: top (upside down stairs).
It is the same for other types of stairs.
(scroll down)
I am working on a custom map, and I noticed Minecraft 1.9 is almost out (I saw a video on YouTube about 1.9). I thought those additions could be very useful in my map, especially those new command blocks and the cooldown on weapons. So I started Minecraft on the latest Snapshot (15w38b) and I started working on my world again.
The first thing I noticed is that the shape of my upside down stairs (for decoration I added upside down stone brick stairs) was wrong. It took some time to discover what was wrong with the shape:
shape: inner_right
]should be shape: inner_left,
shape: inner_left]should be shape: inner_right,
shape: outer_right]should be shape: outer_left,
shape: outer_left] should be shape: outer_right.Note: this is not the case for stairs with half: bottom (regular stairs), only for stairs with half: top (upside down stairs).
It is the same for other types of stairs.
(scroll down)
I am working on a custom map, and I noticed Minecraft 1.9 is almost out (I saw a video on YouTube about 1.9). I thought those additions could be very useful in my map, especially those new command blocks and the cooldown on weapons. So I started Minecraft on the latest Snapshot (15w38b) and I started working on my world again.
The first thing I noticed is that the shape of my upside down stairs (for decoration I added upside down stone brick stairs) was wrong. It took some time to discover what was wrong with the shape:
shape: inner_right should be shape: inner_left,
shape: inner_left should be shape: inner_right,
shape: outer_right should be shape: outer_left,
shape: outer_left]should be shape: outer_right.Note: this is not the case for stairs with half: bottom (regular stairs), only for stairs with half: top (upside down stairs).
It is the same for other types of stairs.
(scroll down)
I am working on a custom map, and I noticed Minecraft 1.9 is almost out (I saw a video on YouTube about 1.9). I thought those additions could be very useful in my map, especially those new command blocks and the cooldown on weapons. So I started Minecraft on the latest Snapshot (15w38b) and I started working on my world again.
The first thing I noticed is that the shape of my upside down stairs (for decoration I added upside down stone brick stairs) was wrong. It took some time to discover what was wrong with the shape:
shape: inner_right should be shape: inner_left,
shape: inner_left should be shape: inner_right,
shape: outer_right should be shape: outer_left,
shape: outer_left should be shape: outer_right.Note: this is not the case for stairs with half: bottom (regular stairs), only for stairs with half: top (upside down stairs).
It is the same for other types of stairs.(scroll down)
I am working on a custom map, and I noticed Minecraft 1.9 is almost out (I saw a video on YouTube about 1.9). I thought those additions could be very useful in my map, especially those new command blocks and the cooldown on weapons. So I started Minecraft on the latest Snapshot (15w38b) and I started working on my world again.
The first thing I noticed is that the shape of my upside down stairs (for decoration I added upside down stone brick stairs) was wrong. It took some time to discover what was wrong with the shape:
shape: inner_right should be shape: inner_left,
shape: inner_left should be shape: inner_right,
shape: outer_right should be shape: outer_left,
shape: outer_left should be shape: outer_right.Note: this is not the case for stairs with half: bottom (regular stairs), only for stairs with half: top (upside down stairs).
It is the same for other types of stairs.
(scroll down)
I am working on a custom map, and I noticed Minecraft 1.9 is almost out (I saw a video on YouTube about 1.9). I thought those additions could be very useful in my map, especially those new command blocks and the cooldown on weapons. So I started Minecraft on the latest Snapshot (15w38b) and I started working on my world again.
The first thing I noticed is that the shape of my upside down stairs (for decoration I added upside down stone brick stairs) was wrong. It took some time to discover what was wrong with the shape:
shape: inner_right should be shape: inner_left,
shape: inner_left should be shape: inner_right,
shape: outer_right should be shape: outer_left,
shape: outer_left should be shape: outer_right.Note: this is not the case for stairs with half: bottom (regular stairs), only for stairs with half: top (upside down stairs).
It is the same for other types of stairs.(scroll down)
I am working on a custom map, and I noticed Minecraft 1.9 is almost out (I saw a video on YouTube about 1.9). I thought those additions could be very useful in my map, especially those new command blocks and the cooldown on weapons. So I started Minecraft on the latest Snapshot (15w38b) and I started working on my world again.
The first thing I noticed is that the shape of my upside down stairs (for decoration I added upside down stone brick stairs) was wrong. It took some time to discover what was wrong with the shape:
shape: inner_right should be shape: inner_left,
shape: inner_left should be shape: inner_right,
shape: outer_right should be shape: outer_left,
shape: outer_left should be shape: outer_right.Note: this is not the case for stairs with half: bottom (regular stairs), only for stairs with half: top (upside down stairs).
It is the same for other types of stairs.
(scroll down)
I am working on a custom map, and I noticed Minecraft 1.9 is almost out (I saw a video on YouTube about 1.9). I thought those additions could be very useful in my map, especially those new command blocks and the cooldown on weapons. So I started Minecraft on the latest Snapshot (15w38b) and I started working on my world again.
The first thing I noticed is that the shape of my upside down stairs (for decoration I added upside down stone brick stairs) was wrong. It took some time to discover what was wrong with the shape:
shape: inner_right should be shape: inner_left,
shape: inner_left should be shape: inner_right,
shape: outer_right should be shape: outer_left,
shape: outer_left should be shape: outer_right.Note: this is not the case for stairs with half: bottom (regular stairs), only for stairs with half: top (upside down stairs).
It is the same for other types of stairs.(scroll down)
I am working on a custom map, and I noticed Minecraft 1.9 is almost out (I saw a video on YouTube about 1.9). I thought those additions could be very useful in my map, especially those new command blocks and the cooldown on weapons. So I started Minecraft on the latest Snapshot (15w38b) and I started working on my world again.
The first thing I noticed is that the shape of my upside down stairs (for decoration I added upside down stone brick stairs) was wrong. It took some time to discover what was wrong with the shape:
shape: inner_right should be shape: inner_left,
shape: inner_left should be shape: inner_right,
shape: outer_right should be shape: outer_left,
shape: outer_left should be shape: outer_right.Note: this is not the case for stairs with half: bottom (regular stairs), only for stairs with half: top (upside down stairs).
It is the same for other types of stairs.
Whenever an item disappears from a player's inventory (by dropping it, moving it around, etc.) while his/her inventory is opened, and another is given back immediately, it does not show up.
Here is a detailed investigation of the bug (sorry if I am not articulation very well in this video):
https://youtu.be/XT0mcDEECE4What I expected to happen was...:
When an item disappears from a player's inventory and one is given back like described above, the given back item is visible in the player's inventory like it should.What actually happened was...:
The given back item is not visible, but still there.Steps to Reproduce:
1. Get three command blocks (/give @p minecraft:command_block)
2. Place the three command blocks in a chain, where the first command block is a repeating command block and the other two are chain command blocks. They are all set to 'Always Active' or powered by redstone.
3. Paste these three commands into the command block in this order:/scoreboard players tag @a[tag=HasStone] remove HasStone /scoreboard players tag @a add HasStone {Inventory:[{id:"minecraft:stone"}]} /give @a[tag=!HasStone] minecraft:stoneYou have now succesfully set up the machine. One piece of stone should be placed into your inventory now.
4. Drop the stone from your hotbar.
5. Notice that one is given back by the machine.
6. Open your inventory, and drop it immediately form there by hovering over the item and pressing 'Q' (by default).
7. Notice that it looked like you got another piece of stone back, but you can't see it in your inventory.
8. Get a different block and place it at the spot where the item should be (usually the first or the second slot in your hotbar).
9. Notice that the stone now shows up.
10. Repeat step 4 and notice that you get the item back again.
11. Move the item in your inventory.
12. Notice that it looked like you got another piece of stone back, but you can't see it in your inventory.
13. Close your inventory and type this command in your chat:
noformat/scoreboard players tag @p list{{noformat}}
14. Notice that you do have the tag HasStone, but you cannot see stone in your inventory.
15. Repeat step 8 and notice that the stone now shows up.Whenever an item disappears from a player's inventory (by dropping it, moving it around, etc.) while his/her inventory is opened, and another is given back immediately, it does not show up.
Here is a detailed investigation of the bug (sorry if I am not articulating very well in this video):
https://youtu.be/XT0mcDEECE4What I expected to happen was...:
When an item disappears from a player's inventory and one is given back like described above, the given back item is visible in the player's inventory like it should.What actually happened was...:
The given back item is not visible, but still there.Steps to Reproduce:
1. Get three command blocks (/give @p minecraft:command_block)
2. Place the three command blocks in a chain, where the first command block is a repeating command block and the other two are chain command blocks. They are all set to 'Always Active' or powered by redstone.
3. Paste these three commands into the command block in this order:/scoreboard players tag @a[tag=HasStone] remove HasStone /scoreboard players tag @a add HasStone {Inventory:[{id:"minecraft:stone"}]} /give @a[tag=!HasStone] minecraft:stoneYou have now succesfully set up the machine. One piece of stone should be placed into your inventory now.
4. Drop the stone from your hotbar.
5. Notice that one is given back by the machine.
6. Open your inventory, and drop it immediately form there by hovering over the item and pressing 'Q' (by default).
7. Notice that it looked like you got another piece of stone back, but you can't see it in your inventory.
8. Get a different block and place it at the spot where the item should be (usually the first or the second slot in your hotbar).
9. Notice that the stone now shows up.
10. Repeat step 4 and notice that you get the item back again.
11. Move the item in your inventory.
12. Notice that it looked like you got another piece of stone back, but you can't see it in your inventory.
13. Close your inventory and type this command in your chat:
noformat/scoreboard players tag @p list{{noformat}}
14. Notice that you do have the tag HasStone, but you cannot see stone in your inventory.
15. Repeat step 8 and notice that the stone now shows up.
Whenever an item disappears from a player's inventory (by dropping it, moving it around, etc.) while his/her inventory is opened, and another is given back immediately, it does not show up.
Here is a detailed investigation of the bug (sorry if I am not articulating very well in this video):
https://youtu.be/XT0mcDEECE4What I expected to happen was...:
When an item disappears from a player's inventory and one is given back like described above, the given back item is visible in the player's inventory like it should.What actually happened was...:
The given back item is not visible, but still there.Steps to Reproduce:
1. Get three command blocks (/give @p minecraft:command_block)
2. Place the three command blocks in a chain, where the first command block is a repeating command block and the other two are chain command blocks. They are all set to 'Always Active' or powered by redstone.
3. Paste these three commands into the command block in this order:/scoreboard players tag @a[tag=HasStone] remove HasStone /scoreboard players tag @a add HasStone {Inventory:[{id:"minecraft:stone"}]} /give @a[tag=!HasStone] minecraft:stoneYou have now succesfully set up the machine. One piece of stone should be placed into your inventory now.
4. Drop the stone from your hotbar.
5. Notice that one is given back by the machine.
6. Open your inventory, and drop it immediately form there by hovering over the item and pressing 'Q' (by default).
7. Notice that it looked like you got another piece of stone back, but you can't see it in your inventory.
8. Get a different block and place it at the spot where the item should be (usually the first or the second slot in your hotbar).
9. Notice that the stone now shows up.
10. Repeat step 4 and notice that you get the item back again.
11. Move the item in your inventory.
12. Notice that it looked like you got another piece of stone back, but you can't see it in your inventory.
13. Close your inventory and type this command in your chat:
noformat/scoreboard players tag @p list{{noformat}}14. Notice that you do have the tag HasStone, but you cannot see stone in your inventory.
15. Repeat step 8 and notice that the stone now shows up.Whenever an item disappears from a player's inventory (by dropping it, moving it around, etc.) while his/her inventory is opened, and another is given back immediately, it does not show up.
Here is a detailed investigation of the bug (sorry if I am not articulating very well in this video):
https://youtu.be/XT0mcDEECE4What I expected to happen was...:
When an item disappears from a player's inventory and one is given back like described above, the given back item is visible in the player's inventory like it should.What actually happened was...:
The given back item is not visible, but still there.Steps to Reproduce:
1. Get three command blocks (/give @p minecraft:command_block)
2. Place the three command blocks in a chain, where the first command block is a repeating command block and the other two are chain command blocks. They are all set to 'Always Active' or powered by redstone.
3. Paste these three commands into the command block in this order:/scoreboard players tag @a[tag=HasStone] remove HasStone /scoreboard players tag @a add HasStone {Inventory:[{id:"minecraft:stone"}]} /give @a[tag=!HasStone] minecraft:stoneYou have now succesfully set up the machine. One piece of stone should be placed into your inventory now.
4. Drop the stone from your hotbar.
5. Notice that one is given back by the machine.
6. Open your inventory, and drop it immediately form there by hovering over the item and pressing 'Q' (by default).
7. Notice that it looked like you got another piece of stone back, but you can't see it in your inventory.
8. Get a different block and place it at the spot where the item should be (usually the first or the second slot in your hotbar).
9. Notice that the stone now shows up.
10. Repeat step 4 and notice that you get the item back again.
11. Move the item in your inventory.
12. Notice that it looked like you got another piece of stone back, but you can't see it in your inventory.
13. Close your inventory and type this command in your chat:/scoreboard players tag @p list14. Notice that you do have the tag HasStone, but you cannot see stone in your inventory.
15. Repeat step 8 and notice that the stone now shows up.
Often when an entity's name is in the chat, a tooltip appears when hovering your mouse over the text. It shows the name, entity ID and UUID of the entity, but the entity IDs have changed in snapshot 16w32a. For example, ArmorStand has now become minecraft:armor_stand. This has not changed on the tooltip though.
Steps to Reproduce:
1. Type the following command in the chat. Make sure you're an operator on a server or have cheats enabled on a singleplayer world. This command will make you say all entity names in the world./say @e2. Hover your mouse over one of the entities that are not players. Notice that the old entity IDs are used.
The bug
You can normally give yourself an item with a tag in theCanPlaceOnorCanDestroyNBT tag. But when you try to select the hotbar slot the item is in, or when you try to see the tooltip of the item, the game crashes. See the attached crash reports.How to reproduce
- Run either of the following commands:
/give @s minecraft:stone{CanPlaceOn:["#minecraft:planks"]}
/give @s minecraft:stone{CanDestroy:["#minecraft:planks"]}Either select the hotbar slot the item is in, or open the inventory and over the mouse over the item. The game crashes immediately.- Reopen the world.
Either you don't have the item any more, orthe game crashes immediately on load.Crash report
Description: Rendering screen g: Non [a-z0-9_.-] character in namespace of location: #minecraft:planks at mx.<init>(SourceFile:33) at mx.<init>(SourceFile:41) at atd.a(SourceFile:143) at ams.a(SourceFile:681) at bqv.a(SourceFile:99) at bqv.a(SourceFile:95) at brz.a(SourceFile:681) at brq.b(SourceFile:176) at brz.a(SourceFile:642) at bzx.a(SourceFile:997) at bne.b(SourceFile:820) at bne.a(SourceFile:380) at net.minecraft.client.main.Main.main(SourceFile:140)The bug
An item that has a block tag (like #minecraft:planks) in the CanPlaceOn or CanDestroy NBT tag, can crash the game. This can happen in two ways:
- By selecting the hotbar slot the item is in, while being in Adventure mode.
- By opening the inventory and hovering the mouse over the slot the item is in. This can be circumvented by setting the HideFlags NBT tag to 24, which hides the CanPlaceOn/CanDestroy flag.
The cause of this issue may be that block tags have not been fully implemented for the CanPlaceOn/CanDestroy NBT tag, or that the game does not know how to display the name of a block tag.
How to reproduce
- Run either of the following commands:
/give @s minecraft:stone{CanPlaceOn:["#minecraft:planks"]}
/give @s minecraft:stone{CanDestroy:["#minecraft:planks"]}- Perform either of the actions listed above. The game crashes immediately.
- Reopen the world. It is possible that the item is still selected and the game crashes immediately, or that the item is not selected. It may also occur that the player data is gone.
Crash report
Description: Rendering screen g: Non [a-z0-9_.-] character in namespace of location: #minecraft:planks at mx.<init>(SourceFile:33) at mx.<init>(SourceFile:41) at atd.a(SourceFile:143) at ams.a(SourceFile:681) at bqv.a(SourceFile:99) at bqv.a(SourceFile:95) at brz.a(SourceFile:681) at brq.b(SourceFile:176) at brz.a(SourceFile:642) at bzx.a(SourceFile:997) at bne.b(SourceFile:820) at bne.a(SourceFile:380) at net.minecraft.client.main.Main.main(SourceFile:140)
When you make player A spectate
playerB using the /spectate command, but they are in different dimensions, then player A will teleport to the correct coordinates, but not the correct dimension and won't actually spectateplayerB.How to reproduce
Get twoplayers,one in spectator mode and one in a differentgamemodeTeleport one player to another dimension, at different coordinates- Use the /spectate command to
make one playerspectateanotherNow
both playerswill be at the same coordinates in different dimensions.When you make player A spectate entity B using the /spectate command, but they are in different dimensions, then player A will teleport to the correct coordinates, but not the correct dimension and won't actually spectate entity B.
How to reproduce
- Spawn an entity (or get another player), and then go to different dimension at different coordinates
- Switch to spectator mode
- Use the /spectate command to spectate the other entity
Now you and the entity will be at the same coordinates, but in different dimensions.
Theinitial size of the world border is wrongThe world border size can be wrong when upgrading from old worlds
The maximum size of the world border is 59,999,968m, and that's also the initial size. However, the /worldborder get command
initially returns 60,000,000. Also, in the level.dat file,Data.BorderSize is set to 60,000,000d.Steps to reproduce
In a world where you haven't modified the world border,run /worldborder get
- It returns 60,000,000.
- Use a program like NBTExplorer to inspect the level.dat file
- The Data.BorderSize value is 60,000,000d.
- Teleport to the edge of the world (/tp @s 29999999 ~ 29999999)
- Notice that the world border is 59,999,968m wide, not 60 million.
- Run the command /worldborder set 60000000
- It gives an error message: "Double must not be more than 5.9999968E7, found 6.0E7"
- Run the command /worldborder set 59999968
- It is successful, but nothing changes about the world border.
- Repeat step
5.
- It gives an error message: "Nothing changed. The world border is already that size"
- Repeat steps
1and2.
- It gives 59999968 this time.
The maximum size of the world border is 59,999,968m, and that's also the initial size. However, the initial size used to be 60,000,000 before Minecraft 1.17. When upgrading from an old world, the world border becomes the correct size, but the stored value remains 60,000,000. This means that the /worldborder get command returns the wrong value.
Steps to reproduce
- Create a world in Minecraft 1.16.
- Open the world in Minecraft 1.17 and run /worldborder get
- It returns 60,000,000.
- Use a program like NBTExplorer to inspect the level.dat file
- The Data.BorderSize value is 60,000,000d.
- Teleport to the edge of the world (/tp @s 29999999 ~ 29999999)
- Notice that the world border is 59,999,968m wide, not 60 million.
- Run the command /worldborder set 60000000
- It gives an error message: "Double must not be more than 5.9999968E7, found 6.0E7"
- Run the command /worldborder set 59999968
- It is successful, but nothing changes about the world border.
- Repeat step 6.
- It gives an error message: "Nothing changed. The world border is already that size"
- Repeat steps 2 and 3.
- It gives 59999968 this time.
The maximum size of the world border is 59,999,968m, and that's also the initial size. However, the initial size used to be 60,000,000 before Minecraft 1.17. When upgrading from an old world, the world border becomes the correct size, but the stored value remains 60,000,000. This means that the /worldborder get command returns the wrong value.
Steps to reproduce
- Create a world in Minecraft 1.16.
- Open the world in Minecraft 1.17 and run /worldborder get
- It returns 60,000,000. Expected: 59,999,968.
- Use a program like NBTExplorer to inspect the level.dat file
- The Data.BorderSize value is 60,000,000d.
- Teleport to the edge of the world (/tp @s 29999999 ~ 29999999)
- Notice that the world border is 59,999,968m wide, not 60 million.
- Run the command /worldborder set 60000000
- It gives an error message: "Double must not be more than 5.9999968E7, found 6.0E7"
- Run the command /worldborder set 59999968
- It is successful, but nothing changes about the world border.
- Repeat step 6.
- It gives an error message: "Nothing changed. The world border is already that size"
- Repeat steps 2 and 3.
- It correctly gives 59999968 this time.
The maximum size of the world border is 59,999,968m, and that's also the initial size. However, the initial size used to be 60,000,000 before Minecraft 1.17 or a newer version. When upgrading from an old world, the world border becomes the correct size, but the stored value remains 60,000,000. This means that the /worldborder get command returns the wrong value.
Steps to reproduce
- Create a world in Minecraft 1.16.
- Open the world in Minecraft 1.17 and run /worldborder get
- It returns 60,000,000. Expected: 59,999,968.
- Use a program like NBTExplorer to inspect the level.dat file
- The Data.BorderSize value is 60,000,000d.
- Teleport to the edge of the world (/tp @s 29999999 ~ 29999999)
- Notice that the world border is 59,999,968m wide, not 60 million.
- Run the command /worldborder set 60000000
- It gives an error message: "Double must not be more than 5.9999968E7, found 6.0E7"
- Run the command /worldborder set 59999968
- It is successful, but nothing changes about the world border.
- Repeat step 6.
- It gives an error message: "Nothing changed. The world border is already that size"
- Repeat steps 2 and 3.
- It correctly gives 59999968 this time.
The maximum size of the world border is 59,999,968m, and that's also the initial size. However, the initial size used to be 60,000,000 before Minecraft 1.17
or a newer version. When upgrading from an old world, the world border becomes the correct size, but the stored value remains 60,000,000. This means that the /worldborder get command returns the wrong value.Steps to reproduce
- Create a world in Minecraft 1.16.
- Open the world in Minecraft 1.17
and run /worldborder get
- It returns 60,000,000. Expected: 59,999,968.
- Use a program like NBTExplorer to inspect the level.dat file
- The Data.BorderSize value is 60,000,000d.
- Teleport to the edge of the world (/tp @s 29999999 ~ 29999999)
- Notice that the world border is 59,999,968m wide, not 60 million.
- Run the command /worldborder set 60000000
- It gives an error message: "Double must not be more than 5.9999968E7, found 6.0E7"
- Run the command /worldborder set 59999968
- It is successful, but nothing changes about the world border.
- Repeat step 6.
- It gives an error message: "Nothing changed. The world border is already that size"
- Repeat steps 2 and 3.
- It correctly gives 59999968 this time.
The maximum size of the world border is 59,999,968m, and that's also the initial size. However, the initial size used to be 60,000,000 before Minecraft 1.17. When upgrading from an old world, the world border becomes the correct size, but the stored value remains 60,000,000. This means that the /worldborder get command returns the wrong value.
Steps to reproduce
- Create a world in Minecraft 1.16.
- Open the world in Minecraft 1.17 or a newer version and run /worldborder get
- It returns 60,000,000. Expected: 59,999,968.
- Use a program like NBTExplorer to inspect the level.dat file
- The Data.BorderSize value is 60,000,000d.
- Teleport to the edge of the world (/tp @s 29999999 ~ 29999999)
- Notice that the world border is 59,999,968m wide, not 60 million.
- Run the command /worldborder set 60000000
- It gives an error message: "Double must not be more than 5.9999968E7, found 6.0E7"
- Run the command /worldborder set 59999968
- It is successful, but nothing changes about the world border.
- Repeat step 6.
- It gives an error message: "Nothing changed. The world border is already that size"
- Repeat steps 2 and 3.
- It correctly gives 59999968 this time.
They're leaking!
Example in seed 1 at /tp @s 3101 -38 3483
They're leaking!
Examples in seed 1:
- /tp @s 3101 -38 3483
- /tp @s 8164 -38 202
When using the summon or data modify commands to s
ummona display entity, the transformation tag can only be set in the matrix (TAG_List) form, and not in the decomposed (TAG_Compound) form. Using the decomposed form causes an error to be logged, and the transformation values to be set to their defaults.As an example, the following two commands do not work as expected:
/summon minecraft:block_display ~ ~ ~ {block_state:{Name:"minecraft:lime_glazed_terracotta"},transformation:{scale:[2f,2f,2f]}} /data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {scale:[2.0f,2.0f,2.0f]}Whereas the following four do work as expected:
/summon minecraft:block_display ~ ~ ~ {block_state:{Name:"minecraft:lime_glazed_terracotta"},transformation:[2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,1f]} /data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {scale:[2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,1f]} /data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation.scale set value [2.0f,2.0f,2.0f] /data merge entity @e[type=minecraft:block_display,limit=1,sort=nearest] {transformation:{scale:[2.0f,2.0f,2.0f]}}Expected behaviour
The decomposed form can be used in all cases where NBT is used, so all the above commands should work.
Actual behaviour
Upon running the command, the following error message is logged by the server thread:
Display entityNot a list: {scale:[2.0f,2.0f,2.0f]}The entity has the default appearance, and all of its transformation data is set to their default values.
When using the summon or data modify commands to set the NBT of a display entity, the transformation tag can only be set in the matrix (TAG_List) form, and not in the decomposed (TAG_Compound) form. Using the decomposed form causes an error to be logged, and the transformation values to be set to their defaults.
As an example, the following two commands do not work as expected:
/summon minecraft:block_display ~ ~ ~ {block_state:{Name:"minecraft:lime_glazed_terracotta"},transformation:{scale:[2f,2f,2f]}} /data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {scale:[2.0f,2.0f,2.0f]}Whereas the following four do work as expected:
/summon minecraft:block_display ~ ~ ~ {block_state:{Name:"minecraft:lime_glazed_terracotta"},transformation:[2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,1f]} /data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {scale:[2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,1f]} /data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation.scale set value [2.0f,2.0f,2.0f] /data merge entity @e[type=minecraft:block_display,limit=1,sort=nearest] {transformation:{scale:[2.0f,2.0f,2.0f]}}Expected behaviour
The decomposed form can be used in all cases where NBT is used, so all the above commands should work.
Actual behaviour
Upon running the command, the following error message is logged by the server thread:
Display entityNot a list: {scale:[2.0f,2.0f,2.0f]}The entity has the default appearance, and all of its transformation data is set to their default values.
Decomposed transformationcannot alwaysbeusedDecomposed transformation sometimes requires all properties to be set
When
using thesummonordata modify commands to set the NBT of a display entity,the transformation tag can only be set in the matrix (TAG_List) form, and not in the decomposed (TAG_Compound) form. Using the decomposed form causes an error to be logged, and the transformation values to be set to their defaults.As an example, the following two commands do not work as expected:
/summon minecraft:block_display ~ ~ ~ {block_state:{Name:"minecraft:lime_glazed_terracotta"},transformation:{scale:[2f,2f,2f]}} /data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {scale:[2.0f,2.0f,2.0f]}Whereas the following
fourdo work as expected:/summon minecraft:block_display ~ ~ ~ {block_state:{Name:"minecraft:lime_glazed_terracotta"},transformation:[2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,1f]} /data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {scale:[2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,1f]} /data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation.scale set value [2.0f,2.0f,2.0f] /data merge entity @e[type=minecraft:block_display,limit=1,sort=nearest] {transformation:{scale:[2.0f,2.0f,2.0f]}}Expected behaviour
The
decomposed form can be used in all cases where NBT isused,so all the above commands should work.Actual behaviour
Upon running the command, the following error message is logged by the server thread:
Display entityNot a list: {scale:[2.0f,2.0f,2.0f]}The entity has the default appearance, and all of its transformation data is set to their default values.
When setting the transformation property in the summon or data modify command in the decomposed (TAG_Compound) form, all four properties are required; otherwise, the entire object is set to default and an error is logged. This requirement does not exist for the data merge command. Setting the transformation property in the matrix (TAG_List) form works as expected.
As an example, the following two commands do not work as expected:
/summon minecraft:block_display ~ ~ ~ {block_state:{Name:"minecraft:lime_glazed_terracotta"},transformation:{scale:[2f,2f,2f]}} /data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {scale:[2f,2f,2f]}Whereas the following do work as expected:
# Specifying all four properties /summon minecraft:block_display ~ ~ ~ {block_state:{Name:"minecraft:lime_glazed_terracotta"},transformation:{translation:[0f,0f,0f],left_rotation:[0f,0f,0f,1f],scale:[2f,2f,2f],right_rotation:[0f,0f,0f,1f]}} /data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {translation:[0f,0f,0f],left_rotation:[0f,0f,0f,1f],scale:[2f,2f,2f],right_rotation:[0f,0f,0f,1f]} # Using matrix form /summon minecraft:block_display ~ ~ ~ {block_state:{Name:"minecraft:lime_glazed_terracotta"},transformation:[2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,1f]} /data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {scale:[2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,1f]} # Modifying a specific property /data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation.scale set value [2f,2f,2f] # Using data merge /data merge entity @e[type=minecraft:block_display,limit=1,sort=nearest] {transformation:{scale:[2f,2f,2f]}}Expected behaviour
The command summons an entity with the specified transformation values set, and the unspecified values set to default.
Actual behaviour
Upon running the command, the following error message is logged by the server thread:
Display entityNot a list: {scale:[2.0f,2.0f,2.0f]}The entity has the default appearance, and all of its transformation data is set to their default values.
When setting the transformation property in the summon or data modify command in the decomposed (TAG_Compound) form, all four properties are required; otherwise, the entire object is set to default and an error is logged. This requirement does not exist for the data merge command. Setting the transformation property in the matrix (TAG_List) form works as expected.
As an example, the following two commands do not work as expected:
/summon minecraft:block_display ~ ~ ~ {block_state:{Name:"minecraft:lime_glazed_terracotta"},transformation:{scale:[2f,2f,2f]}} /data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {scale:[2f,2f,2f]}Whereas the following do work as expected:
# Specifying all four properties /summon minecraft:block_display ~ ~ ~ {block_state:{Name:"minecraft:lime_glazed_terracotta"},transformation:{translation:[0f,0f,0f],left_rotation:[0f,0f,0f,1f],scale:[2f,2f,2f],right_rotation:[0f,0f,0f,1f]}} /data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {translation:[0f,0f,0f],left_rotation:[0f,0f,0f,1f],scale:[2f,2f,2f],right_rotation:[0f,0f,0f,1f]} # Using matrix form /summon minecraft:block_display ~ ~ ~ {block_state:{Name:"minecraft:lime_glazed_terracotta"},transformation:[2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,1f]} /data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {scale:[2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,1f]} # Modifying a specific property /data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation.scale set value [2f,2f,2f] # Using data merge /data merge entity @e[type=minecraft:block_display,limit=1,sort=nearest] {transformation:{scale:[2f,2f,2f]}}Expected behaviour
The command summons an entity with the specified transformation values set, and the unspecified values set to default.
Actual behaviour
Upon running the command, the following error message is logged by the server thread:
Display entityNot a list: {scale:[2.0f,2.0f,2.0f]}The entity has the default appearance, and all of its transformation data is set to their default values.
When setting the transformation property in the summon or data modify command in the decomposed (TAG_Compound) form, all four properties are required; otherwise, the entire object is set to default and an error is logged. This requirement does not exist for the data merge command. Setting the transformation property in the matrix (TAG_List) form works as expected.
As an example, the following two commands do not work as expected:
/data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {scale:[2f,2f,2f]}Whereas the following do work as expected:
- Specifying all four properties:
**
/data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {translation:[0f,0f,0f],left_rotation:[0f,0f,0f,1f],scale:[2f,2f,2f],right_rotation:[0f,0f,0f,1f]}- Using matrix form:
/data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {scale:[2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,1f]}- Modifying a specific property:
- Using data merge:
/data merge entity @e[type=minecraft:block_display,limit=1,sort=nearest] {transformation:{scale:[2f,2f,2f]}}Expected behaviour
The command summons an entity with the specified transformation values set, and the unspecified values set to default.
Actual behaviour
Upon running the command, the following error message is logged by the server thread:
Display entityNot a list: {scale:[2.0f,2.0f,2.0f]}The entity has the default appearance, and all of its transformation data is set to their default values.
When setting the transformation property in the summon or data modify command in the decomposed (TAG_Compound) form, all four properties are required; otherwise, the entire object is set to default and an error is logged. This requirement does not exist for the data merge command. Setting the transformation property in the matrix (TAG_List) form works as expected.
As an example, the following two commands do not work as expected:
/data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {scale:[2f,2f,2f]}Whereas the following do work as expected:
- Specifying all four properties:
**
/data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {translation:[0f,0f,0f],left_rotation:[0f,0f,0f,1f],scale:[2f,2f,2f],right_rotation:[0f,0f,0f,1f]}- Using matrix form:
/data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {scale:[2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,1f]}- Modifying a specific property:
- Using data merge:
/data merge entity @e[type=minecraft:block_display,limit=1,sort=nearest] {transformation:{scale:[2f,2f,2f]}}Expected behaviour
The command summons an entity with the specified transformation values set, and the unspecified values set to default.
Actual behaviour
Upon running the command, the following error message is logged by the server thread:
Display entityNot a list: {scale:[2.0f,2.0f,2.0f]}The entity has the default appearance, and all of its transformation data is set to their default values.
When setting the transformation property in the summon or data modify command in the decomposed (TAG_Compound) form, all four properties are required; otherwise, the entire object is set to default and an error is logged. This requirement does not exist for the data merge command. Setting the transformation property in the matrix (TAG_List) form works as expected.
As an example, the following two commands do not work as expected:
/data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {scale:[2f,2f,2f]}Whereas the following do work as expected:
- Specifying all four properties:
/data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {translation:[0f,0f,0f],left_rotation:[0f,0f,0f,1f],scale:[2f,2f,2f],right_rotation:[0f,0f,0f,1f]}- Using matrix form:
/data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {scale:[2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,1f]}- Modifying a specific property:
- Using data merge:
/data merge entity @e[type=minecraft:block_display,limit=1,sort=nearest] {transformation:{scale:[2f,2f,2f]}}Expected behaviour
The command summons an entity with the specified transformation values set, and the unspecified values set to default.
Actual behaviour
Upon running the command, the following error message is logged by the server thread:
Display entityNot a list: {scale:[2.0f,2.0f,2.0f]}The entity has the default appearance, and all of its transformation data is set to their default values.
When setting the transformation property in the summon or data modify command in the decomposed (TAG_Compound) form, all four properties are required; otherwise, the entire object is set to default and an error is logged. This requirement does not exist for the data merge command. Setting the transformation property in the matrix (TAG_List) form works as expected.
As an example, the following two commands do not work as expected:
/data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {scale:[2f,2f,2f]}Whereas the following do work as expected:
- Specifying all four properties:
/data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {translation:[0f,0f,0f],left_rotation:[0f,0f,0f,1f],scale:[2f,2f,2f],right_rotation:[0f,0f,0f,1f]}- Using matrix form:
/data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {scale:[2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,1f]}- Modifying a specific property:
- Using data merge:
/data merge entity @e[type=minecraft:block_display,limit=1,sort=nearest] {transformation:{scale:[2f,2f,2f]}}Expected behaviour
The command summons an entity with the specified transformation values set, and the unspecified values set to default.
Actual behaviour
Upon running the command, the following error message is logged by the server thread:
Display entityNot a list: {scale:[2.0f,2.0f,2.0f]}The entity has the default appearance, and all of its transformation data is set to their default values.
When setting the transformation property in the summon or data modify command in the decomposed (TAG_Compound) form, all four properties are required; otherwise, the entire object is set to default and an error is logged. This requirement does not exist for the data merge command. Setting the transformation property in the matrix (TAG_List) form works as expected.
As an example, the following two commands do not work as expected:
/data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {scale:[2f,2f,2f]}Whereas the following do work as expected:
- Specifying all four properties:
/data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {translation:[0f,0f,0f],left_rotation:[0f,0f,0f,1f],scale:[2f,2f,2f],right_rotation:[0f,0f,0f,1f]}- Using matrix form:
/data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {scale:[2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,1f]}- Modifying a specific property:
- Using data merge:
/data merge entity @e[type=minecraft:block_display,limit=1,sort=nearest] {transformation:{scale:[2f,2f,2f]}}Expected behaviour
The command summons an entity with the specified transformation values set, and the unspecified values set to default.
Actual behaviour
Upon running the command, the following error message is logged by the server thread:
Display entityNot a list: {scale:[2.0f,2.0f,2.0f]}The entity has the default appearance, and all of its transformation data is set to their default values.
The changelog for 23w18a says:
- Walking on the ocean floor will produce a step sound for the block you are walking on at a lower volume and pitch
However, there seems to be no change between 23w17a and 23w18a.Steps to reproduce
- Open Minecraft in both 23w17a and the latest snapshot
- Place some blocks underwater with loud stepping sounds
- Make sure Players sounds is at 100%
- Walk over them and compare the volume and pitch of the sound in both versions
The changelog for 23w18a says:
- Walking on the ocean floor will produce a step sound for the block you are walking on at a lower volume and pitch
However, there seems to be no change between 23w17a and 23w18a.
Steps to reproduce
- Open Minecraft in both 23w17a and the latest snapshot
- Place some blocks underwater with loud stepping sounds
- Make sure Players sounds is at 100%
- Walk over them and compare the volume and pitch of the sound in both versions
Volume and pitch of underwater step sounds are unchanged
Thanks. I did search for other issues, but I could not find one that was like mine.
I'll delete my issue now.
This is also the case if the player teleports to the ArmorStand. And I agree with FVbico.
"Reopened" means that the issue appeared to be fixed first, but then it broke again and the issue had to be reopened. Your issue is not fixed and won't be fixed, so it can't be reopened and is marked as "Won't Fix".
Confirmed this for Minecraft 1.12.1. The item frames seem to be also positioned randomly, and don't take into account where there's a block to attach to. They pop off after a second or so, like item frames always do.
I also noticed that you cannot put any item into the item frame.
This can be used by mapmakers as a method to generate random numbers, though.
Can confirm for Minecraft 1.12.1. Only the last anvil is left.
What I did notice though, is that when an anvil falls on a torch, the torch disappears and the anvil remains. The torch didn't seem to drop its item, which is probably because it was "crushed" by the anvil.
Can confirm for 1.12.1.
Can confirm for (vanilla) Minecraft 1.12.1
It only happens with /reload for me in 1.12.1. /ban, /kick and /stop don't appear for me.
Still affects 1.12.1. It's an annoying issue, I had to use a workaround in my Redstone contraption for this.
This also appears to be the case for entities. This is especially annoying because the dx/dy/dz selectors don't accept floats. Is there currently any way to select only the bottom center of an entity, rather than anywhere inside the hitbox?
I'm afraid this is intended behavior, but this would be good if this gets changed. It would be amazing to have a proper way to let mobs fight using commands.
Can confirm also for 1.12.2. This is an annoying bug, because in a command system I'm making I use leash knots for centering entities on a block.
Can confirm for 1.12.2
Just did this on 1.12.2. It's really easy to duplicate by eating chorus fruit, which always teleports you down if you're levitating.
For me, it still does not work. I typed in this exact command:
/gamerule doDaylightCycle false
The sun kept moving. In chat there was a message saying that "Gamerule doDaylightCycle is now set to: false". And when I run /gamerule doDaylightCycle it says: "Gamerule doDaylightCycle is currently set to: false". But also after relogging, this seems to have no effect.
Edit: just tested doFireTick and that one also has no effect. This may be not related to doDaylightCycle but to gamerules in general.
Edit: also, I just realised that this is an issue for a version a long time ago, whoops.
Is this still an issue in the latest version?
Haven't been able to reproduce in 17w50a, unless the difference is too small to be noticable. Could you give an example where this behaviour is clear?
Haven't been able to reproduce in 17w50a, could you maybe clarify what you mean with "Half doors" and give a description on how to reproduce this issue?
Can confirm for 18w01a
Can confirm for 18w01a
I don't think that's it, because I don't have any resource packs enabled, and I don't believe my graphics card is out of date.
Confirmed for 18w03b
Updated my drives and it worked. No clue why it stopped working, but I guess that's just the nature of computers. Thanks for the help.
Confirmed for 18w03b
Still the case in 18w03b
Weird. When I just tried it, the item was still there when I reopened the world.
Another thing I noticed is that the game no longer crashes when you hold the item. It only happens when you try to see the item's tooltip.
Edit: I did some further testing and apparently the game crashes when you hold the item in Adventure mode, but not in Creative or Survival. However, the game always crashes when trying to show the item's tooltip, independent of the game mode.
Another thing I noticed, when I set the HideFlags tag of the item to 24 to hide the CanPlaceOn and CanDestroy flags, then the game does not crash. Therefore the bug probably occurs while trying to render the name of the block tag, which of course does not exist.
Also the case in 18w05a and 18w07c.
When I try to switch language, Minecraft stops responding for a long while, but in the end it does work. Could you please attach the crash report to see what the issue is?
Still in 18w10d
Confirmed for 18w10d
Edit: Oh wait I can just do it myself
Can confirm for 18w14b
I tried this twice in 18w14b. The first time, I did find an igloo at the location found by the locate command. The second time, I didn't find an igloo, but I did find some oddly placed snow blocks. I attached a screenshot.
Still an issue in 18w15a
Can confirm for 18w16a
Can confirm for Minecraft 18w19b
This appears to be fixed in 18w21a. When I enchant a Trident using an Enchanting Table it shows the enchantment glow.
Edit: sorry, I think I misunderstood the bug report. There is no enchantment glow in third person view, nor does a thrown trident have the glow.
Also in 18w21a
Still affects 1.13-pre6
The bug report that mine duplicates was posted later than mine, and it contains wrong information...
Edit: nevermind, I looked at the updated time instead of the created time.
It is not the southwestern block for me, but the southeastern block (positive x and positive z)
Can confirm for Minecraft 1.13-pre8
Can confirm for 1.13-pre8
Can confirm this. Happens to me too. Same launcher log.
I closed all other applications when I tested it, but I didn't check if any were running in the background. I'll try again.
Yeah, it appears to work when I don't have OBS open. Thanks!
I think this should be made more specific; it happens when you have no empty slots in your inventory, not only if your inventory is entirely full.
Can confirm for Minecraft 1.16.1
Appears to be fixed in 1.16.1.Edit: nevermind.
Can confirm for 1.16.1
Can confirm the second part of the bug (UUIDs not working) for 1.16.1.
The command /tp @p @e now gives the error message "Incorrect argument for command at position 7: /tp @s <--[HERE]".
The command /tellraw @p {"score":{"objective":"","name":"@e"}} gives the error message "Only one entity is allowed, but the provided selector allows more than one".
I think the issue should be updated.
Can confirm @Sonicwave's comment for 1.16.1.
Can confirm for 1.16.1 but you have to make the window really narrow to make this work.
Can confirm for 20w27a
This applies to any kind of portal, not just nether/end.
And it's still here in 1.16.3
Still in 25w45a
Still exists in 21w03a.
Can confirm in 21w05a. I attached a video which demonstrates that it can be used to break through the bedrock ceiling.
Can confirm this is fixed in 21w17a
Can confirm this is fixed in 21w17a.
Can confirm that this is fixed in 21w17a.
Can confirm in 21w17a
Can confirm in 21w18a.
Edit: it doesn't actually have to be another player, it also happens when spectating other entities
This appears to not be fixed.
It seems that this hasn't been fixed. They are only more common now.
Affects 1.17-pre1
Another example: seed 1, X: 7937, Z: 11337
Affects 1.17-pre1, and also affects new advancements like Surge Protector.
+ 1.17.1-rc2
Still affects 1.17.1
That issue was indeed fixed; it is stored as a double now. This is a different issue.
I have found
MC-187668though which appears to be a similar issue.Ah. It seems to be only when upgrading from old worlds
Appears to not be fixed in 21w37a
Affects 21w37a
Affects 21w37a
Affects 21w37a.
Affects 21w37a.
Affects 21w37a.
Affects 21w37a.
Affects 21w37a.
Affects 21w37a.
Affects 21w37a.
Affects 21w37a.
Affects 21w37a.
Affects 21w38a
Affects 21w39a (also, I found out this wasn't fixed before it was cool 😎 /s)
Affects 21w40a
Affects 21w43a
Affects 1.18-pre1
Affects 1.18-pre1
Affects 1.18-pre1
Another side effect of the world border moving in real time is that it can move while the world is still loading, effectively jumping a big distance even though the world isn't even ticking yet.
Can confirm that this was fixed in 1.18-pre3
As of 1.11.1.0 it looks like it is fixed
Affects 22w06a
Kinda fixed in 22w06a, but there's still a particle on screen off to the side a bit, on the side where you are holding the firework.
small_portal_statue is an identical structure to small_statue.
May be related to the fix of
MC-249764because it seems to be always the same pillar. Some more examples (both seed 1):Can confirm. It seems to be always ½ block to the left and down.
Can confirm for 1.19.2
Probably caused by MC-186538 or a similar bug.
I cannot reproduce this. If I remove the blocks supporting a painting, the painting breaks after a short amount of time also if I don't walk through it.
Caused by
MC-259838Interesting. For the data merge command specifying all properties is not a requirement though, it's only summon and data modify.
Not fixed. I can't find any difference between the behaviour in pre3 and pre4.