mojira.dev
MCPE-44700

Villagers will once again wander around constantly after they're beds are destroyed

Another bug which relates to villagers (See MCPE-43958). When you break a bed while a villager has "claimed" the bed, the villager will aimlessly wandering around and will not stop. In one of the 1.13 betas, the behavior has changed. They will no longer wander constantly, but they will still do this only for 5 seconds.

To Reproduce
1. Spawn villager
2. Place bed
3. Break bed once the villager particles appeared in the bed and villager.

Obvserved results
Breaking villager-claimed beds will make them wander around constantly and never stops

Expected Results
Villagers shoudn't wander around too much when their beds are destroyed

Note: There was a bug where if you spawn villagers, they'll start wandering unless you put a bed and they will claim the bed (MCPE-43958). They still do that in 1.12 (though it was fixed in beta 1.11.0.10) by breaking their beds.

Linked issues

Attachments

Comments 9

I don't get it. How is this a bug exactly? All mobs are supposed to wander around. Especially Villagers when their requirements are not met. If a bed or workstation is missing, they are supposed to walk around, even to the outskirts of the village to find a job or a bed.

That is NOT wandering movement when village is destroyed.

The behavior should be when the village is destroyed as in no more bed within area. The villager will be running around looking/ reaching for village boundary for a few seconds. If none or not make it to the boundary, it will be stopped running and begins wandering normally.

This current behaviour should NOT happen when the village is destroyed, villager will be running straight to center x0, z0 without stopping. Continued running amok on center.

I don't know if this is part of pillager update the villager would become a refugee heading for the center when a village is lost.

See MCPE-45509 await for response whether it's WAI or not.

Drownedzombie

Your video shows the villagers running in the same direction. I am guessing to the world center. If you confirm the behaviour in 1.12 beta. I will update the ticket.

@Eyeth Well I have seen this before. Usually in betas of 1.11, spawning villagers with a spawn egg would make villagers wander constantly. It might be related to your ticket and my ticket (MCPE-43958). In betas of 1.12 this still occurs in a different way. Also the confirmation status is "Confirmed".

Allright I might have misinterpreted wandering constantly as running. They do walking non stop toward world center after bed destroyed.
In creative, egg spawned villager wandering normally until bed was placed and destroyed. It won't stop wandering and head for the center in 2 newly generated worlds.

I feel that we have provided enough information.

Yeah, I see what you mean now. It seems as though the villagers will keep walking in one direction non-stop after their beds are destroyed for some reason. Sorry for the misunderstanding.

@unknown: Please clarify for me: Is the bug you're describing associated with breaking a bed that leaves the villager with no village, or just with no bed? If you break the last or only bed in a village, that might destroy the village and the villager should start looking for a new village to belong to. If the village isn't destroyed, the villager should claim another bed if one is available, or should start wandering to help it find one. The behaviors are different for the two cases. The last time I tested it (which was in the 1.11 Betas), a villager looking for a new village walked or ran continuously in a nearly straight line, but one who only needed a new bed wandered normally, pausing and changing direction frequently.

@[MCPE Mod] Auldrick Unlike the issue MCPE-43958, this issue is about villagers wandering endlessly after their beds are destroyed. I've tested this again in 1.13.0.6 Beta, and the behavior has changed. They "panic" (as in wander) for 5 seconds and eventually stop wandering.

Is this still an issue? Last comment seems to indicate that it has at least changed in 1.13.

Thank you for bringing this to our attention, Michael.

The developers resolved this issue as Fixed in 1.12. However, I'm no longer able to enter 1.12 as a fix version, so I had to leave it blank.

DrownedZombie

(Unassigned)

196032

Confirmed

Android

1.13.0.13 Beta, 1.13.0.9 Beta, 1.12.0.13 Beta, 1.12.0.12 Beta, 1.12.0.11 Beta, ..., 1.12.0.6 Beta, 1.13.0.4 Beta, 1.13.0.2 Beta, 1.12.1, 1.12.0

Retrieved