Content Log error appears "[Structure][error]-[[Jigsaw Structure]] couldn't be constructed, no pool named `minecraft:trial_chambers/chamber/end`" in worlds

Confirmed on 1.20.71 server for Windows (not preview).

Update: After testing a bit, the error occurs after I load the world and then try to walk between chunks. I can break blocks in another chunk, but as soon as I move into the other chunk, the error occurs and I am disconnected from the server.

Confirmed on 1.20.71 server for Windows (not preview).

Update: After testing a bit, the error occurs after I load the world and then try to walk between chunks. I can break blocks in another chunk, but as soon as I move into the other chunk, the error occurs and I am disconnected from the server.

have same issue

have same issue

Confirm. The server has the same problem.

Confirm. The server has the same problem.

This isn't an issue only in new worlds, I'm seeing this issue when opening a long established world. Abandoned Village seed. 

This isn't an issue only in new worlds, I'm seeing this issue when opening a long established world. Abandoned Village seed. 

After updating and established bedrock server to 1.20.71.01, that I am running on Ubuntu 22.04.4 in a PVE container. The first time I logged into the world it gave me the same error code. After I logged out and logged back in I did not get it again. Will update if the error persists again.

After updating and established bedrock server to 1.20.71.01, that I am running on Ubuntu 22.04.4 in a PVE container. The first time I logged into the world it gave me the same error code. After I logged out and logged back in I did not get it again. Will update if the error persists again.

Can confirm:

Since update 1.20.71, both starting a local world (new or existing) or the second someone tries to connect to the Bedrock Edition Dedicated Server, the issue comes up.

[2024-03-13 19:04:11:818 ERROR] [Structure] [[Jigsaw Structure]] couldn't be constructed, no pool named `minecraft:trial_chambers/chamber/end`

Server unplayable at the moment, it gives an error, crashes and repeat.

Can confirm:

Since update 1.20.71, both starting a local world (new or existing) or the second someone tries to connect to the Bedrock Edition Dedicated Server, the issue comes up.

[2024-03-13 19:04:11:818 ERROR] [Structure] [[Jigsaw Structure]] couldn't be constructed, no pool named `minecraft:trial_chambers/chamber/end`

Server unplayable at the moment, it gives an error, crashes and repeat.

Same here. The error appears a few seconds after a player login on the server.

Same here. The error appears a few seconds after a player login on the server.

I started seeing this error and getting crashes after upgrading my server to 1.20.71.01. If I take the world and play locally, it runs just fine. I tried a clean copy of server preview 1.20.80.22 with a new world and also experienced the error and crash.

I started seeing this error and getting crashes after upgrading my server to 1.20.71.01. If I take the world and play locally, it runs just fine. I tried a clean copy of server preview 1.20.80.22 with a new world and also experienced the error and crash.

This also occurs on version 1.20.72.01.

This also occurs on version 1.20.72.01.

So this has been going on for 3 weeks.  An update distributed to all clients Forcing everyone to update their servers now makes our server unplayable...  There has been no response beyond closing similar cases.  If there is no solution other than switching your server to using experimental module 1.21, can someone post a link on how to configure a dedicated server's (bedrock) properties file to do so as a work-a-round?  Thanks!

So this has been going on for 3 weeks.  An update distributed to all clients Forcing everyone to update their servers now makes our server unplayable...  There has been no response beyond closing similar cases.  If there is no solution other than switching your server to using experimental module 1.21, can someone post a link on how to configure a dedicated server's (bedrock) properties file to do so as a work-a-round?  Thanks!

Just updated server to version 1.20.72.01 and client to 1.20.72, still having the same issue. As soon as I change chunks, I this error occurs: [2024-03-19 21:07:59:349 ERROR] [Structure] [[Jigsaw Structure]] couldn't be constructed, no pool named `minecraft:trial_chambers/chamber/end`

