LexManos

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.

Working as intended, just play the game.

We know, bug optifine to update.

If you REALLY don't want to install a normal JRE, then you can use the one bundled with the mojang launcher, just navigate to the runtime folder, then the bin folder. And run our installer.jar with the java.exe in there.

Its on optifine to fix. We do not support coremods on this forum especially closed sourced coremods.

https://github.com/MinecraftForge/MinecraftForge/commit/61d00dd05f918acf77dcfa96464a4d103bc243f2

One or more of your coremods are wholesale replacing the Profiler class, most likely optifine, remove it.

There are a few texture packs out there that exploit leaked GL state in the creative inventory that break when new tabs or items are added. This looks like one of them. If you want things to be transparent, then just made a transparent texture not a filtered one.

You dont, its most likely a Modder error, post here to figure it out or go to the mod's forums. And don't hijack old threads.

The only 'slightly different' part of the syntax is that we require you to name things. This is compatible with vanilla loaders, but also uses provides the necessary information for code to interact with the tables. Think of it, like many other things we do in Forge, Vanilla+

Well first off, you need to be careful what chunks your generator is loading. Read this for some info: https://www.reddit.com/r/feedthebeast/comments/5x0twz/investigating_extreme_worldgen_lag/ The reason you're getting more chunk loading, specifically for the BiomeDict stuff is that you're now generating in MORE then just EXACTLY Forest. You're generating in anything thats CONSIDERED a Forest, which in vanilla is 21 of the 61 known biomes. Just as a note your 'BEFORE" would be better written {and have the same effect} as: if (biomegenbase == Biomes.FOREST)

We do not support coremods on this forum.

This is EXACTLY what the installer is supposed to do. The Jar is not needed as it's in the normal version folder. Please search there are dozens of this question. It's 2017 you NEVER need to edit the jar files anymore!

1, 2, 3) There are functions that can be applied on loot tables. We just need to expose the information and its a matter of sitting down and writing up exactly what people want and implementing it. 4) We allow people to modify loot tables so you can already do this 5) The new fishing event added the other day can be used to enforce thice 6) This.. actually may not be able to be done as as from our point of view players and machines are the same. I guess we could just add more info to the event. We want to enhance the loot table functionality not replace it all with the old system we used before they were introduced. Not having biome, player info, enchantment info is all just info we need to push in. I'm not sure what you mean by mod loot tables not hooked into whatever, they should all be hooked into exactly whats needed to load them all... Or, they should be available to be hooked in if you write your code correctly.

Disable the loading screen.

We are still working on the backend and getting it all together. Sadly its a slow process as there arnt many people working on it. We're trying to bring on another person but ya, it's slow. The other side of this, is we don't really collect much data. So there isn't much to actually show. The only real important thing this has shown us so far is that J8 is by far the java version of choice. Which is what allowed us to decide to force J8 for 1.12+. Minecraft following suit is just bonus reason to do it If you can think of a metric that you'd like to see on the public front let us know and we can consider it, If we have the data.