LexManos

We do not provide support here for a version that is several years out of date.

Update to 1.9.4+

Show your log, your setup is really messed up.

Use 2002

Write a real mod.

1) We do not support Optifine, if you install it go to them for support 2) Read the rules, "Forge 1.10" means nothing to us you need to tell us specific versions, this is why we state int the EAQS and on the top of the forums that we need your log files.

You waited a grand total of 50 seconds before posting bitching that people need to help you... Seriously, stop being a cunt. YOU are the one who breaking your mod install by not installing the mod correctly. Seriously, JUST PUT THE FILE IN THE MODS FOLDER. STOP EXTRACTING IT. The Error message literally says whats wrong..

Explain better what you're talking about. What steps are you doing to reproduce. What are you expecting to happen. What is happening?

Fixed in next build, seems some logic changed. Updated forge to reflect.

You have something besides forge installed, and its for the wrong MC version, AND it's a coremod/tweaker/jar mod. AND you're on 1.7.10, seriously dude you should update, so much cooler content and better performance, also you'll actually get support here if you update.

Don't click the loading screen, some windows versions hate the threaded way we do it. Does it actually freeze without you doing anything, or is the progress bar still going?

Post your full logs, or what ever you're seeing that makes you think you're crashing...

You should really mod for 1.9+

Thought we removed that flag in 1.8, as it was literally only there to keep backward compatibility with mods when we introduced the feature in 1.7 Oh well

Alright so heres the deal, i've got your exact version exact launcher everything and I can't reproduce the error. SOMETHING is causing it on your end. However, In the process of tracking this down I did find that MIGHT cause a similar issue IF something bypasses some features we have in Forge. So as it sits, i'll push a potential fix and we'll see if it works for you.

There is no crash there.

Due to a licensing issue some PRs had to be rolled back this is one of them. I'll be deleting the builds for 1.9.4 that were done on the 1.10.0 branch later tonight for now, it's suggested the modder updates or you revert.

Update to 1.9+

Is been fixed, just a small patch shift in the update.

It's been fixed, jsut a slight patch shift in the update.

[08:01:00] [Client thread/WARN]: Texture minecraft:textures/white.png with size 0x0 limits mip level from 4 to -1 That would do it, something is screwed with your texture... We create a generic white 16x16 texture here in code: https://github.com/MinecraftForge/MinecraftForge/blob/92914f82ae1e2ca007bdb9629611d120a4c58fe2/src/main/java/net/minecraftforge/client/model/ModelLoader.java#L865 It shouldn't be an issue. Unless you have a mod in your system that is screwing with rendering.

Just like EVERY fucking update we've ever done. We'll most likely finalize 1.9.4 with one final RB after we finish 1.10 and make it master.

That's not how subclasses and overrides work. Not trying to be insulting but this is a obvious case where you need to go learn some of the basics of java {or any programming} There are plenty of free resources such as MIT classes, Standord has some, and TONS of online tutorials. Going to lock this as there isn't anything more we can do to help you besides advise that you learn a bit more.

Umm, that's a standard java thing it means that the error, and the cause of the error share the same stack at that frame. So no need to display it again because it'll be displayed in the cause stack trace. Google jar signing. It's a method of signing the class files so that people can verify that they are from YOU and have not been modified by someone else. There is a SHIT ton different seriously do you know basic java? Your mod class is an entity what the hell!?! You're not gunna be able to do this right now.

Same Answer