Just updated server to version 1.20.72.01 and client to 1.20.72, still having the same issue. As soon as I change chunks, I this error occurs: [2024-03-19 21:07:59:349 ERROR] [Structure] [[Jigsaw Structure]] couldn't be constructed, no pool named `minecraft:trial_chambers/chamber/end`

Issue persists on iOS hotfix version 1.20.72

Edit: should say that issue persists in both new worlds and previously generated worlds dating back before the v1.20 releases.

Issue persists on iOS hotfix version 1.20.72

Edit: should say that issue persists in both new worlds and previously generated worlds dating back before the v1.20 releases.

Can also confirm this is happening in my server. Can we get a hotfix for this?

Can also confirm this is happening in my server. Can we get a hotfix for this?

also can confirm...no fun for my kids for three plus weeks. Please save this Dad and his crying kids. 🙂

also can confirm...no fun for my kids for three plus weeks. Please save this Dad and his crying kids. 🙂

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`
👎😞

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`
👎😞

PointedPhoenix8 said:

> I did some testing, If the 1.21 Experimental update is enabled, the server loads and does not crash when a user connects.

How do you enable the Experimental update if you can't log in to the world because of this bug?  Is it an entry in server.properties?

PointedPhoenix8 said:

> I did some testing, If the 1.21 Experimental update is enabled, the server loads and does not crash when a user connects.

How do you enable the Experimental update if you can't log in to the world because of this bug?  Is it an entry in server.properties?

@Lightborne, 

There are two ways to do this. Backup your world before doing either of these methods. 

Method one:

1. Copy the world off your server from the worlds folder to a machine with the Minecraft client installed. It will need to be place in the %localAppData%\Packages\Microsoft.MinecraftUWP_8wekyb3d8bbwe\LocalState\games\com.mojang\minecraftWorlds folder.

2. Open up Minecraft and go to the local worlds. 

3. Find the world that was copied and hit the edit button. 

4. Scroll down to the experiments and toggle the one for "Update 1.21"

5. Start it and exit Minecraft. 

6. Copy the world back to the server and start it up. It will start with an additional line reading "Experiments(s) active: ul23" There may be more depending on your world's configuration. 

Method two: More risky

1. Download NBT Studio or another NBT editor. 

2. Navigate to the level.dat file for the world and open it.

3. Find the section labeled experiments and open it.

3a. If experiments does not exist add a new compound/array item with that name. 

4. Add a new byte item in experiments. 

Name: updateAnnouncedLive2023

Value: 1

5. Save the file and exit the app

6. Relaunch the server. 

Would be nice if this could somehow be marked as URGENT since it's game breaking. Been over a month now with no hotfix or movement.

Would be nice if this could somehow be marked as URGENT since it's game breaking. Been over a month now with no hotfix or movement.

i can confirm the error: client 1.20.71 | server: 1.20.72.01
no crash while joining tho.

How come this haven't been flagged as URGENT yet? It's a major issue and completely blocking the game experience.

How come this haven't been flagged as URGENT yet? It's a major issue and completely blocking the game experience.

This bug CRASHES dedicated server making playing with friends impossible! When will this be fixed?

This bug CRASHES dedicated server making playing with friends impossible! When will this be fixed?

Even after doing the work-around proposed by @PointedPheonix8 the Windows bedrock client still crashes on connect to a bedrock dedicated (Linux) server (with the "fixed" world which was exported from the very same windows client). 

However, the android client on my phone was able to connect, as well as the android client running on my Mac (via Bedrock Launcher).

Some more background: Downloaded latest stable release of bedrock (Linux) server, created a new world. Was able to connect on Windows and play, etc. Eventually I noticed the message in the server logs. Then, the following day, the windows client started crashing on connect. Then I tried the work around.

Crash Error:

Even after doing the work-around proposed by @PointedPheonix8 the Windows bedrock client still crashes on connect to a bedrock dedicated (Linux) server (with the "fixed" world which was exported from the very same windows client). 

However, the android client on my phone was able to connect, as well as the android client running on my Mac (via Bedrock Launcher).

