Leaderboard

The supported versions are in the blue banner above. Please update to one of those versions mentioned to receive support.

Well, in my opinion, it's just as computationally efficient to use the RecipeManager and scrap the reload listener as it pretty much is a simple stateless filter. The only benefit here is a transition from O(n) -> O(k) where n is the number of recipes while k is the number of specific recipes. So, it all depends on if you want to cache your data, which still doesn't technically need a reload listener. Yes. You can technically invalidate cache without the need of a reload listener. However, I will not argue nor complain that the current implementation isn't okay as well. It's just better if you understand the reason why compared to using just a simple baseline.

Sorting a list is a Java concept. Take the time to learn about comparators and how to use them.

It's text.... The forum supports text, you can just copy and paste. You want code formatting, click the <> button. If there was an issue with your code and I wanted to fix it, I'd have to completely retype your code if you post an image. You post text I can edit it.

This solved the problem for me First register your entity with custom client factory like this .setCustomClientFactory((spawnEntity, world) -> new ExempleEntity(world)) And then use NetworkHooks#getEntitySpawningPacket to get Entity Spawning Packet @Override public IPacket<?> createSpawnPacket() { return NetworkHooks.getEntitySpawningPacket(this); } that's it ?