MC-153370Villagers don't move - 1.14.2
Villagers don't move since 1.14.2, they just stand in place for good, not refreshing trades, not sleeping, not trading food, not mating, day and night
Created Issue:
Villagers don't move - 1.14.2
Villagers don't move since 1.14.2, they just stand in place for good, not refreshing trades, not sleeping, not trading food, not mating, day and night
Environment
vanilla 1.14.2
![[Mod] violine1101](../../../data/avatars/users/92858.png){kind=small}
![[Bot] Arisa](../../../data/assets/gravatar/mustek2.png){kind=small}
vanilla 1.14.2
is duplicated by
![[Mojang] slicedlime](../../../data/assets/gravatar/slicedlime.jpeg){kind=small}
Importantis duplicated by
I confirm this bug too.
But this seems to happen only on servers. Anyway it's really boring, villagers are totally stunned, they only walk when you open their interfaces to exchange with them so they come to you but that's all.
All farms/breeders are broken and we can't do anything.
relates to
![[Mojang] Adrian Östergård](../../../data/assets/gravatar/nighter.jpeg){kind=small}
See MC-153370
Duplicate of MC-153370
Duplicate of MC-153370
This might also be MC-153370, even though that has only been reported for 1.14.2.
MukiTanuki, does this issue still happen in 1.14.3, and if so, does MC-153370 describe it?
The bug
Despite MC-153370 has been resolved as Cannot Reproduce, Villagers from meeting points REALLY have AI that becomes frozen when freshly generating new chunks. These don't go to bed, even if there are many free beds, don't work, don't breed and don't even move until a zombie or illager gets close to it, then it will try to flee. After that, its AI is frozen again.
How to reproduce
- Start a new world
- Use /locate to find a nearest village
- Teleport there
- Look at the meeting point
→
Observe that those villagers are not doing anything
Noticed this issue as well, when near a bed they also seem to spam a movement noise as if attempting to access the bed but are stuck in place.
EDIT: This only happens in multiplayer
Seeing something similar happening, using XBox One, single player
Villagers are stuck standing in doorways (most commonly on the outside of the building) seeming to not be able to open them or move. However, if you or another villager comes along and opens the door or moves them out of the doorway they will then continue along. [I wonder if this doorway problem is caused or related to the recent correction where villagers were not closing doors]
Also, seeing them stuck standing on beds next to the wall or in a corner of a wall on a bed not moving or doing anything. However, when you force them to move they will then proceed to move along; if at night they will not sleep or go to their workstation etc.
I believe this goes to a greater issue of bugs and flaws with the new villager rule sets, as there are several reported bugs related to their behavior or lack of correct behavior.
Same issue on multiplayer, bug also won't let villagers resupply.
Can confirm that this has also happened to me on a multiplayer world. Villagers will not move but can be moved around by players.
L, this project is for Java Edition only. For Bedrock Edition please visit the MCPE project.
This sounds like server lag. Do you have other lag issues on your server (such as blocks reappearing after being mined, chests taking a long while to open, and so on)? If so, this might just be another symptom of
MC-138550.this is on java
and its not just lag, they don't EVER move, they haven't moved in 3 days since the update, at all, no refresh of trades either
this is twice i opened this ticket, and there several people confirming it.. this is a real bug, on java, that needs to actually be addressed not just closed immediately..
this is a village and pillage update and the villages are broken
its separate from the bad lag one, we HAD bad lag, i killed a few villagers and the lag went away, so the lag is probably also related to broken villager AI, but the villager AI is broken regardless of the lag it might be causing
Confirmed. The villagers also cause a huge amount of lag (the game only becomes playable after killing them (or letting them be killed by pillagers)); this update is really a bad joke, with abysmal performance regardless of the machine that the game is ran on.
I confirm this bug too.
But this seems to happen only on servers. Anyway it's really boring, villagers are totally stunned, they only walk when you open their interfaces to exchange with them so they come to you but that's all.
All farms/breeders are broken and we can't do anything.
i noticed something btw, me and my friends were playing on a third party server which we had rented and i also had this issue. then we changed to another server provider (because of another issue, the first server providers had bad servers) and this issue was gone, the villagers started moving, breeding, sleeping, and of course restocking. i do belive that switching servers was the fix for this issue, but there might have been something else too who knows. just wanted to tell you. the last server was quite laggy and at 100% all the time, the new server is at 5-10% so try to switch servers and see if this fixes the issue. maybe the server isnt able to handle the AI of villagers when its at max cappacity
Might be related to or even the same issue as
MC-152067.I was seeing this issue with 1.14.2 using a paper server (v51) but when I got current with paper version 81 and even though this is still 1.14.2, the villagers are now behaving normally.
I had this problem with villagers, it turned out to be the multiplayer sleeping datapack we used. try to remove any databack such as these that change the tick cause of the villagers getting confused over day / night
Ringing a bell got them back to normal for me.
I have this problem too.
The bell does not help. All of villagers do not move in ALL villages after the update to 1.14.2. The remaining mobs are fine. The problem is only for villagers.
This is the multiplayer game.
Does
MC-170612describe this issue? I recently reported something very similar.W_V, my problem was on Spigot server. At that time, i switched to papermc, this resolve the problem. papermc had more recent and operational updates. sorry for my English. Now I think this bug is gone for new vershions