Some more background: Downloaded latest stable release of bedrock (Linux) server, created a new world. Was able to connect on Windows and play, etc. Eventually I noticed the message in the server logs. Then, the following day, the windows client started crashing on connect. Then I tried the work around.

Crash Error:

While I'm seeing possible workarounds for Bedrock, I see nothing suggested for PocketEdition for IOS or Android.

How to do a reinstall of the app without deleting previously created worlds for IOS / Android?

While IOS users (at least this user) is seeing this error, the error does not crash the application like it seems to be doing for Bedrock private servers. If I play on my saved worlds, what risk does this error pose for the future stability and playability in these saved worlds? I have not been playing any world where I've invested any time and effort because I don't want to lose all the work I put in.

Any suggestions? Can I play on my old worlds without risk? Is there an IOS manual back up and restoration process for saved worlds so that I can attempt a reinstall?

While I'm seeing possible workarounds for Bedrock, I see nothing suggested for PocketEdition for IOS or Android.

How to do a reinstall of the app without deleting previously created worlds for IOS / Android?

While IOS users (at least this user) is seeing this error, the error does not crash the application like it seems to be doing for Bedrock private servers. If I play on my saved worlds, what risk does this error pose for the future stability and playability in these saved worlds? I have not been playing any world where I've invested any time and effort because I don't want to lose all the work I put in.

Any suggestions? Can I play on my old worlds without risk? Is there an IOS manual back up and restoration process for saved worlds so that I can attempt a reinstall?

I wanted to say "Thanks" to PointedPhoenix8 for showing a couple of fixes.  So far, I tried the first one and can get back into the world, but it appears to be both wiped to the beginning (nothing we built is there) and removed my operator "Super Powers" (non-command line perks).  I will investigate this further to see what I may have done incorrectly on my end.  So far, you have been the only helpful response to I and my kid's plight.

That said, I'm considering moving over to the Java version with Chromebooks as  the client rather than iPads.  The Java version seems to have more cool features (Multiverse multiple, different worlds and move between them on one server anyone?)  Just as importantly, I'm going to look for a client that doesn't require constant, server breaking updates.  M$ and Mo-Jank could give a crap less about our home servers and just want to keep raking in $$$ for prefab worlds and ala cart features. Hence, the month long wait.  Suggestions would be welcome and I will try to report whatever I find.  Good Luck All.

I wanted to say "Thanks" to PointedPhoenix8 for showing a couple of fixes.  So far, I tried the first one and can get back into the world, but it appears to be both wiped to the beginning (nothing we built is there) and removed my operator "Super Powers" (non-command line perks).  I will investigate this further to see what I may have done incorrectly on my end.  So far, you have been the only helpful response to I and my kid's plight.

That said, I'm considering moving over to the Java version with Chromebooks as  the client rather than iPads.  The Java version seems to have more cool features (Multiverse multiple, different worlds and move between them on one server anyone?)  Just as importantly, I'm going to look for a client that doesn't require constant, server breaking updates.  M$ and Mo-Jank could give a crap less about our home servers and just want to keep raking in $$$ for prefab worlds and ala cart features. Hence, the month long wait.  Suggestions would be welcome and I will try to report whatever I find.  Good Luck All.

I don’t know if this makes a difference, but although I have the error messages in my server log, it does not crash my clients of any flavour. Why? Maybe because I’m running the Ubuntu version of BDS, not Windows. 

I don’t know if this makes a difference, but although I have the error messages in my server log, it does not crash my clients of any flavour. Why? Maybe because I’m running the Ubuntu version of BDS, not Windows. 

I updated one of my servers to 1.20.73, no change for me at least.

I updated one of my servers to 1.20.73, no change for me at least.

Version 1.20.73.01 didn't solve the issue on my side (Windows server). It as the same faulty behavior as for 1.20.71.01 and 1.20.72.01. The players can connect to the world, but is promptly disconnected, making it unplayable. 

