Leaderboard

You changed the server proxy string, but it is the client proxy string that is wrong.

You can Google for "github" at site:http://www.minecraftforge.net/forum/topic You can go to github and then search for Forge projects. Stick to mods using the same version of Minecraft (1.12.2). After looking at a few, you'll quickly distinguish between matters of style versus matters of necessity. You'll also quickly get a sense for who knows what he's doing (and who knows even less than you do). Once you've settled on one or two worthy examples, emulate them (don't cut and paste). You learn by assimilating and doing. Finally, when you are getting ready to run something, run it in debug mode (with some break points set within your own code). Step through and into the various methods, examining some of the changing fields as you go. More than any static examination of vanilla code can ever teach you, a ride-through will illuminate how the program functions. Try to scan each operation at least once so you have some idea how it hangs together. No need to sit through 500 cycles of a loop, but try a few at least once. And have fun.

Okay. My question was not even remotely specific enough... I want to know, how I can make my machine recipes be shown with JEI. I found the API docs of JEI just yesterday, so this question is essentially solved.

Never register things like this. ForgeRegistries#<REGISTRY> are solely for querying & iterating over. If you want to register an object, use the RegistryEvent's. I believe that lang-file(en_US) have to be lower-case only(en_us) in 1.11+. @Choonster goes over why here.

Have you looked at any of the vanilla recipes that involve metadata items? Say...cookies?

@Subscribe public static void onItemRegister(RegistryEvent.Register<Item> event) { event.getRegistry().registerAll(ItemInit.ITEMS.toArray(new Item[0])); } replace @Subscribe w/ @SubscribeEvent reference: @SubscribeEvent public void registerBlocks(RegistryEvent.Register<Block> event) { event.getRegistry().registerAll(block1, block2, ...); } Retrieved from: http://mcforge.readthedocs.io/en/latest/concepts/registries/

This tutorial is not the best, on a couple of notes: There is not, and never has been, a "CommonProxy". Per definition, a Minecraft-proxy can only be either Client-side only, or Server-Side, the very antonym of "common". "CommonProxy" is a misnomer and based on faulty logic. Never call ForgeRegistries#<REGISTRY>#register. Use the RegistryEvent's for this. ForgeRegistries is, and I quote the documentation, "...a central place to access registries directly... queries and iterations can use this" Likely due to #2. The code for setting the models, is never actually called. Just because you have the method doesn't mean it's gonna get used. Use the ModelRegistryEvent, and for each of your items with IHasModel, call IHasModel::registerModel.

Yeah, no shit. Creating a new biome instance is not the same as referencing an existing instance.