Quick answer: Carry the character with the platform's movement each frame, move the platform before resolving the character, and use continuous collision for fast vertical platforms.

Falling off a moving elevator is a carry or update-order problem. Attaching the player to the platform's motion fixes it. Here is how.

How to fix it

1. Carry the player with the platform

Add the platform's per-frame movement to the character standing on it (or parent them), so a rising or moving elevator brings the player along instead of leaving them behind.

2. Move the platform first

Update the platform before the character resolves movement, so the character reacts to the platform's new position. The wrong order lets a fast elevator move through or away from the player.

3. Use continuous collision for fast platforms

A fast vertical elevator can pass through the character between frames. Use continuous collision detection so the contact is not skipped and the player is not dropped or clipped.

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

A crash you can name from its stack trace is a crash you can usually fix in minutes.