Autom

Doesn't this make sense though? The top hopper is pushing an item into the container below, the bottom hopper is pulling an item from the container above. I do realise that this may not have been the same as previous versions, but it does make sense 🙂

Can confirm!

The reason for this is that when you "interact" with a redstone ore block, it will change into a "different block", called: "minecraft:lit_redstone_ore". If you add that to the list it will work.

Same thing happened to me just now with a double chest...? Can anyone else confirm?

@Kumasasa: Yes there are, on the left side of the screenshot, there is a whole row of "holes" 🙂 Let me add another screenshot, where i get the exact same situation where he has:

Here you go!

So, from what i'm understanding, you're killing an monster/animal with a stick that has a very high amount of looting enchantment level. This increases the amount of drops you get from killing stuff, but it is also very randomized! That's why you're getting "less" when you try it a couple times. Just the randomness of the looting enchantment.

Now, for the "items disappearing" part: When there's more than 1 of the same item on the ground, and they're close enough together they will merge into one and be a stack of items, but they will still have the correct amount of items in that stack. This is to prevent lag, in larger case scenario's you could have 10 stacks of items on the floor, which would result in 640 entities, if they weren't stacked together. Hope this is understandable 🙂

I hope this is what you're experiencing. If it is, then this is not a bug!

I don't think mojang intended to have a model for the arm when you are holding something in your hand and are looking in first person mode.

So: Intended behaviour

Two questions:
Could you add a screenshot so we can see what is going on?
What block were you standing on top of when you logged out?

I posted a similar response to a potential duplicate (MC-76857) of this bugreport, but this might clear up some things about this bug here too.

Expected behaviour:

Unwanted behaviour:

I've placed down lapis blocks where the water should have flowed, but because of the two holes in the back, the algorithm thinks water should go down there.

This has nothing to do with chunk borders or random tick speed, it's got to do with a bug in the "water flow checking" algorithm. Here's some screenshots to demonstrate:

Expected behaviour:

Unwanted behaviour:

I've placed down lapis blocks where the water should have flowed, but because of the two holes in the back, the algorithm thinks water should go down there.

So, my conclusion: Yes it's a bug, but nothing to do with chunk borders or tickspeed.
This bugreport might be a duplicate of: MC-42387

It's a visual representation of a player descending in creative mode, so in my opinion: Works as intended.