Quick answer: Move the platform as an AnimatableBody3D (which updates in the physics step) and ensure platform_floor_layers includes its layer so move_and_slide carries the rider smoothly.

Godot's CharacterBody3D can carry riders on moving floors automatically, but only if the platform is the right body type on the right layer. Here is how.

How to fix it

1. Use AnimatableBody3D for platforms

Move platforms with an AnimatableBody3D (or set sync_to_physics) so they update during the physics step. A platform moved in _process or as a RigidBody desyncs from the rider and stutters.

2. Set platform_floor_layers

Ensure the platform's collision layer is included in the character's platform_floor_layers so move_and_slide recognizes it as a moving floor and applies the platform velocity to the rider.

3. Keep movement in _physics_process

Drive both the platform animation and the character's move_and_slide in _physics_process so they advance on the same clock and the carry stays smooth.

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.