Animefan8888

Which must never be instantiated into an instance.

Don't you mean 33?

If it is on anything 1.8 or lower then we do not support it.

No clue. But maybe the normal minecraft forums do.

1.7.10 is not supported on these forums any more please update to receive assistance.

Use ForgeRegistries.ITEMS.getValue

I'm not sure what you mean by this. Is anything drawing on your screen? Are you sure your x y positions for the drawing are correct?

Considering the changes between 1.12 and 1.13 were big I would assume that what the developers are doing is re-writing for 1.13.0 and then before the release will switch to 1.13.1 fix all the minor changes there and then release. Though it might not be 1.13.1 but 1.13.2 or whatever the most recent release is at the time.

Subscribe to the RenderPlayerEvent.Pre cancel it and render your own model.

Anything below 1.9 is not supported on this forum any more. Update to receive assistance. Soon 1.9 won't be supported either so you should update to 1.12.2

My best guess is that your problem comes from SmoothWaterCore.

Removed.

@InternalCow You never register an instance of LunariumHelmet

Sorry I was off a line. It seems like your lunarium_helmet is null. Are you sure you registered an instance that has that registry name.

Of course it does the error is saying that your lunarium_sword field is null. Are you actually registering an instance of LunariumSword?

I believe if you are using @ObjectHolder the fields need to be public static final and equal to null. And the string passed into the annotations needs to match the registry name of the object. Also it seems that it is erroring on your Lunarium Sword because the field is null.

What are you trying to do, not how you want to do it?

Try updating your iron chest mod, and then your forge download. To the most recent version.

The list there, doesn't contain any of the mobs and that was the authors problem. If you know where things such as EntityZombie or EntitySkeleton gain these values that is more of what they where looking for.

It probably has built in numbers deeper into the code specifically for all EntityMobs.

Try a smaller value for the second parameter like 2. IE mimicing the EntityPlayerMP value.

It is one of the coremods that you have. The last part of that message says not to contact forge, here you are contacting forge. Forge didn't make the code that is causing the problem. A coremod injects code into vanilla code to change functionality which can very easily cause problems.

The last part of that message in the quote. By the way I am quoting your crash report there.

Typically I just check the file locations, net.minecraftforge.client.event, net.minecraftforge.event, net.minecraftforge.fml.client.event, net.minecraftforge.fml.common.event, or net.minecraftforge.fml.common.gameevent. Note fml.common.event are the mod life-cycle events.