Previous Ticket MC-151376
This issue was marked as fixed in a previous Ticket, unfortunately it seems to be only fixed in a 50% since pre-generated villagers (Those ones that generate naturally from the jigsaw blocks on villages) still suffer a bad pathfinding, compared to villagers generated from spawn eggs or from breeding, from my recent tests the always buggy behavior that was present ever since the first 1.14.1 snapshot remains here, the new generated villagers (From spawn eggs, summon commands and natural breeding) have a lot less of problems detecting the POIs and they have a wide detection range. Overall for survival players the problem still very visible, specially in freshly generated villages where it can take up to 2-3 in game days to see a villager take a profession along with the frequent deaths due to the lack of detection for beds or meeting points.
⚠️ As you can see, currently using the first 1.15 Snapshot
[media]
❌ It seems like it doesn't reach the door, more like these villagers pathfind straight up using the close path.
[media]
➕ An interesting observation that I noticed is that this issue is not present in every Villager, there's some villagers that can access to their POI with no problem, probably due to how the Doors are facing, I believe this can be a factor as these naturally generated villagers do pathfind using the closest alternative even if this is blocked.
❌ More examples
[media][media]
[media]
Related issues
relates to
Attachments
Comments
migrated
New ticket from the previous issue that wasn't fixed at all MC-151376
tryashtar
Could you please provide the seed of this world for reproduction purposes?
Yes sure, here is the seed
-1713528529566441739
Superflat World, the Village is very close to Spawn
As for reproduction purposes you can try to reproduce this issue in any Seed, you just need to find a Village and set the time to night, preferably in Peaceful Mode to let Villagers behave normally, you will notice lot of them not entering their Houses or trying to, but failing in the process.
[media][media]
Snapshot 20w11a as you can see in the Debug Screen, the Bed is empty and the Villagers are not even trying.
If you use F3+I (to receive the selected entities NBT) on a villager that has spawned due to a jigsaw block(world generation) you will see that these villagers have a follow range of 16 blocks instead of the intended 48 that all other villagers have (From spawn eggs, breeding etc...). I believe that this lowered follow range is the issue to this behavior.
Interesting observation, I believe that since 1.14 was released with a poor Chunk generation and slow performance Mojang had to optimize some things in the game and it was until a 1.14.1 Snapshot that they cut this range for Villagers in an attempt to optimize some calculations with the new AI and I believe it wasn’t intentional to let Villagers with this conflicted behavior, I made a previous report where it got addressed by a Developer in 1.14.3 but unfortunately it only fixed this Issue for New Generated Villagers (From breeding, spawn eggs, summon or curing)
So, addressing this Issue is pretty simple in theory, like @Spook Ster mentioned, these Villagers naturally generate with a follow range attribute of 16, while it’s supposed to be 48, I tested the last week some things and end up fixing and addressing this issue by making a Data Pack where I changed the outdated Villagers in the Jigsaw Block entries with others spawned by Spawn Eggs which by default has a 48 Range, so I made the Data Pack that changes the Jigsaw entries for these Villagers, all those 3 Unemployed, Baby and Nitwit changed with updated ones and it worked, the Data Pack allowed these Villagers finally Pathfind correctly. It was this value that was making a lot of difference since it had just a third part of the supposed range standard for every villager.
Here's the Data Pack for testing
[media]
Will the fix for 20w19a and later 1.16 also fix already existing naturally generated villagers-,- i.e. is the follow range something in their NBT data or in the game code itself?
Edit: Ok, found in MC-166764 that it's in their NBT data, but my original question kind of remains: Will that value be updated when updating the world to 1.16?
No, this Issue fix does't have an impact in Villagers generated in versions prior to 20w19a, unfortunately the problem had to do more with an attribute value rather than a more complex programming in their AI.
Here are 2 Screenshots from the Superflat World I used for this report back in 1.14.4, this is in 20w19a.
[media][media]
Im seeing a lot of the below in console i feel maybe related to this issue
[03:58:31] [Server thread/ERROR]: Failed to read POI section: No key Valid in MapLike[{Records:[{pos:[I;-506,74,15684],free_tickets:1,type:"minecraft:leatherworker"}]}]
[03:58:31] [Server thread/ERROR]: Failed to read POI section: No key Valid in MapLike[{Records:[{pos:[I;-479,70,15686],free_tickets:32,type:"minecraft:meeting"}]}]
[03:58:31] [Server thread/ERROR]: Failed to read POI section: No key Valid in MapLike[{Records:[{pos:[I;-464,68,15683],free_tickets:1,type:"minecraft:farmer"}]}]
[03:58:36] [Server thread/ERROR]: Failed to read POI section: No key Valid in MapLike[{Records:[{pos:[I;-716,64,15578],free_tickets:0,type:"minecraft:home"}]}]Apparently, 1.16.2 (or earlier) fixes existing villagers, too. I updated the other day and wanted to fix them manually with "data modify entity", but they all had their values changed from 16 to 48 already. Thank you 🙂
coschevi