Geeeri

This is still indeed an issue, though it seems like I was able to discover some more information.

On systems using XFS with the `ftype` flag set to `0` servers with these resource packs were no longer able to launch. 

Here is a download link to the testing files: https://archive.geri.dev/bedrock_test_v3.zip

For reference, here is what happens on all of our other nodes that are working, where we use different file system types or `ftype` `1`:

• Server logs: https://p.geri.dev/raw/zipifidoninihisemide

• Login screen: https://i.geri.dev/YWeRFLSgMhjX.png

• Inventory: https://i.geri.dev/XvsD2VxfAjIh.png

—

On a node with XFS and `ftype` 0, here is the startup crash: https://p.geri.dev/raw/lewipejokeficagoqifo

Out of curiosity, I tried disabling the resource/behaviour pack to see if that's the issue and it still crashed with the same log.

After poking around I found that simply removing the `level.dat` file allows the server to launch even when the resource/behaviour packs are enabled. 

I do not know much about the format of this file but from reading the wiki, it seems like experiments are stored here: https://minecraft.fandom.com/wiki/Bedrock_Edition_level_format#level.dat

After a closer look and a DIFF check, it does seem like the freshly generated `level.dat` file has none of the experiments: https://i.geri.dev/iuKaQpolLV7j.png (aside from some of the other, seemingly irrelevant differences)

Just to confirm, I checked in-game and indeed the resource/behaviour packs are not working without these experiments: https://i.geri.dev/9dGTxw3Dy0Om.png

I went back to check if these specific experiments were enabled for the packs that we reported before and that indeed appears to have been the case. 

Using a combination of hex editors and other 3rd party tools, I was able to modify the original level.dat to discover that in this case, the `gametest` experiment when it's set to `1` was causing this crash

Modifying the `level.dat` file to set this to `0` allowed the server to boot without crashes and the resource/behaviour packs worked without any issues as well.

For reference, here are all the files at the end of this test: https://archive.geri.dev/bedrock_test_v4.zip

—

Lastly, I tested a resource as well as a behaviour pack that did not require any experiments to be enabled and sure enough, that appears to work without any issues as well across all different file system types and file system flags. 

—

To summarize: It seems like the issue is being caused by some of these experiments that are failing to load correctly on systems using the XFS file system type with the `ftype` flag set to `1`.

While we completely understand that experiments are just that and may cause instability, it'd be great if the team could check why it would not work on such a widely used file system type and configuration.

Though with the mentioned configuration and full server file downloads, it should be fairly easy to replicate this issue, we would be more than happy to provide a testing server and tools to replicate this issue consistently.

Thanks,
Geri K.

This still appears to be an issue in the latest BDS version (v1.19.2.xx) downloaded from https://minecraft.azureedge.net/bin-linux/bedrock-server-1.19.2.02.zip

The issue appears to be present on the latest release of The Wild Update. The client says it's using v1.19.0 while BDS itself is using v1.19.1.01 if I understand correctly.

Using the same setup, it works perfectly unless it is on AlmaLinux with XFS using ftype=0.

The 1.19 files can be downloaded from here: https://archive.geri.dev/bedrock_test_v2.zip

Shortly after posting it, I realized there was a dedicated section for BDS. — I'm unsure whether moving it to that section would be more appropriate but apologies for the headache.

Alright sweet.

That's most likely an issue with an older texture pack.