What causes a Godot cyclic resource inclusion error when saving?

Two resources reference each other and both are set to save embedded, so the serializer cannot write one without infinitely nesting the other and reports a cyclic inclusion.

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 “cyclic resource inclusion” Error When Saving

Quick answer: Break the cycle by saving at least one of the resources as an external .tres file (so it is referenced by path rather than embedded), or remove the mutual reference.

Saving a scene or resource fails with a cyclic resource inclusion error. Two resources point at each other and both are being embedded, which cannot be serialized.

How to fix it

1. Externalize one resource

Save one of the mutually referencing resources as a standalone .tres on disk. Once it is external, the other can reference it by path instead of embedding it, breaking the cycle.

2. Use a uid reference, not embed

Ensure the reference is a resource path or uid:// link rather than an inline sub-resource. Inline sub-resources get fully embedded, which is what creates the loop.

3. Reconsider the data model

If two resources truly need to know about each other, hold one direction as a weak path or look it up at runtime instead of serializing both references directly.

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 errors you never hear about are the ones quietly costing you players. Visibility turns them into a worklist.