mojira.dev
MC-232272

Villagers with a fixed profession will use any workstation after being zombified and cured

A Farmer villager (Journeyman - I already traded with him and he shouldn't change his profession) used a smoker, a brewing stand, and a blast furnace as he would use a composter as a workstation. The Farmer won't use a composter again if one is placed nearby, thus keeping the other workstation.

I did a test in a creative world and the villager I spawned wasn't bugged at the beginning. Then, after I had the villager zombified and cured (I had done that to the one in my survival world too), the bug appeared

Edit: I originally discovered the bug while playing a modified version of the game, OptiFine 1.17.1. In order to ensure, that the bug wasn't caused by the modification, I tested it in a world that I had created in vanilla 1.17.1. The same problem occurred in vanilla as well

Related issues

Comments

Avoma

This report is invalid as your game was modified when experiencing this issue.

migrated

Thanks for your answer, Avoma.
Although the modification OptiFine only affects client gameplay and things such as rendering normally, I have just tested the issue on a vanilla 1.17.1 world to make sure that the bug wasn't caused by a modification.

The farmer Villager will still use any workstation block as a composter. Even the sound effect played when using a composter will play when the villager works with the other workstations

Avoma

In that case, does this issue happen in a completely new and vanilla world, (not a world that you've previously opened with modifications)? Additionally, providing some screenshots and/or videos of the problem occurring whilst the F3 debug screen is enabled would also be greatly appreciated. Thanks 😃

migrated

I tested the bug in a completly new and vanilla world. The world was also generated using a 1.17.1 vanilla instance of the game (latest release)

ampolive

Can confirm. I was able to reproduce this issue.

tqz78

Duplicate of MC-177505.

ampolive

Thanks, @unknown.

migrated

Thanks for your comment tqz78
I reviewed that bug report and it describes the same issue I was having in 1.17.1. It doesn't include releases 1.16.5 , 1.17 and 1.17.1 though.
My Report assures that the bug is still occuring in 1.17.1

migrated

(Unassigned)

Unconfirmed

(Unassigned)

1.17.1

Retrieved