How to Implement a Conveyor Belt or Moving Surface

A conveyor belt or moving surface—a surface that moves objects on it—applies its movement to the objects standing on it, and should combine cleanly with the objects' own movement so the result feels solid rather than janky. Implementing the movement combination cleanly is what makes moving surfaces feel solid.

Apply the surface's movement to objects on it

A conveyor belt or moving surface moves objects on it—an object standing on a conveyor is carried along it (moved by the belt's motion). Applying the surface's movement to objects on it means the surface's motion (the belt's direction and speed) is applied to objects on the surface, so they're moved by the surface (carried along the conveyor, pushed by the moving surface). This is the core of a moving surface: objects on it are moved by its motion, carried or pushed along, much like a moving platform carries the player but here applying a continuous surface motion. Applying the surface's movement to objects on it—moving objects by the surface's motion—is the foundation of a conveyor belt or moving surface, carrying or pushing the objects on it.

Combine the surface movement cleanly with the object's own movement. The key to a solid moving surface is combining its movement cleanly with the object's own movement—so the object on the surface, moving itself (walking, etc.), combines its movement with the surface's correctly. Combining cleanly means the surface's movement and the object's own movement are combined correctly (the object's walking plus the conveyor's carrying producing the correct combined motion—walking against the conveyor, with it, or across it), so the result feels solid and correct, rather than the two movements conflicting or producing janky results. This combination is where moving surfaces can go wrong (the surface movement and the object's movement conflicting, jittering, or producing incorrect motion), so combining them cleanly (the correct combined motion) is essential to a solid moving surface, much like the edge cases of moving platforms. The object's own movement combined with the surface's movement should produce the correct, solid result (the object walking on the moving surface naturally), rather than janky conflict. Combining the surface movement cleanly with the object's own movement—the correct combined motion—is what makes the moving surface feel solid. Combining applying the surface's movement to objects on it (moving objects by the surface) with combining the surface movement cleanly with the object's own movement (the correct combined motion) is what makes a conveyor belt or moving surface feel solid—applying the surface's movement to objects, combined cleanly with their own movement. Implementing the moving surface this way—apply the surface movement, combine cleanly with the object's movement—is what makes it feel solid, carrying or pushing objects correctly while combining cleanly with their own movement, rather than the janky conflict that incorrect movement combination produces. Apply the surface's movement to objects on it, combined cleanly with their own movement, and the conveyor belt or moving surface feels solid, moving objects correctly while they move themselves on it, which is what makes moving surfaces work reliably rather than janky.

Let real players be the judge

It's remarkable how differently real players behave from how you imagine they will. The tutorial you think is obvious confuses them; the feature you agonised over goes unnoticed; the thing you almost cut becomes their favourite. None of that is visible from inside your own head, which is why watching real people play is the single highest-leverage thing most developers under-do.

Watch without intervening, resist the urge to explain, and pay attention to what players do as much as what they say. Their confusion and their choices are data, and acting on that data is what turns a game that works for you into one that works for everyone.

Polish where players actually look

Polish is not evenly valuable. Players form an impression in the first minutes and spend most of their time in the core loop, so effort spent there returns far more than effort spread thin across content few people reach. The opening, the moment-to-moment feel, and the things every player touches are where polish converts directly into how good the game feels.

Be deliberate about it. Make the first impression strong and the core interactions satisfying before widening out, because a great core with less content almost always beats a sprawling game that never feels good to play.

Scope is a decision, not an accident

Almost every overscoped game got that way one reasonable addition at a time, with no single decision ever feeling like the mistake. The finish line recedes a little with each new feature, and because the project always feels nearly done, the developer rarely notices how far the goal has drifted until they're exhausted and the game still isn't out.

Treat scope as something you actively decide rather than something that happens to you. Write down what the finished game contains, make every addition a conscious trade against that, and keep most new ideas in a backlog where they belong — because a small game you finish beats a large one you abandon.

Measure before you optimise

Intuition about what's slow, what's confusing, or what's driving players away is usually wrong, and acting on it wastes effort on problems that don't matter while the real ones persist. The developers who improve their games efficiently are the ones who measure first — profiling performance, watching real sessions, capturing actual errors — and let the data set their priorities.

It's slower than trusting your gut, but it's the only approach that reliably improves the game instead of just changing it. Find the biggest real problem, fix that, and measure again, rather than optimising guesses.

The first impression is most of the battle

More players leave in the opening minutes than at any other point, which makes the first few minutes the highest-leverage stretch of the whole game — and also the part the developer can least see clearly, having played it a thousand times. What feels obvious to you is often confusing to someone seeing it fresh, and that gap quietly costs you players before they ever reach the good part.

Get the player into the interesting part fast, let them feel competent quickly, and watch first-time players go through the opening without helping them. Nobody quits a game they're enjoying, so making the early minutes land is most of the battle for retention.

A conveyor belt or moving surface applies its movement to objects on it (carrying or pushing them), and should combine cleanly with the objects' own movement so the result feels solid. Apply the surface's movement to objects, combined cleanly with their own movement, so moving surfaces feel solid rather than janky.