What causes a Godot export not including files?

Non-resource files (text, data, custom assets) are not matched by the export's resource filters, so they load in the editor but are absent in the exported game.

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 a Godot Export Not Including Certain Files

Quick answer: Add the file types or paths to the export preset's included files filters, or use resource files Godot exports by default.

A Godot export missing files is the export filters excluding them. Here is how to fix it.

How to fix it

1. Add files to the export filters

The export preset has filters for which non-resource files to include. Add the patterns or paths for your data and custom files so they are packed into the export, not left out.

2. Confirm the files are referenced

Godot includes resources that are referenced, but standalone data files need the filter. Make sure the files you load at runtime are either referenced resources or explicitly included by the filter.

3. Test the exported build

Run the actual export, not just the editor, to confirm the files are present. A file that loads in the editor but is missing from the export is exactly the symptom of an exclusion filter to fix.

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 Godot 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.