Minecraft için Not Enough Recipe Book [NERB]

Bizim özetimiz

Bu proje ne yapıyor

How player data bloat happens

Large modpacks add thousands of items and recipes to the game. When your character learns these recipes, Minecraft writes every single recipe identifier into your player data.

You can see this directly. In a large pack with many learned recipes, running the /data get entity @s command spits out massive text walls of recipe tags.

That data stays attached to your player file. Every time a script inspects your character, it has to parse through that pile of text. Every time you log in, the server has to pack those recipe strings and push them across the network to your client. It adds dead weight to routine operations.

What the mod changes

Not Enough Recipe Book stops this cycle by wiping the recipe book system from the game entirely.

Some mods choose to hide the green recipe icon in your inventory menu. This mod goes further by removing the underlying book functionality. It deletes the recipe list from your player data file. Once the mod is active, those recipe strings vanish from entity lookups.

The inventory stays clean. The underlying save file drops the extra text.

Scripting and connection gains

Cutting this data gives immediate help to scripts that read player tags.

Mods like KubeJS and CraftTweaker often check player data in event scripts, such as through event.player.data calls. When the recipe registry bloat is gone, these read calls run faster because they no longer search through thousands of recipe entries.

Network traffic drops as well. The mod speeds up data synchronization between the server and the client. You get faster world join times because the server sends less player data during the initial login handshake.

Fewer bytes to sync. Real talk, quicker joins.

Installation and compatibility

Not Enough Recipe Book is created by SSKirillSS and is classified under Performance, Utility & Quality of Life categories.

You must install the mod on both the client and the server. Putting it on only one side won't work because both ends need to handle the removed recipe functionality during data sync.