ChampionAsh5357

Please provide the entire debug.log from the logs folder. Additionally, what version are you on?

Hmm, well those are both considered negative directions in the source code; however, I don't know why that would have a bearing since they are both squared when checking the distance. My guess is that it would have to do with how the targeting and stopping system works since if the block position is used, positions that are north and west would be slightly farther away than those south or east since the positions are in the corners. Though, since this doesn't happen in vanilla, I'm still relatively confused on whether that could be the correct answer.

Looking at the log, there's nothing that really suggests what is happening. So, you'll probably need to remove mods until you find out which one is causing the issue. The simplest way would be to separate the mods into mods that you absolutely want and ones that you don't. Then, just test the setting with the preview until you find the incompatible mod.

I don't know how curseforge stores its file data, but provide the one for the mod profile in question.

I think we need a profile of when the server was being held up by the leak since the profile you sent doesn't really contain anything out of the ordinary, at least from my view.

Remove OptiFine, it is currently not compatible with Forge.

You can set the RenderShape to ENTITYBLOCK_ANIMATED via #getRenderShape. If you want the original model to render occasionally, you can change it via the block state. You need to translate it to the center and then translate it back. If you want to understand what's going, I suggest rotating the model every 4 or 5 ticks so you can see where the center point is located. Rotation not around the origin point constitutes translating the model to the origin, rotating, then translating back to the original position.

What do you have right now? What don't you specifically understand?

Remove OptiFine and try again.

Use Java 17, not Java 19. There are numerous mods which don't work with versions that are not the version Minecraft uses.

Is this for WorldEdit? If so, you should probably ask wherever they provide support.

Please provide proof with the 1.18 or 1.19 versions. This forum does not support 1.16 anymore.

In order to root out one of the more common issues, we'll need to see your hosts file. Here's the steps to getting this file. 1) Press the Win + R key on your keyboard. 2) Paste the following into the prompt that opens: 'notepad %windir%\system32\drivers\etc\hosts' 3) Use Ctrl+A to select everything in the file, then Ctrl+C into the textbox to post to this thread.

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).

Definitely not. But otherwise: 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).

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).

OptiFine currently does not support Forge 1.19.3. I would use more compatible mods anyways (rubidium, oculus, etc.).

We are not CurseForge, ask wherever they provide support (they do have a discord iirc).

Please provide the relevant classes or a repo containing the information. My best guess would probably be you don't have an item model without it.

Well, the error says there's a duplicate element in some location the code is pulling from, so you could go and find the associated location in the nbt file to solve the issue. Though, I think it would be better to provide the debug.log to mekanism as an issue since this seems like a bug on their end or a compatibility problem.

Typically the game directory is your .minecraft folder.

That most likely means that the data on the server is not being synced to the client properly. You'll probably need to override #getShareTag to send the capability data. Additionally, you probably should make sure the stack doesn't have the items stored in two different locations.

Generally, this would be the responsibility of the world carver, but there are ways to get around it. You could do something where you check if the entire placement area is within blocks and the opening to the cave is touching some other air block. In general though, you would need to program most of your logic from scratch since I don't believe Minecraft does anything like this itself. The closest I can recommend as an example would probably be the GeodeFeature, though I don't think that's gonna get you anywhere to close to what you would need.

If you haven't been testing with a new world each time, I would recommend doing so. Otherwise, it seems like there is a bunch of mod compatibility issues (e.g. waila, etc.) with some classes in certain mods not being found or located. You should also make sure there are no client-only mods on the server as well.

There seems to be a crash with flywheel and something else; could be mod or with your graphics drivers since I'm pretty sure there are some newer versions of the AMD drivers that do not work properly with Forge and mods.