LexManos

It is NOT a Forge issue, stop saying stuff you know nothing about. It is a OPTIFINE issue. Update/Remove Optifine.

Yes, in the event. Before anything can be run in a class, it must first run a special <cinit> function which will run all the code needed to populate the static fields {or custom cinit methods you add} The problem is this line: public static final CookingMeal FRIES = new CookingMeal("fries", "Fries").setIngredients(2, Items.POTATO, Itemizer.SALT).setValues(new int[]{1, 2}, new int[]{2, 4}); So first it calls CookingMeal, which calls setResourceName, but since the class is being statically initialized it isn't claimed as your mods code yet. So it'll throw the warning. Then it also accesses Itemizer.SALT, but in order to know what that field is, it has to run THAT class's static internalizer. Which is all of this crap: https://github.com/Oeku/RPG-Mod/blob/master/src/main/java/net/zeldadungeons/init/Itemizer.java#L43-L76 Which calls a boat load of other classes initalizers. Stop doing that. Only create your Blocks/Items/Whatever in the Register event. If you want to use static final fields, use @ObjectHolder that's what its designed for. Or you could use a normal field thats non final and populate it in the Register event.

Stop initalizing your items in static blocks

Tell MCEdit to update. We've stored the ID map for the last 4 years or so. It wouldn't be hard for them to read it and put the correct ids in.

The official answer is to remove optifine.

There is nothing wrong with that log. Seems the game started fine. Post the real log from the logs folder.

Yes, it is called minecraft. You seem to be under the inital false understanding that any of that should be triggered by the client doing anything. Unless you're explicitly doing it from a GUI, and even in that case you should use the generic button click handlers and the like to talk to the server. None of this logic should touch any client side code.

Forge does not include extended shader support. That is an external mod. Vanilla supports a small set of shader functionality but that should be able to be loaded through resource packs.

https://github.com/MinecraftForge/MinecraftForge/compare

First problem: Texture loading being slow. This is MOST likely due to your resource packs being broken. Forge logs extra information when resource packs are broken. Thus the extra time, tho unless your packs are EXTREAMLY broken it shouldn't be to much extra time. At least thats the only logical reason I can think of. So link your exact resource packs and I can take a look. But honestly its more likely that you have something wrong. Also the fact that you're on 1.8.9 doesn't help things at all as that is notoriously broken. Scratch all that, you're using OptiFine. It does a lot of things broken/off thread that makes the model loading system appear faster. Compare us to vanilla not OptiFine. Second Problem: That it literally nothing to do with us. All we do in that scenario is send a fml marker in the "Send me your server info" packet. And parse any extra data the server sends in response. Any slowdown would be on Hypixels end. Either way, update to 1.12.2 if you want us to care about supporting you.

cpw is still working on the replacement for LaunchWrapper. But ya, possibly, we'll see. It depends on if java breaks backwards compatibility again. They usually don't so we should be good.

1) THats not a Forge log 2) That just says that it couldn't find the file. So either you dont have access to read that file, or it doesn't exist. 3) That's 1.7.10... stop.

Optifine 'works' by doing dirty hacks into the jar file. Forge uses our https://github.com/Mojang/LegacyLauncher LaunchWrapper system. Which allows us and the rest of the MC community to edit the loaded classes on the fly, and thus skirt around some legal issues. Amungst other things. J9 screwed up the classpath which means our system for editing classes doesn't work. Cpw is working on a replacement and will be functional for 1.13+

1) You have Java9 Installed, Minecraft/Forge will not work on Java9, please use Java8 2) You are trying to run the universal.jar Which is NOT the installer. The installer is called... installer... The universal jar is one of the things the installer installs. The other things are all the required libraries. So.. go download the installer, and run it. It should popup a window asking if you want to install the server or the client and where you want to install it to. Typically for the client, just leave the target directory default if you're just running the Mojang launcher normally.

Overrides.

Well since that field has no @Holder annotation then you're always gunna have null as nothing ever sets it. As for when things can be null with the holder annotation, that can happen when the capability is never registered. Which is one of the main points of the capability system to allow you to have soft links to other dependancies. You should always be checking the Capability<> instances for NULL before using them. You also shouldn't be holding the cap instance in a strongly typed field unless you've already guarded the call it's in with a null check.

1) Those are the correct hashes, if you get something else then you're getting an incorrect file. That's the POINT of the hashes... 2) Stop modding for 1.6.4, you won't get support here. Seriously dude... Its been years, update.

You need to talk to Thermal Expansion it would appear to be them crashing based on what you said. Or you could use a NBT editor to kill the itemstack in your inventory. Neither of this is cause by Forge.

Humm.... I'm just going to assume you're actually misinformed but no, Java is NOT compiled at runtime. Java is all precompiled. So there is no files in the jar you can just 'edit'. Anyways. The Observer issue is a bug that was fixed several months ago. Again if you would just update you wouldn't run into these issues. As for 1.12 vs 1.12.2. Diesiben is correct, modders should update. Its only a minor change, if any, that they need to do. Please stop arguing with our moderators when they are answering your questions.

Try gradlew cleanCache That should nuke your cache folder and let it rebuild. However this shouldn't happen at all. YOu may want to try updating your referenced Forge to 1.12.2 not 1.12.

We're going to writeup something soon, but for now nothing is collected. We have shut down the servers. They were costing WAY to much for NO benefit. So until things get actually written to a nice aggregated front end, we've stoped gathering anything. But beyond that, you can see everything it did gather here: https://github.com/MinecraftForge/Mercurius/tree/master/src/main/java/net/minecraftforge/mercurius/dataModels

No its not you need to use some form of proxy between the different servers so the client thinks its connected to a single server.

You'll be fine as long as you don't have special mods installed. To solve your issue, just install a 1.12.2 version of Forge....

The official answer, and the only one I will encourage or endorse people to do. Is to actively develop your mod for the current stable version of Minecraft. Backporting only bug fixes and other NECESSARY things. As for 1.12.1 vs 1.12.2... Just go with the .2, As stated, sub releases exist for a reason. Bugs get fixed. Users should update.

If you can take a screenshot of the advert including the address bar I can go directly to our advertisers and have it removed. This stuff should not be making it through and we take it seriously.