It's not caused by random ticks, but it used to be fixed by them. It has been in the game for a long time, that is true.
Why? It's inconsistent and doesn't really serve any purpose. It also makes it impossible to use "/execute say" the way you'd expect, you have to use /tellraw instead if you want to simulate chat messages.
@Jason Wilkosz Can you clarify what the bug is here?
Levi, what commands are you using to place the chests?
Confirmed in 1.12. Does not occur with beds. I do not think this is intended.
This has been fixed.
Confirmed in 1.12, only applies to the statistics screen now.
This is a legitimate bug, it's Won't Fix.
Fixed in 1.12.
@Joseph Parenti
What? That's intentional. You played it with a command.
I actually have no idea what I meant by that 😛. Removed.
To clarify the "bug", tab completion will output the possible completions into the chat, but they will only stay in the chat log until tab completion is used again. Personally, I find this to be useful. Leaving them all in the log forever would waste a lot of space.
Confirmed in 16w21b. The cause for this issue is that autojump doesn't take the player's momentum into account. When the player is sprinting, it will jump too late and the player runs into the block since they are moving faster.
Confirmed. The sprint-jump behavior is expected, the player is moving fast enough that they don't hit the top block until after they've already moved under it.