🍄 Nintendo1996NintendoHARDMario Kart 64 rebuild deck
HARD
Drift charging, the position-weighted item table and the track spline all come out of one prompt working; the skill ceiling does not, and finding it means driving your own build and moving stage thresholds one at a time.
You will get the loop working. Then the real work starts.
A genuinely great agent build, because the entire game is three well-defined systems — drift charging, position-weighted items, and a track spline — and all three are promptable in one go. The KINDA is track design and the item-table tuning, which is where Nintendo spent its twenty team-years. Get the drift sparks right and you will not care.
- Difficulty
- HARD · 3 of 5
- First playable
- A weekend
- The original
- 20 team-years
- Released
- 1996 · Nintendo
- Genre
- Racing
Build a 3D kart racer with items and drift boosting. three.js, four racers, one track, split-screen optional. Requirements: - Kart handling: arcade, forgiving, and momentum-light. Fixed acceleration to a class-dependent top speed, a turn radius that tightens at low speed, and NO simulation-style tyre model. - Drift boost is the skill mechanic and must be exact: hold the drift button while turning to enter a slide with a fixed outward angle, steer within the drift to charge a meter in stages, and release for an impulse scaled to the stage reached. Show the charge as coloured sparks. This one mechanic carries the entire skill ceiling. - Item system driven by race position: a weighted item table per position, so first place draws defensive items and last place draws catch-up items. This is the design that makes the genre work, and it must be data, not code. - Items: a homing projectile that tracks the next racer ahead along the track spline, a straight-line projectile, a dropped trap, a speed boost, and a temporary invincibility. - Track as a spline with width, banking and a checkpoint sequence, used for lap validation, respawn-after-falling, item homing, and AI navigation. Build the spline system first — everything hangs off it. - AI racers that follow the racing line with per-corner target speeds, use items sensibly, and rubber-band gently: a small speed multiplier based on distance from the player, capped so it is never visible. - Surface types with different grip and a speed penalty off-track, plus boost pads and jump ramps with a mid-air trick input. - Camera: behind the kart with lag, swinging wider in drifts, with speed-scaled FOV. Definition of done: I chain three drift boosts through a corner sequence and gain a full second on the AI.
- Sixteen tracks of hand-tuned layout, which is the real content
- Nintendo's characters and trademarks
- Four-player split-screen on a console, and the sofa it implies
- Rubber-band AI tuned so precisely that it feels fair while cheating
A charge meter that costs you speed
A charge meter is only interesting when charging hurts — the slide is slower than the clean line, so every drift is a bet on getting paid back at release. That structure, accept a worse state now for an impulse later, is the whole skill ceiling, and it transfers to any input you can hold and release.
ScopeA weekend— build just this, not the game
Build a drift-charge control toy. Single self-contained HTML file, Canvas 2D, top-down view, one vehicle on an empty plane with a few cones for reference, no build step. - Arcade steering: fixed acceleration to a top speed, a turn radius that tightens at low speed, no tyre simulation of any kind. - The mechanic: holding the drift key while turning locks the vehicle into a slide at a fixed outward angle. The slide is strictly worse than a clean line — you scrub speed and your steering authority narrows. Holding it charges a meter through three stages; releasing grants a forward impulse scaled to the stage reached, and releasing before stage one gives nothing at all. Steering further into the slide charges faster than steering out of it. - Show the current stage as a colour change on the particle trail, and print speed and stage as numbers. - Every constant in one CONFIG object: slide angle, scrub rate, stage thresholds, impulse per stage, cooldown. Definition of done: taking a corner on a clean line is measurably faster than a stage-one drift, and only a stage-three release beats it.
Not a clone — Mario Kart 64 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.
Matchday One Run
Mario Kart 64, but a roguelike run instead of a campaign, set in pro sports. Rendered in hand-drawn ink on paper.
Build a browser game called "Matchday One Run". The pitch in one line: a racing in the spirit of Mario Kart 64, but a roguelike run instead of a campaign, set in pro sports. WHAT THIS IS Take the SHAPE of Mario Kart 64 — 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 A roguelike run instead of a campaign. Twenty to forty minutes, procedurally assembled from hand-authored chunks, permadeath, and a meta-progression drip. Replaces authored content volume with combinatorics. 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 Pro sports. Rules of a real sport as the combat system, a crowd that reacts, and a season structure even if you only ship one match. 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 Hand-drawn ink on paper. Rough stroked outlines with per-frame jitter so lines boil, a paper-grain texture over everything, and ink-bleed on impacts. 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 20 team-years to the counter on the homepage.
Then try these
Questions
How hard is Mario Kart 64 to rebuild with an AI agent?
Yes — every game is buildable at some scope. The question is how hard, and Mario Kart 64 is HARD (3 of 5). You will get the loop working. Then the real work starts. Drift charging, the position-weighted item table and the track spline all come out of one prompt working; the skill ceiling does not, and finding it means driving your own build and moving stage thresholds one at a time. Reckon on a weekend to something you can actually play — not to something that matches the 20 team-years Nintendo spent.
What makes Mario Kart 64 hard to rebuild?
Drift charging, the position-weighted item table and the track spline all come out of one prompt working; the skill ceiling does not, and finding it means driving your own build and moving stage thresholds one at a time. 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 charge meter that costs you speed — a weekend of work.
How long does it take to build a Mario Kart 64 clone?
Wrong question, and it is worth saying why. Nobody rebuilds Mario Kart 64 — the original took Nintendo on the order of 20 team-years, released in 1996 on Nintendo. 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 Mario Kart 64?
Sixteen tracks of hand-tuned layout, which is the real content. Nintendo's characters and trademarks. Four-player split-screen on a console, and the sofa it implies. 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.