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 RigidBody3D That Will Not Wake When Pushed by an Area

Q: What causes a Godot RigidBody3D that will not wake when pushed by an area?

A sleeping rigid body skips force integration, so applying a central force or impulse from an Area without first clearing the sleeping flag does nothing.

Quick answer: Set sleeping to false (or call apply_impulse, which wakes the body) before applying continuous forces, or disable can_sleep for bodies you push externally.

Your wind zone applies force every frame but a settled crate ignores it. The body fell asleep and apply_central_force is being skipped. Waking it first, or using an impulse, makes the push register.

How to fix it

1. Wake the body explicitly

Set body.sleeping = false right before applying a continuous force, because a sleeping body does not integrate apply_central_force.

2. Use an impulse to wake it

Call apply_central_impulse instead of a per-frame force for one-shot pushes; impulses wake a sleeping body whereas steady forces on an already-asleep body are ignored.

3. Disable sleeping for pushed bodies

For objects that are routinely affected by area forces, set can_sleep = false so they never enter the sleep state that drops your forces.

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.