🎮 PS32010PlaydeadHARDLimbo rebuild deck
HARD
The silhouette-and-blur look is thirty lines of shader and effectively free, so the whole build is authoring puzzles where the first death teaches and the second is your fault — and a physics sandbox has nothing in it to solve.
You will get the loop working. Then the real work starts.
The only game on this list where the signature art style is genuinely free — silhouette plus parallax blur plus grain is thirty lines of shader, and it looks like the real thing instantly. The KINDA is puzzle design: Playdead's puzzles are individually authored lessons, and a prompt gives you a physics sandbox with nothing to solve.
- Difficulty
- HARD · 3 of 5
- First playable
- A weekend
- The original
- 12 team-years
- Released
- 2010 · PS3
- Genre
- Puzzle Platformer
Build a monochrome physics puzzle-platformer in the Limbo mould. 2D side-scroller, Canvas or Phaser with Matter.js. Requirements: - The look is the product and is achievable in code: silhouettes only — everything renders pure black against a light-grey fogged background. Depth from four parallax layers with progressively heavier blur, a vignette, film grain, and a subtle horizontal jitter on the whole frame. No colour anywhere, ever. - Character controller: physics-driven, deliberately weighty. Slow acceleration, real momentum, a grab-and-push interaction with boxes, ledge grabbing, and rope swinging using a chain of constraints. - Puzzle objects as physics bodies: crates, ropes, levers, pressure plates, water with buoyancy, rotating platforms, and a magnet. Puzzles are built by combining these, never by scripted sequences. - Death is core: instant, physical, and gruesome in silhouette; respawn at the last checkpoint within 500ms. Checkpoints roughly every 30 seconds of progress. The loop is die-learn-retry, so retry must be nearly instant. - Zero UI. No health, no score, no text, no tutorial prompts. Every mechanic is taught by a safe version of the hazard placed before the lethal one. - Audio: near-silence, punctuated by physical sound — chains, water, wood. Use an ambient bed that drops out entirely just before a set piece. - Level format as JSON with a simple editor page for placing bodies and checkpoints. Definition of done: I die, immediately understand why, and retry without thinking about it.
- The art direction, which is the entire product and is one studio's signature
- Puzzle design where every death teaches you exactly one thing
- Sound design built almost entirely from silence
- The trial-and-death pacing, tuned so failure never feels cheap
A harmless rehearsal before every lethal hazard
Every mechanic gets a safe rehearsal before it is allowed to kill you — that is the whole of wordless tutorial design, and it replaces the tooltip in any game you will ever build. The part nobody builds is the instrumentation: count deaths to unrehearsed hazards and you have a number for how badly you are teaching.
ScopeA weekend— build just this, not the game
Build a wordless teaching corridor as a single self-contained HTML file. Canvas 2D, no build step, and no text or icons on screen at any point. - Four hazard types: a crushing weight, a swinging saw, a collapsing ledge, and a pressure plate that fires something across the screen. - Every hazard type appears twice, in this order. First a rehearsal instance the player cannot lose to: it triggers in full view, close enough to read, but out of reach. Then a lethal instance placed so that the rehearsal is the answer to it. - Death respawns at the last checkpoint in under 300ms with no screen, prompt or fade in between, so retrying costs nothing but the walk back. - Instrument it: log every death with the hazard type and whether the player had already witnessed that type's rehearsal. Print the unrehearsed deaths at the end of a run. - Silhouettes only, one grey background, no colour at all. It costs nothing and it stops you decorating instead of teaching. Definition of done: three people play it cold and the unrehearsed-death count is zero for all of them.
Not a clone — Limbo re-themed and cut down to something you can finish. The angle is the important reel: it is what turns a project into a weekend. 24,360 ways to land.
Once Idle
Limbo, but an idle version that plays while you are away, set in a fairy tale gone wrong. Rendered in CRT arcade with scanlines.
Build a browser game called "Once Idle". The pitch in one line: a puzzle platformer in the spirit of Limbo, but an idle version that plays while you are away, set in a fairy tale gone wrong. WHAT THIS IS Take the SHAPE of Limbo — its core loop, and whatever makes that loop good — and rebuild it as your own game in a different world at a smaller scope. Use your own names, art and audio, which you want anyway: a reskin of somebody else's game is less interesting than a new one that works the same way. THE ANGLE — this is the important constraint, honour it above everything else An idle version that plays while you are away. Offline progress on load, big-number maths from line one, and a prestige reset. The fantasy survives; the input does not. This is what makes the project finishable. If a decision would push the scope back towards the original's, take the smaller option every time. THE THEME A fairy tale gone wrong. Rules of stories treated as physics — deals, thirds, true names — and a moral that costs something. The theme is not a coat of paint. Let it change what the mechanics mean — a reload, a health pack and a locked door should all be things that make sense in this world and nowhere else. LOOK CRT arcade with scanlines. Post-process pass with scanlines, barrel distortion, phosphor bloom and slight chromatic aberration at the edges. Keep it subtle enough to read text through. REQUIREMENTS - Runs in a browser with no build step. Canvas 2D unless the angle genuinely requires 3D, in which case three.js. - Fixed-timestep update loop with interpolated rendering, so it behaves the same at 60Hz and 144Hz. - Every tuning constant in one CONFIG object at the top, exposed as live sliders in a debug panel. You will find the feel by dragging those, not by prompting. - All content — levels, entities, balance numbers — in JSON or plain data files, never inline in the logic. - Audio generated with the Web Audio API rather than asset files. - Respect prefers-reduced-motion: keep the fades, drop the shake and the parallax. BUILD ORDER 1. The core loop with placeholder rectangles, at the reduced scope the angle demands. No theme, no art, no audio. Make it fun as rectangles first. 2. The angle's consequences. Cutting to bots, or to turn-based, or to one level changes the design rather than just shrinking it — find out how and rewrite step 1. 3. The theme, as content and data. 4. The look, applied last as a rendering layer over a game that already works. Start by writing a one-page plan: the core loop, what the angle removes and what that frees you to do properly, and what you are deliberately leaving out. Wait for me to approve it before writing code.
Half the time one of these already does what you wanted, and the other half it saves you a week of solving a problem someone documented in 1997.
One count per game. No account — it is tied to a salted hash of your IP, which is not stored in a form anyone can reverse. Every build adds 12 team-years to the counter on the homepage.
Then try these
Questions
How hard is Limbo to rebuild with an AI agent?
Yes — every game is buildable at some scope. The question is how hard, and Limbo is HARD (3 of 5). You will get the loop working. Then the real work starts. The silhouette-and-blur look is thirty lines of shader and effectively free, so the whole build is authoring puzzles where the first death teaches and the second is your fault — and a physics sandbox has nothing in it to solve. Reckon on a weekend to something you can actually play — not to something that matches the 12 team-years Playdead spent.
What makes Limbo hard to rebuild?
The silhouette-and-blur look is thirty lines of shader and effectively free, so the whole build is authoring puzzles where the first death teaches and the second is your fault — and a physics sandbox has nothing in it to solve. That is why it sits at HARD rather than a tier either side of it. If you want the idea without the project, the transferable part is a harmless rehearsal before every lethal hazard — a weekend of work.
How long does it take to build a Limbo clone?
Wrong question, and it is worth saying why. Nobody rebuilds Limbo — the original took Playdead on the order of 12 team-years, released in 2010 on PS3. What you can do is reach something playable and genuinely yours in about a weekend, and then keep going for as long as it stays interesting. Any figure that claims otherwise is measuring a prototype and calling it a game.
What do I lose by building my own Limbo?
The art direction, which is the entire product and is one studio's signature. Puzzle design where every death teaches you exactly one thing. Sound design built almost entirely from silence. Those are the parts a prompt will not hand you.
Which AI coding agent should I use to build it?
Any of Claude Code, Codex or Cursor will handle this prompt. Paste it as your first message, let the agent scaffold the project, then iterate on feel — the second, third and tenth prompts are where a game actually gets good. Work in an empty folder or a fresh git branch so you can throw it away cheaply.
One email when new games go on the list. No other reason to email you, ever.