Understanding Why Cucumber Appears in Your Mods Folder

New players often spot Cucumber in their mods folder, see that it adds nothing in-game, and assume it is junk or leftover. It is neither. Knowing what a library mod is will save you a lot of confusion when troubleshooting.

What a Library Mod Is

A library mod is a shared foundation. Instead of every mod rewriting the same plumbing — config screens, tag lookups, registration helpers — they all call into one common mod. Cucumber plays that role for a family of mods. It has no creative tab, no recipes, and no world content, because its entire purpose is to be used by other code.

Why You Should Leave It Alone

If you delete Cucumber, every mod that depends on it will fail to load, often with a crash before you even reach the main menu. The symptom looks like "mod X is broken," but the real cause is the missing library. This is why Cucumber shows up in modpack manifests even though it seems to do nothing.

How to Identify Its Dependents

Check the mod list in-game; many loaders show which mods require which libraries. Alternatively, read the dependencies section on each mod's download page. Once you know which of your mods rely on Cucumber, you will understand why it is there and why it must stay.

Rule of Thumb

Treat library mods like Cucumber as infrastructure: keep them installed, keep them matched to your game version, and only change them when something that needs them demands it.