joe

Can confirm in 26.2.

Hello,

I’ve replicated this issue in 26.2 Snapshot 4.

/give @s minecraft:wooden_sword

/gamemode spectator (or F3+F4 > Spectator)

/enchant @s minecraft_unbreaking 2

When the commands are applied, it targets the main hand slot and enchants said item regardless of the gamemode.

This also works when giving an item:

/gamemode spectator (or F3+F4 > Spectator)

/give @s minecraft:nether_brick

The hotbar slot remains as it is no matter the gamemode and the only difference in spectator mode is that item usage and interaction with the world are disabled. The inventory contents can still be interacted with externally by commands.

Therefore, I believe this feature is working as intended.

Hey, Elizabeth

I’ve tested this (26.2 Snapshot 4)

Even after creating a world, closing it and reopening it, this problem doesn’t appear.
I believe it’s a device issue.

Hey, Henri
I’ve tested this (Release 26.1.2)
Under normal conditions, this feature works totally fine. I suppose it’s something that you’ve done incorrectly.

Hey, Zack

I have tried this on a previous version (Release 26.1 - Release 26.1.1) and it also doesn’t work. It looks like an intentional game design; the hitbox height for a Java villager is 1.95m, and a carpet’s hitbox thickness is 1/16 of a block therefore making it 0.0625m thick. The result is 2.0125m which doesn’t allow the mob to pass through.

So I recently started a world with a few people, with two of us playing split screen. We decided to transfer the world to a realm to be able to all play whenever but now when they try to join split screen they join as “my username(1)” rather than their character even though it’s still the same account they were playing on before turning it into a realm. Is there a way to fix this or is it just something we’re stuck with?

As a follow-up: Beyond the technical error in 1.21.132, I strongly request that the 'Export' button be officially unhidden for Android. Mobile creators need this for parity with PC to transfer builds and create guides. Supporting this officially would eliminate the need for workarounds and fix this 'Not Supported' error for the community."

To clarify for the technical team: I am using a UI Resource Pack to reveal the Export button on my Android device. While I understand this button is hidden by default on mobile, the functionality worked perfectly in versions prior to 1.21.130. Starting with 1.21.132, the game now explicitly blocks the export with the 'Not Supported' error. My report is to request that this technical block be removed, as the feature is vital for mobile creators who need to transfer structures.

I am an Android player and I rely on the Structure Export feature to create building guides (holograms) for my survival worlds. Since version 1.21.132, this button now returns a 'Not Supported' error. This change makes it nearly impossible for mobile players to transfer builds between worlds without extremely long and difficult workarounds. I really want this functionality to be reverted so mobile players have the same creative tools as PC players.