Ya its much better when you submit full details and a test case we can actually debug it then.
Either way the bug has been fixed. https://github.com/MinecraftForge/MinecraftForge/commit/3e6099055e228dc73a0947047c725a0548809f07
Go get the latest 1.10.2.
The wiki is for archival purposes only at this point.
It will eventually be deleted all together.
It's not worth the effort of maintaining on our end.
If you want to help submit documentation go do it at https://github.com/MinecraftForge/Documentation
Also, coremods are not supported, tell whoever is making your mod to stop coremodding.
We do not go out of our way to help coremods because coremods are inherently bad.
So I highly doubt anything will be backported unless cpw feels like being generous because I sure as hell won't do it.
Not sure who would want to buy your account information.
But you know how a little while ago, you had to do a password recovery on your account before you could log back in to these forums?
Ya, we know.
http://www.minecraftforge.net/forum/index.php/topic,39636.0.html
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..
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?
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.