Tag
21 pages tagged “Devlogs”.
21 pagesClear filters
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.
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.
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.
A Manager session on top, one session per game system, and a log that tags every design decision as USER or AI. Here is the workflow behind a fishing game with a public demo.
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 adds co-op: two heroes clear rooms, pick loot and fight big enemies, with a debug panel showing room and player count. Here's the structure, and how to add co-op one feature at a time with an AI coding model.
An indie action roguelike's archer turns into a Dark Elf inside a burst of purple shards, with a 60-second timer. Here's the swap, the timer and the palette, and how to build the form as a clean enter/exit state 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.
An indie character-action game answers an X trend with four lines of dare copy and an 86-second gameplay cut. How the copy is written, how each line gets a shot, and what the order and length cost it.
Eyes of the Sky posted one 32-second cut twice, a day apart, changing the caption and the trend it rode and dropping the opening banner: 1,161 views, then 4,170. What that comparison shows, what it doesn't, and how to get more mileage from one master.
An indie action game's entry in the 32-second promo trend: day, purple night and a dark courtyard, one in-game-style banner, one shatter transition. The structure, and what the missing end card costs.
On the playtest's last day, Eyes of the Sky posted a 60-second cut that argues in four banners (live, limited, help us, store page) and a post that names exactly which players it wants. The structure, plus the missing link and closing time.
Testers told Eyes of the Sky its air combos felt static, so the developer recorded the same fight with and without pushback and asked X to pick. How to capture a one-variable comparison, how pushback is usually built, and where labels and walls get in the way.
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.
In a 32-second clip the hero runs through the combat gym and barrels, jars and tables burst as he touches them. What probably causes it, and how to decide whether to fix the bug or keep it as a mechanic.
A 9-second Unity editor capture: 600 health points gone to a squad of archers in about 0.6 seconds. The useful habit behind the joke: a grey-box gym, time-to-kill, state logs, and test scripts an AI model can write.
In 8.6 seconds the hero jumps into a forest stream and goes down under a volley of arrows. The meme doubles as a clear death-feedback chain: direction, damage, cause, pause, verdict, fade, and how to have an AI model write it as one script.
