I first noticed this in 1.16.40 but didn't report it.
Villagers are supposed to stand next to their workstations when they're working, occasionally taking a random walk around and returning. Clerics, however, will climb on top of their brewing stands if they are able to.
If the brewing stand is on the ground, they climb on top of it. If the brewing stand is on a solid block, they climb onto the block, then onto the brewing stand. If the brewing stand is floating above the ground, they stand on the ground beside it looking up, as if looking at the block above it. I have attached screenshots of all three situations. Note: If the space above the brewing stand is obstructed, they will stand beside it and jump for a while as if trying to climb on top of it but failing.
Steps to Reproduce
Create an empty, flat world.
Disable the daylight cycle and weather cycle.
Place a bed and a brewing stand somewhere.
Spawn or summon a villager (must not be a baby or nitwit).
Wait for the villager to become a cleric.
Observed Results:
The cleric stands on top of the brewing stand.
Expected Results:
The cleric stands beside the brewing stand.
Impact:
This seems to be a generally rather harmless bug. The only damage it causes is to the seeming realism of a cleric's behavior.
Linked issues
is duplicated by 1
relates to 1
Attachments
Comments 11
Perhaps related to the fix for MCPE-58244 or MCPE-47075?
If its brewing stand is sitting atop a solid block, a cleric will not always climb onto the block, then onto the brewing stand as I originally reported, even if there is room above the stand for it to stand in. The issue does seem to occur reliably when the brewing stand is on the floor, however.
About the clerics looking at the block above their brewing stand, that's actually always the case for all villagers: MCPE-43207.
Another way to request updates to tickets is to join the Mojira Discord and submit requests there.
The bot does not detect comments that say "affects <version#>". Rather, it copies affected versions from duplicate reports when they are linked.
Oops! My bad. Thanks, GoldenHelmet!
@unknown: I guess you can go back to updating your comments, if you prefer that.
@unknown: Just as info: It never hurts to have up to date info on a report, of course, but it's not always important to test every single release for the bug. As long as the affected versions include either the current full release or the current Beta release, the report is in no danger of being canceled. In fact, they usually don't even look at reports that have been updated in the last 6 months, even by adding a comment, when they try to cull the obsolete ones. So while we appreciate your diligent testing, it would be fine if you want to save yourself some effort by not testing every bug in every new release.
One other thing: Please don't leave the word "Beta" off the release number, as that could cause an ambiguity problem later when viewing archived reports.
Confirmed to be affecting 1.16.200.