We are able to interact with Minecraft code in many such ways - this is the whole point of an Application Programming Interface, to be able to interact with a program via our own code.
![how to make a curse forge modpack how to make a curse forge modpack](https://i.imgur.com/8tGnDJn.png)
Another type is the GameRegistry - you can add new Blocks and Items simply by extending the appropriate class and registering them to the GameRegistry.
#HOW TO MAKE A CURSE FORGE MODPACK MODS#
It's a vanilla interface, but many mods use it because it implies a certain behavior. You can retrieve or set the inventory contents, etc. Think of vanilla Minecraft's IInventory interface - you can trust that any class implementing that interface has inventory-like functionality, and can therefore treat any such class as an inventory.
![how to make a curse forge modpack how to make a curse forge modpack](https://i.imgur.com/SoDcupL.png)
An API can also be a collection of classes and methods, but with the intent that there are some, usually interfaces, that, if used, will provide some functionality with your mod. What would I need to do to create a library as opposed to a regular mod?Ī "library" is really just a collection of classes / methods. After some study on this, I have come to the conclusion that an API on it's own is insufficient for what I want to do, and may need to supply an optional library to go along with it.