Diagnosing Lag or Crashes Caused by Component Synchronization

Why Synchronization Matters

Cardinal Components can synchronize data between server and client. If a dependent mod syncs a large or frequently-changing component, you may see stuttering, packet spam in the log, or disconnects on multiplayer servers. The library provides the mechanism; the dependent mod decides how aggressively to use it.

Narrowing Down the Cause

1. Reproduce the issue in a fresh world with only Cardinal Components and the suspected dependent mod installed.

2. Watch the log for repeated sync or packet warnings while the lag occurs.

3. Note what you were doing — opening a specific GUI, entering a chunk, or interacting with a particular entity often points to the offending component.

4. If the lag stops when the dependent mod is removed, that mod's sync behavior is the source.

Mitigation

Check the dependent mod's config for options to reduce sync frequency or disable client-side syncing of non-essential data. On servers, ensure clients and server run matching versions of both the library and its dependents, since mismatched component registrations can cause constant resync attempts. If no config option exists, report the behavior to the dependent mod's author with your log excerpt.