God game / voxel simulation
One-Hand Voxel God Game With Proven-Winnable Islands
Tested with Claude · produced HANDFUL: Island God Game
The Prompt
Build a 3D voxel god game in ONE self-contained HTML file (inline CSS/JS). Three.js from a single pinned CDN import is the only library; all terrain, materials and effects are procedural. No external models, textures or audio files. The core verb (one hand): - The player has exactly one interaction: hold on the terrain to grab the material under the cursor, drag while holding, release to pour it. No tool menu, no build palette, no second action. - Grab a sphere of roughly 600 voxels at a time (radius about 5 cells), rendered as a floating clump that follows the cursor and casts a soft shadow on the ground so the player can aim the pour. - Pouring fills empty or replaceable cells gravity-first, from the bottom of the clump upward. A pour must never leave floating material. - Desktop: hold left mouse, orbit with right-drag or A/D. Mobile: one finger grabs and pours, two fingers orbit. Portrait and landscape both playable. World and simulation: - An island of roughly 8 million voxels on a 256x128x256 grid. Only surface cells and a shallow shell need full simulation: use a heightmap plus a sparse delta layer for edits so memory stays inside a phone budget. - Materials: air, sand, dirt, stone, grass, wood, sea water, lava, fire, steam, rain, cooled rock. Interactions live in one small rule table: water flows downhill and levels; lava + water -> stone + steam; fire spreads through wood and is put out by water; steam rises, condenses and falls as rain; sand collapses past a slope limit. - Run the simulation on a fixed tick (about 12Hz) decoupled from rendering, and keep cost bounded: simulate active cells within a radius of recent edits, plus the ambient tide and weather. - The sea has a slow tide cycle, so a causeway built at low tide can be lost later. Campaign: - 24 islands, each with a village, a glowing beacon and one clear problem: a broken causeway, a flooding valley, a wildfire, a volcano, a drought, a wall that must be opened. - Villagers pathfind to the beacon automatically the moment a walkable route exists. Never require a start button; the level reacts to the world. - Prove every island winnable: write a headless bot that uses the same grab-and-pour interface, not a cheat API, and can solve each island. Fail the build if any island has no bot solution. - Three-star scoring based on time, villagers saved and material moved. Unlock the next island on any win and show the star thresholds before the player starts. - A sandbox mode with an endless volcano and no scoring, available from first launch. Presentation: - Low-poly voxel look with flat lighting and a readable palette: blue water, black cooled rock, orange-hot lava, green grass. Keep the horizon visible and never hide hazards behind UI. - HUD: island number, stars, a small tide meter and a reset button. No minimap. Testing and delivery: - Run a headless solver over all 24 islands and print: solution time, voxels moved, whether the solution survives one tide cycle, and any island requiring more than three times the median moves. - Report frame-time p95 at 720p on a mid-range phone, peak memory, and the active-cell count during a large lava flow. Deliver in stages: heightmap island and grab/pour first, then water, then lava/fire/steam, then villagers and pathfinding, then the 24 islands, then stars and sandbox. Print the material table and the solver report at the end.
What This Prompt Produces
HANDFUL is the reference: one grab-and-pour hand, an eight-million-voxel island, emergent water, lava, fire and rain, 24 islands each proven winnable by a bot using the same hand, and a sandbox with an endless volcano, built with Claude Fable 5.2 and Claude Code. The winnability bot is what keeps a physics sandbox from becoming a physics toy.
Modification Tips
- Give the player one verb and make the world do the rest. Every extra tool dilutes the fantasy of being a hand rather than a cursor.
- Prove levels with a bot that uses the real input. A solver with cheat access can approve islands the player can never finish.
- Simulate only active cells. A full-grid voxel update is fine on a desktop and fatal on a phone.
- Make the tide matter. A build that can be partially undone later turns a one-time puzzle into a decision about margin.
The Game This Prompt Produced
Want to try it? Open Claude, paste the prompt, and you'll have a playable game in minutes. When you're happy with the result, submit it to Daily AI Games.