LexManos

I've highlighted the OBVIOUS issue with your post. Anyways, We are not 'ModLoader' we are Forge, ModLoader is outdated, complicated, and not useful anymore.

Make sure you load it atleast once using the latest 1.6.4 Forge then update it to 1.7. If not you can try submitting the world for me to look at so that I can try and see if anything is wrong on our end.

No.

Unlocalized name has NOTHING to do with registry name. STOP USING IT THAT WAY. It breaks everything.

No The command you use to start the server 'java -jar whatever.jar' you add that to the command. This sets a environment variable that FML reads and follows.

The answer is straight forward, use the mojang launcher, and load 1.8 minecraft. It's right there in the error message.

Why not just use your own packets wrapping around the same code instead of hacking ASM like that.. seems like a better idea..

It seems like whatever ISP you have is having issues navigating from canada to ovh. I've told Overmind to take a look but as it's dieing in the middle somewhere we have no control over, there isn't much I can do.

https://github.com/SpigotMC/BungeeCord/issues/1277#issuecomment-67766243

They are sorted alphabetically by file name, no clue what you mean by extracted or anything like that.... Give logs and directory listings.

Problem with BungeeCord, nothing I can do about it, contact the server admins.

Your network is borked. Do a trace, see where its dieing.

or, you could use the hooks that are in place for rendering the hud and do the same thing it does for rendering pictures.

Start with only one mod in the folder and see what happens. Then add another, and so forth until things break. Forge loads mods, nothing in this reguard has changed in a year.

Nothing we can really do on our end the server is up and running. Check your network and see where it is dieing.

NEI is broken, complain to ChickenBones.

"being a regular Eclipse user I proceeded to remove one of the Jars that was creating an error" How is that a 'standard solution'... No... Re-run the eclipse task and reload eclipse.

The 'old launcher' and the 'new launcher' ARE THE EXACT SAME THING. The 'new launcher' is just a native wrapper around the old one to automate installing java for you. The answer is in the EAQs either use 1.7.10+ or use the fix. If you claim to have errors on 1.7.10+ POST THE LOG FILES so we can see them.

This falls under the 'I want my old stuff because change is scarry' category so.. no. Please pay attention to what is going on in Forge, and the active PRs, notably RainWarrior's for more information.

You need to install 'cslib', any version will do apparently.

Remove optifine.

you have 1.7 stuff installed on 1.8...

User was banned for using a cracked launcher.

Interesting, I'll put that into the bank: "Is encountering _JAVA_OPTIONS issue disable Razer Synapse"

That is interesting. Something somewhere is setting the variable. You could try running the launcher manually from the command line after setting the _JAVA_OPTIONs to something empty/better.