warjort

If you know which mods are causing the problem, check you have the latest versions then contact the mod authors.

Looks like something related to project mmo is missing. Probably you have the wrong version?

You can't have both jei and rei.

I already answered your question on the other post: https://forums.minecraftforge.net/topic/122683-game-crashed-while-exploring/#comment-533925

Not really. AFAIK, the normal blocks can only use the hardcoded RenderTypes known to the Chunk builder code. See RenderType.CHUNK_BUFFER_LAYERS. Obviously there is overhead in BlockEntitys over normal Blocks. They use more memory because they can have custom state. And more cpu if they also tick. In your usecase, using a custom renderer will have worse performance than using a static model, because minecraft won't be able to cache as much information. That is somewhat mitigated in the example code above since it mostly just delegates to static (prebaked) model rendering code.

This is a duplicate post.

Check you have the latest version then contact the mod author.

https://forums.minecraftforge.net/topic/117560-solved-blockentity-rendering-too-dark/#comment-517765

But I bet you are eventually going to find you have another mod breaking something in the Entity class hierarchy. This is essentially the error as you got for creeper overhaul. You would probably save some time if you just uploaded your debug.log to a file sharing site so we have all the information and/or installed your mods individually or in small groups so you know which mods are breaking the game without having to ask us.

That's not true, the source code is here: https://github.com/MinecraftForge/MinecraftForge/tree/1.7.10 But it refers to the old (now defunct) maven repository: https://github.com/MinecraftForge/MinecraftForge/blob/9274e4fe435cb415099a8216c1b42235f185443e/build.gradle#L7 so I doubt it will build without changes. If you are looking for help with 1.7.10 you should ask those that still use it, e.g. the GTNH project which also updates/fixes mods for that version.

The crash is indeed with Creeper Overhaul. But what is going on with that crash report? spongepovered instead of spongepowered HixinInfo, AixinProcessor, NixinTransformer instead of Mixin* Very suspicious.

So? That doesn't mean the rest of the code does anything useful. Your super call just marks the part entity as hurt which means it will flash red. But it doesn't have any health to actually damage. Why not? "It does not work" is not a bug report. That's what I said is your problem. What code? If you looked a the code in a debugger you can step through it and see what is being called and what conditional statement stops it reaching the code you expect. All in all, your "question" is unanswerable. It is full of undefined "it/that/the"s. Finally, when I went back to look at the code you posted to see if I could guess what you are talking about, I noticed this: That will crash at runtime because uppercase characters are not allowed in ResourceLocations. So that class you posted cannot possibly be code that is actually getting used.

https://github.com/SuperMartijn642/Rechiseled/issues/25

The problem with doing what you are trying to do is discussed here: https://github.com/MinecraftForge/MinecraftForge/pull/8744

The issue is with you calling getCapability() from inside the AttachCapabilities. That sends it into recursive death.

Check you have the latest version then contact the mod author.

I am no expert on the SoundManager, but I don't believe the sound manager has any general support to monitor for when something stops playing. But, if you are just interested in music disks. You might be able to listen for GameEvent.JUKEBOX_STOP_PLAYING using this? https://github.com/MinecraftForge/MinecraftForge/blob/1.19.x/src/main/java/net/minecraftforge/event/VanillaGameEvent.java That and the start playing event, is what the Allays use to know when they should dance.

The getObject() associated the Entity might be an ItemEntity, it will never be an ItemStack.

The error appears to be at this line of code: https://github.com/MinecraftForge/EventBus/blob/84663719be842aedaddabf9cd8d46a2450959c9d/src/main/java/net/minecraftforge/eventbus/EventBus.java#L329 Where it is trying to use a lambda expression to create a log4j MessageSupplier and for some reason this is causing the linkage error? The actual error is not very informative about why there is a linkage error. I don't see any mention of log4j in your build so it doesn't look like you are downloading a conflicting version? Or any other dependency that might transitively do that. If you run the gradle build with --debug in amongst all the other rubbish, you should be able to see the command line used to start minecraft. This should say where it is getting log4j from and whether there might be more than one on the classpath or something. I assume you are actually using the gradle build and not some IDE launch configuration? Obviously, your attach capabilities is throwing an error for it to reach that error handler. But then it crashes trying to report the error. I tried deliberately, throwing an exception from a similar event handler and I don't see any problem with reporting the error. Beyond that, you are going to need to put your project on github to see if we can reproduce the problem using it.

That's not the 1.19.4 version of wthit: https://www.curseforge.com/minecraft/mc-mods/wthit-forge/files

The class that gives the error: org.apache.logging.log4j.util.MessageSupplier e.g. compile over version 1 public class ClassFromLibrary implements A {} public class MyClass extends ClassFromLibrary {} runtime is over version 2 public class ClassFromLibrary implements B {} // ClassFromLibrary no longer implements A which breaks MyClass As I said above, it could also be a classloading issue where runtime is still over A but from different classloaders. public class ClassFromLibrary { public void consume(A a) {} // A from classloader1 } public class MyClass implements A {} // A from classloader2 new ClassFromLibrary().consume(new MyClass()); // Error not the same A Linkage errors are usually a bit more subtle than the examples above. But, since you don't show the full error, debug.log, your build file or any other way for me to see what is really going on, I can only give you a general explanation of the error under the assumption that it is enough for you to debug the problem for yourself. As I have said many times in this forum. If you want help, you need to provide all the information. Not code snippets out of context or truncated error messages. Otherwise unless the problem is immediately obvious, you will likely just get ignored. Something I almost did with your original question since it is a java question not a forge question anyway.

It isn't necessarily create related. All I can tell you is something has broken recipe (de)serialization logic, that is messing up the transfer of recipes from the server to the client. Without an error identifying the mod, the only way you will find it is to experiment with removing mods until the problem goes away. Backup your world(s) before removing mods.

That narrows it down to something with a broken RecipeSerializer, but does not identify the mod. There are warnings just before where create is complaining about broken recipes from "createchromaticreturn" maybe the 2 are related?