Cardinal Components API Mod FAQ

It's a library that lets other mods attach custom data to things like players, entities, chunks, or the world itself. On its own it adds nothing you can see or craft — it only matters because other installed mods depend on it.

Check that mod's dependencies on its download page or in its mod list entry; if Cardinal Components is listed as required, you need it. If you remove it while such a mod is installed, that mod will usually fail to load or crash.

Yes — it's a background library, so once it's installed alongside the mods that use it, you don't interact with it directly. There's no config screen or item to use; it just needs to be present.

Component data is tied to how a mod defines and names its components, so if the mod changed its data format or IDs in an update, old data can no longer be read. This is a change made by the mod using Cardinal Components, not by Cardinal Components itself.

This usually means a mod that stored component data was removed or updated incompatibly, so the saved data references something that no longer exists. Re-add the missing mod at a matching version, or restore a backup from before the change.

The library itself is lightweight; problems usually come from a mod that syncs large or frequent component data between client and server. If you see lag spikes or sync-related crashes, identify which dependent mod is doing the heavy syncing and check its settings or updates.

Look at your mod list and check each mod's dependencies for Cardinal Components, or check the log for component registration messages during startup. Any mod listing it as required is a user of it.

It's designed as a shared library so multiple mods can use it at once without conflict, and it generally coexists with other libraries. Conflicts are rare and usually stem from two mods fighting over the same game object's data rather than from Cardinal Components itself.

Yes — because it handles synchronizing data between sides, it must be installed on both the client and the server (or on all players in a LAN world). A mismatch will cause connection or sync errors.

Only if no installed mod depends on it — check your mod list first, because many mods silently require it. Removing it while a dependent mod is present will break that mod and can corrupt or fail to load worlds that stored its data.

It is a developer library for Minecraft mods that lets you attach reusable data components to game objects. It provides a standardized interface so mods can store and synchronize custom state without adding blocks or items.

It lets mods attach data components to a variety of vanilla classes and interact with otherwise opaque objects and behaviors. This helps both mod creation and compatibility between mods.

Yes, it is a library for Minecraft mods to create data components that can be attached to various providers.

It supports Fabric on both the client and server.

Yes, it is a components API for Fabric that is easy, modular, and extremely fast.

Yes, it supports both client and server.

It lets you attach components to vanilla classes, implement once and plug anywhere with automatic saving, synchronize data with a single helper interface, choose how components are copied on player respawn, tick components alongside their target, and fine-tune everything.

No, it is a developer library that enables other mods to store and synchronize custom state without adding blocks or items.

Your data is saved automatically once you implement it, and you can synchronize data with a single helper interface.

It uses ASM-generated extensions, which the mod describes as blazing fast.