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 Construct 3 Save State Losing Instance Variables on Restored Objects

Q: What causes Construct 3 save state losing instance variables on restored objects?

Logic runs against objects before the Load completes, or objects are created/destroyed in ways the snapshot did not capture, so restored instance variables appear missing.

Quick answer: Wait for the On load complete trigger before touching restored objects, and avoid creating or destroying relevant objects between the save snapshot and the load.

Construct 3's System Load restores instances, but reading their instance variables before On load complete (or recreating objects) loses state. Gate logic on the load trigger.

How to fix it

1. Wait for On load complete

Do not read or modify restored instance variables until the On load complete trigger fires; before that, the snapshot is not yet applied.

2. Avoid mutating objects mid-load

Do not create or destroy the objects you expect to restore between taking the snapshot and loading it, or their instance variables will not match.

3. Save and load the full state

Use System Save to capture the whole game state rather than manually persisting selected instance variables, so object identity and variables stay consistent.

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 Construct 3 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.