Mod Version: 1.19.2

Mod Loader: forge

Description:
My server crash when i launch it

To Reproduce:
Steps to reproduce the behavior:
Launch the server

Screenshots:

Additional context:

could you try reproducing this crash with only deeper darker? if not, it is most likely another mod.

Adding here - getting the same issue on my server.
This is NOT the other mods issue. This is the way how snakeyaml lib is packaged. From what I have read, this is most likely related to the use of much newer version of the library comparing to what the majority of mods are using for version 1.19.2. Or it is related to the way of packaging (possibly, try to exclude the lib, it is already included in the Forge).

So, to understand the problem: there is a lib version loading collision in here. I'm getting this error for different library or mod every time I start the server. Sometimes I get it like this:

java.lang.module.ResolutionException: Module org.lz4.pure.java reads more than one module named org.yaml.snakeyaml
at java.base/java.lang.module.Resolver.resolveFail(Resolver.java:901)
at java.base/java.lang.module.Resolver.checkExportSuppliers(Resolver.java:722)
at java.base/java.lang.module.Resolver.finish(Resolver.java:380)
at java.base/java.lang.module.Configuration.<init>(Configuration.java:140)
at java.base/java.lang.module.Configuration.resolveAndBind(Configuration.java:494)
at MC-BOOTSTRAP/[email protected]/cpw.mods.modlauncher.ModuleLayerHandler.buildLayer(Mod

And sometimes like this:

java.lang.module.ResolutionException: Module forge reads more than one module named org.yaml.snakeyaml
at java.base/java.lang.module.Resolver.resolveFail(Resolver.java:901)
at java.base/java.lang.module.Resolver.checkExportSuppliers(Resolver.java:722)
at java.base/java.lang.module.Resolver.finish(Resolver.java:380)
at java.base/java.lang.module.Configuration.<init>(Configuration.java:140)
at java.base/java.lang.module.Configuration.resolveAndBind(Configuration.java:494)

I have tried different versions of DeeperAndDarker mod for 1.19.2, and version 1.1.3 of the MOD worked for me. 1.1.6 did not.

Please, fix.

hmm i've never seen this error before

i am also unable to reproduce it, but maybe this issue has been fixed in dev. i'd say wait until the next update of deeper darker to see if the error still persists