Leaderboard

When I run this in CMD, it gets stuck on 56% (> Building 56% > :decompileMc > Resolving dependencies ':forgeGradleMcDeps') Anyone have any solutions?

Yes, it wouldn't be caused by not having Forge installed. Post the FML log (logs/fml-client-latest.log in the game directory) using Gist/Pastebin if you want help with the crash. In future, you should post in the Support & Bug Reports section. This thread should be moved there once a moderator comes online.

FML and Forge come in the same JAR/installer. You have both installed.

It depends on where you initialize your creative tab. The RegisterEvents are called before preInit, so if you initialize your creative tab in preInit, you will set the Item's creative tab to null at the point when you register your Items. You should initialize it at the same time you declare the creative tab variable.

"foundationsmod/items/itemNeedle" 1) Domains are followed by a colon, so it should be "foundationsmod:items/itemNeedle" 2) Resources should not have any capitalizations. This is enforced in 1.11, and has been heavily urged since before 1.7. If following the naming conventions, the file should be called "item_needle" instead

Just a little? Haha. diesieben knows A LOT more about this than he does! However, that might now always work. And in this case, it doesn't. And you came to the forums for help, diesieben gave you help and information and now you're complaining? Please, just leave the forums then.

1) Make sure you initialize the CreativeTabs before your Items. 2) Make sure your Items get register in preInit, not init. 3) Use the ModelLoader instead of ItemModelMesher. 4) Only register the models on the client side (client proxy).

The network I'm part of, makes use of TickProfiler, a Forge mod that lists resource-hogging Tile-Entities and Entities, per time/tick average, per tps%¹ they are draining, per chunk² and per type³ ¹Take this with a bit of salt. If something states it is causing 50% of the drain, it may very well be a big drain, but the profile cannot see everything, yet tries to stretch what it can see to how much is drained. ²allows you to see the chunks with highest activity, most of the time player-bases centered in a single chunk, for example ³Shows the tile-entities and entities that collectively stand for the most drain. Take this with a bit of salt as well, as it does not take into account -how many- of said type there are. While this may not solve your issue, it should enable you to find the largest TPS-drains on your server.