Leaderboard

For reference, this: @CapabilityInject(IItemHandler.class) public static Capability<IItemHandler> CAPABILITY_SET1 = null; Is how you define a capability. It's equivalent to CapabilityItemHandler.ITEM_HANDLER_CAPABILITY It is not the implementation thereof. For that, you need a new ItemStackHandler().

This is a common problem in most large games. It is very difficult to keep performance up if all the logic for all the things you cannot see is still running. Most games need to deactivate complicated objects that are "off screen". Minecraft uses this technique in many ways. For example, whole chunks get unloaded when possible. Entities can be unloaded as well, and even if they are still running on the server they will stop "tracking" (sending packets to the client) beyond a certain distance. Some of these things can be overridden a bit, for example the tracking range. I would start by seeing if using the Minecraft methods can help you. I would first make sure that the entities are registered with a very long (like 8000) tracking range. Secondly I would us the enablePersistence() method on your entities to prevent despawning. Just keep in mind that if you do this a lot it will cause performance issues.

Bingo

This line: https://github.com/HalestormXV/Runic-Sorcery/blob/master/src/main/java/halestormxv/objects/blocks/BlockStones.java#L130 Says to drop the item "Mystic Cobble" While this line: https://github.com/HalestormXV/Runic-Sorcery/blob/master/src/main/java/halestormxv/objects/blocks/BlockStones.java#L123 Says to drop the item "Lupresium Cobble" combine that with this line: https://github.com/HalestormXV/Runic-Sorcery/blob/master/src/main/java/halestormxv/objects/blocks/BlockStones.java#L58 Which sets the item stack of the above item (mystic or lupresium cobble) to have a metadata value. For mystic cobble, this value is 4. You never register a model for Mystic Cobble with metadata 4.

Either that or run java -jar minecraftforge-installer.jar --installServer