This event is also logged in the statistics as the player breaking a sunflower.
migrated
Having the same issue.
migrated
Blah and Marquis Owens,
Yes, only a mod can do this. No, don't expect any action any time soon. There are so many bugs in the 14w snapshot branch now I am starting to think Mojang don't know where to start in debugging. They are going through a core code re-design (refactoring some mods have called it) and it's actually introducing bugs. At the same time they are insisting on adding new features, further complicating the already monumental job. Is that smart? I'll let you decide, but they don't seem very interested in making their process more professional, no matter how willing they are to take money for products and services.
kumasasa
@@unknown: Don't make assumption about things behind the scenes.
migrated
I haven't saw this issue yet...sorry π
rene_z
The issue occurs because of the way the data IDs work. Each double plant contains a bit for upper or lower, the additional bits are used for variant on the bottom half and orientation on the top half. This means that the top half alone can't "know" their variant.
You can observe this with the debug screen (F3) and looking at the data in the top right when aiming at the top and bottom half of a double plant.
This issue will probably be resolved when the new block state mechanisms are fully implemented and there can be stored more information per block.
Confirmed for 27a, but it now shows peonys instead of sunflowers.
00Pokemon00
I should also mention you don't have to place it you can place a block on the bottom half of the double grass will do the same but on the previous snapshot 26c you can't place blocks on the grass also
migrated
Confirmed for 14w28a
migrated
1. This it always take this long for a bug to get fixed? 2. Someone should edit the description into this:
Breaking a sunflower, lilac, double tall grass, large fern, rose bush, and peony has the top part of a peony pop up.
marcono1234
Confirmed for 14w29b as MC-62371 describes this too
A similar issue happens with doors, when they are broken both blocks very shortly display in their defaultβ state.
migrated
Confirmed for 1.8 pre-1
migrated
Confirmed for 1.8-pre2.
migrated
Confirmed for 1.8-pre3
migrated
Confirmed for 1.8
migrated
confirmed for 1.8
migrated
confirmed for 1.8
migrated
confirmed for 1.8
migrated
What the mean of confirmed? The glitch still exist on the 1.8 release
migrated
I've seen it happening without the slighest amount of doubt and/or confusion in 1.8.
...for the sake of variety π
migrated
Overwatch C-17: "confirmed" in comments means that that person has experienced that bug in an updated release. "Confirmed" as as a status on the bug itself (up there at the top, with "assigned to," and all the other bug info), I'm guessing is that someone in the Mojang team has duplicated the bug successfully as part of their workflow and will get around to assigning its fix eventually. Not that I think 400 bug testers need to each leave a "Confirmed for v123" comment, but you'll see it on any bug that's been around for more than one version.
migrated
For me, it's been flashing Peony as the top block whenever I break a two-block tall flower. I also noticed a single tall grass block with peony as the top block, but it reverted to normal grass when broken.
migrated
Another Example
migrated
It still occurs in 1.8 full...
migrated
There is no need to keep confirming it for 1.8. This is an easily reproducible bug, and many people have already said that they see it.
ZaCloud
A similar occurrence I reported was breaking wheat changing into a smooth stone for a split second sometimes, on Survival Multiplayer on a vanilla server.
I wonder, does anyone else have MC-11834 happening around the time this happens to them (the "has no item" error)? Could the two be connected? It seemed to coincide for me.
migrated
This is still happening in version 1.8.1-pre2
migrated
And 1.8.1-pre3...
migrated
1.8 version / vanilla biome: Taiga
fren bug :/
migrated
Confirmed for 1.8.1 release.
Sonicwave
Confirmed for 1.8.2-pre1.
Erik Broes
Confirmed for every version upto 1.10.
migrated
Well, is it going to be fixed in 1.10 or no?
migrated
@Grum Wait a minute, i'm confused, is it going to be 1.10 or 2.0?
migrated
@Lucas
Normally a 2.0 (Or anything with X.0.0) implies some major major changes, like a complete re-write or something like that. I'd imagine that unless Mojang do a major change they will just continue with 1.X until they do, that way it keeps it clean with versioning.
migrated
@Lucas 1.10.
kumasasa
@@unknown: Stop troling, there is no version 1.10 in the "Unreleased versions" list π
kumasasa
@@unknown: @unknown said:
Confirmed for every version upto 1.10.
Means: Cannot be fixed until Minecraft 1.10
migrated
@Kumasasa But he said it as a joke
Sonicwave
Confirmed for 1.8.2 and 1.8.3.
migrated
If you delete this one, please at least say why.
@unknown, because it has nothing to do with this bug report.
migrated
If people would stop spamming my email inbox with useless comments, that would be great.
Ezekiel
You can choose to stop receiving emails about a ticket by clicking "Stop watching this issue" on the right, under "People"
migrated
Confirmed for 1.8.5
migrated
You don't need to keep confirming this issue, it has already been said this won't be fixed before 1.9.
migrated
Oh, okay, I apologize, I don't see where that is said but alright, thank you.
migrated
Its not a big deal. In future just check the description because there is a "Confirmation Status" section, for this particular issue it has been confirmed. You can also see the versions that it affected above that.
migrated
Videogamer555,
I know it's not made clear, but if you read back in the comment history that it'll be fixed when 1.9 data structure is implemented. We're in early snapshots for 1.9, so it's a bit early to expect this to be finished.
That being said, I have a host of bugs I have been watching, many over two years old, and I was told in several of those that they would be fixed in 1.8, and they weren't, and haven't had a mod or dev post on them since 1.8's release, so I wouldn't hold my breath.
migrated
still in 15w31b
migrated
and 15w32c
migrated
flower shows when putting blocks in place of double tall grass as the video shows. it happens twice in the video.
Actually it's not fixed. From the reddit link you posted: "Unfortunately you can still place stuff on the bottom block and it will still flash peony. Try with a torch if you donβt believe me. π"
I can confirm this new behaviour. It is just the description/topic of this bug report which needs a slight update to reflect the new behaviour.
migrated
Confirmed for 15w39c
migrated
I am not having this issue in 15w39c. It has plagued my game for every version in 1.8, but finally in 1.9 it is not happening anymore.
I also switched my video card from a GeForce 9500GT to a GeForce GTX 970. The GTX 970 still has the peony issue in 1.8.8, and I am unable to test how the 9500GT responds to 15w39c.
edit: the peony still appears in 15w39c when I remove the tall grass by placing a block where its base lies. Breaking the tall grass does not show the peony. I'd call it 90% fixed.
migrated
Confirmed for 15w40b
migrated
Confirmed in 15w41b, it actually flashes peony again (instead of sunflower)
migrated
Confirmed for 15w42a
migrated
Fixed in 15w43a.
migrated
Not fixed in 15w43b
wobst.michael
Can confirm it's NOT fixed in 15w43b
migrated
@unknown: Hmm.. It's not like that to me. I went back to 1.8.8 to see if the problem was there, it was. So it can't be lag. I don't know.
migrated
Confirmed for 15w44a and 15w44b
migrated
Confirmed for 15w45a, and now it's a sunflower again instead of a peony.
migrated
Confirmed for 15w46a.
migrated
Also confirming for 15w46a. Shows a peony.
migrated
Confirmed for 15w47a, shows a sunflower again
migrated
Also confirmed for 15w47c, today it shows a peony again
migrated
By now, it's actually quite funny how it switches from sunflower to peony and back again each new snapshot (it's just a minor aesthetic bug, not game hindering in any way), and I saw that Grum commented a while ago, so maybe until 1.10, he's just switching it as a joke XD.
migrated
I think it doesn't switch, it just is different per plant.
migrated
I have never seen anything other than a peony, but maybe I am just not breaking the right plants.
migrated
@@unknown No, I always tested with plain double tall grass
shufboyardee
Still happens in 15w49a. In 1.8 through the present, the flowers have had no issue with placing a block at the bottom, but tall ferns and grass do. Should probably change the description to match that.
migrated
Despite reports here that the bug still exists in version 15w49a, I've discovered that on my PC that it was resolved in 15w47c, and has not come back in 15w49a. Of those who report that it's still not been resolved, I'm not sure what version of Java you are using (1.7 or 1.8, or something even newer), or what version of Windows you are using (XP, Vista, 7, 8, 8.1, or 10). I have Windows 7 Home Premium with SP1. It is the 64bit version of Windows. I'm using Java 1.8.0_51, and it's the 64bit version of Java. Double-tall grass no longer flashes the top segment as a flower when it is destroyed for me.
migrated
@@unknown It works for me in version 15w50a. I tested with double tallgrass and large fern. Often a sunflower is displayed, but sometimes a peony. I use JRE8u66 x64, launcher 1.6.44 and NVIDIA GeForce GT 720M on Windows 10.
migrated
Confirmed for 15w51b
wobst.michael
Still in an issue 16w06a
wobst.michael
Still an issue in 16w07b
migrated
Confirmed for 1.9-pre1 and 1.9-pre2
migrated
Is it only me that it is not confirmable in 1.9-pre3?
migrated
@@unknown Yes, it's only you (I think). Place a block at the bottom of Double Tallgrass or a Large Fern, and you'll see a peony/sunflower flash at the top. So, confirmed for 1.9-pre3.
migrated
Sorry, I forgot to place the block. I was just destroying it.
migrated
Confirmed for 16w15b
[Mod]Les3awe
Confirmed for 1.9.3-pre3
migrated
Confirmed for 1.9.3-pre3.
migrated
Confirmed for 1.9.4.
migrated
Confirmed for 16w20a.
migrated
Confirmed for 16w21a.
migrated
Confirmed for 16w21b.
migrated
Confirmed for 1.10-pre1.
migrated
Actually, I think it might be fixed! π
migrated
No, it's still an issue. It is just that it is no longer possible to manually place the block; you have to use a piston to break it.
migrated
Oh, I see how I messed up. I only broke the bottom block of the plant instead of placing a block there, although with that you said Anon, it wouldn't even be possible to do that.
migrated
Confirmed for 1.10-pre2.
migrated
Confirmed for 1.10.
migrated
Confirmed for 1.10.1.
migrated
Confirmed in 1.10.2
migrated
I tested this with all of them in 1.10.2 and it seems to have been fixed.
migrated
Can still reproduce in 1.10.2.
wobst.michael
Still an issue in 16w32a & 16w32b
wobst.michael
Still an issue in 16w38a
migrated
Issue still relevant in 16w40. Double Tall grass and Large fern
wobst.michael
Still an issue in 16w41a
migrated
In 16w41a fully not corrected. When Mojang fix this bug?
wobst.michael
Still an issue in 16w42a
Sonicwave
Still an issue in 1.11.
migrated
Still an issue in 1.11.2.
migrated
Still in 1.12!
bug
Still in 17w43a!
migrated
Can no longer reproduce in 17w47b but I am able to reproduce in 1.12.2.
migrated
Resolved in snapshots. Clever resolution: you can no longer place a block inside the double plant.
migrated
I'm seeing this in 1.12.2
violine1101
@unknown, 1.12.2 is already marked as affected. Also note that this will be fixed in 1.13.