larsgerrits

1.7.10 is no longer supported on this forum.

That is not the FML log... The FML log is located in the logs/fml-client-latest.log inside your game directory.

1.7.10 is no longer supported on this forum.

1.7.10 is no longer supported on this forum.

1.7.10 is no longer supported on this forum.

What version are you even playing?

And next time: make your own thread. This one is almost a year old...

Post the FML logs (logs/fml-client-latest.log).

First of all, update to the latest Forge, especially if it's in beta, as the issue might already be resolved. If it still crashes , post the updated logs.

There was a thread in 2013 about resizing the lightmap to make colored light. Maybe that can help you: Also, you probably have to pass in an instance of the EntityRender to ReflectionHelper#findMethod. The EntityRenderer instance is located in Minecraft#entityRenderer.

Did you try the Block#setBlockUnbreakable method in combination with the Block#canEntityDestroy method?

First of all, Blocks are singletons. You should only ever have 1 instance of each block, and not call new TestBlock() each time you want an instance. Store a single instance in a static field somewhere to reference later. That alone will fix a lot of your issues if not all. Also, Reflection for Block registering? You'd be better of with the RegistryEvents (http://mcforge.readthedocs.io/en/latest/concepts/registries/).

I think some mod is messing with the EntityTracker as there are multiple mods crashing on the same function. Try removing the coremods (yes, including Sponge). Also, did you read the EAQ? It says:

From the top of the page: "Forge for 1.12 is still in early development. Do not use it yet, crashes and bugs are to be expected." Also, post the logs (logs/fml-client-latest.log).

Only download from the official file server (files.minecraftforge.net), never from shady websites.

On the top of the page it says: "Forge for 1.12 is still in early development. Do not use it yet, crashes and bugs are to be expected."

Post the fml-client-latest.log.

Well, as it says, contact their authors before contacting Forge. Try to remove them and see what happens.

That's why you have to post it here, so we can use it.

There's always more than that. Post the FML logs (logs/fml-client-latest.log inside your profile folder).

It is just a normal text file with a different extension, so you can open the file with any text editor.

1.7.10 is no longer supported on this forum. Update if you want help.

Report this to the Optfine author. Optfine is the one who does a lot of shady stuff around Forge.

The first thing to note is that the Minecraft class is @SIdeOnly(Side.CLIENT). This means, you can access the class with a client or a remote server, but not on a dedicated server. Trying to load it in a dedicated server will cause Minecraft to crash with a ClassNotFoundException. So be careful to use this for client-side things only, like rendering. 1) 2 separate instance will have 2 seperate Minecraft classes, and they don't know about each other. So the first instance won't return the Minecraft as the other instance. 2) The Minecraft#player variable is initialized when the world is loaded. I don't think there's an event for that. 3) The Minecraft#world variable is initialized in the same method as the player, so they'll be accessible at the same time. Again, there's no event to catch that.

Post the FML logs (logs/fml-client-latest.log). You might have a mod version incompatible with the Minecraft version.