CorgiLib FAQ

CorgiLib is a shared code library that other mods by the same author depend on, so it adds no content of its own. It provides the config system, codec helpers, and registries those mods use behind the scenes. If you installed it expecting new gameplay, that's normal — its job is to make the mods that require it work.

Check the dependencies listed on each mod's project page, or look at the crash log — a missing CorgiLib usually names the mod that failed to load. Any mod that lists CorgiLib as a required dependency will refuse to start without it.

They live in the normal config folder for your instance, but they're written in JSON5 rather than the usual TOML or .properties format. Look for files ending in .json5 inside the config directory. You can open them in any text editor.

CorgiLib uses JSON5 serialization, which is a superset of JSON that permits comments and trailing commas. That's why you'll see explanatory lines starting with // or /* */ inside the config. Don't strip them out — they're there to explain what each option does.

Yes, if you remove a required field or introduce a syntax error, the mod may fail to load or fall back to defaults. Keep a backup of the file before editing, and only change values, not the structure. If something breaks, restoring the original file usually fixes it.

They control how values transition over time or space — for example, how a color fades or how a terrain feature blends into its surroundings. CorgiLib registers them as codecs so a config can name a blending style instead of hardcoding math. You pick one by name in the config rather than writing the formula yourself.

An entity filter is a rule that decides which entities a mod's feature applies to, such as only hostile mobs or only a specific tag. Configuring it lets you include or exclude entity types without editing the mod's code. This is useful when a mod's default behavior is too broad or too narrow for your pack.

CorgiLib generally has little or nothing to configure on its own — the settings you care about live in the configs of the mods that depend on it. Treat CorgiLib as infrastructure and edit the dependent mod's config files instead.

As a code library it adds no world content, so its performance impact is minimal and mostly indirect through the mods using it. Conflicts are rare but possible if two mods register similar codec types; if you see registry errors, check whether another library mod is involved.

Make sure the CorgiLib version matches what the dependent mod expects, since a mismatch can still cause a load failure. Also confirm both are for the same Minecraft version and loader. If the error persists, the dependent mod may be outdated rather than CorgiLib itself.

CorgiLib is a library of common code shared across Corgi Taco's projects. It provides reusable utilities that other mods can depend on.

No, it is a library mod meant to support other projects rather than add standalone gameplay features. Its purpose is to supply shared code.

It supports .json5 config serialization using Mojang's codecs. This allows for commented json files.

Yes, it supports commented json files and commented codecs. This makes configs easier to read and document.

It provides a trees from NBT feature. This lets tree data be defined and loaded via NBT.

It offers a blending/easing functions codec registry and a villager trade codec registry. Both make it easy to serialize these via codecs in configs.