Version 1.20.73.01 didn't solve the issue on my side (Windows server). It as the same faulty behavior as for 1.20.71.01 and 1.20.72.01. The players can connect to the world, but is promptly disconnected, making it unplayable. 

Issue still persists on build 1.20.73.01. Client can connect and in a few seconds it throws the [Structure][error]-[[Jigsaw Structure]] couldn't be constructed, no pool named `minecraft:trial_chambers/chamber/end` error and server restarts, disconnecting the users. This is an existing world and is 100% unplayable.

Windows server and client

Issue still persists on build 1.20.73.01. Client can connect and in a few seconds it throws the [Structure][error]-[[Jigsaw Structure]] couldn't be constructed, no pool named `minecraft:trial_chambers/chamber/end` error and server restarts, disconnecting the users. This is an existing world and is 100% unplayable.

Windows server and client

Hosting 2 servers on my windows machine. One of them (super flat creative) seems to still be working fine. The survival server seems to have this issue causing the server to restart. This has been going on since .70 update for this world when will this be fixed? This is an URGENT bug that needs to be fixed because currently all of my players can't play on the survival server.

Hosting 2 servers on my windows machine. One of them (super flat creative) seems to still be working fine. The survival server seems to have this issue causing the server to restart. This has been going on since .70 update for this world when will this be fixed? This is an URGENT bug that needs to be fixed because currently all of my players can't play on the survival server.

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 😞

