What causes a Godot water current not pushing floating objects?

The river current is just an animated shader; nothing applies a force to rigidbodies in the water, so floating objects stay where they are.

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 Water Current Not Pushing Floating Objects

Quick answer: Use an Area3D to detect rigidbodies in the water and apply a flow force along the current direction each physics step, scaled by submerged amount, so they drift downstream.

A Godot river whose surface flows beautifully but leaves a dropped barrel sitting in place has no physical current; the flow is purely visual. Applying a force to bodies in the area makes them ride the stream. Here is how.

How to fix it

1. Track bodies in the water

Use an Area3D for the water and track bodies via body_entered/body_exited (with monitoring on), so you know which rigidbodies the current should affect.

2. Apply the flow force

In _physics_process, for each body in the water call apply_central_force(flow_dir * flow_strength), optionally scaled by how submerged it is, so it drifts downstream.

3. Vary current by region

For bends or rapids, sample a flow field or a path tangent at the body's position so the push follows the river's shape instead of pointing one fixed direction everywhere.

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.