warjort

You have a large number of mods that were written for the 1.19 beta, that won't work the recommended/stable release. Search for "Failed to create mod instance" in your log and look at the mod ids. Check you have the latest versions of these mods, if you do, contact the mod author(s).

Its an optifine issue: https://github.com/sp614x/optifine/issues/6974

This error message means you have mods that are conflicting in the way they are changing world gen. Unfortunately, your error message only identifies one of the mods - byg. This issue for byg: https://github.com/AOCAWOL/BYG/issues/801 suggests the other problem mod might be terrablender?

Click on your link. See where it says "all" - click on it and it will change to "flat". Now click the arrow next to "Server Thread 100%" at the bottom. You will get something like the following: This says your server thread is spending ~84% of its time ticking entities. Now click where it says "flat" and it should change to "sources". You should see something like the following: So at least 34% is in alexmobs and dungeonmobs. It will be more than this, since it is only counting where it is actually inside their code. It does not include time spent by Minecraft handling the entity before it calls their code. Things you can do include: * Look at the mods documentation and talk to the mod author about optimisation these mods, e.g. changing mob caps to spawn less mobs * Change the "simulation-distance" in server.properties so that the server can stop ticking mobs when they are closer to the player, the default is 10 chunks

Just continue this one, unless it is for a different install. You also need to post your logs/debug.log - just posting the crash report will not always give all the information needed to identify the problem (usually it does not). It is likely your new problem is the same as the original one, but for a different mod? Make sure the mods you downloaded have been confirmed to work on 1.19 by the mod author and are not for some other version. Look at the "Game Version" for your mod files on curseforge.

You are trying to use security craft for 1.19.1/1.19.2 with minecraft 1.19 There are different files for these versions (See Game Version or the prefix in the file name): https://www.curseforge.com/minecraft/mc-mods/security-craft/files

I don't see any problem with JEI. I do see you trying to use JEI for 1.18.2 and trying to use 1.18.2 minecraft methods while you have specified minecraft 1.18.1 in your build. Changing it to use 1.18.2 and net.minecraftforge:forge:1.18.2-40.1.0 allows me to compile and run the game with JEI available. You do have errors in your assets/data json files.

Mob.getMeleeAttackRangeSqr()

It looks like it is trying to run 41.1.0 from the 43.0.2 loader. My guess is you haven't run the gradle task to update the intellj run configs?

Maybe you have a class called ResourceLocation that is not the minecraft class?

The only recommended build is for 1.19 https://files.minecraftforge.net/net/minecraftforge/forge/index_1.19.html The builds for 1.19.1 and 1.19.2 are still beta - they don't have a recommended/stable build (yet). The "experimental settings" warning means you have a mod that is using the datapack mechanism to change world generation. Mojang regard this feature as experimental (even in vanilla).

The code you posted is the not the code getting used. With the code you posted, you would get "genesis:textures/gui/inventory.png"

Issue with "roots classic" contact the mod author.

Issue with valhelsia_core check you have the latest version the contact the mod author.

The "minecraft comes alive" mod is attempting to load client classes on the server. Check you have the latest version then contact the mod author.

Your problem is the electrified mod using an invalid ResourceLocation Check you have the latest version then contact the mod author.

Subscribe to the FurnaceFuelBurnTimeEvent You can find information about events (along with other information) here: https://forge.gemwire.uk/wiki/Main_Page For your own items override getBurnTime() in your Item class.

You are correct there is no direct equivalent in 1.18 There is the BlockEvent.EntityPlaceEvent, but this is for players, dispensers, endermen, etc. placing blocks. It does not get used for worldgen. If you just want to change the drops of a block, you can use a GlobalLootModifier. https://forge.gemwire.uk/wiki/Dynamic_Loot_Modification/1.18 You would need to write your own LootItemCondition to do your y position check. One example that changes loot conditions using a BlockPos is the vanilla LocationCheck If you want to change the world gen blocks, then you are going to need to understand how modern worldgen works. For ores this is OreFeaure/OreConfiguration/OrePlacement To override vanilla configuration you can use the vanilla datapacks mechanism (every mod is a datapack) But personally I think mods overriding vanilla configurations by default is a bad idea, because it leads to conflicts when other mods try to do the same thing. You would probably be better off adding new ore definitions for your blocks and then using the BiomeLoadingEvent to add them to the relevant biomes.

No the file name has to match the tag name. src/main/resources/data/minecraft/tags/blocks/mineable/pickaxe.json In general data/<tag-namespace>/tags/blocks/<tag-location>.json The contents are your blocks you want to be mined with pickaxes, e.g.: https://github.com/BluSunrize/ImmersiveEngineering/blob/1.18.2/src/generated/resources/data/minecraft/tags/blocks/mineable/pickaxe.json The above IE file is created using data gen so it is in a src/generated instead of src/main, otherwise it is the same.

I did not say it was the "Pollution of the Realms" mod. I said I did not know which mod is the problem. All I said was that mod was trying to spread a fluid, so it could be the cause and that you should check with the mod author. You still have the same error message. Except now it is a different mod trying to do a block update that. Again it might not be tinker's constuct. The error message does not say which mod has the problem fluid. But again check you have the latest version and contact the mod author to see if it has a problem. Another clue might be this: which says the immersive_weathering mod is modifying how the LiquidBlock works. So this might also be the problem mod? Without a a definitive error that says which mod has the problem, you are going to have to experiment with removing mods until you find the problem one. Make sure you have a backup of your world before doing this.

The way to do it is the way I said. What you call "code" is a command a player with cheats enabled can type into the chat window. It does something similar.

You downgraded forge to the beta, 41.0.93. Now you have a lot of mods that don't work with that version. Including some that need the stable release you had before. The actual fix your issue is in forge 42.0.2: https://maven.minecraftforge.net/net/minecraftforge/forge/1.19.1-42.0.9/forge-1.19.1-42.0.9-changelog.txt

You will have to ask curseforge: https://support.curseforge.com/en/support/home

It looks like you are using curseforge. Click on the settings button in the bottom left of its screen, then click on minecraft. In the "Java Settings" there is a slider for "Allocated Memory".