fmease
- Fmease
- fmease
- Europe/Berlin
- Yes
- No
MC-103135![[Mojang] Agnes Larsson](../../../data/avatars/users/10122.svg){kind=small}
2016-06-06_17.08.42.png
/enchant command doesn't allow to put "Curse of Binding" on all types of skull or pumpkins
/enchant command doesn't allow to put "Curse of Binding" onall types ofskull or pumpkins/enchant command doesn't allow to put "Curse of Binding" on skulls or pumpkins
The new enchantment "Curse of Binding" can be put on all types of skull (thus player, Creeper, Ender
dragon, skeleton,witherskeleton, zombie) and pumpkins using an ANVIL andtheenchanted book.And it properly works
,I cannot remove the head I dragged into the armor slot (in SURVIVAL!).
Using the command,the"selected enchantment can't be put on selected target item".The new enchantment "Curse of Binding" can be put on all types of skull (thus player, Creeper, Ender Dragon, skeleton, Wither Skeleton, zombie) and pumpkins using an ANVIL and an enchanted book.
And it properly works: I cannot remove the head I dragged into the armor slot (in SURVIVAL!) any more.
But using the command, it outputs "selected enchantment can't be put on selected target item".
The new enchantment "Curse of Binding" can be put on all types of skull (thus player, Creeper, Ender Dragon, skeleton, Wither Skeleton, zombie) and pumpkins using an ANVIL and an enchanted book.
And it properly works: I cannot remove the head I dragged into the armor slot (in SURVIVAL!) any more.
But using the command, it outputs "selected enchantment can't be put on
selectedtarget item".
This won't affect normal survival gameplay. I used a firework with flight duration of 127 to demonstrate (might not occur with flight:3, gonna test, will edit)
What I expected to happen:
The boost of a firework vanishes after landingWhat actually happened:
After landing, particles still come out of my body. When I launch myself up again, I am immediately boostedTo reproduce:
- /give @p minecraft:fireworks 1 0 {Fireworks:
Unknown macro: {Flight}}
- Activate your elytra and fly
- Boost yourself with that firework you have given yourself
- Land with the elytra
- Observe the trail of fireworks particles
- Fly again
- You are boosted
This won't affect normal survival gameplay. I used a firework with flight duration of 127 to demonstrate (might not occur with flight:3, gonna test, will edit)
What I expected to happen:
The boost of a firework vanishes after landingWhat actually happened:
After landing, particles still come out of my body. When I launch myself up again, I am immediately boostedTo reproduce:
- /give @p minecraft:fireworks 1 0 {Fireworks:\{Flight:127b\}}
- Activate your elytra and fly
- Boost yourself with that firework you have given yourself
- Land with the elytra
- Observe the trail of fireworks particles
- Fly again
- You are boosted
This won't affect normal survival gameplay. I used a firework with flight duration of 127 to demonstrate (might not occur with flight:3, gonna test, will edit)
What I expected to happen:
The boost of a firework vanishes after landingWhat actually happened:
After landing, particles still come out of my body. When I launch myself up again, I am immediately boostedTo reproduce:
- /give @p minecraft:fireworks 1 0 {Fireworks:\{Flight:127b\}}
- Activate your elytra and fly
- Boost yourself with that firework you have given yourself
- Land with the elytra
- Observe the trail of fireworks particles
- Fly again
- You are boosted
This won't affect normal survival gameplay. I used a firework with flight duration of 127 to demonstrate (might not occur with flight:3, gonna test, will edit)
What I expected to happen:
The boost of a firework vanishes after landingWhat actually happened:
After landing, particles still come out of my body. When I launch myself up again, I am immediately boostedTo reproduce:
- /give @p minecraft:fireworks 1 0 {Fireworks:\{Flight:127b\}}
(remove backslashes)
- Activate your elytra and fly
- Boost yourself with that firework you have given yourself
- Land with the elytra
- Observe the trail of fireworks particles
- Fly again
- You are boosted
This won't affect normal survival gameplay. I used a firework with flight duration of 127 to demonstrate (might not occur with flight:3, gonna test, will edit)
What I expected to happen:
The boost of a firework vanishes after landingWhat actually happened:
After landing, particles still come out of my body. When I launch myself up again, I am immediately boostedTo reproduce:
/give @p minecraft:fireworks 1 0 {Fireworks:{Flight:127b}}- Activate your elytra and fly
- Boost yourself with that firework you have given yourself
- Land with the elytra
- Observe the trail of fireworks particles
- Fly again
- You are boosted
I used a firework with flight duration of 127 to demonstrate the bug, but it also occurs in survival/no-cheats with flight duration set to 3
What I expected to happen:
The boost of a firework vanishes after landingWhat actually happened:
After landing, particles still come out of my body. When I launch myself up again, I am immediately boostedTo reproduce:
/give @p minecraft:fireworks 1 0 {Fireworks:{Flight:127b}}- Activate your elytra and fly
- Boost yourself with that firework you have given yourself
- Land with the elytra
- Observe the trail of fireworks particles
- Fly again
- You are boosted
I used a firework with flight duration of 127 to demonstrate the bug, but it also occurs in survival/no-cheats with flight duration set to 3
What I expected to happen:
The boost of a firework vanishes after landingWhat actually happened:
After landing, particles still come out of my body. When I launch myself up again, I am immediately boostedTo reproduce:
pminecraft:fireworks 1 0 {Fireworks:{Flight:127b}}- Activate your elytra and fly
- Boost yourself with that firework you have given yourself
- Land with the elytra
- Observe the trail of fireworks particles
- Fly again
- You are boosted
I used a firework with flight duration of 127 to demonstrate the bug, but it also occurs in survival/no-cheats with flight duration set to 3
What I expected to happen:
The boost of a firework vanishes after landingWhat actually happened:
After landing, particles still come out of my body. When I launch myself up again, I am immediately boostedTo reproduce:
/give @s minecraft:fireworks 1 0 {Fireworks:{Flight:127b}}- Activate your elytra and fly
- Boost yourself with that firework you have given yourself
- Land with the elytra
- Observe the trail of fireworks particles
- Fly again
- You are boosted
I used a firework with flight duration of 127 to demonstrate the bug, but it also occurs in survival/no-cheats with flight duration set to 3
What I expected to happen:
The boost of a firework vanishes after landingWhat actually happened:
After landing, particles still come out of my body. When I launch myself up again, I am immediately boostedTo reproduce:
1 0{Fireworks:{Flight:127b}}- Activate your elytra and fly
- Boost yourself with that firework you have given yourself
- Land with the elytra
- Observe the trail of fireworks particles
- Fly again
- You are boosted
I used a firework with flight duration of 127 to demonstrate the bug, but it also occurs in survival/no-cheats with flight duration set to 3
What I expected to happen:
The boost of a firework vanishes after landingWhat actually happened:
After landing, particles still come out of my body. When I launch myself up again, I am immediately boostedTo reproduce:
- Prior to 17w45a:
/give @s minecraft:fireworks 1 0 {Fireworks:{Flight:127b}}Since 17w45a:
/give @s minecraft:fireworks{Fireworks:{Flight:127b}}- Activate your elytra and fly
- Boost yourself with that firework you have given yourself
- Land with the elytra
- Observe the trail of fireworks particles
- Fly again
- You are boosted
What I expected to happen:
The boost of a firework vanishes after landingWhat actually happened:
After landing, particles still come out of my body. When I launch myself up again, I am immediately boostedTo reproduce:
- Prior to 17w45a:
/give @s minecraft:fireworks 1 0 {Fireworks:{Flight:127b}}Since 17w45a:
/give @s minecraft:fireworks{Fireworks:{Flight:127b}}Since 17w47a:
/give @s minecraft:firework_rocket{Fireworks:{Flight:127b}}
{/code}- Activate your elytra and fly
- Boost yourself with that firework you have given yourself
- Land with the elytra
- Observe the trail of fireworks particles
- Fly again
- You are boosted
What I expected to happen:
The boost of a firework vanishes after landingWhat actually happened:
After landing, particles still come out of my body. When I launch myself up again, I am immediately boostedTo reproduce:
- Prior to 17w45a:
/give @s minecraft:fireworks 1 0 {Fireworks:{Flight:127b}}Since 17w45a:
/give @s minecraft:fireworks{Fireworks:{Flight:127b}}Since 17w47a:
/give @s minecraft:firework_rocket{Fireworks:{Flight:127b}}
{/code}- Activate your elytra and fly
- Boost yourself with that firework you have given yourself
- Land with the elytra
- Observe the trail of fireworks particles
- Fly again
- You are boosted
What I expected to happen:
The boost of a firework vanishes after landingWhat actually happened:
After landing, particles still come out of my body. When I launch myself up again, I am immediately boostedTo reproduce:
- Prior to 17w45a:
/give @s minecraft:fireworks 1 0 {Fireworks:{Flight:127b}}Since 17w45a:
/give @s minecraft:fireworks{Fireworks:{Flight:127b}}{/code} Since _17w47a_:/give @s minecraft:firework_rocket{Fireworks:{Flight:127b}}
{/code}- Activate your elytra and fly
- Boost yourself with that firework you have given yourself
- Land with the elytra
- Observe the trail of fireworks particles
- Fly again
- You are boosted
What I expected to happen:
The boost of a firework vanishes after landingWhat actually happened:
After landing, particles still come out of my body. When I launch myself up again, I am immediately boostedTo reproduce:
- Prior to 17w45a:
/give @s minecraft:fireworks 1 0 {Fireworks:{Flight:127b}}Since 17w45a:
/give @s minecraft:fireworks{Fireworks:{Flight:127b}}{/code} Since _17w47a_:/give @s minecraft:firework_rocket{Fireworks:{Flight:127b}}
{/code}- Activate your elytra and fly
- Boost yourself with that firework you have given yourself
- Land with the elytra
- Observe the trail of fireworks particles
- Fly again
- You are boosted
What I expected to happen:
The boost of a firework vanishes after landingWhat actually happened:
After landing, particles still come out of my body. When I launch myself up again, I am immediately boostedTo reproduce:
- Prior to 17w45a:
/give @s minecraft:fireworks 1 0 {Fireworks:{Flight:127b}}Since 17w45a:
/give @s minecraft:fireworks{Fireworks:{Flight:127b}}Since 17w47a:
/give @s minecraft:firework_rocket{Fireworks:{Flight:127b}}- Activate your elytra and fly
- Boost yourself with that firework you have given yourself
- Land with the elytra
- Observe the trail of fireworks particles
- Fly again
- You are boosted
/no-cheats with flight durationset to 3What I expected to happen:
The boost of a firework vanishes after landingWhat actually happened:
After landing, particles still come out of my body. When I launch myself up again, I am immediately boostedTo reproduce:
- Prior to 17w45a:
/give @s minecraft:fireworks 1 0 {Fireworks:{Flight:127b}}Since 17w45a:
/give @s minecraft:fireworks{Fireworks:{Flight:127b}}Since 17w47a:
/give @s minecraft:firework_rocket{Fireworks:{Flight:127b}}- Activate your elytra and fly
- Boost yourself with that firework
you have given yourself- Land with the elytra
- Observe the trail of fireworks particles
- Fly again
- You are boosted
What I expected to happen:
The boost of a firework rocket vanishes after landingWhat actually happened:
After landing, particles still come out of my body. When I launch myself up again, I am immediately boostedTo reproduce:
- Prior to 17w45a:
/give @s minecraft:fireworks 1 0 {Fireworks:{Flight:127b}}Since 17w45a:
/give @s minecraft:fireworks{Fireworks:{Flight:127b}}Since 17w47a:
/give @s minecraft:firework_rocket{Fireworks:{Flight:127b}}
- Activate your elytra and fly
- Boost yourself with that firework rocket
- Land with the elytra
- Observe the trail of fireworks particles
- Fly again
- You are boosted
What I expected to happen:
The boost of a firework rocket vanishes after landingWhat actually happened:
After landing, particles still come out of my body. When I launch myself up again, I am immediately boostedTo reproduce:
- Prior to 17w45a:
/give @s minecraft:fireworks 1 0 {Fireworks:{Flight:127b}}Since 17w47a:
/give @s minecraft:firework_rocket{Fireworks:{Flight:127b}}
- Activate your elytra and fly
- Boost yourself with that firework rocket
- Land with the elytra
- Observe the trail of fireworks particles
- Fly again
- You are boosted
Since 1.12, items inside a crafting table or an enchanting table etc don't drop to the ground anymore but go back in the player's inventory.
This doesn't happen when leaving the trading GUI.
For example, if I put paper in the left slot andy close the interface, the paper dropson the ground. I expected to see the items go back in my inventoryHence, this is inconsistent with the other GUIs.
Since 1.12, items inside a crafting table or an enchanting table etc don't drop to the ground anymore but go back in the player's inventory.
This doesn't happen when leaving the trading GUI.
For example, if I put paper in the very left slot andy close the interface, the paper will drop on the ground. I expected to see the items go back in my inventoryHence, this is inconsistent with the other GUIs.
Since 1.12, items inside a crafting table or an enchanting table etc don't drop to the ground anymore but go back in the player's inventory.
This doesn't happen when leaving the trading GUI.
For example, if I put paper in the very left slot andyclose the interface, the paper will drop on the ground. I expected to see the items go back in my inventoryHence, this is inconsistent with the other GUIs.
Items inside the trading GUI drop when closing the interface[inconsitency] items inside the trading GUI drop when closing the interface
The bug
Since 1.12, items inside a crafting table
oran enchanting table, etcdon't drop to the ground anymore but go back in the player's inventory. This doesn't happen when leaving the trading GUI.
For example, if I put paper in the very left slot and close the interface, the paper will drop on the ground. I expected to see the itemsgo back in my inventory.
Hence, this is inconsistent with the other GUIs.Since 1.12, items inside a crafting table, an enchanting table and others don't drop to the ground anymore when the interface is closed but go back into the player's inventory. This doesn't happen when leaving the trading GUI.
For example, if I put paper in the very left slot and close the interface, the paper will drop on the ground. I expected to see the item go back into my inventory. Hence, this is inconsistent with the other GUIs.
The bug
Since 1.12, items inside a crafting table, an enchanting table and others don't drop to the ground anymore when the interface is closed but
go back into the player's inventory. This doesn't happen when leaving the trading GUI.For example, if I put paper in the very left slot and close the interface, the paper will drop on the ground. I expected to see the item go back into my inventory. Hence, this is inconsistent with the other GUIs.Since 1.12, items inside a crafting table, an enchanting table and others don't drop to the ground anymore when the interface is closed but go back into the player's inventory. This doesn't happen when leaving the trading GUI.
For example, if I put paper in the very left slot and close the interface, the paper will drop on the ground. I expected to see the item go back into my inventory. Hence, this is inconsistent with the other GUIs.
Items inside the villager trading GUI drop whenclosing the interfaceItems inside the villager trading GUI drop when interface is closed
Items inside the villager trading GUI drop when the interface is closed
I am not certain whether this is a bug.
All I can say is that prior to 17w47a, the NBT-tag "Fireworks" matched the item name "fireworks". This tag specifies details about the item like "Flight".
Under the The Flattening, the item got renamed to "firework_rocket", but the tag still remains "Fireworks".
The tag should be adapted to the new name as it contains additional itemsabout it.
I am not certain whether this is a bug.
All I can say is that prior to 17w47a, the NBT-tag "Fireworks" matched the item name "fireworks". This tag specifies details about the item like "Flight". In the scope of The Flattening, the item got renamed to "firework_rocket", but the tag still remains "Fireworks".
The tag should be adapted to the new name as it contains additional information about it.
I am not certain whether this is a bug.
All I can say is that prior to 17w47a, the NBT-tag "Fireworks" matched the item name "fireworks". This tag specifies details about the item like "Flight". In the scope of The Flattening, the item got renamed to "firework_rocket", but the tag still remains "Fireworks".
The tag should be adapted to the new name as it contains additional information about it.Edit: With "adapted" I mean:
firework_rocket{FireworkRocket:{}}
Can confirm.
In general, the Observer doesn't check for meta values like "open" (fence gates, doors), "level" (cauldron), "age" (crops like wheat)
Works as intended!
"/xp 10L" is equivalent to "/xp 160" because the 10 level (thus "L") are 160 XP Points
@redstonehelper I switched from creative into survival
I don't understand why you declared this as 'resolved' because you cannot enchant the skulls with /enchant but only using an anvil.
I switches to survival to check whether "Curse of Binding" works.
In gamemode 1, it doesnt work by default: Test it out by yourself, you can remove a diamond chest enchanted with "Curse of Binding" in creative.
EDIT2: Do you find enchanted books "curse of binding" in dungeons? If yes, then you can reproduce it in survival using an anvil and a skull/pumpkin
@ShelLuser To my knowledge, the block updates run from one side of the redstone wire to the other. So you are wrong. This isn't a bug. Only because it isn't visual, it doesn't mean nothing's happened
Works as intended.
You made a unsuitable setup using two white Shulker boxes (the one placed in the world, and the falling_block one).
What's happening is not what you guessed. I followed your instructions, playing around a little bit.
Everything in this test is dependent on the `Time` tag which is zero by default. If you set it > 0, you will see the Shulker box dropping as an item
(which is normal looking at e.g. sand falling on a torch).
So the block you placed isn't even replaced by falling_sand, thus the content stays.
Try it out with Block:stone etc. first Time:0 then e.g. Time:200
It is
MC-45050which had been fixed in 14w05a (1.8 snapshot). Apparently, the bug is now the second time in the game!The problem is that the skulls whose meta key "facing" is either "north", "east", "south" or "west" doesn't render correctly: the model and the hitbox is offset.
Note: using /fill => facing:north is default
Note2: the values "north", "east", "west", "south" aren't currently used. "up" takes it all by containing block entity data to define the actual direction
@mods please resolve this submission as 'works as intended'
@Grum Why is this a bug?
I don't understand .. this works as intended
@Paroma Don't try to annihilate the effects but the cause/root of a problem, otherwise you would just create side effects. And we don't want more unecessary bugs on the tracker, right?
It is not your PC but how Minecraft loads the packs into memory I guess. And after all, it is a huge amount of work for the computer: Opening hundreds of images and rules written in JSON and evaluating them. And if you do this while in game, it has to reload all the textures. I don't think it is fixable otherwise they'd done this before, choosing the smartest/fastest algorithm.
Check in Options > Controls whether Attack/Destroy is set to Button 1
please read the extended changelogs in the future ... this is a change made in 1.11.2
I have a similar issue: When I create a new survival world and mine my first log with the fist, I'll receive 2 logs.
@timothy abraham Ctrl+Backspace is already in the game (even in 1.12 and prior
)
can confirm. relates to
MC-130096works as intended. this (block outlines underwater) has never been a thing. neither in version prior to 1.12, nor in 1.13 snapshots