Collective Library Wiki › Guides › Optimizing Performance When Using Multiple Dependent Mods
Optimizing Performance When Using Multiple Dependent Mods
How Event Combining Works
Collective Library automatically detects when multiple mods subscribe to the same game events. Instead of processing each mod's event handler separately, it combines them into one, reducing the number of calculations per tick.
What This Means for You
You don't need to configure anything—optimization happens automatically. The more mods you have that use Collective Library, the more noticeable the performance improvement becomes, especially on servers or lower-end machines.
Best Practices
- Use mods from the same author: Mods designed to work with Collective Library gain the most benefit
- Monitor performance: Use F3 debug screen to watch tick times. Collective Library should help keep them stable
- Avoid redundancy: Don't install multiple mods that do the same thing, as this negates optimization benefits
When Optimization Matters Most
Performance gains are most noticeable when:
- Running many mods simultaneously
- Playing on servers with many players
- Using mods that trigger frequent events (entity updates, block ticks)
On single-player with few mods, the difference may be subtle but still beneficial.