Tag
40 pages tagged “Games”.
40 pagesClear filters
Stefan rebuilt his childhood favourite, F-Zero X, as the browser racer ZERO-G with AI in two days, and it was played 1,000+ times. Here's the asset pipeline and the design that makes people finish a race.
Stefan is building the strategy game he has wanted for 15 years with AI. Day 20 adds a golem that hides as a pile of rocks and a tavern where you hire fighters. We follow the golem from reference images into Unity.
genevieve__h from Google AI Studio turned photos of her home-office desk into a kart racing game with Gemini 4 Argon, Blender MCP and Three.js. We rebuild the method frame by frame.
Sac built a planet-by-planet 3D Little Prince with Opus 5.5, Tripo and Blender, playable in the browser. Here's the asset pipeline and how the scenes are organised.
Tesana says a user's space game, made with a few prompts, went from 2.5M to over 3M views in just over a week. Here's how it added a Ring world and multiplayer without breaking what already worked.
A fox-eared scout runs, launches off Wind Springs and glides between floating islands. We break down how the movement set becomes the whole game, and how the collectibles feed it.
A fill-in brief you paste into a coding model at the start of a game: loop, controls, rules, camera, feel numbers, scope cuts and acceptance tests, plus working rules that make it ask questions first, plan milestones and build one verified step at a time.
A four-part prompt set for the play → report → fix loop with a coding agent: session rules, bug and feel report templates, and a verify step, so every round is one small diff checked against one number.
A fill-in prompt that turns a description of your game into a trailer shot list: timecodes on the beat grid, gameplay or camera for each shot, captions, music cues and a capture checklist.
Write a one-page spec (core loop, controls, win and lose, camera, scope limits, acceptance tests) before you prompt, then build in small milestones you verify by playing. What goes in the spec, how big a step should be, and when to restart.
How to make the 30–90 s trailer or gameplay demo that most of the AI-made games we studied were posted with: clean 60 fps capture, in-engine camera paths, a hook in 2 s, a cut on the beat, captions, and 16:9 plus 9:16 masters.
How to brief AI music, SFX and ambience, build seamless game loops and stingers, sync sound to cuts and gameplay events, hit platform loudness targets such as −14 LUFS, and avoid licensing traps.
Shot sizes, camera moves and lenses in the exact words video models follow, when each move works, and how to build the same move with a Unity, Unreal, Godot or Three.js camera.
Turn playtest words like floaty, slippery or weak into measured numbers (acceleration and stop times, coyote time, input buffers, camera damping, hit-stop, screen shake) and tune them with an AI model one or two values at a time.
The full path from one concept image to a game-ready 3D model with Tripo, Meshy, Rodin or Hunyuan3D: input image rules, picking candidates, decimation and retopology budgets, UV and texture fixes, scale, pivot and export.
How to split game work between separate AI agents (planner, builders, playtester, reviewer), connect them with task cards, hand-off notes and screenshot evidence, stop them undoing each other, and keep token costs in check.
How to turn photos of a real place into a playable level, with a desk race track as the example: capture and scale reference, blockout, modelled, generated or scanned props, collisions and the racing line, and lighting that keeps the real look.
The release checklist between a playable prototype and a link anyone can open: WebGPU-to-WebGL fallback, a loader that paints in under a second, progressive loading, touch and performance on phones, hosting, link previews and publishing on OpenDrama.
The seven layers that take a Three.js scene from flat tech demo to a console-grade image: colour management, tone mapping, HDRI lighting, one shadowed key light, fog, bloom and lens, with the frame-time cost of each.
Tesana says a user built this fly-to-any-planet game from one prompt plus an image reference. We look at what that single prompt has to carry, and what it can't.
Tesana says Aestra's first build took one weekend. We break down how it makes permanent death harsh without driving players away.
lxfater had a locally hosted ~100B-parameter model write the code, Tripo3D make the car shells and Godot hold it together: a Mini 4WD game with car select, swappable parts and races, in one day.
Stefan Vaskevich opens the local workspace he makes games in: chats beside project pages, saved skills, MCPs for the engines, and a 36-hour Unity run documented card by card.
The Eyes of the Sky developer posted 93 seconds of himself getting hit. What the frames show about attack warnings and damage feedback, and why difficulty should be tuned from damage logs and fresh players, not from the developer's own hands.
