Happened again in 1.18.2 (Vanilla), by directing a leashed bee through a nether portal (from Nether to Overworld, when that matters)…
Having this issue now in 1.15.2...
(and in different villages. Breaking and replacing their beds isn't helping either.)
On slower/weaker systems, the game first freezes, then crashes with a Java Heap Exception on opening the treasure map chest in sunken ships. (1.15.2)
@Asteraoth:
I have experienced the same thing now three times already in 1.14.4 (on Win10/i7/16GB/GeforceGTX1050Ti) – without the game becoming "glitchy" before:
When you ride a horse and then save and exit the game without dismounting, when you restart and reload the game you'll sometimes no longer be riding and your horse (or, in my case, donkey) is missing…
If this is indeed the cause of several cut ravines and caves as well, then this does still exist in 1.14.4 van. on Win10/i7/16GB
Example:
Demo seed "North Carolina" or -343522682, F3-n, F3-g
/tp @s -48.42 18.94 0.10 -463.95 55.80
sigh
Still happens in 1.14.4…
… and still in 1.14.4.
It seems that villagers (mobs) don't really know how to use ladders; I mean: Climbing up or down ladders doesn't seem to be incorporated into the pathfinding routine.
It's actually more like, when a climb-able mob hits a ladder, it automatically starts to climb it.
Why:
I built a two storied room for a villager with a ladder leading upstairs to the bed, but instead of climbing it, the villager rather tried to climb the table in another corner and obviously couldn't reach the bed from there…
(Maybe that's why they also can't walk across trapdoors and several other obstacles…)
Also 1.14.3 van. (without any mods/addons) on win10/i7/16GB
One thing I noticed – maybe due to the mechanisms of the game:
When you dismount a horse/donkey/whatever, it looks as if it's being teleported from somewhere, presumably from the point where you mounted it.
I suspect, when that distance gets too long and/or the chunk where you mounted the horse/… is unloaded, this may occur.
Still in 1.14.3 van. on Win10/i7/16GB.
Still in 1.14.2van on Win 10/i7/16GB.
@violine1101: Aren't the two related? o.O
Still in 1.14.2 - genocide for the entire horse and donkey population? 😞
[EDIT]:
Following a hunch, I just had a look at the hitboxes of horses and donkeys – they're massive!
No other mobs I've ever seen (well, except ravagers, which are a little bit bigger, and bosses) have such incredibly huge hitboxes in comparison to their body size, especially considering the hitboxes of cows or even iron golems, that look almost tiny… – and the hitboxes of donkeys are only marginally smaller than those of horses, even when donkeys are a little bit smaller than cows(?!?)
– No wonder horses suffocate at each opportunity, even when their bodies aren't really next to a wall; the trouble with hitboxes that don't turn according to the viewpoint, when an animal's body length is considerably bigger than its body width….
@Marcono1234
[1.14.2van. on Win10/i7/16GB]
Sure, I have this happen in MC Vanilla (NO MODS) since 1.14.2, as well as seeing them spawned into solid blocks (and subsequently dying) after passing a nether portal.
This was resolved before, but now it happens again and again!
Every time, I have to leave the game and reload it…
My best guess is:
The village boundaries are too extended for villagers to be able to still find their way back to their claimed job site, their claimed bed or even the bell.
So when villagers wander off, due to restricted pathfinding abilities, at some point they are no longer able to find their way back and thus their job site goes unclaimed and can/will be claimed by another unemployed villager.
Just until that villager, too, wanders off too far… (and so on and on)
Resolutions may be:
Reducing the village boundaries to a range that matches the villagers' pathfinding abilities or
extending the pathfinding range of the villagers to match the distance across a village.
Workaround:
Confine certain villagers to their workplaces or reduce the reachable village boundaries with fences or barricades so that the villagers aren't able anymore to wander off too far.
(1.14.2v on i7/16GB/Win10)
This doesn't only happen, when the job site is broken, but also when a villager with a job site, even with a leveled profession, wanders off too far –even inside the village– and can't make it back in a given time, so that his proper job site becomes unoccupied and then gets taken by another unemployed villager.
This usually results in a leveled-up villager with improved trading values never again being able to refill their inventory.
Had this happen again and again.
This obviously results from the villages being far too extended for the villagers to find their way back to a claimed job site or even to the bell at day's end, when they wander off beyond a certain range where they could still find them.
In other words:
The villagers' pathfinding abilities doesn't match the ability of the villagers to claim job sites and the range of the village boundaries.
(1.14.2v on i7/16GB/Win10)
Can we please add trapdoors to this, or are they really meant to trap animals and villagers?
I have an entire village population (including foxes) trapped in the trapdoor decorations of their village…
[media][media](1.14.1v on Win10/i7/16GB)
Also, it does NOT help any, if you keep all the treasure maps or carry them with you and fill them one and all by exploring over and over again, although you already looted and destroyed that specific chest.
When you get the next map, even if the game lags (see MC-126244), the next map will again point to that very same treasure.
Example: In demo seed (-343522682), all maps lead to the treasure at -77 60 427 …
(1.14.1v on Win10/i7/16GB)
Also, in the demo seed (-343522682), near 80 -240, there's a buried shipwreck, which is "checkered" along the chunk borders; two diagonally opposite quarters made of birchwood and the other two quarters made of jungle wood… (screenshot included)
Still in 1.14.1 (when villagers go to bed, use their workstation or talk to other villagers).
Hmm.
Having this problem, too.
Just ocurred to me, that the nesting of the brackets in the error message is wrong.
It says:
"…
MapLike[{event_delay:0,event_distance:0.0f,range:8,source:{pos:[I;-15,-38,258],type:"minecraft:block"
]}}",were it should say:
"…
MapLike[{event_delay:0,event_distance:0.0f,range:8,source:{pos:[I;-15,-38,258],type:"minecraft:block"
}}]".(The square brackets should be the outermost, however, at the end, they are the innermost….)
Could that be causing this error message?