Server Crashes on Startup after Update

[OatmealOnToast]

Hi!

Updated to build 55 for the latest Bedrock update and the server crashes on startup with the following error: [main/WARN]: Failed to load datapacks, can't proceed with server load. You can either fix your datapacks or reset to vanilla with --safeMode

Removing datapacks from the folder results in the same crash, as well as removing all other mods besides the Fabric API (which is up to date). The server starts again normally after reverting to the backup I made before I updated. The server also starts normally if I remove Geyser entirely.

After some trial and error I've discovered that a change between builds 50 and 51 has caused the error, as build 50 doesn't throw the error but 51 does.

Server log can be found here: https://mclo.gs/L1qd6GZ

Thanks for any help!

[mangosurvival]

As someone said in my issue, a temporal solution is installing the latest stable Floodgate-fabric build, after that the issue should be gone.

You can download it here: https://ci.opencollab.dev/job/GeyserMC/job/Floodgate-Fabric/job/master/81/

[OatmealOnToast]

As someone said in my issue, a temporal solution is installing the latest stable Floodgate-fabric build, after that the issue should be gone.

You can download it here: https://ci.opencollab.dev/job/GeyserMC/job/Floodgate-Fabric/job/master/81/

I'll try it, thanks!

[Camotoy]

Has this issue been resolved?

[ghost]

Hello @Camotoy, since this issue is still open = I think not yet.

[Camotoy]

I'm asking to see if we can close this issue.

[OatmealOnToast]

It has not been resolved. Indeed, the server was able to start while using Floodgate, but without it the server still crashes on startup using the latest Geyser Fabric build (#64): https://mclo.gs/evFBuA2

The issue was marked "closed" before in error, sorry about that.

[TheLukeGuy]

It looks like, for whatever reason, the CI build isn't using the unshaded JAR file of core like it should be, so the "problematic" dependencies are still included in the Geyser-Fabric JAR. But when I run ./gradlew build in a new VM, it behaves correctly and uses the unshaded JAR. Strange.

[Konicai]

https://repo.opencollab.dev/main/org/geysermc/geyser/core/2.1.0-SNAPSHOT/ This seems kinda odd...

15 and lower have sources.jar only 15 has unshaded.jar 16 doesn't have sources.jar nor unshaded.jar

[MartijnMuijsers]

Same issue, and I can't build with Geyser as a dependency due to missing -unshaded.jar

[TheLukeGuy]

I've been trying to figure that out as well... it's causing Geyser-Fabric builds to fail:

* What went wrong:
Could not determine the dependencies of task ':shadowJar'.
> Could not resolve all files for configuration ':shadow'.
   > Could not find core-2.1.0-SNAPSHOT-unshaded.jar (org.geysermc.geyser:core:2.1.0-SNAPSHOT:20221003.144245-16).
     Searched in the following locations:
         https://repo.opencollab.dev/maven-snapshots/org/geysermc/geyser/core/2.1.0-SNAPSHOT/core-2.1.0-20221003.144245-16-unshaded.jar

14 and lower shouldn't have anything besides sources, but the discrepancy between 15 and 16 is weird. Jenkins shows all of the correct artifacts, so I'm not sure why they're inconsistent like that in the actual Maven repo.

[Konicai]

Seems like it was alright and now things are weird again with 19. This is mirrored in the api module, too

[MartijnMuijsers]

I fixed my build process with the comical solution of directly referencing the shaded JAR from the artifacts by its URL.

I'm not looking into it further right now, but it's also weird by the way how the API artifacts appear twice.