I am having the same issue as Rich Harris, the bees on my island keep flying out over the ocean and dying. It's challenging to breed up their numbers since they don't avoid the water.
I can confirm this bug. I uploaded some screens of my friend just holding a shield, and then blocking. There was no movement, and no way for another player to tell if the shield is idle or brought up.
I may have solved the chunk problem. It seemed to be related when the switch to UUID's, which made older dogs/cats unable to stand/sit (MC-50339) I noticed that the affected chunks, were chunks where said dogs could be found. I killed all the dogs while in 15w32c and then loaded up 15w34a and there was no chunk issues.
I have attached a txt file of the console output when I loaded up the world in 15w33c
Just to clarify, you need to load up a 1.8.8 world folder that has NEVER gone into 15w32c. I took my 15w32c world and reloaded it into 1.8.8 and then from there went to 15w33c, I had the exact same result, chunk not loading.
Hrmm well that is both good and bad. Good because it's a real bug, so it should get fixed. Bad because I thought I might have a work around to finish my map room. Thanks for the clarification Surburb
@ SuburbSomeone,
So if I follow along with the new grid, to have a 2048 map centred at ~x,~z I need to make the first map at (~x - 256),(~z - 256), -64 x 4 layers of zooming?
I did skim over it all, it's 90+ comments to read through, and some of them sort of explain a solution or a way to get a correct centre point. But I was looking for a simplified, concise answer. It would not only help me, but anyone in the future would see it, and not have to read through 90+ comments and sort out bits and pieces from multiple comments.
How exactly does this grid system work? As in what numbers/axis do the maps affix to? I am experiencing the problem with my map's centre point moving as I zoom out. But if I can make a 128x128 map centred on the correct point, why does zooming out move the centre point? Is that actually related to the grid changes? I feel if I can make a small map on the correct point, that centre of that map should stay the same as I zoom out. Maybe we could zoom out an empty map and then when we started it it would centre to a grid, but if you zoom out an active map, the centre x/z should stay the same.
Confirmed for 14w32d. I'm a little surprised this bug doesn't have more votes, given how long it's been around
I can confirm this bug. If a daylight sensor is inverted when it's broken, it doesn't drop anything. It doesn't matter with any tool or you fist, no item drop. If you switch an inverted sensor back to normal, it can be broken and picked up like normal.
Still happening in 14w30c. I forgot about this bug, went through the nether and map not working. /stop and then restarting the server fixed it. But that is not a good solution if other people are online
Like Anton van Es said, the only glitch with the 2x2 crafting is when you place just a banner in the grid and it adds the corner pattern. I have also noticed this glitch.
I can confirm this bug. The delay between a block being broken and rendering accordingly makes 14w29b very frustrating to play in.
I can confirm this bug as well. My friend and I were playing on our smp world, we both have multiple dogs. We noticed today and are playing in 14w18b
Confirm. It crashed upon opening my creative world. The crash report showed the error with the rendering of item frames.
Yes I know, but it was relevant to the topic. This bug needs to be corrected, but it might be possible to leave the stone double slab after correcting the bug.
@ Blah, I understand this bug is unintended. I meant the double smoothstone block, when made out of smoothstone slabs stays should stay. Previously if you stacked 2 smoothstone slabs it looked like 2 slabs; where conversely all the other slabs looked like a full block, eg: 2 sandstone slabs looked like a solid sandstone block.
This bug also effects nether quartz slabs. I do like the change in texture of the double smoothstone slabs, hopefully that was intended.
Confirmed in 1.15.2