Performance tuning works best after compatibility is stable. If the game is already crashing or desynced, lower graphics settings will not solve a loader or dependency mismatch.
Establish a clean baseline
Measure performance with Better Combat and its required dependencies before adding optional weapon, animation and visual mods.
Separate visual cost from combat logic
Shaders, high-resolution packs and particle-heavy mods can affect frame rate independently of Better Combat. Disable visual layers during troubleshooting.
Keep multiplayer versions synchronized
A stable client cannot compensate for a server running a different Better Combat or dependency version. Keep the mod stack consistent where required.
Add expansions gradually
Introduce weapon packs and combat addons one at a time, watching frame time, startup logs and gameplay behavior after each change.
Update with rollback points
Copy the working profile before major loader or Minecraft updates. A rollback lets you compare performance and compatibility without rebuilding the pack from memory.
Related guides
Continue with the focused resources in the sidebar for another loader, compatibility check or troubleshooting path.