fmease

works as intended. this (block outlines underwater) has never been a thing. neither in version prior to 1.12, nor in 1.13 snapshots

can confirm. relates to MC-130096

@timothy abraham Ctrl+Backspace is already in the game (even in 1.12 and prior❓ )

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.

please read the extended changelogs in the future ... this is a change made in 1.11.2

Check in Options > Controls whether Attack/Destroy is set to Button 1

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.

@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?

@Grum Why is this a bug?

• The player stands on a red Shulker box (for example)

• He summons a falling green (for example) Shulker box below him = inside the red box. The lifetime of the falling block is zero ⚠️

• The falling block dies

• The red box stays the same
  I don't understand .. this works as intended

@mods please resolve this submission as 'works as intended'

It is MC-45050 which 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

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

@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

@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

Works as intended!

"/xp 10L" is equivalent to "/xp 160" because the 10 level (thus "L") are 160 XP Points

Can confirm.
In general, the Observer doesn't check for meta values like "open" (fence gates, doors), "level" (cauldron), "age" (crops like wheat)