GamerGever

I cannot edit the bug report for some reason, but I somehow missed the first paragraph when copying important info I told my friends into the ticket so the language manner might be a bit off… 😅
Please ignore (or perhaps edit out, if possible) the first sentence of the ticket

Is this a new issue introduced in 1.21.4 or has it existed before?

This wasn't mentioned in the 25w02a change log (technical section) as far as I can see and so it describes a feature that has unexpectedly (and perhaps mistakenly) broken/changed with no mention.

If it IS intentional, shouldn't this be WAI instead of outright invalid?

Can confirm.

Shouldn't this be WAI (as it is consistent with pink petals and wildflowers) and a Java ticket opened instead?

Is this by design for both types of bush? I can understand the firefly one but shouldn't the regular bush drop seeds like all other similar types of foliage? (Ferns and Grass)

This is an inconsistency and was probably forgotten as to produce a visual distinction that does not make sense logically nor artistically, creating a visual bug. The same "artistic critique" fallacy could be said about the ticket MC-5228 too, however it wasn't closed prematurely and as such was able to be evaluated correctly by Mojang and fixed. Such unintentional and dated inconsistencies have always been properly accepted by Mojang, tracked, and fixed (MC-80468, MC-126564, MC-203594, MCPE-179323, and many more). I don't see how this one is any different to be stamped as invalid immediately like that without consideration.

Following Mojang's past logic and decisions, either the Temperate Pig's texture should be modified to match the Variants', or the Variants' texture should be changed to much the classic Temperate Pig's. However this could be an exception and a WAI, but even in that case, the 'invalid' label would still be wrong.

Requesting reopen to let Mojang properly decide.

@unknown Sorry, I forgot to tag. Still awaiting and curious as to your response

@unknown Which of these criteria does the report not meet, given the note in the description?

If it really is somehow invalid right now, would it be considered valid if a Bedrock update releases to the swamp flora generation as well (in a preview) and still has a different generation compared to Java?

How is this a feature request? All other bushes, grasses, ferns and most leaves are affected by biome tint, and this is an inconsistency that shouldn't occur with this type of plant based on everything else in the game.

Shouldn't it be left to Mojang to decide?

@unknown Thank you for the notice! I have updated the report accordingly.

Update: I found this instance of a couple Firefly Bushes generating in the border between a regular Swamp and a Mangrove Swamp. I cannot say for sure if it generated as part of the classic Swamp or not but it is the only instance I found so far of them generating this close to this biome. Even if it DID spawn as part of the MS - it is still far too rare and doesn't spawn nearly as frequently as in Swamps and Rivers.

This being labeled as a feature request makes no sense

Affects 25w02a.

Also, the wording on this ticket seems to imply the distance traveled has any impact on the bug. I only observed it being affected by velocity and angle.

Seems to be (unintentionally?) fixed in 25w02a due to the fix of MC-7697. I couldn't reproduce

Edit: Nevermind, when shooting at the very very corner of the block it still sometimes does not register the arrow. I find it harder to reproduce in the new version however, it seems it happens less.

@unknown now that this issue is resolved, I'd suggest to open a new report for the other instances of the bug remaining, and in that report you could detail the root cause and point Mojang towards the direction to fix all of them at once and remove unnecessary code.

Note: I have removed Nether Quartz from the ticket.

While at the time, the quartz texture was indeed considerably too low with 3 empty rows at the top and 1 at the bottom instead of 2 rows of empty pixels on both the bottom and the top - the new texture added in 1.14 has since fixed that, being considerably more centered and is consistent with other items which contain one empty row of pixels. prioritizing the top row over the bottom one. For example, textures of Minecart with Chest items and Minecart with TNT items act the same way.

(Attached in order from left to right, with markers: Old Nether Quartz texture, Fixed Old Nether Quartz texture as an example, New Nether Quartz texture, Minecart with Chest texture for comparison, Minecart with TNT texture for comparison.)

Kind of weird that this is invalid. It was a feature that was liked and got broken/removed for a specific reason, which is now completely fixed/resolved yet the feature will remain "broken" in the game?

How is this invalid? I could see a won't fix or a WAI but not only is a mob's pathfinding being unaffected by the larger jump height, but it is also an inconsistency with the camel. Is basic consistency in the core mob behavior considered a "feature request" now?

Edit: Okay, seeing as the resolution on the camel-specific ticket being resolved as "won't fix" I guess it makes more sense, since it is technically a bug (albeit one that Mojang don't want to fix) and a bug shouldn't be transfered for "consistency" so this one I can understand

Still, my first point still stands. Why are animals with 1.5 block-high jumps not able to jump the 1.5 blocks and why is it considered invalid to point that out?

Requesting reopen of this ticket and MC-90580. The resolution of the bugs (Invalid) was pre-maturely given at the time by a mod which meant Mojang never saw it, and any time someone new reports it, it is resolved as a duplicate of this ticket, again eliminating the chance of Mojang seeing it.

My reasoning to saying that this ticket is not invalid, other than the fact there was no provided reason for this resolution, are these bug reports:

• MC-199560 is confirmed by Mojang and has an assigned priority.

• MC-257153 is confirmed by Mojang and has an assigned priority.

• MC-154779 was confirmed by Mojang, given an assigned priority and Fixed.

• MC-217608 was confirmed by Mojang, given an assigned priority and Fixed.

• MC-236117 was confirmed by Mojang, given an assigned priority and Fixed.

• MC-249279 was resolved by Mojang as Works as Intended, confirming it's a valid ticket and getting a proper resolution.

• MC-249689 was resolved by Mojang as Won't Fix, confirming it's a valid bug (that just won't be fixed in the specific case of that individual ticket)

...and many more.

These examples confirm that this issue is to be decided by Mojang and not closed prematurely.

(If the final decision is that the ticket should be re-opened, I would like to request ownership as well please.)