Daniel S.
- dms123
- dms123
- Europe/Stockholm
- Yes
- No
MC-131986
When opening a pruned world originally generated in 1.12.2 there are some interesting chunk boundaries in Mesa biomes. As can be seen in the screenshots, on both sides of the boundary where the chunks were kept/deleted it previously showed the biomes as "Mesa Plateu F", no
ton the kept side it's "mesa_rock" and on the newly generated side "mutated_mesa", which a clearly visible boundary.I do not know if this is intended/expected behaviour or a bug, as I could not find any information on this. My understanding was that changes in tarrain generation should not create chunk boundaries this time?
When opening a pruned world originally generated in 1.12.2 there are some interesting chunk boundaries in Mesa biomes. As can be seen in the screenshots, on both sides of the boundary where the chunks were kept/deleted it previously showed the biomes as "Mesa Plateu F", now on the kept side it's "mesa_rock" and on the newly generated side "mutated_mesa", which results in a clearly visible boundary.
I do not know if this is intended/expected behaviour or a bug, as I could not find any information on this. My understanding was that changes in tarrain generation should not create chunk boundaries this time?
When opening a pruned world originally generated in 1.12.2 there are some interesting chunk boundaries in Mesa biomes. As can be seen in the screenshots, on both sides of the boundary where the chunks were kept/deleted it previously showed the biomes as "Mesa Plateu F", now on the kept side it's "mesa_rock" and on the newly generated side "mutated_mesa", which results in a clearly visible boundary.
I do not know if this is intended/expected behaviour or a bug, as I could not find any information on this. My understanding was that changes in t
arrain generation should not create chunk boundaries this time?When opening a pruned world originally generated in 1.12.2 there are some interesting chunk boundaries in Mesa biomes. As can be seen in the screenshots, on both sides of the boundary where the chunks were kept/deleted it previously showed the biomes as "Mesa Plateu F", now on the kept side it's "mesa_rock" and on the newly generated side "mutated_mesa", which results in a clearly visible boundary.
I do not know if this is intended/expected behaviour or a bug, as I could not find any information on this. My understanding was that changes in terrain generation should not create chunk boundaries this time?
I have observed the same behaviour of baby zombie pigmen and jockeys seemingly attempting to pathfind through half-block spaces, making them pile up.
EDIT: I have also had Baby Zombie Pigmen glitch into the gold/xp farm several times now. Not sure if related, but it didn't happen in 1.12 with much longer afk times.
Possibly related:
When entering a server running on 1.13, nearby item frames seem to play item frame fill or rotation sound. This occurs whether the item in the frame is rotated or not.
Similar behaviour here + lag spike upon first opening. So far every chest this happened with had a buried treasure map.
Attempted to illustrate this in a non-farming, simple nether environment:
When using the pictured simple layout, baby pigmen walk up the stair blocks and pile up in front of the gap. Adult pigmen will pathfind into the pit with the trapdoors. Even when spawning in a bunch of pigmen and mostly keeping the little guys to attempt this without the pit being there at all, they will still pile up, while the single adult in range correctly pathfinds and kills me.
Yes that appears to be describing this exact issue. Mobs just seem to be unaware of half slabs. Regular zombies attempt to walk through 1.5 block gaps, babies attemt to walk through 0.5 block gaps.
So this was just resolved as duplicate. I don't really think it is an actual duplicate. I'm not sure if anyone actually read this beyond the title, and of course this does have something to do with the issue of XP getting stuck in hoppers and such. I was mainly referring to the grindstone though, as the issue seems to be caused by the fact, that Xp is always emitting towards negative X. I'm guessing that is not intended behavior, as it is not case for instance with the furnace (afaik).
Adding a comment here cause my issue[
MC-164656|https://bugs.mojang.com/browse/MC-164656] was closed as a duplicate of this (I don't think it quite is). This is also an addition to the problem described in the comment by Paul Ronquillo.In 1.14.4 (can't make any claims about previous versions), the XP orbs apparently are always emitted in the directions of negative X, which causes them to get stuck when placed against a wall that is facing west. Placing the grindstone anywhere else results in the XP being picked up just fine (at least for me). Have not tested this phenomenon at other coordinates (tested around - 50 / -125). Probably not intended behaviour?