LexManos

You just moved files around that you shouldn't of, You can delete it. However for your new issue read the EAQs as listed at the top of this forum and disable the loading screen. Before you ask how to do that, it's in the EAQs -.-

Because I do not accept anecdotal 'my stuff is laggy it's all Forge's fault!' Forge is constantly Profiled by many people. None of whom see anything like what you're reporting. All reports always either come with a bunch of mods/coremods installed, or absolutely no real information to go off of. So start providing actual stuff we can act on and I might start caring. VERY basic would be providing a log file from your test runs. Which is why it's part of the EAQs under "READ THIS OR YOU WILL BE BANNED" section. Slightly higher, and more useful, would be to provide some form of profiler run. JVisualVM and JProfiler are both excellent tools for doing this. Again, you guys give us no information to work with, make unsubstantiated claims. We can't do anything without any information. Simple as that.

I have already updated our internal tools to support the last few snapshots, its not that big of a deal. It'll be some work but it shouldn't take to long. Just waiting on 1.12's official drop.

yes, you should never open the jars, just put the jars in the mods folder.

you did

Sorry, I missed one symbol in my response, you are at ~10%. Either way, if you have actual issues report them properly not this. I've answered your original post.

1) We do not support 1.7.10 on this forum 2) If you MUST use 1.7.10 atleast use the latest 1.7.10...

Logs

1) This is a common error the solution is there if you search 2) We no longer give support for 1.7.10 on this forums, update.

We do not support or endorse people bypassing downloading he installer. Sadly this is just how it has to be, as the ads are our sole source of revenue to pay for the servers that run this thing. And trust me they aren't cheap.

Disable the loading screen.

If all server side mods say that they are server side only, or accept the mod missing on the client then Forge will allow it to connect. You have to talk to the mod authors.

THere is a way to specify the modList by command line, it's documented if you just look. Also, as I said in the other thread you necroed, DO NOT MAKE CUSTOM LAUNCHERS. This is THE rule Mojang has, DO NOT have users input their credentials into non-mojang shit.

Don't make custom launcher, use Mojang's. This is like THE strict rule that Mojang has.

This is not so much forge's 'Poor server optimization' More 'Spigots pseudo-optimizations hiding real issues' Forge will never run as 'fast' as Spigot because flat out, Vanilla does more stuff than Spigot does, and Forge does more than Vanilla. Only real way to actually look into anything is with a proper profiler. If you get real numbers/hotspots that others haven't found before you then we can take a look. You also don't actually post your logs so if there WERE issues in it, we have no idea. Edit: Actually watching your videos I have one major thing to note... Jesus christ do you even watch your own videos? you are at ~10 of The guys on TS so I have to listen to his keyboard/smacking down the hall just so I can hear your mouse talk. Please either mute the TS or boost the volume of the important person talking. So those watching can actually hear it.

English only please, And disable the loading screen as described in the EAQs

Just put them in the mods folder, that's it.

Interesting seems you have a corrupt vanilla jar. Delete ./versions/1.11.2/ folder and re-run the launcher.

Update to 1.11.2.

That doesnt fix it, that just stops loading Forge. And don't hijack other's threads.

It has nothing to do with the speed of the splash updates, your screen renders it every frame anyways. It's a issue with your specific graphics card/drive set that doesn't like multi-threaded rendering. There isn't anything you can do besides just disabling the loading screen.

Remove these files: LoadingPlugin (RandomThings-MC1.10.2-3.7.7.1.jar) LoadingPlugin (ResourceLoader-MC1.9.4-1.5.1.jar) ChiselCorePlugin (Chisel-MC1.10.2-0.0.10.22.jar) CCLCorePlugin (CodeChickenLib-1.10.2-2.5.8.255-universal.jar) EnderCorePlugin (EnderCore-1.10.2-0.4.1.65-beta.jar) RebornCoreASM (RebornCore-1.10.2-2.13.5.136-universal.jar) AppEngCore (appliedenergistics2-rv4-alpha-11.jar) FMLPlugin (InventoryTweaks-1.61-58.jar) ArsMagica2-Preloader (ArsMagica2-1.10.2-1.5.0-18.jar) CoFH Loading Plugin (CoFHCore-1.10.2-4.1.1.156-universal.jar) CorePlugin (MrTJPCore-1.10.2-2.0.0.17-universal.jar) AstralCore (astralsorcery-1.3.2-beta.jar) ShetiPhian-ASM (shetiphiancore-1.10.0-3.3.8.jar) SurgeLoadingPlugin (Surge-1.10.2-1.1.0.70.jar)

So a little update for you guys. Turns out the server had electrical issues this morning that OVH had to take care of. The physical box is now up, and Flamegoat is working on bringing all the services back online. So it should be back up soon. Its back up. As for anyone who has issues with downloading the libraries, always remember, they only need to be installed once. So you could get them all manually from maven central.

Then you have a broken launcher, use the mojang one. The jar is not needed there anymore as it uses the vanilla jar.