Watermelon_Sir
Assigned
Reported
View all
MC-307926
Items with conflicting components disappear entirely instead of attempting to resolve the conflict
Plausible
MC-306901
Half of the Tripwire texture is unused and made obsolete
Won't Fix
MC-306588
Items with the `equippable` component and `equip_on_interact` set to true cannot be equipped on villagers by using them, even if they're in the `allowed_entities` list
Confirmed
MC-297931
Unlike wind charges, Fireballs do not Despawn when crossing a certain Y level.
Confirmed
MC-276371
Equip sound in Equippable component cannot be set to a sound event from a resource pack
Invalid
MC-275286
Salmon in buckets do not keep their new 'type' size tags
Duplicate
MC-273470
Snowballs with CustomModelData landing do not display the proper particle for their item model.
Duplicate
MC-269425
Foxes holding the Mace do not deal any more damage when doing a pounce attack than when doing a normal attack
Duplicate
Comments
Can confirm 26.4 Snapshot 1
Can confirm in 26.3. I also suggest the resolution status be reconsidered.
Can confirm in 26.3
Can confirm in 26.3
To make my previous submission more brief:
Steps to reproduce:
Drop damagable item, like a golden hoe.
Run command /data modify entity @n[type=item] Item.components.”minecraft:max_stack_size” set value 99
Pick up the item and attempt to place it in either a shulker box or bundle. View tooltip of the storage item.
Observed result: Item is replaced with air. (In bundles this can trigger a crash which was reported in MC-306072, but this report I am making is about the items being replaced with air, not the bundle crash that causes.)
Expected results: Rather than the entire item and all attached data being removed, only the component resulting in a conflict, such as max_damage, is removed.
Can confirm in 26.1.2. My inventory is a minefield. On my favorite creative server, the custom items I create with ‘/data modify’ seem to be big offenders of this bug. If stackable-damagable items never appear in vanilla, why make them invalid at all? It seems like that would be the easiest fix, just allowing them to exist in any context even with strange behavior.
The player model itself is also pixel inconsistent. I'm pretty sure scaling differences as miniscule as 0.8 like the cat uses are pretty inconsequential and are intentional behavior.
Even if there was intent behind switching the kitten scaling back (bedrock parity because they never fixed this problem to begin with) I really doubt anyone intended for kittens to be wider than adults.
This bug has been Re-Introduced in 26.1 Pre-Release 2. The baby cats once again have a head larger than the adults as they are once again the same size as baby ocelots.
Can confirm. Here is an adult cat’s head and a baby cat’s head directly overlayed on top of each other.
This still occurs in 1.21.4. They're affected by lighting, if you put fireworks down two tubes of tinted glass, you'll see that one in a tube that is lit on the inside displays brighter that an unlit tube, even on the outside of the tube where the lighting is the same. This is odd for a light flash, that you'd not expect to act like fog.
Oh, I see. Since putting a plain sound ID from playsound in there works I had mistakenly assumed that was the format. Thank you for clarifying!
This definitely describes a bug.
I think this is a bug. If it worked properly it would work more like player heads' note_block_sound component which accepts any sound event rather than just vanilla ones. Please check again.
You can also see this bug with only one salmon, bucketing it and placing it down repeatedly and observing as its size randomly changes.
Can confirm in 1.21.
If I were a PVPer I would probably just avoid 15-block-tall towers.
Steps to reproduce:
1. Angle dispenser directly upward.
2. Fill this dispenser with fireballs.
3. Activate it with redstone clock or by spamming a lever.
Observed results:
Once shot these fireballs fly into the sky far beyond where they could ever impact an entity or block. They continue to fly for as long as the chunk they’re in is loaded, and when fired in high enough quantities can cause significant server lag.
Expected Results:
Like wind charges, both small and large fireballs reaching far enough beyond the height limit should despawn or explode on the spot.