Quick answer: Disable plugins you do not use in the Plugins browser (or your .uproject) so their modules and bundled content stop shipping, then verify nothing breaks at cook time.

Unreal enables a broad set of plugins by default, each potentially adding code modules and starter content to your package. A game that uses none of a plugin's features still pays its size cost. Turning off unused plugins reduces the build.

How to fix it

1. Audit enabled plugins

Open Edit > Plugins and review what is enabled. Look for features your game does not use, such as unused media frameworks, editor-only helpers, or sample content.

2. Disable unused plugins

Uncheck the plugins you do not need and restart. This removes their modules and content from the cook. Disable conservatively and recook to catch dependencies.

3. Confirm with package size

Recook and compare the package size and the size map. If a disabled plugin breaks the build, re-enable only the specific dependency rather than the whole set.

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 Unreal Engine 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.

Most of the time the fix is small. Seeing the failure clearly is the part that actually costs you.