Any updates on this bug? Will it be fixed for 1.18?
Yes
I've just made another world and tried it in creative and if you try to level a cartographer to level 3 it happens the same, but it doesn't happen when you try with other types of villagers
How???
We tried to leave the game loading to see if it eventually opens. Sometimes after 5 minutes it opens. Others, we have to wait more than 45 minutes (!!!) to be able to play.
I,ve uploaded two videos where I realized of an exception (see videos attached). When a piston is powered directly with a redstone torch (that torch is on the previous block), piston will pull back the slime block when the torch is removed. But if the piston is powered by redstone dust (it doesn't matter what power that redstone dust) the piston won´t pull back the slime block when redstone is powered off.
Please, if I don't explain myself well, see de videos attached. I know my english is quite bad.
Zi-Wen Lin, it could be a logical reason, but I would like to have a direct answer from Mojang. An explication of why they consider it works as intended after two years treating it as a bug.
(sorry if I've written somethign wrong, my english is quite bad)
But if it works as intended, why did they consider it as a bug from 1.8 snapshot until now? Almost two years have passed since then...
I liked singleplayer more when mobs see you immediately.
I can confirm in 1.8.8. A cat teleported to me suddenly. I had bred a couple a few minutes before.
@Shi-Ron Morman I totally agree with you. I don't mind if beds have a worng texture, or if there is a shadow bug. This kind of bugs don't affect gameplay at all. But this issue...
In my opinion, this is one of the most important bugs in Minecraft. It affects gameply directly. Minecraft 1.7.4 was released almost a year ago... But the problem still persist. Maybe we have to open a new bug report.
I'm not sure if delete the world or use an old version is considered a solution...
Confirm in 1.8
I can confirm.
I'm going to play a few more hours, but I'm almost sure the problem still persists.
I think this still happen in 14w34d.
I can reproduce it in 14w34d.
It happened to me in 1.7.2.
In my server, it crashes when a rail is placed. With an io.netty.handler.timeout.ReadTimeoutException also
Can confirm in 1.21.8