Leaderboard

thanks for wasting my time found it on their github.

You can get the current GUI opened with Minecraft.currentScreen. Then if it's a chest that GUI will be an instance of GuiContainer. You can then access the Container of that GUI with GuiContainer.inventorySlots. Finally you can iterate all ItemStacks of that container with Container.inventoryItemStacks.

Well first of all this recipe's json is broken, it's syntax is invalid. Secondly if the item in the recipe has subitems(read: metadata that defines different states) you need to specify the data property in your recipe too. has 2 variants - normal apple and notch apple thus requires the data property Has 2 variants - dirt and coarse dirt thus requires the data property There is no item with a registry name of grass_block. This should work without issues since it has no subitems. Has 7 variants - stone, granite, diorite and andesite(+ polished variants) thus requires the data property Since potions use NBT data to differentiate between different potion types you would need to specify that NBT data in the ingredient. Unfortunately 1.12.2 isn't capable of recognizing NBT in ingredients. You would need a custiom recipe ingredient parser.

This means you did not register the tile entity. However if you store this in a TileEntity it will only store it once for all players. So you should store it in the player as a capability instead.

Most models are created upside down because of how texture coordinates work. It’s easier for humans to create them upside down and then rotate them in the rendering. This is because texture coordinates (UV) have the V axis going down when pretty much every axis ever goes up. Here are a couple diagrams to illustrate this

I mean rotate it in your mod, in your renderer. GlStateManager#rotate

To me this looks like the entity is upside down. Maybe something is wrong with your modelling software and the way it exported the model? In any case you can rotate the entity by 180 degrees around the z axis to fix this.

If it was from our official site, then it's fine. Windows likes to say anything it detects as a executable file, that hasn't paid them a stupid amount of money to be on their whitelist, can harm your computer. Because it can, even stuff on their whitelist can, any executable code you download from the internet can harm your computer. But if you trust the people you're getting it from, then you just ignore that. Always be on your guard, make sure you're getting what you expect from the host you expect. We also provide the signatures of each file on the downloads page so people can verify that it didnt get corrupt while downloading.

Personally, 1.7.10 will always have a special place in my heart. While I was a beta player, I never really got into modded until 1.7.10. That being said, I was one of the people that was very resistant to the combat update, but I came around eventually. New mods and packs eventually won out, and here I am on the bleeding edge with the rest of what I used to refer to as "the crazies". Some of my favorite packs of all time are back on 1.7.10, and I don't think that's likely to change any time soon. Outdated, sure. Obsolete? Not hardly!