MC-232550Legacy flower pots are not correctly upgraded
This bug affects 1.17.1 most recently, but seems to go back as far as 1.13.
Screenshots attached show a world in 1.4.7, then upgraded to 1.17.1
Flower pots have had multiple storage formats through Minecraft versions. Original flower pots used the block data field to store the type, when slots ran out in later versions, this was changed to a block entity, and finally in 1.13 "flattened" to a unique block for each flower pot/plant type.
All flower pots created with block data, when directly upgraded to 1.13 and above (including 1.17), are given a default of potted_cactus. Flower pots created with a block entity are upgraded correctly. Note that if a world is first upgraded to 1.7-1.12, then to 1.13+, these versions give it a block entity which is correctly processed by 1.13+.
Edit: Added sample world created in 1.4.7.
Created Issue:
Legacy flower pots are not correctly upgraded.
This bug affects 1.17.1 most recently, but seems to go back as far as 1.13.
Screenshots attached show a world in 1.4.7, then upgraded to 1.17.1
Flower pots have had multiple storage formats through Minecraft versions. Original flower pots used the block data field to store the type, when slots ran out in later versions, this was changed to a block entity, and finally in 1.13 "flattened" to a unique block for each flower pot/plant type.
All flower pots created with block data, when directly upgraded to 1.13 and above (including 1.17), are given a default of potted_cactus. Flower pots created with a block entity are upgraded correctly. Note that if a world is first upgraded to 1.7-1.12, then to 1.13+, these versions give it a block entity which is correctly processed by 1.13+.
Attachments2
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
This bug affects 1.17.1 most recently, but seems to go back as far as 1.13.
Screenshots attached show a world in 1.4.7, then upgraded to 1.17.1
Flower pots have had multiple storage formats through Minecraft versions. Original flower pots used the block data field to store the type, when slots ran out in later versions, this was changed to a block entity, and finally in 1.13 "flattened" to a unique block for each flower pot/plant type.
All flower pots created with block data, when directly upgraded to 1.13 and above (including 1.17), are given a default of potted_cactus. Flower pots created with a block entity are upgraded correctly. Note that if a world is first upgraded to 1.7-1.12, then to 1.13+, these versions give it a block entity which is correctly processed by 1.13+.
Edit: Added sample world created in 1.4.7.
![[Mod] tryashtar](../../../data/avatars/users/41963.png){kind=small}
Not related, that's about data which was in-memory only, this data absolutely was stored on the saved block.
![[Mod] Jiingy](../../../data/avatars/users/91802.png){kind=small}
![[Mod] turbo](../../../data/avatars/users/92867.png){kind=small}
Legacy flower pots are not correctly upgraded.
– I am a bot. This action was performed automatically! If you think it was incorrect, please notify us on Discord or Reddit
Could also be worth testing note blocks, as they were handled via block entities prior to 1.13.
May relate to
MC-123142Not related, that's about data which was in-memory only, this data absolutely was stored on the saved block.
Old note blocks seem to upgrade fie (1.12.2 and 1.2.5 tested), so the flower pot must be the only block with a deprecated block entity that breaks like this.