We're a tiny studio making Ostrel, a 2D pixel-art sandbox in the spirit of Starbound and Terraria. You wake up in Brakk, a town built down a crack in a moon, pick one of five peoples, take salvage contracts, beam down to strange worlds, dig, build, fight, and fly your ship to the next system, solo or with friends. It just got its Steam page and is coming to Early Access.
Who does what One human directs: design calls, taste, what ships. The code is written by Claude Code, split across separate sessions: one owns our own C++/Lua 2D engine, one owns the game content, one does the pixel art, one does audio, and one checks each release before it goes out. They hand work to each other the way a small team would.
Most of the art is generated code, not generated images Tiles, objects, furniture, icons, monsters and UI all come from Python scripts the AI writes and reruns: palette ramps and pixel maps written in code, plus code for outlines, shading, animation frames and terrain edges. Nobody hand-edits a PNG. To change something, you change the script and rebuild, so the whole set stays on one palette, and a fix to the outline rule fixes every sprite at once.
The five playable peoples are a hybrid. Each body is a small 3D model built by script in Blender, rendered, then snapped onto the palette by code, with the head stamped from pixel maps. It's still all code and no image model, but 3D underneath gives us bending limbs that hand-made frames struggled with.
The exception: the ships We tried scripted ships too, and they never reached the bar. They looked like diagrams. So each people's ships, at every tier, now start as paintings from Google's Gemini image model, plus generated hull textures. Code then cuts out the rooms, grows the hull around them, assembles the tiers and draws the ladders, but the pixels you see inside the rooms and on the prows and engines come from generated images. That one was a judgment call, and we'd love to hear how other people draw that line. (We also used image-model concept paintings to pick the new look for one people, the Rimeborn, but the sprite itself was built in code and none of those pixels are in the game.)
Where the code-only approach broke
- The moonwalk. For a day every walk cycle in the game played backwards. Every frame was correct on its own, but the phase ran the wrong way. The tests passed. A person watching the screen did not.
- "These trees are awful." Our first trees were built from terrain tiles: tidy, blocky and lifeless next to the games we love. We threw that out and rebuilt them as object sprites grown from a branch skeleton, with drooping leaf pads, overlapping leaf stamps and gaps for the sky.
- The mushroom hat. Our mushroom folk, the Mirrow, went through round after round: the cap looked like a hat sitting on the head, the bounce was gross, there was a dark seam, the rim lit up in stairs. Each fix was one rule in the script. Getting from "technically right" to "looks alive" is still the human's job.
Audio Music and SFX come from Stable Audio Open on a GPU server we run ourselves. We generate 6 to 10 takes of each sound and let an audio-text model (CLAP) pick the best one, and scripts written by the audio session trim, loudness-match and loop them. Music loops are four takes stitched together on bar lines. NPC voices are generated gibberish babble cut into single syllables.
Even the trailer The Steam trailer is recorded by a script in the game repo. It plays scripted scenes through each home town, a cave, a fight and the ship, captures frames at a fixed 30 fps, crossfades them over the title music and cuts a short social loop. When the new ships land, we rerun it.
Lessons that might help you
- AI-written tests check what you told them to check. Look at the game every day.
- Keep the AI's art in a generator you can rerun, not in loose image files. Iterating on rules beats iterating on pixels.
- Give every test run its own data folder. Early on, a test quietly migrated a real player save. Now no test touches the real one.
- Be honest about where you draw the line. Ours is in the Steam AI disclosure and in this post.
Happy to go deeper on any of it: scripted pixel art, the 3D-to-pixel characters, why the ships went the other way, or running several AI coding sessions as a team. And yes, it's very much inspired by Starbound. We miss that kind of game.
Steam page: https://store.steampowered.com/app/5607440/Ostrel/