BDS-706New Villagers are Broken
The new Villagers have a few issues on the Bedrock Server 1.10.0.7 (this version is not able to be selected from the version listing).
-The do not have their new skins except for the wandering villager.
-All of the new villagers do not have a trade interface.
-All of the new villagers, if struck, they fly straight up into the sky and do not return.
The old villagers are still available as an option, and those still work as intended and they react as intended.
I run the server of a Win 10 system, and access it from PC, Xbox One, and Android. All get the exact same results with the new villagers.
Linked Issues
duplicates1
Comments1
History3
Added description:
The new Villagers have a few issues on the Bedrock Server 1.10.0.7 (this version is not able to be selected from the version listing).
-The do not have their new skins except for the wandering villager.
-All of the new villagers do not have a trade interface.
-All of the new villagers, if struck, they fly straight up into the sky and do not return.
The old villagers are still available as an option, and those still work as intended and they react as intended.
I run the server of a Win 10 system, and access it from PC, Xbox One, and Android. All get the exact same results with the new villagers.
Removed environment:
The new Villagers have a few issues on the Bedrock Server 1.10.0.7 (this version is not able to be selected from the version listing).
-The do not have their new skins except for the wandering villager.
-All of the new villagers do not have a trade interface.
-All of the new villagers, if struck, they fly straight up into the sky and do not return.
The old villagers are still available as an option, and those still work as intended and they react as intended.
I run the server of a Win 10 system, and access it from PC, Xbox One, and Android. All get the exact same results with the new villagers.
Added duplicates link: MCPE-43464Villagers float/flyFixed
Resolution: Unresolved → Duplicate
Thank you for your report!
We're actually already tracking this issue at
MCPE-43464, so we will resolve and link this ticket as a duplicate.If you would like to add a vote and any extra information to the main ticket it would be appreciated.