Quick answer: Your game's frame rate drops in combat because combat does much more per-frame work than calm gameplay, all at once: many entities (enemies, projectiles), particle and visual effects, physics interactions, and AI computation, which spikes the frame's workload above budget. The game is fine at baseline; combat's extra load is what exceeds the performance budget, so the drop is tied to that specific situation.
When a game runs smoothly until combat starts and then drops frames, it's a situational performance problem, fine at baseline, but combat pushes it over budget. This is actually good for diagnosis: the drop is tied to a specific, reproducible situation, so you know exactly when to profile and what's different about those moments.
Why Combat Drops Frames
Combat typically does much more per-frame work than calm gameplay, simultaneously. The usual culprits: many entities active at once (enemies, projectiles, summons), each needing updates, AI, and rendering; particle and visual effects (explosions, hits, spells), which can be very expensive, especially many at once; physics interactions spiking as things collide and move; and AI computation as multiple enemies think and act. Any of these, or their combination, can spike the frame's workload above budget specifically during combat.
Because the drop is situational (combat-only), the cause is whatever combat adds that calm play doesn't. The frame is over budget only when that extra load is present, so identifying which part of the combat load dominates is the key.
How to Diagnose It
Profile during combat, not calm play, since that's when the drop happens. Capture a frame in a heavy combat scene and see what's consuming the time: particle/effect rendering, entity updates, physics, or AI. The profiler shows the dominant cost during the spike, which is your target. Test the worst case (the most chaotic combat) since that's where the drop is worst.
Bugnet's performance monitoring surfaces where frame drops occur and on what hardware, so combat-correlated drops show up (and may be worse on lower-end machines with less headroom for the spike), confirming it's a real player problem and where, complementing your local combat profiling.
What to Do About It
Optimize whatever the combat profile showed as dominant, often particles/effects (cap simultaneous counts, use cheaper effects), entity load (limit active entities, use level-of-detail), physics (simplify under load), or AI (stagger updates). A key technique is budgeting the combat load, cap the things that scale with combat intensity so the worst-case combat can't blow the frame budget.
See our guide on fixing a game that drops frames during combat for the steps. Since combat is often the most important, most intense moment, keeping it smooth matters disproportionately for how the game feels.
Combat frame drops are a situational spike from everything at once, entities, particles, physics, AI. Profile a heavy combat scene to find the dominant cost, then budget it.