mojira.dev

SmokeyStack

Assigned

No issues.

Reported

MCPE-226990 Jigsaws don't generate before features do in the same step Unconfirmed MCPE-189716 Interacting with Structure Block UI crashes the game Fixed MCPE-189371 ScriptAPI cannot use the place feature command Won't Fix MCPE-189368 Using a vanilla item as an icon breaks custom groups. Community Consensus MCPE-185868 Item Display Transforms break when using bone visibility Fixed MCPE-180331 "minecraft:enchantable" component value uses a modulus formula Confirmed MCPE-180112 "minecraft:durability" component values above 32767 can result in negative values Confirmed MCPE-180074 "minecraft:damage" component value uses signed 16-bit integer Duplicate MCPE-180073 "minecraft:damage" component value has unexpected integer behaviour Confirmed MCPE-179928 Any Custom Component makes blocks interactable Fixed MCPE-179447 Structure API rotation does not match the structure block or ccommand Fixed MCPE-179262 Custom Components Duplicate Fixed MCPE-178538 Point Light Shadows Does Not Update Properly Cannot Reproduce MCPE-170520 Custom blocks are broken Cannot Reproduce

Comments

[media][media][media]

Can confirm. Via a QNA, a Mojangster stated that only the Trail Ruins and Trial Chambers use the new Jigsaw system that is accessible via the place command and other related APIs.

[media]

Fixed in Preview 1.21.0.24 according to changelogs: https://feedback.minecraft.net/hc/en-us/articles/26354480452109-Minecraft-Beta-Preview-1-21-0-24

@GoldenHelmet The issue is the content log does not say it expects a value from [0, 255], all it says it needs to be a value >= 0 per the content log. If that is the case, then the content log error should be updated, if not, then it needs to stop using the modulus formula. Other components such as "minecraft:use_modifiers -> "movement_modifier" have content log errors that specifically states it has to be within [0,1] and doesn't parse the item correctly. It does not just say, "Value must be >= 0" and use a modulus formula.

>I don't understand why you would expect 32767 damage to be functional and yet convert to 255.

I don't expect it to convert to 255, I expect it to have a damage of 32767 but due to this bug, it converts to 255

Fixed in 1.20.80.22 from my testing!

@v-weszaj I have updated the report with a new world just in case and the add-on as a separate attachment

I have updated the bug report to include a world download and how to reproduce

Custom biomes do not work since 1.18.0 per this bug report: MCPE-100700 . This is a duplicate report in my opinion

As of 1.20.80.21, Mojang has decided to temporarily remove this feature, but should return in an upcoming preview

As of 1.20.80.20, this bug report is no longer relevant. Mojang has replaced the indicator with a slider instead which is separate from the Shadow Quality settings

Preview 1.20.70.22 - Medium Shadow Quality doesn't seem to be affected. High or Ultra settings however causes the circles to appear once again

[media]

Can confirm, fixed in Preview 1.20.0.25

(y)That was my mistake, I used the wrong extension. Uploaded the same pack with a .mcaddon extension instead.

I can confirm, after updating to 1.19.60, any world whose folder name contains a space, is uneditable.

Workaround: Open your `com.mojang` folder, delete any spaces in the folder's name. Restart Minecraft and you are now able to edit the world in-game.

I can confirm, that custom biomes no longer generate while the C&C toggle is turned on. I tested it out by making my biome generate everywhere(No C&C). But when I create a new world with C&C toggle turned on, it no longer generates.