What causes damage numbers overlapping?

Many damage numbers spawn at once, overlap into an unreadable cluster, and each is a separate UI object that allocates and costs to render, hurting both readability and performance.

How do I catch this when it only happens for some players?

Capture it automatically from the player's device with the full stack trace, the device and OS, the build, and a breadcrumb trail of what they did. That turns a vague complaint into a specific, reproducible issue you can fix without owning the hardware it happens on.

How to Fix Damage Numbers Overlapping and Hurting Performance

Quick answer: Pool the number objects, offset or stack overlapping numbers, and combine rapid hits into a single accumulating number to reduce count.

Overlapping, costly damage numbers are an instancing and clustering problem. Pooling and combining fix it. Here is how.

How to fix it

1. Pool the number objects

Spawning and destroying a UI object per damage number allocates and hitches under heavy fire. Pool them so you reuse a fixed set, removing the per-number creation cost.

2. Offset overlapping numbers

Stack or scatter numbers that appear at the same spot so they do not pile into an unreadable blob. A small offset or upward arc per number keeps them legible.

3. Combine rapid hits

For fast repeated damage, accumulate into a single rising number that ticks up rather than spawning one per hit. This cuts both the visual clutter and the object count dramatically.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.

Ship the fix, watch the signature disappear from the next build. That's how you know it's really gone.