15Redstones

pre-4: Blocks got fixed, entity collisions didn't.

MC-131094 is probably the same, but also descibes behaviour with other mobs.

Other possibly related issues: MC-124126 and MC-126595

Did you open the world to LAN? I encountered a similar issue in the end dimension when a LAN connected player left the game, the end wouldn't get saved.

In 1.11, this also affects marker:1 armor stands, so creations using makers holding blocks for "micro blocks" are pretty much useless.
This is a HUGE Issue for map makers.

Another problem with the gamerule being defaulted as on:
When you have loads of entities in one block in the spawn chunks (for example because of an iron farm) it's going to be nearly impossible to:
1. Join the world
2. Open the world to LAN with cheats on
3. Open chat
4. Type /gamerule maxEntityCramming 0
All before the villagers in the iron farm start to die. This will be extremely annoying when people update their old maps to 1.11, especially for servers where the villagers would start dying when the first person joins, who might not have the permission to set the gamerule to 0.

I tested it with both the default %appdata%\.minecraft and the %appdata%\.minecraft\snapshot which I use for snapshots so my worlds dont get messed up.
It didn't work in any case.

Not intended for witchut-spawned witches

Why is this marked as works as intended? I don't think that empty huts are intended.

No, it isn't.
I tried it and it doesn't work,

I want the following:
Enabled:
Only "Remove" (not "Replace") o only the head slot.
All other slots and Placing/Replacing Items are disbaled.
What number do I need?

That implementation just doesn't make sense....

Why?
The "how it should work" is how the devs intended it to work, not my request.

Here is what I think how it should work:
1 << slot should only disable removing Items, but allow replacing and placing
1 << slot+8 should only disable replacing items, but still allow removing Items and placing items
1 << slot+16 should only disable placing Items, but allow replacing and removing

To disable an armor stand completely, add them together:
10000000100000001 (binary)

Here is how it works at the moment: (1.9)

1 << slot completely disables all actions
1 << slot+8 disables removing and replacing, but allows placing Items
1 << slot+16 disables placing but allows replacing and removing

This is not good because it doesn't allow for some combinations, for example only allow removing but disable replacing and placing which could be used to detect right-click actions on armor stands.

It also doesn't support the off-hand at all, which should get fixed.

I think fall damage should be based on the speed you had when hitting the ground. If you glide down slowly (elytra, levitation with a level that makes you glide down) you shouldn't take damage.

It's not really fixed in 16w07b.

I hope that mojang makes some of these arguments more useful.
For example, [y=0] should select anything with y atleast 0.
[y=0,dy=10] should select anything between y=0 and y=10.
[y=!0] should detect anything in the void under y=0.
[y=!-64,score_deaths_min=1] could be used to detect a player who died in the void.
That way we could select entitys in specific areas of the world more easily.
Since the old mechanics are pretty broken, these changes wouldn't conflict with many old designs.

confirmed for 15w35a.....

This Looks like the second half of the Entity ID isn't loaded from the scoreboard file. A vrey nasty bug when working with scoreboards and entitys. Nasty.