What problem did this project solve?

A 2D browser platformer looks simple until you start fighting jump physics, collisions and smoothness on weaker hardware. It is a project where the control "feel" matters more than the feature count.

A game running in the browser; Tuned movement physics and collisions; A game loop stable even on weaker hardware; Simple, readable code that is easy to extend.

How much does a project like pixel-platformer cost?

We price every project individually, because two projects with the same name can differ in scope several times over. For a rough outline we give a range, and the quote is free.

How long does a project like this take?

It depends on the scope. We give the deadline in the quote together with the stages, and you accept each stage on a test version before it reaches people.

Will I see the design before any code?

Yes. We show the mockup on our server and you correct it before any code exists, so changes at that stage are quick.

You do. After acceptance and full payment, the economic copyright in the code and the materials made for you passes to you.

Other

pixel-platformer

A complete 2D pixel-art platformer - character physics, levels, enemies and collectibles. Proof that we go down to the game-engine layer, not just assemble ready-mades.

Overview

A platformer is one of those projects that look trivial from the outside. A square hops across tiles, how hard can it be? All the difficulty sits in things a player never sees yet feels within a few frames: whether the jump is springy, whether the controls lag, whether you can reach that ledge.

In this project, instead of piling on mechanics, we took to a high standard the thing good controls depend on: character movement that sits well in the hand, and a game loop that behaves the same on any hardware.

A player judges a game in the first few seconds, and not with reason but by touch. A character that is too light slips out from under your fingers, one that is too heavy drags and frustrates. Between the two lies a narrow band where the jump feels good - and that band is found only by tuning single values: jump force, gravity, friction on landing.

That is why a platformer tests craft so mercilessly. There is no grand architecture to design, but there is merciless feedback: one badly chosen number and the game stops being fun at once.

One physics step, every machine equal

The most common mistake in browser games: a loop tied to the frame rate. On a 60 Hz monitor the character jumps normally, on 144 Hz it flies twice as fast, and on a weak laptop dropping frames it slows down. The physics cannot depend on how fast the screen draws.

The fix is simple and proven: the simulation runs on a fixed step, and drawing happens separately, with interpolation between ticks. The world updates exactly sixty times a second regardless of the monitor, and the renderer gets the state plus a fraction of the step so the motion stays smooth.

gameLoop.js · javascript

let accumulator = 0;
const step = 1 / 60;

function frame(now) {
  accumulator += (now - last) / 1000;
  last = now;

  while (accumulator >= step) {
    world.update(step);
    accumulator -= step;
  }

  renderer.draw(world, accumulator / step);
  requestAnimationFrame(frame);
}

Two game loops

Approach	On a fast screen	On a weak laptop
Loop tied to frames	character flies too fast	character crawls
Fixed step plus interpolation	same pace	same pace

Collisions that do not cheat

The second thing that ruins the "feel" is collisions. The character has to stop exactly at the edge of a tile, not a pixel early and not a pixel late, otherwise the player senses something is off even without being able to name it. The simulation computes it more simply than it seems: velocity, then the X and Y axes separately against the tile grid, with a position correction on contact.

Input

we read keys once per frame, but feed them to the simulation, not straight into movement.

Simulation

the fixed step computes velocity, gravity and collisions against the tile grid.

Draw

the renderer gets the world state plus a fraction of the step so motion stays smooth between ticks.

The result you feel in your hand

What comes out is a small game that genuinely plays well, with code that stays readable and easy to extend. The jump has good weight, collisions are honest, and the pace is the same on every monitor. This is not a tech demo pretending to be a game, but something taken to a state where you want to play it longer than it takes to launch.