Nick

Date: May 11, 2025

Version: Bedrock 1.21.80

Platform: Xbox One

Seed: -1467574839

Bug: Efficiency 1 Enchanted Golden Apple

Just tried using the exact same thing to make a banner pattern, and it doesn't work. Absolutely FANTASTIC job, Mojang. Asking for an enchanted apple for something, getting one, and then saying "No, thats not the RIGHT enchanted apple."

Attached a copy of my world.
I think it was created around 1.16 - 1.17 as a single player world but was later moved to a bedrock server.
Red village will not link to workstations. (No Green Particles)
Green village links without any problems. (Has Green Particles)
This world was huge and had many large farms and machines, as such amulet was used to remove everything except the Red village.

Red village originally started at the location of green village and was used as the breeding site. All beds and workstations where removed, villagers moved far far away and then Red village was constructed.

I apologize for the late response but updating did not solve the problem. I still get the same error whenever I try to join MC Bedrock servers (iOS device). 

Same issue for over a year. Trying to play Bedrock servers on an iOS device and get the error.

Bedrock Server still unplayable after months!
No experiments, No Addons & No cheats.
World created January 2023.
Server starts fine but instantly crashes upon player joining!
Not happy with the lack of response from Mojang 😞

Just upgraded both client & server (Both on Windows) to 1.20.73

Still unable to play as server crashes as soon as a player tries to join 😞

Just upgraded both client & server (Both on Windows) to 1.20.73

Still unable to play as server crashes as soon as a player tries to join 😞

Definitely still an issue.

This also affects Bedrock Dedicated Servers V1.20.72.01 (Downloaded just moments ago) and crashes the server as soon as a player joins the world.

Can confirm that creating a new world in Minecraft for windows V1.20.72 also gives the error but I have not had any crashes yet:
ERROR] [Structure] [[Jigsaw Structure]] couldn't be constructed, no pool named `minecraft:trial_chambers/chamber/end`
👎😞

Oh, ok, thank you for suggestion, I will try...

So, you think the issue will not occur never again if I update my mcpe to 1.18?

Sure, I sign out and in again, so now Im signed in

This bug also affect 1.17.40.6 Windows 10 Edition.  Single player, LAN Multiplayer worlds & BDS hosted servers.

Steps to reproduce, observed and expected results as per @unknown  instructions.

A newly generated world has been included.

Thank you for your time and effort @unknown . With this world you should also be able to confirm that this problem is not just multiplayer related.

After my original post I continued testing and found that with just one player logged in the exact same behavior could be observed.

Step 1) Load world and confirm the spawner is working.

Step 2) Travel to the nether & back.

Step 3) Move within activation range of the spawner & observe.

Observed Results: The spawner stops spawning new mobs

Expected Results: The spawner's spawn activity is unaffected.

I'm not sure if this info changes how things get reported but it is worth mentioning.

Thank you to everyone who has commented & voted 👍

Thanks for reporting this bug Shaine 👍 I usually play on two different worlds both from my PC (Minecraft Win10 Edition). One is my long term local world hosted on my pc from within Minecraft without BDS. The other is hosted by someone else using BDS. Both worlds have been affected by this bug which renders spawners useless after updating to 1.17.3.

The easiest way to replicate this bug is to have two players in the overworld.

Step 1) Stand Player 1 within range of a working spawner. 

Step 2) Player 2 enters any nether portal from the overworld.

Outcome) Spawner at the first players position will no longer spawn mobs.

On a BDS hosted word with many players, if your spawners stops working you can relog to "fix" this temporarily or at least until another player enters a portal. On this world other players have reported that another player being within range of a spawner has been enough to stop theirs from working. 

If you are locally hosting your world then this "fix" does not apply and the spawner will remain inactive until the host relogs, kicking every player.

This is a big issue that affects all multiplayer game modes as well as single player worlds. 

I think everyone can agree that one active spawner per world is definitely going to have a negative effect on gameplay and needs to be fixed asap. 

MCPE-142285 seems to be the same problem. Please up-vote so these issues get fixed!

Thank you 😃

Thanks for reporting this bug👍 I usually play on two different worlds both from my PC (Minecraft Win10 Edition). One is my long term local world hosted on my pc from within Minecraft without BDS. The other is hosted by someone else using BDS. Both worlds have been affected by this bug which renders spawners useless after updating to 1.17.3.

The easiest way to replicate this bug is to have two players in the overworld.

Step 1) Stand Player 1 within range of a working spawner. 

Step 2) Player 2 enters any nether portal from the overworld.

Outcome) Spawner at the first players position will no longer spawn mobs.

On a BDS hosted word with many players, if your spawners stops working you can relog to "fix" this temporarily or at least until another player enters a portal. On this world other players have reported that another player being within range of a spawner has been enough to stop theirs from working. 

If you are locally hosting your world then this "fix" does not apply and the spawner will remain inactive until the host relogs, kicking every player.

This is a big issue that affects all multiplayer game modes as well as single player worlds. 

I think everyone can agree that one active spawner per world is definitely going to have a negative effect on gameplay and needs to be fixed asap. 

BDS-15605 seems to be the same problem. Please up-vote so these issues get fixed!

Thank you 😃

I think I understood why spawn rate in the end was broken, and now it's fixed (hopefully).

I resolved my issue, for windows 10 version on PC at least. Sonic Studio 3 was where my issue spawned from. I recently installed voicemod for my mic and it was interfering with Sonic Studio III - causing Audacity and Minecraft, when loading in, to crash, always at 46% on MC. This is only for PC obviously, but I resolved my issue by going to Control Panel > Hardware and Sound > Sound > Recording (Second tab in new window) > Scrolled to Microphone (subname: Sonic Studio Virtual Mixer) > Properties > Device Usage: (set to: "Do Not Use This Device (disable)"). I then set Voicemod as my primary recording option.