Protect your eggs from prying eyes and Russian Hackers with BetterBreeding's military grade, high tech, completely required encryption.
As of BetterBreeding v1.6.0, you can now encrypt your egg data. In BetterBreeding, the data of the baby inside of an Egg is stored on the item itself. This means that the client (players) can read that data. Popular client side mods like MoreCobblemonTweaks even explicitly support BetterBreeding's data format.
MoreCobblemonTweaks leaking the egg data before it's born in BetterBreeding v1.5.2!
Savvy players will also use the NBTTooltip mod to easily see NBT data from the client side, you can see the output from that below the MoreCobblemonTweaks data.
Why not just store this data on the server-side? The issue is that Eggs are items - and items can be destroyed/removed in many ways, without any way of BetterBreeding knowing they're gone. This means BetterBreeding would potentially store data for thousands of eggs, with no way of ever getting rid of that data. Overtime, this would balloon server sizes, and just generally be annoying.
The solution implemented in BetterBreeding v1.6.0 is to encrypt the "baby data" stored on the egg. This solves the storage issue (everything is still on the egg), and the client side issue (the data is encrypted, only the server knows the key).
MoreCobblemonTweaks no longer detects it as an egg, and NBTTooltip just lets the client see the encrypted JSON string
Egg Encryption is configurable, and enabled by default. Enabling egg encryption will not break existing eggs. Changing your Egg Encryption key will break encrypted eggs. Only the first 16 characters of your encryption key will be used.
