Ciosciaa
Assigned
Reported
View all
MCPE-242206
Smithing transform recipes require durability on base item
Unconfirmed
MCPE-242205
Redstone producer component directions not updating on permutation change
Awaiting Response
MCPE-242204
Blocks with redstone producer component not orienting adjacent redstone dust correctly
Confirmed
MCPE-242161
Fossil features’ outputs are their input positions
Unconfirmed
MCPE-242159
Fossil features place to useless locations
Unconfirmed
MCPE-242146
Horizontal tree decoration features too restricted
Unconfirmed
MCPE-242145
Scatter interface grid distribution extents not offset properly
Unconfirmed
MCPE-242144
Feature rule identifier raw names must match their filenames
Unconfirmed
MCPE-242143
Many basic Vanilla features are not data-driven
Unconfirmed
MCPE-242142
Feature definitions not loading without proxying them in no-op feature rules/jigsaws
Unconfirmed
Comments
I’d like to contest this. This is not a feature request. These 2 components are effectively present on a block whether they’re defined or not. There isn’t any indicator transformation should only be considered when explicitly defined. It forms a parity discrepancy between default values (e.g., true) and explicitly stated intents of such.
It’s hard to say, since I don’t know the internals. Here are some related reports pertaining to block permutations. The first is the strongest conceptual fit.
Found out this is a duplicate of MCPE-240790 .
As of Preview 26.50.27, the shears destructibility tag works now. The others still don’t.
Ugh, ignore those attachments. Use these instead.
Fixed video upload:
I can confirm this also affects custom blocks on the latest Preview (26.50.26).
Ah, yes, it does work on the hotfix. I guess Preview hasn’t received this change yet.
Interestingly, this set of blocks also seems to emit sounds and particles on liquid destruction whereas most (all?) other blocks don’t.
The attempted fix of this bug has led to a new bug: MCPE-240720.
Okay, while what I said is true for blocks, compositing for items is still bugged.
Confirmed fixed in recent Preview:
Confirmed fixed in recent Preview
Confirmed fixed in recent Preview:
Looks like this was fixed in a recent Preview!
This bug was more correctly “fixed” in https://feedback.minecraft.net/hc/en-us/articles/46506466842125-Minecraft-Beta-Preview-26-40-22-23:
Small geometries using the
"item_display_transforms" -> "gui" -> "fit_to_frame": falseoption will now be properly centered in format_version 1.21.130 and above (MCPE-234752)
However, the geometry itself is now incorrectly centered in the space, even if the model/display configurations did not indicate such.
Confirmed fixed in Preview 26.30.28.
Confirmed fixed in Preview 26.30.26. The other item dyeable component bugs have not yet been fixed.
I’d like to contest this. This is not a feature request. This is a mishandling of the cases where
minecraft:collision_boxis considered for the sake of allowing snowlogging.[]defines full-block collision, just the same astrue. In every way in the engine except this one,[]equalstrue. This is a special handling oversight on the end of the precipitation interactions component.As for the summary, I wouldn’t have minded if they’d instead redefined
[]asfalse: that would make things more sensible and simpler. But until they do, the point still stands.