Naturally-generated chorus plants have chrous flower at the bottom
The chorus plants that spawn naturally always have the white chorus flower at the bottom. Player-grown chorus plants (and chrous plants in the Java edition) do not.
Linked Issues
Created Issue:
Chorus plants have flower always on bottom + drop the wrong type of flower
The chosus plants that spawn naturally always have the white chorus flower at the bottom
When you break the whole plant you get the white flowers. in the pc version you only get the darker chorus flower pieces and the white ones only if you break the top ones manually
is duplicated by
Chorus plants have flower always on bottom + drop the wrong type of flowerNaturally-generated chorus plants have chrous flower at the bottom
The cho
sus plants that spawn naturally always have the white chorus flower at the bottomWhen you break the whole plant you get the white flowers. in the pc version you only get the darker chorus flower pieces and the white ones only if you break the top ones manually
The chorus plants that spawn naturally always have the white chorus flower at the bottom. Player-grown chorus plants (and chrous plants in the Java edition) do not.
relates to
Closed as a duplicate in favor of the much more descriptive MCPE-18324. (Even though that ticket is newer.)
Revised the title & description to be more descriptive. Also, the second bug in the report (the one about naturally-generated chorus plants having chorus flowers at the bottom) has already been reported as MCPE-18324 ... Please make sure to check for existing bug reports before making your own, and please don't report multiple issues in one report. See this helpful guide on how to make helpful/descriptive bug reports ...Thank you! ![]()


Revised the title & description to be more descriptive, and created a separate issue for the chorus flowers dropping when indirectly broken:
MCPE-18635... Please do not report multiple issues in one report. See this helpful guide on how to make helpful/descriptive bug reports ...Thank you!Fixed in 1.0.0.0 Let us know if you can still reproduce the problem with a newly created map.
Checked back and looks good now!