This bug is still present in the official release of minecraft 1.8,though I have observed something else that may lead to the solution to this problem. Last night when replacing all of my 2 block tall flowers in my grand garden, i noticed that every time i would break the bottom block of a two block tall flower (that was not glitched and actually had its upper half) the top half would momentarily turn into the upper half of a peony before disappearing moments afterwards, no matter what type of two block tall flower it was.
if anyone can go ahead and look into proving this next part please do because it may be the solution to our flower problems.
After a while of thinking i resolved that this peony bug and the popping off flower bug must be related to an issue of missing/corrupted/mismatched metadata. here's my reasoning, of course all two block high flowers were designed to break and fall as an item if either the top or bottom blocks were broken (we all already knew that part, but just keep that in mind), and from the peony bug we might be able to assume that the top blocks of all two block high flowers use the same block id, just different metadata to determine what type of flower and which orientation (thus resulting in them reverting to metadata 1 or 0 when in the process of being deleted, which then must be a south facing peony). Finally the reason why the top block goes missing must be because somehow in the crossover from 1.7 to 1.8 the orientation metadata is lost, and the orientation metadata for the southern facing flowers must be 0, because when no value for a variable is specified the computer will assume it to be 0, allowing only south facing flowers to retain their upper half because the orientation variable for them was already 0, also meaning that any flower that is not south facing will of course glitch out because the bottom half remembers is orientation but the upper half is attempting to go into an orientation that should not be according to the lower half, and when the game realizes this it deletes the conflicting upper half possibly in order to avoid crashing or to avoid other conflicts, and last but not least when the flowers receive some form of update they realize their upper half is missing and break the lower half and drop the item.
I hope everyone here can understand what i am trying to say and that you can understand that this is all just conjecture based on my observations and i have not the time nor the java coding experience needed to prove or fix this issue. but if anyone else here does have the time/experience then it would be wonderful if you can look into this.
S. Sweetnam
This bug is still present in the official release of minecraft 1.8,though I have observed something else that may lead to the solution to this problem. Last night when replacing all of my 2 block tall flowers in my grand garden, i noticed that every time i would break the bottom block of a two block tall flower (that was not glitched and actually had its upper half) the top half would momentarily turn into the upper half of a peony before disappearing moments afterwards, no matter what type of two block tall flower it was.
if anyone can go ahead and look into proving this next part please do because it may be the solution to our flower problems.
After a while of thinking i resolved that this peony bug and the popping off flower bug must be related to an issue of missing/corrupted/mismatched metadata. here's my reasoning, of course all two block high flowers were designed to break and fall as an item if either the top or bottom blocks were broken (we all already knew that part, but just keep that in mind), and from the peony bug we might be able to assume that the top blocks of all two block high flowers use the same block id, just different metadata to determine what type of flower and which orientation (thus resulting in them reverting to metadata 1 or 0 when in the process of being deleted, which then must be a south facing peony).
Finally the reason why the top block goes missing must be because somehow in the crossover from 1.7 to 1.8 the orientation metadata is lost, and the orientation metadata for the southern facing flowers must be 0, because when no value for a variable is specified the computer will assume it to be 0, allowing only south facing flowers to retain their upper half because the orientation variable for them was already 0, also meaning that any flower that is not south facing will of course glitch out because the bottom half remembers is orientation but the upper half is attempting to go into an orientation that should not be according to the lower half, and when the game realizes this it deletes the conflicting upper half possibly in order to avoid crashing or to avoid other conflicts, and last but not least when the flowers receive some form of update they realize their upper half is missing and break the lower half and drop the item.
I hope everyone here can understand what i am trying to say and that you can understand that this is all just conjecture based on my observations and i have not the time nor the java coding experience needed to prove or fix this issue. but if anyone else here does have the time/experience then it would be wonderful if you can look into this.