Just updated client (iPad) to 1.20.73 and server (Windows) to 1.20.73.01. As soon as I enter particular chunks, the error is logged on the server ([Structure][error]-[[Jigsaw Structure]] couldn't be constructed, no pool named `minecraft:trial_chambers/chamber/end`), the server restarts, and the client is disconnected. I have so far discovered two chunks that this happens on, but haven't looked for more, yet.

Just updated client (iPad) to 1.20.73 and server (Windows) to 1.20.73.01. As soon as I enter particular chunks, the error is logged on the server ([Structure][error]-[[Jigsaw Structure]] couldn't be constructed, no pool named `minecraft:trial_chambers/chamber/end`), the server restarts, and the client is disconnected. I have so far discovered two chunks that this happens on, but haven't looked for more, yet.

I really wish somebody from Mojang would pipe up with a comment about impact of this error on various platforms. It looks like private server Bedrock players can not play at all. What is the work around for that user base?

For Minecraft PE players on their device's local worlds seeing this error, what is the impact? I can launch the Minecraft IOS app. I can open a saved local world but I see this error while the world loads. Appears I can interact in the saved world after it opens. Can a world be permanently corrupted by this error if played?

I really wish somebody from Mojang would pipe up with a comment about impact of this error on various platforms. It looks like private server Bedrock players can not play at all. What is the work around for that user base?

For Minecraft PE players on their device's local worlds seeing this error, what is the impact? I can launch the Minecraft IOS app. I can open a saved local world but I see this error while the world loads. Appears I can interact in the saved world after it opens. Can a world be permanently corrupted by this error if played?

Morning all,

Just wanted to see where this is at...Minecraft is how my kids and friends stay connected and spend time together since they all have working parents. Without my server up and running, they all want social media accounts and that is not a good sign. Please make these kids happy and safe again.

Morning all,

Just wanted to see where this is at...Minecraft is how my kids and friends stay connected and spend time together since they all have working parents. Without my server up and running, they all want social media accounts and that is not a good sign. Please make these kids happy and safe again.

I can't help wondering why this has been going on for so long. I just got my server back up after going through divorce (my husband usually did server work) and It is how many of my friends who are long distance and I hang out... So i hope a solution is found soon.

I can't help wondering why this has been going on for so long. I just got my server back up after going through divorce (my husband usually did server work) and It is how many of my friends who are long distance and I hang out... So i hope a solution is found soon.

I'm going to add some information as I see others saying this completely kills the game for them. I have people playing on both the windows client, andoid and amazon app store version and everyone connects fine. I get the error on the server console but people can connect fine and play. I have add this issue for a while but just updated to version 1.20.73.01 today and still see the error. 

Not sure if it will help anyone but server settings are:

gamemode=creative

force-gamemode=false

difficulty=easy

allow-cheats=false

max-players=10

online-mode=true

allow-list=true

max-threads=8

content-log-file-enabled=true

All other settings I left at default. 

I get this error with the 1.20.73.01 bedrock Server and can't play on it with my family 😞 [2024-04-13 08:46:31:892 ERROR] [Structure] [[Jigsaw Structure]] couldn't be constructed, no pool named `minecraft:trial_chambers/chamber/end`

Mine is a pre-exisiting server world but happens when I try to remake the world with a new one as well. When I load the worlds in my client they work fine. 

I have similar settings to Adam below. Only difference for me is max-threads=0 but mostly default besides his settings. 

I get this error with the 1.20.73.01 bedrock Server and can't play on it with my family 😞 [2024-04-13 08:46:31:892 ERROR] [Structure] [[Jigsaw Structure]] couldn't be constructed, no pool named `minecraft:trial_chambers/chamber/end`

Mine is a pre-exisiting server world but happens when I try to remake the world with a new one as well. When I load the worlds in my client they work fine. 

I have similar settings to Adam below. Only difference for me is max-threads=0 but mostly default besides his settings. 

Unplayable for almost 2 months. Nice.

Unplayable for almost 2 months. Nice.

I am also facing this issue 

[Structure] [[Jigsaw Structure]] couldn't be construed no pool named `minecraft:trial_chambers/chamber/end`

I am also facing this issue 

[Structure] [[Jigsaw Structure]] couldn't be construed no pool named `minecraft:trial_chambers/chamber/end`

Is there no workaround? Surely this has to be higher priority than it is

Edit: I might have found a workaround, logged into the server as a different user for 5 minutes in a different area. It didn't lock up immediately but still shows the error. Logged in again with my user and not locking up. Still see the error but no issue for the player.

Is there no workaround? Surely this has to be higher priority than it is

Edit: I might have found a workaround, logged into the server as a different user for 5 minutes in a different area. It didn't lock up immediately but still shows the error. Logged in again with my user and not locking up. Still see the error but no issue for the player.

I also have this message in my console log, but my server works fine. Ironically, I came across this thread because I wanted to make sure I would not have problems down the line.

So if your server isn't working it may well be due to some other factor than whatever is spitting out this error message.

I will say the only different setting I have is that armadillos are enabled, but I still don't have any 1.21 features  or mods other than that.

I also have this message in my console log, but my server works fine. Ironically, I came across this thread because I wanted to make sure I would not have problems down the line.

So if your server isn't working it may well be due to some other factor than whatever is spitting out this error message.

I will say the only different setting I have is that armadillos are enabled, but I still don't have any 1.21 features  or mods other than that.

Also have the issue.  However if I load my server up with the preview edition and also my client my world loads, so at least I know my world is intact.

Also have the issue.  However if I load my server up with the preview edition and also my client my world loads, so at least I know my world is intact.

1.20.80.05 has not fixed the issue. As soon as I went near a portal, I crashed

1.20.80.05 has not fixed the issue. As soon as I went near a portal, I crashed

Months now that I can't play my world.

This feels disrespectful.

Months now that I can't play my world.

This feels disrespectful.

Can confirm, same issue still occurs on 1.20.80.05. Log in, Error triggers, disconnects user, and server crashes/needs to be restarted. PLEASE FIX!

Can confirm, same issue still occurs on 1.20.80.05. Log in, Error triggers, disconnects user, and server crashes/needs to be restarted. PLEASE FIX!

Still no update about the fix?, come on that error make my server crashed after up about 4-18hours

Still no update about the fix?, come on that error make my server crashed after up about 4-18hours

Been watching this for weeks hoping for a fix. I guess I will put myself in for a me too. Unbelievable that there has been no word from Mojang regarding this. 

Linux bedrock server with Windows clients. Doesn't crash my server but throws error logs and kids traveling lose sync with the server. Terrain stops generating. Chat says players are dead but they keep roaming. Made my 9 year old cry.

Haven't played as a family since

Thanks

Been watching this for weeks hoping for a fix. I guess I will put myself in for a me too. Unbelievable that there has been no word from Mojang regarding this. 

Linux bedrock server with Windows clients. Doesn't crash my server but throws error logs and kids traveling lose sync with the server. Terrain stops generating. Chat says players are dead but they keep roaming. Made my 9 year old cry.

Haven't played as a family since

Thanks

I emailed the Minecraft support team about this bug, they sent me this:

I emailed the Minecraft support team about this bug, they sent me this:

That response from Mojang support provided by DeadlyPark is troubling. I'm experiencing this issue on a vanilla iPhone 13, device not jailbroken, latest version of iOS v17.4.1. User profile set to English on the US app store. No private server. No linux. The worlds where I see this issue are local to on my device and saved to iCloud per the usual application installation and backup for an Apple user. You can't get any more straightforward than my set up for an Apple user. These days, I'm not even playing multiplayer, although those worlds have had other MC players in them a long while ago.

That response from Mojang support provided by DeadlyPark is troubling. I'm experiencing this issue on a vanilla iPhone 13, device not jailbroken, latest version of iOS v17.4.1. User profile set to English on the US app store. No private server. No linux. The worlds where I see this issue are local to on my device and saved to iCloud per the usual application installation and backup for an Apple user. You can't get any more straightforward than my set up for an Apple user. These days, I'm not even playing multiplayer, although those worlds have had other MC players in them a long while ago.

This problem potentially broke my server with the 1.20.80.05 update.

It is very disappointing that this issue has yet to be fixed. I want to add that the comment by PointedPhoenix8 (method 1) is probably the only way you can "fix" this issue. If you can copy the your world to your local computer and toggle the Update 1.21 on, then copy back to your sever location this will fix the issue. The only real drawback is once the experiments are turned on you cannot turn them off.

If you have not turned cheats on your world, the experiments on will still give achievements if you are concerned with that.

I did all the updates to get the same issue, including the 1.20.80, but with the experiments turned on in your world file, the server should not have the issue moving forward. I have been able to play for about 2 weeks now.

I hope this helps, it does not appear Mojang/Microsoft will fix this issue before 1.21 comes out. the only hope is that having experiments turned on does break something when 1.21 comes out.

It is very disappointing that this issue has yet to be fixed. I want to add that the comment by PointedPhoenix8 (method 1) is probably the only way you can "fix" this issue. If you can copy the your world to your local computer and toggle the Update 1.21 on, then copy back to your sever location this will fix the issue. The only real drawback is once the experiments are turned on you cannot turn them off.

If you have not turned cheats on your world, the experiments on will still give achievements if you are concerned with that.

I did all the updates to get the same issue, including the 1.20.80, but with the experiments turned on in your world file, the server should not have the issue moving forward. I have been able to play for about 2 weeks now.

I hope this helps, it does not appear Mojang/Microsoft will fix this issue before 1.21 comes out. the only hope is that having experiments turned on does break something when 1.21 comes out.

I am experiencing this on an existing world.

I just upgraded my server to bedrock-server-1.20.80.05 and I see lots of that message:

[ERROR] [Structure] [[Jigsaw Structure]] couldn't be constructed, no pool named `minecraft:trial_chambers/chamber/end`T

The errors continue as long as players are connected.

I am experiencing this on an existing world.

I just upgraded my server to bedrock-server-1.20.80.05 and I see lots of that message:

[ERROR] [Structure] [[Jigsaw Structure]] couldn't be constructed, no pool named `minecraft:trial_chambers/chamber/end`T

The errors continue as long as players are connected.

version 1.20.81.01: Issue still persists... Cannot play game due to server crash.

version 1.20.81.01: Issue still persists... Cannot play game due to server crash.

Confirmed, also crashes for me on 1.20.81.01

Confirmed, also crashes for me on 1.20.81.01

Confirmed, also crashes for me on 1.20.81.01

Confirmed, also crashes for me on 1.20.81.01

BDS STILL CRASHES ON 1.20.81.01 because this error.

I'm going to expose my case, using exactly the same world I've been playing since 1.19 Seed #8624896:

On Win11 Store Bedrock Edition crashed till 1.20.80, actually in 1.20.81.01 stopped crashing (even with a 96 chunk ViewDistance and 12 chunk TickingDistance setting). Being on 1.20.80 when I travel close to a chunk that should spawn a Trial Chamber on a future 1.21 game was just crashing surely because of this error, even when the chunk was already created way back in the 1.19 version. Tried to delete the chunk and adjacents where Trial Chamber should spawn with editors does not work, it crashes too by the same way upon the chunks are loaded.

On BDS 1.20.81.01 still keeps crashing when approaching a chunk that should spawn a Trial Chamber, equally for early loaded chunks and new/deleted chunks. This depends on the ViewDistance setting, not the TickingDistance. So with less ViewDistance the closer you can be to a chunk that will have a Trial Chamber.

BDS STILL CRASHES ON 1.20.81.01 because this error.

I'm going to expose my case, using exactly the same world I've been playing since 1.19 Seed #8624896:

On Win11 Store Bedrock Edition crashed till 1.20.80, actually in 1.20.81.01 stopped crashing (even with a 96 chunk ViewDistance and 12 chunk TickingDistance setting). Being on 1.20.80 when I travel close to a chunk that should spawn a Trial Chamber on a future 1.21 game was just crashing surely because of this error, even when the chunk was already created way back in the 1.19 version. Tried to delete the chunk and adjacents where Trial Chamber should spawn with editors does not work, it crashes too by the same way upon the chunks are loaded.

On BDS 1.20.81.01 still keeps crashing when approaching a chunk that should spawn a Trial Chamber, equally for early loaded chunks and new/deleted chunks. This depends on the ViewDistance setting, not the TickingDistance. So with less ViewDistance the closer you can be to a chunk that will have a Trial Chamber.

Maybe it only appears when generating new chunks. I afking, and there is no error, but when I walking to some new place, the error msg will spam my console..

Maybe it only appears when generating new chunks. I afking, and there is no error, but when I walking to some new place, the error msg will spam my console..

Almost 3 months, still broken as of 1.20.81.X, still can't play. Please update.

Almost 3 months, still broken as of 1.20.81.X, still can't play. Please update.

Hello world ! Hello MOJANG team ! 🙂
I have this message displaying on my BDS server console (see attached file)
it's not causing any crash, but it sends this message at spawning, and when I move especially.

Hello world ! Hello MOJANG team ! 🙂
I have this message displaying on my BDS server console (see attached file)
it's not causing any crash, but it sends this message at spawning, and when I move especially.

I can confirm that this is still happening as of 3rd June 24 on bedrock-server-1.20.81.01 - with a freshly generated map - occurs every 2 minutes.

It doesn't effect play but is noticeable - I attached the log

I can confirm that this is still happening as of 3rd June 24 on bedrock-server-1.20.81.01 - with a freshly generated map - occurs every 2 minutes.

It doesn't effect play but is noticeable - I attached the log

Can confirm this is still happening with a fresh install of a Bedrock server Version: 1.20.81.01.

Those error log keep spamming on the console while a user is logged in to the server. 

Here are the logs:

ERROR] [Structure] [[Jigsaw Structure]] couldn't be constructed, no pool named `minecraft:trial_chambers/chamber/end`

Can confirm this is still happening with a fresh install of a Bedrock server Version: 1.20.81.01.

Those error log keep spamming on the console while a user is logged in to the server. 

Here are the logs:

ERROR] [Structure] [[Jigsaw Structure]] couldn't be constructed, no pool named `minecraft:trial_chambers/chamber/end`

Can you say "Abandonware"? ...I knew you could!