warjort

To check if it is your damage type you would probably use damageSource.is(resourceKey) where resourceKey is the ResourceKey to the damage type. It looks like you can now also use tags to group and check damage types.

The DamageSources are now made from DamageTypes that are part of datapacks See "DAMAGE TYPES" here: https://www.minecraft.net/en-us/article/minecraft-java-edition-1-19-4 That means they can only be created when you are loaded into the world. Because the game needs MinecraftServer.registryAccess() to lookup the DamageType from the data packs. This is not something I have done myself. But here's an example from BOP. With a its "bramble" DamageType https://github.com/Glitchfiend/BiomesOPlenty/blob/BOP-1.19.4-17.3.x/src/generated/resources/data/biomesoplenty/damage_type/bramble.json And here is where it applies the damage using the ResourceKey of that damage type: https://github.com/Glitchfiend/BiomesOPlenty/blob/551bff467ade42cb2a0b23609f439137ca7fa60f/src/main/java/biomesoplenty/common/block/BrambleBlock.java#L67

You have a mod trying to load client classes on the server. The error message does not say which mod. I can see oculus mentioned previously which is a client side mod not needed on the server. You probably have others?

Use a mod like https://www.curseforge.com/minecraft/mc-mods/spark to diagnose what is taking time on the server thread.

Issue with the flywheel mod. Check you have the latest version then contact the mod author.

Contact the vivecraft mod author for vivecraft problems. These are the forge support forums. We can't fix vivecraft. Only the mod author can do that.

I am not going to write your code for you. If you are incapable of using your IDE to read and understand the vanilla code, here are 500+ other modders on github who already worked out how to do it. https://github.com/search?l=Java&q=getAverageFoliageColor&type=Code You should be able to find something that is close to what you want to do.

That's not a forge issue. It a gradle issue. Something is wrong with your build.gradle.kts or your gradle installation/cache which means it cannot find/download that jar Since you don't post that file it's impossible to say. And using the gradle support forums is more likely to get you better help anyway.

You need to posta link to your logs/debug.log and/or the crash report.

That's a link to the gist website in general, not your file.

Issue with the betterweather mod, check you have the latest version then contact the mod author.

As I said above, look at how the BlockColors class uses it for vanilla leaves.

Looks like some issue with Mekanism's MekaSuit. Check you have the latest version then contact the mod authors.

The issue is with vivecraft trying to apply a mixin into the minecraft options. The error doesn't say what is conflicting. That version of optifine is not the latest version recommended by them for your version of forge, see their download page.

Use java 17, mixin does not support java 20

https://forge.gemwire.uk/wiki/Tinted_Textures For leaves you will want to use BiomeColors.getAverageFoliageColor() and FoliageColor.getDefaultColor(), see the BlockColors class for the vanilla implementation.

The purpose of this forum is to answer questions about forge/minecraft. It's not here to give you free code reviews. Or to let you proxy the work of debugging your mod to us. Since the question looks like a trivial logic error, I will answer it. But in future your question should be about forge or minecraft, NOT your code. Otherwise, expect to just have your question ignored as off topic. Here you don't enter the loop that calls that method if spawnCustomParticles() returns false which is the default https://github.com/BluMasc/slimed/blob/e785fd4324a1559e220cb2cc4b8f55d60038053b/src/main/java/de/blumasc/slimed/entity/BaseSlime.java#L130 Your "broken" mob doesn't override that method so it too will return false and not spawn particles. https://github.com/BluMasc/slimed/blob/master/src/main/java/de/blumasc/slimed/entity/LovelySlime.java

If it doesn't crash for you, but does for them, then there is clearly something wrong with their installation. The error message is uninformative, it just says "NullPointerException" so we can tell what is causing the issue from that. Get them to do a full reinstall of forge and the modpack from scratch. So you know for sure they are using what you think they should be using. Also tell them not to install any additional/optional client side mods like optifine. Those are always the first candidates for strange bugs.

Please don't post logs in the forum use a file upload site. They are impossible to read/search in the forums, especially when there is more than 1 on a topic. I don't see an error in what you posted. The last thing in the log is some informational message from alexsmobs. If that really is the whole log and not just trunctated by the forum, post a link to your launcher_log.txt

It's likely only your friend can see the block in question. Try teleporting to your friend's location and see if you crash. The problem block appears to be at:

Some issue with divinerpg entity drops. Check you have the latest version then contact the mod author.

Use java 17. Mixin does not support 19 or 20

Install the latest preview release of optifine.

https://github.com/MinecraftForge/MinecraftForge/issues/9311