Prevent Duplicate Cape Repository Checks Across Multiple Mods

Understand Repository Sharing

When multiple mods in your modpack use the Essential Blueprint Framework, they can all reference the same remote cape repository. Without proper configuration, each mod might check the same source independently, causing redundant requests and performance issues.

Use Shared Repository Configuration

Set up a single, centralized cape repository URL in the framework's shared settings. Configure all dependent mods to point to this same source rather than maintaining separate lists.

Enable Caching

The framework includes built-in caching to store cape data locally after the first fetch. This prevents repeated downloads of the same repository file across mod restarts and player sessions.

Monitor Performance

Check your logs to confirm that cape repository checks happen only once per session, not repeatedly. If you see duplicate checks, verify that all mods are using the identical repository URL and that caching is enabled in the mod configuration.