SmokeyStack

I guess this can be closed as “Won’t Fix” or “Works as Intended” per this comment: https://github.com/MicrosoftDocs/minecraft-creator/issues/962#issuecomment-3553274424

I can verify this too, using scripting API as well, whether you unleashed via breaking the block the lead is attached to or going away super far that the leash break, it will not trigger the on_unleash event. This is actually because the docs lied! on_unleash_interact_only default value is actually set to true! Adding, "on_unleash_interact_only": false will now work as intended.

You’re trying to install a UWP version of Minecraft 1.21.120. Starting with version 1.21.120, Minecraft no longer uses UWP — it now runs on GDK instead.

When you download the msixvc link from XBOX themselves, they give you a file called MICROSOFT.MINECRAFTUWP_1.21.12004.0_x64__8wekyb3d8bbwe.msixvc. So this comment of yours has no relevance in this bug report.

You can create a desktop shortcut using minecraft-preview://creator/?Editor=true for now.

This behaviour is now on Bedrock.

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.

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

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.