LexManos

Also you need a internet connection for the install to work.

Side not why are you writing this for 1.7.10-?

You don't have to change all the settings, just enabled, that being false disables the entire thing. As for whats wrong, a few drivers don't like multi-threaded graphics access. And just dies instead of throwing something useful we can catch and recover from. The loading screen is optional, and is just a nice progress screen instead of a blank window. It's not needed, so disabling it is fine if you have issues. Also, don't necro old threads.

We don't write those mods.. we can't update them.. talk to the author..

You installed a 1.7.10- coremod in 1.11.2, remove them from your mods folder and try again.

And update to at least 1.8.9 there is literally no reason to not be on 1.8.9 as 1.8 mods are compatible with 1.8.9 with very little work if any by the modder.

"Can not perform the specified operation on a file whose user-mapped section open " Some other process on their system has the file held open. This is bad, and most likely a anti-virus or something. HOWEVER Stop using 1.7.10, if you do use it as per the forums rules you're on your own for solving any issues that arise. If you're making a mod pack just freaking update the pack -.-

We will not help you make backdoors into your own mods.

Why? Dont skip over this question like you did twice. Mods shouldn't be phoning home or anything to need users information.

Its float[] https://docs.oracle.com/javase/specs/jvms/se7/html/jvms-4.html#jvms-4.3.2 Float[] != float[]

its not the same problem so it would not be the same fix. I've just tested 1.10.2 and it works just fine. You have something else wrong in your installation.

No, translations are uppercase in 1.10, so this fix is not needed.

Vanilla only supports vanilla english translations. Obviously it'd be our job to inject modder's english translations. This was area that cpw had written and I didn't know how it was implemented until about 5 mins ago. 1.11 forced lcasing, sorta {big PITA}, hence the simple fix.

Nothing is being used 'wrong' Just a area we missed when doing 1.11''s update: https://github.com/MinecraftForge/MinecraftForge/commit/7c9b67b574836729dd73f04fd49d800a67dd121f Should fix it.

https://github.com/MinecraftForge/MinecraftForge/commit/6ae39ac027146edc9a73d0b22412ee87ec82a9e1

Update your server. 1.7.10 is over 2 years out of date..

Mojang's new launcher changes the way that logs are writen, Dinnerbone has been made aware that it stops Modded logs from showing for some people so it should be fixed.. eventually... A note, 'latest.log' is not useful you want the fml log that has all the information.

1) 2)

No, that's not why your mod pack isn't working, There is nothing in Forge that prevents older versions from working. By not supported it means we will no longer help you with it. If you take it upon yourself to use old versions of Forge/Minecraft then it's on you to fix your own errors.

1) Read the error 2) 1.7.10 isn't actively supported on the forums anymore, you should update.

The 'Forge' profile is just for convenience. You can select any version you want in the profile editing screen. Do that. The install process hasn't changed in ages so you should be able to install both just fine.

Logs

It's a theme issue, Paleo has been notified for the time being the 'fix' is to zoom out, or make your screen wider. It happens because of the way the poster info is written to not force the page down. Once Flame and Paleo get time they will fix it. It's reproducible on ALL systems and ALL browsers just make your window smaller. Anyways my point is WE GET IT! Don't need 30 posts about the same thing!

1) As I said before the icon for the exes is just the default Launch4J icon 2) You *shouldn't* need admin permissions but if your computer has you locked down you might 3) Why are you suddenly switching tot he src/mdk? Yes, the old name for the MDK was src. This is not a bug.

No, the 1.6.4 installers are fine. They still shouldn't require admin access but its a matter of launch4j being a hackish system. If/when we do re-build launcher for older versions we'll do it with our new system that's being developed. But that probably won't be for a while as they currently work fine. The 1.7.10 in your screenshot looks fine as well, thats just the default icon for launch4j.