Quick answer: Reduce independent keywords, group mutually exclusive options into a single keyword set, and strip unused combinations so the variant matrix stays small.

Uber shaders pack every feature behind keywords, but N independent keywords yield 2^N variants. The count and build time grow exponentially, often into the tens of thousands. Here is how to fix it.

How to fix it

1. Make exclusive options share a keyword set

Replace several boolean keywords that are never combined with one enum-style keyword group (e.g. _MODE_A _MODE_B _MODE_C) so they add variants linearly, not multiplicatively.

2. Strip unused combinations

Use a build-time variant stripper (Unity's IPreprocessShaders, an engine permutation filter, or a whitelist collection) to drop combinations the game never uses.

3. Split rarely-mixed features into separate shaders

Move features that are almost never used together into distinct shaders rather than one uber shader, removing their keywords from the shared variant matrix entirely.

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.

The bug you can't reproduce isn't gone — it's just invisible until you capture it from the player's device.