Tag
19 pages tagged “Game design”.
19 pagesClear filters
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 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.
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.
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.
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.
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.
genevieve__h built a voice D&D table where Gemini 3.8 Live narrates, rolls dice, draws scenes and updates the character sheet while it talks. Here's the tool-calling structure, scene continuity and state handling, and how they carry over to a voice NPC of your own.
genevieve__h made a 3D fruit fly spend calories on CS:GO cases; across 1,000 runs, every fly starved. We break down the urge threshold, the case economy and the loss-chasing loop, and how to build a satire toy like it.
An indie developer revisits an RTS side project built with no goals, just to practise. Its "INCOMING!" panel uses a second camera to show off-screen events without stealing the main view. How to build it, and what it costs.
Three minutes of gameplay from a hex-tile island builder made with Opus 5.5. We break down the cards, the placement preview and the objective chain so you can build a small version.
An indie action roguelike rebuilt its damage numbers into four distinct tiers: normal, big, crit and element reaction. Here's the tier logic, and how to build and tune the same system with an AI coding model.
An indie action roguelike plays a burst build and a control build through the same 23-enemy room. Here's why that comparison works, and how to run it with an AI coding model logging the numbers.
The new boss in an indie action roguelike marks its hits with red ground circles and rings the arena with fire orbs. Here's the attack rhythm, the HP budget, and how to build a tunable boss state machine with an AI coding model.
An indie action roguelike's archer pulls enemies into one spot with Gravity Shot, then wipes them with Lunar Beam. Here's how a setup-and-payoff combo works, and how to measure and tune it with an AI coding model.
When players build their own combos, every attack has to flow into every other one. From a 10-second editor clip: how many transitions that means, why stance is the real variable, and how an AI model can test every pair.
A follower suggested grenades; the developer answered with an 8-second clip and one rule: bombs work, but they are scarce and come from three sources. The design logic, and how to hand it to an AI coding model.
How the five steps to join Claim Avenue live inside the world: a two-door intro, key hints per mode, open plots shown on the street, and a fallback when WebGL fails.
What sits behind Claim Avenue's biggest update: day-night and weather computed from a shared clock instead of pushed by a server, capped position updates, and a world that slows itself down under lag.
