ChampionAsh5357

The version you are using is no longer supported on this forum. Please update to a modern version of Minecraft to receive support. Currently supported versions are 1.19.3 (Latest), 1.19.2, and 1.18.2 (LTS).

Please provide the entire crash report provided by gradle. This does not tell us anything. Did you make sure to add curse maven to the repositories or as a plugin (i think that's what it is).

Did you use the default mdk and only modified the parts you needed to? It should solve that issue. If you didn't modify the default mdk, generated should have come up as a separate sourceset. If that's the case, there's nothing to worry about. There's nothing really to worry about if it didn't anyways since the directory doesn't need to be a sourceset.

In FMLCommonSetupEvent within the deferred work queue (#enqueueWork).

Hmm, try removing terrablender and see if that fixes the issue.

You can try splitting the mods into two piles. If one pile doesn't work, you know they contain the duplicate mods. If both piles work, it means you split the duplicate mods. You can keep splitting the erroring pile until you find the mod conflicts.

Hmm, well you can try going into your machine or router and disable ipv6 traffic in both directions and see if that fixes your issue. You're going to need to google how to do this on your own machine. Nothing else really stands out to me.

I would suggest reading the mixin docs since they explain that you need to remap the refmap file if you are depending on a mod which has a mixin.

It probably needs to be enabled with your launcher settings then. I remember the CurseForge launcher having a similar thing. However, the most I can see is that the server cannot be reached from your computer. Do you want to try pinging the server manually through a terminal and see if your machine gets a response back?

I mean, this is not how you add a model. You register the layer definition to get the baked layer via EntityRenderersEvent$RegisterLayerDefinitions#registerLayerDefinition, then, construct the model only once using the EntityModelSet. You can construct the model during EntityRenderersEvent$AddLayers which contains the associated model set. You can roughly follow giga's gist on this.

More or less. It would be better if you could store all the blocks you want to outline once so that you can just loop through that list. You may also want to take a look at the GameRenderer to see how block outlining is done when the player hovers over it and just modify the depth test.

Not really, you would essentially need to modify all the nbt files to remove any trace of the mods. Minecraft does not make any guarantee that removing a pack within a world will not mess up your save.

Try removing spelunkerscharm. It seems to be causing the issue.

Please provide the debug.log from the logs folder in your game directory.

What does the method accept, and how can you get it from the registry object?

I saw, but the issue is that everything looks correct since it seems the memory leak was either caused after a certain point in time or was from some action. So unless you could profile the exact moment when the game starts to slow down, you may just have to remove mods and see whether the crash still occurs.

Could you please provide the debug.log from the logs folder on your client rather than the server?

This is indicating that you most likely have a duplicate mod or a mod with the same mod id in your mods folder.

Try deleting all your config files and restarting the game.

I'm confused, this is indicating the server has started. The only issue is that some client side mod is causing this error.

There are likely duplicate mods or mods with the same mod id in your mods directory.

Use the GuiComponent methods. There should be one for drawing a rectangle and one for drawing textures.

You should have access within the structure to some form of the level that allows you to read the blocks in the area. As for checking the entire area, it depends on how much you want to check or optimize. In general, you could probably get away with only checking the borders. If you really don't care how much spawns outside a mountain, you just need to check the corners.

I would suggest looking at the Minecart, AbstractHorse, Boat, etc. and see how it is implemented there.

The version you are using is no longer supported on this forum. Please update to a modern version of Minecraft to receive support. Currently supported versions are 1.19.3 (Latest), 1.19.2, and 1.18.2 (LTS).