warjort

Essentials completely reworks the networking of minecraft. You need to ask them.

It's the other way around. the reeses_sodium_options mod wants rubidium. If you are trying to build a modpack with 400 mods, dumping them all in the mods folder and expecting it to work is not the way to do it. Whole teams of experienced modpack developers take weeks to months getting such kitchen sink modpacks to work properly. They do it by building the modpack incrementally, adding mods one at time or in small groups, then testing to make sure each newly added mod doesn't cause problems.

One of your mods is not for minecraft 1.19.3. I think the LeashFenceKnotEntity had the above name in Forge for minecraft 1.16?

Why don't they go well? Mods are datapacks too. You could use a mod like this: https://www.curseforge.com/minecraft/mc-mods/drp-global-datapack or I believe kubejs also adds a folder to be used as a resource/datapack https://wiki.latvian.dev/books/kubejs/page/loading-assets-and-data (old docs) or you could just make your own mod that is little more than whatever worldgen files you want to modify.

You have minecraft 1.19.4, try the 1.19.4 version of that mod: https://www.curseforge.com/minecraft/mc-mods/openblocks-elevator/files

It could also be other worldgen is adding things that are not "ore replaceable", e.g. some other type of stone?

Unless they are actually changing the vanilla ore definitions they won't change the chance to spawn. Except maybe that it will try to spawn and find other ore blocks (which are not "ore replaceable") occupy the spaces instead of stone, deep slate, etc. If you make your own datapack: https://minecraft.fandom.com/wiki/Data_pack you can replace the definitions yourself and change how the veins generate. e.g. how many veins it tries to spawn per chunk: https://github.com/misode/mcmeta/blob/6770559daf160f81f38a8d8a6e1558498efed37f/data/minecraft/worldgen/placed_feature/ore_iron_middle.json#L6 or how large the veins should be: https://github.com/misode/mcmeta/blob/6770559daf160f81f38a8d8a6e1558498efed37f/data/minecraft/worldgen/configured_feature/ore_iron.json#L5

Contact the mod authors to figure out why they conflict.

https://forums.minecraftforge.net/topic/123416-exit-code-1/#comment-536369

There is no error in that log. Post a link to the launcher_log.txt from directly after the crash.

https://github.com/ValhelsiaTeam/Valhelsia-Structures/issues/147 As it says, unless optifine fixes it, you can't have both Valhelsia and Optifine together.

Looks like it is betterpiglintrade, it references the client side class here: https://github.com/Venodez/BetterPiglinTrade/blob/1.19.2/src/main/java/fr/venodez/betterpiglintrade/mixin/MixinPiglinAi.java#L37

That has a bit more information. It likely one of the underlined mods. Check you have the latest versions then contact the mod authors.

No. Forge does nothing with mixins except include the mixin jar in its classpath for mods to use. Mixin hooks into the classloader and decides for itself (based on what mods tell it) if/how it will modify classes.

I don't see any hints near the actual error. There is this much earlier warning Which hints it might be enigmaticlegacy? But it is not conclusive. They are not in the same message. There is also this (again a warning), but it is not for a mixin, so probably not related? There is nothing that says for definite what is the causing the problem.

The you can also contact the modpack author for help as well. From my footer and also the EAQ at the top of the forum.

Then check you have the latest version of that mod and if you already do contact mod author. But the error is with a mixin, so it could be any mod.

And please stop posting logs in the forum. Use a file sharing site.

Something is trying to incorrectly load client classes from a mixin. The error message does not say which mod. The logs/debug.log might have more information?

https://forge.gemwire.uk/wiki/Events#/media/File:Guide_to_Event_Handlers.png

Use java 17

maybe install infinitylib?

That's private - probably awaiting moderation. Search it yourself for the phrase "problematic frame" like on the other thread.

https://forums.minecraftforge.net/topic/123416-exit-code-1/#comment-536369 You need to post a link to the launcher_log.txt from directly after the crash to confirm the error.

Json files (datapacks) is the way you do this. You will find a lot of information about them on the internet. The main community developed documentation I know about are: https://misode.github.io/ and https://minecraft.fandom.com/wiki/Data_pack the second of those is really just a collation of all the minecraft release notes. The first also has the vanilla world gen files: https://github.com/misode/mcmeta/tree/data/data/minecraft/dimension https://github.com/misode/mcmeta/tree/data/data/minecraft/dimension_type https://github.com/misode/mcmeta/tree/data/data/minecraft/worldgen Those json files are just configuration files that create java objects using codecs: https://forge.gemwire.uk/wiki/Codecs either as; * simple values or "records"/collections of them * references to objects created from other json fles * references to objects that are constructed and registered programmatically such as the vanilla provided presets, dimensions, chunk generators, carvers, features, structures, etc. If you want to create flat terrain, I would suggest you start with vanilla's FlatLevelSource and FlatLevelGeneratorPresets and follow the rabbit hole. As for tutorials, even if you find one, it is likely out-of-date. The modern worldgen has been marked as experimental since 1.16. Mojang keep iterating on it without any real constraints of compatiblity across versions - the json file formats are more stable than the code they configure I would suggest you read the vanilla source - net.minecraft.world.level.levelgen.* and net.minecraft.data.worldgen.* or search on github for up-to-date implementations by other mods of the classes you are interested in.