🖥️ PC2017Epic GamesBRUTALFortnite Battle Royale rebuild deck
BRUTAL
A global build grid and a support flood fill really are a weekend; replicating a hundred people rewriting the level thirty times a second is a netcode project the rest of the genre never had to attempt.
The hard part is not game design at all.
Battle Royale was bolted onto a six-year PvE project in roughly two months in 2017 and became one of the largest entertainment businesses on the planet, which is the least repeatable fact in this directory. The building system is the interesting engineering and it is promptable — a global grid plus a support flood fill really is a weekend. Replicating a hundred people editing the world thirty times a second is not, and that is before you reach the part where the game stopped being a game and became a venue.
- Difficulty
- BRUTAL · 5 of 5
- First playable
- A project
- The original
- 250 team-years
- Released
- 2017 · PC
- Genre
- Building Battle Royale
Build a battle royale with a real-time building system, against bots. three.js, one small island, local only. Requirements: - Every piece snaps to a single global grid, never to the piece you are looking at. Four types — wall, floor, ramp, cone — each occupying a defined face or volume of a grid cell, selected by the direction you face and committed in one click. A system that snaps relative to the last placement drifts and becomes unusable inside about four pieces; the global grid is the only reason this mechanic works at speed. Budget under 200ms from key press to solid geometry, and treat that as a hard requirement rather than polish. - Structural support is a flood fill from the ground, re-run whenever a piece is destroyed. Anything no longer connected falls and is removed. This is what makes shooting the base of somebody's tower worth doing. - Materials come from destroying the world: harvest wood, brick and metal from trees, walls and vehicles with a melee tool at different rates per material. Each tier has a low placement health that ramps to full over about a second, so a fresh wall is briefly weak. - Editing: with a placed piece selected, choose cells on its face to remove, creating a doorway or window. Editing beats rebuilding, and that gap is the skill. - Otherwise a standard shrinking-zone match with floor loot, rarity tiers, and bots that fight and build simple ramps. Definition of done: a bot shoots at me, I place a wall and a ramp in one motion and get above them, and then someone knocks out my base and I fall.
- A hundred players building structures in real time, replicated — a networking problem the rest of the genre does not even have
- Live service: a new season every ten weeks, forever, operated by hundreds of people
- The crossover licensing and the concerts, which is what the game turned out to be for
- Unreal, and the streaming, physics and replication stack you are getting free by not writing it
Scenery as inventory
One verb turns every object on the map into a resource and a second turns the resource back into geometry, so a player can answer a problem by changing the level instead of by aiming better. Most games treat the environment as decoration; this makes the tree line a supply depot and the wall you are hiding behind a withdrawal.
ScopeA weekend— build just this, not the game
Single self-contained HTML file, Canvas 2D, side-on view, no build step. A player who runs and jumps, a ground line, and scenery objects (trees, crates, a wall) each with hit points and a material type. Two verbs, and nothing else. First, a swing that damages the nearest scenery object and credits its material to your stock at a different rate per material. Second, a placement mode that spends stock to put a block or a ramp on a global grid, snapped to that grid and never to the last piece placed, committed in a single click. Placed pieces have hit points and fall to the same swing. After any destruction, flood fill from the ground and drop everything no longer connected. Show stock per material. Definition of done: I chop a tree, build a ramp to a ledge I could not otherwise reach, then knock out its base and watch the whole thing come down.
Not a clone — Fortnite Battle Royale 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.
ARR Endless
Fortnite Battle Royale, but an endless survival mode instead of levels, set in a SaaS company. Rendered in 16-colour pixel art.
Build a browser game called "ARR Endless". The pitch in one line: a building battle royale in the spirit of Fortnite Battle Royale, but an endless survival mode instead of levels, set in a SaaS company. WHAT THIS IS Take the SHAPE of Fortnite Battle Royale — 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 endless survival mode instead of levels. One arena, escalating waves on a data-driven timeline, a run timer and a score. Replaces level design with a difficulty curve. 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 SaaS company. Customers, uptime and roadmap as systems. The fantasy is shipping product under metric pressure, not casting spells. 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 16-colour pixel art. A fixed 16-colour palette (start from a Lospec palette), a hard pixel grid, and no sub-pixel movement — snap all rendering to whole pixels. 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 250 team-years to the counter on the homepage.
Then try these
Questions
How hard is Fortnite Battle Royale to rebuild with an AI agent?
Yes — every game is buildable at some scope. The question is how hard, and Fortnite Battle Royale is BRUTAL (5 of 5). The hard part is not game design at all. A global build grid and a support flood fill really are a weekend; replicating a hundred people rewriting the level thirty times a second is a netcode project the rest of the genre never had to attempt. Reckon on a project to something you can actually play — not to something that matches the 250 team-years Epic Games spent.
What makes Fortnite Battle Royale hard to rebuild?
A global build grid and a support flood fill really are a weekend; replicating a hundred people rewriting the level thirty times a second is a netcode project the rest of the genre never had to attempt. That is why it sits at BRUTAL rather than a tier either side of it. If you want the idea without the project, the transferable part is scenery as inventory — a weekend of work.
How long does it take to build a Fortnite Battle Royale clone?
Wrong question, and it is worth saying why. Nobody rebuilds Fortnite Battle Royale — the original took Epic Games on the order of 250 team-years, released in 2017 on PC. What you can do is reach something playable and genuinely yours in about a project, 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 Fortnite Battle Royale?
A hundred players building structures in real time, replicated — a networking problem the rest of the genre does not even have. Live service: a new season every ten weeks, forever, operated by hundreds of people. The crossover licensing and the concerts, which is what the game turned out to be for. 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.