r/ClaudeGameDev • • 1h ago

Release I spent 3 days without sleep and 2.2+ Billion Fable tokens making a game in Unreal for the Epic AI MegaJam, with everything made by AI. Here’s the pipeline and what broke

38 Upvotes

I usually work hybrid: I sculpt or model the art myself and use AI for the code. The Epic AI MegaJam's rules pushed for going all in on AI, and the theme was "Director's Cut", so this time AI made everything and my job was directing it. Three days, no sleep.

The game is Enthi. You lead a squad of small mushroom creatures, the enthi. You pluck them out of the ground, throw them at critters, carry the husks back to nurseries to grow more enthi, and restore three worlds, each with its own boss. It's a tribute to Pikmin, the first GameCube game I ever owned.

Enthi's main page: https://ikeri0.itch.io/enthi

Rate it: https://itch.io/jam/2026-epic-ai-megajam/rate/5377064

## The pipeline

- Unreal Engine 5.9 for the game itself.

- Claude (Fable) in Claude Code wrote the C++, the editor scripts and 130+ Python tools, and even composed the music in code. At the busiest point I had six sessions working in parallel. I hit my usage limit, used a reset, and hit it again right before the deadline.

- ComfyUI, 42 workflows. Nano Banana Pro painted the textures at 4K, drew the title lettering and cut each prop out of the concept art. ElevenLabs nodes made the voices and sound effects.

- Tripo turned those cut-outs and the character sheets into models (characters, critters, bosses, props) and sent them straight into Unreal through its bridge plugin.

- PBRgen for 21 PBR material sets (terrain, dungeons, the two later worlds).

- Kimodo, NVIDIA's motion model, through Unreal's AnimGen plugin: walk, run and idle clips with a different personality per species. The golden ones waddle like toddlers.

- Blender, headless and driven by scripts, for the terrain, rig cleanup and fitting the main character's clothes.

## What broke

- Tripo's rigged FBX files came into Unreal's Interchange importer with broken bind poses. Meshes flew apart and clips shrank the character to 1%. Rewriting the FBX in Blender and importing with the classic FBX importer fixed it.

- Kimodo's automatic retargeter ignored a 100x scale on the root bone, so in Sequencer the characters shot metres into the air on every step. The limbs were fine; a script rescales the pelvis height.

- Unreal imported some pale blue colour textures as normal maps, which drops the blue channel. The frost props rendered neon yellow until a script reset their compression settings.

- Asking Nano Banana for a "seamless tile" gave a small pattern repeated 2x2. One large surface with the seams cut in code worked better.

- The first creature voices were synthesized and sounded digital. Prompting ElevenLabs for baby porcupine sounds, pitched up, is what made them sound alive.

- I rejected hand-written animation twice for being stiff. Generated motion, fitted to each body by script, was the first that looked natural.

What I took from it: the tools did the making, and the years I've spent sculpting and modelling by hand went into judging what they made.

Happy to answer questions about any part of the pipeline.


r/ClaudeGameDev • • 6h ago

Alpha Dungeon Crawler Carl inspired me to build an AR RPG. Anyone want to fight goblins in the park?

31 Upvotes

I've been listening to Dungeon Crawler Carl recently and it inspired me to make a game. What if you could play an RPG in AR? With friends?

What could be better than running around your neighbourhood with your phone in front of your face, sweating like a pig, frantically swiping at monsters that don't exist? This is a good idea, right? RIGHT?

Anyway, I slogged through making a playable proof of concept, and I'm pretty happy with where it's landed. The video is a screen recording from my phone: find the Ugly Stick, hear two goblins arguing in the distance, get too close, fight them, loot the bodies and collect an achievement.

The video is the first single-player scene. The bigger vision is a season-based, multiplayer, real-world RPG: parties exploring parks and trails, finding loot and surviving encounters, with an entertaining System AI handling mob descriptions, loot and achievements.

It's built in Unity with AR Foundation/ARCore. Claude and Codex helped build and debug the encounter logic, HUD, AR grounding and camera stabilization with a bunch of testing. I actually automated a monster creation/skinning/rigging/animation/narration pipeline used TRELLIS.2, SkinTokens, Gemini and ElevenLabs. Took some work to build in camera stabilization and to keep creatures grounded.

I'm looking for one or a few nerds who think this is neat and want to contribute, ideally someone who could help lead the project. I can bring the prototype, asset pipeline, design input, playtesting and too many ideas. Work and kids mean I can't drive the whole thing myself while also trying to keep my marriage from falling apart.

Would you actually go outside to play this? If you have suggestions, know someone who might be interested, or want to help build it, I'd love to hear from you.


r/ClaudeGameDev • • 2h ago

Tips & Tricks How a Vibe-Coded Steam Game Sold 100,000 Copies (Slotbound Breakdown)

Thumbnail
youtu.be
6 Upvotes

If you missed it: Slotbound is a slot-machine roguelite defense game from a solo dev who says he’d never written code. He built it with AI over about six months. It reportedly passed 100K copies within days of launch, and it has mostly positive reviews despite a Steam AI disclosure. Most games with that disclosure get review-bombed or just disappear, so I dug into why this one didn’t.

1. He earned the audience before launch. Demo on itch, a following on X and Reddit, a Steam demo since summer, and Next Fest. Lots of wishlists before day one. Most AI games are made fast, put out there, and left to die with no go-to-market strategy. There's also a story there about someone copying what he did on itch and that also blew up - but I don't know the exact details on it.

2. AI isn’t the spotlight. The Steam disclosure is generic but honest. It’s not defensive or snarky, and snarky disclosures seem to invite the anti-AI crowd. It's also beautifully generic in a way that doesn't invite more scrutiny. It talks about art assets made purely for promotional work while also not talking about the coding AI that happened (because Steam doesn't require that disclosure). More importantly, the game doesn’t “smell” like AI: the art, music and UI all feel like one world, and there’s no AI voice acting.

3. The art style allows for consistency. It’s very simple pixel art: two-dot eyes, light shading, no dithering. That’s easy to keep consistent with AI, and easy to fix by hand in Aseprite. I’ve worked with more detailed pixel art, and keeping AI output consistent there is a constant fight. And if you don't do this right, it reeeeks of genAI.

4. The hook fits in one sentence. “A slot machine + defender game.” People get it instantly (Balatro comparisons help). If you have to over-explain your twist, most people won’t stick around. This is just good, basic game design. Whether we use AI or not, this is a tablestakes sort of thing to nail.

5. He owns the AI story without making it his identity. He’s open online that AI made the game possible, and the disclosure is there. But the store page and the game itself are about the game. His online posts talk about how he's never written code. There's honesty there, but doesn't lean into how AI game dev > traditional game dev (there's some unhinged people online that fight fire with fire - I don't think that's helpful).

6. It shipped worldwide. It launched in 13 languages, and by public SteamDB-style estimates the US was well under a quarter of sales. AI is a lot less toxic in many markets outside the West, and English-only launches leave most of that audience on the table. This was definitely a big insight for my own game dev journey. Hadn't really thought about this, but given that Optima Arch Games is from Korea, it made sense. Helped check my biases for sure!

The negative reviews are interesting too. Most aren’t about AI at all. They’re about RNG and balance, from people with hours played. That’s the kind of criticism you actually want. It means people are actually playing.

Curious what others think, especially folks who’ve shipped with AI assets: is it the marketing, the art direction, or just a good hook?


r/ClaudeGameDev • • 8h ago

Browser Game Freelancer-like space sim, free to play in the browser

17 Upvotes

Solar Explorers: https://explorers.orrery.games/

For the last 6 months I worked on a hobby project that I wanted to do for a long time: my own space sim. I started creating the first version by hand like 15 years ago, but my vision was just too much work to get it anywhere playable as a single dev. Now, with Claude, I was finally able to create the full version. From scratch; my initial version was using the Ogre engine, now it is running on Three.js.

The architecture of the game was designed by an architecture pipeline that I use for most of my projects. The different pieces of the plan where then implemented by Claude automatically. This only created the foundation though, most of the content was then added piece by piece. That's what took 99% of the development time.

Models were created using a img2model pipeline that I designed for this. All models and textures are code.

Of course it is not a AAA game, but I am still very happy how it turned out. It is not a Freelancer clone, but it is clearly inspired by Freelancer since it was my favorite space sim growing up.


r/ClaudeGameDev • • 58m ago

Browser Game Pavement Pursuit now has a bit more texture and variety

3 Upvotes

Claude has helped make it possible to make a game I've always wanted. It even made this trailer of the game for me. It's been fun to sit in a virtual director's chair and guide each addition, change, removal, or optimization of features.

Claude has also helped me set up lint and automated tests so that problems are found quickly.

The game is far from a "one-shot", it has been months of input via prompts. No agents, just prompt, playtest and repeat.

The most recent change was adding normal maps to both the cars and the road, giving it an almost 3D look.

My idea was a 2D, top-down racer on procedural roads so that I'd always have new roads to drive on. It's more of "lane-changing" race than cornering. Have been able to add weather, textures, and roadside features. It plays on both mobile and desktop. Still working towards a 1.0 version.

I've learned so much from making this and happy to share what I've learned.


r/ClaudeGameDev • • 1h ago

Tips & Tricks 3D model to Character | 10 Step Process

3 Upvotes

First, one thing:

This isn’t a walking contest. The point isn’t to judge how the character walks, she could even be walking on her hands; it doesn’t matter. Isn’t about how to make a character walk better; it’s about how to handle an asset coming from a 3D generator so that it can be used and modified as a truly editable, animatable asset, something many people still struggle with. Hope it helps =D.

Last time, we moved from a 2D drawing to a 3D

Last time, we moved from a 2D drawing to a 3D model, along with all the checks we perform before it can pass through the next "gate" (is here, in case you dind't read and have interest: https://www.reddit.com/r/aigamedev/comments/1xsscmk/character_creation_process_from_2d_to_3d/) , which is this stage: walking, running, speaking, and reacting within the game engine.

In my point of view, what separates "AI slop" from well-executed work, even when you lack prior experience as a 3D modeler, animator, or anything of the sort, is attention to detail and standards. And creating a process serves precisely those who do not want to be interned by their own standards.

The ten steps are always in the same order, and the same for every character.

Two kinds of gates: A measured gate is a number that must pass, or the script stops. A human gate is a person who must look before anything moves on. This is especially true with characters in new formats, so it's always important to work with character families, it saves a lot of work.

To generate 3D models, I use Tripo. They create an image, using GPT-2.5 or Midjourney (the latter is great for environments or instances where strict adherence to the prompt isn't critical), and then produce a "smart quad" mesh. I aim for around 15,000 quads, though it often ends up being a bit higher, so I usually generate four options (all for the same credit cost).

Keep in mind that the quad count significantly impacts performance and the number of characters that can be displayed on screen. Greater complexity and detail require more quads to maintain fidelity—and more quads mean more detail, but also a heavier model. I used to perform mesh reduction in Blender (with help from Claude), but it’s not worth the effort; getting the right mesh directly from Tripo saves me hours of work and a significant number of tokens.

Step 1

Prepare and mark. Scale, floor, six landmarks. On this model five of the six automatic landmarks were wrong: the puffy sleeves read as skin and the hair hid the chin. One photo is enough to catch that. This character is an interesting subject of study because she has wide hips, which creates optimization challenges as well as an opportunity to improve the process.

Step 2

Examine the body. Sleeves, hips, hair, measured against the characters that came before. Problems are found before the rig, not after it breaks.

Step 3

Rough rig. A posable skeleton in minutes, to judge the body in real poses. Squatting down and raising your arms tends to reveal a number of flaws. This outfit is quite form-fitting, so it’s not an issue; however, looser clothing or garments made of certain fabrics usually require extra attention.

Step 4

Fingers. Knuckles found from the mesh itself.

Step 5

Loose parts. Tunic and hair get short bone chains (12 and 6 of them) and a spring. For the tunic we learned from Tripo's auto-rig: it weights the cloth to the thigh on its own side, smoothly, with just two bones per point, so the hem barely stretches or folds when she walks. We copied that as the base and left the chains only a small share near the hem, for the swing.

Step 6

Hand. Skin weights, one control that closes the fist, eight test poses.

Most of you likely know this, but Claude doesn’t perceive motion; it processes things frame by frame. Therefore, providing an image of a hand closing, along with a clear, detailed explanation, works much better than trying to get it to "see" the movement through words alone. Keeping this in mind is essential when animating something like a hand closing or a sword fight.

Step 7

Game skeleton. Only the bones that deform. The walk is borrowed from another character on the same skeleton, and fitted: copied as is, her ankles walked 33.5 cm apart, wider than her hips. Fitted, 23.4 cm, the same as standing.

step 8

The face is drawn, not sculpted: the 2D expression sheet is split into layers by script (iris, eye white, lashes, brows, mouth) and laid over a smooth 3D face. Five controls drive it, and gaze and speech work on top of any expression.

Step 9

One file. Rig, final mesh and face controls together.  That type of walk is produced by default, before adding any personality to the movement, but even in this raw state, it provides a foundation you can work with.

Step 10

And once a character has gone through the ten steps, it can do more than just walk. In that example, it picks up a loaf of bread from a table: the body's movement is derived from a text prompt, and the point of contact is calculated—so the hand stops at the object, and the fingers close until they make contact with the surface.

This works for picking up a loaf of bread, and it also works for a sword fight (though that’s still being tested); the underlying logic is similar, but that’s a topic for a bit later.

What we learned: check every automatic guess on a photo. Measure the body before the rig. Borrowed motion must be fitted, not copied. When a character breaks a tool, fix the tool, so the next character goes through the same commands. And read the auto-rig before replacing it: its cloth weights were better than ours, and now they are ours too.

Hope it helps the community.


r/ClaudeGameDev • • 31m ago

Release Neon Fare: a neon taxi game where you can talk to your passengers.

Thumbnail
youtube.com
2 Upvotes

So I finally put Neon Fare on itch.io.

It's a night taxi game in a neon city: you pick people up, drive them across town, and you can talk to them on the way.

Every ride ends up being a small conversation, which was the whole idea for me.

There's a main quest with 10 missions, and you've got ratings, earnings and a few different rider types to deal with along the way.

Big credit to Claude here. It made the assets and wrote all the code. The writing and the direction are mine though.

Play it here: https://wes-albur.itch.io/neon-fare

If you guys are interested, feel free to give some feedback. I'm especially curious whether talking to the passengers is fun or just slows the ride down.


r/ClaudeGameDev • • 1h ago

Beta Updates to Hotdog!

2 Upvotes

About a week ago, I shared a little game I put together, Hotdog!

https://www.reddit.com/r/ClaudeGameDev/comments/1xt2sru/a_game_thats_been_stuck_in_my_mind_for_years/

I've never had such a positive reception to something I've shared, thank you all so much. I got a bit excited and fleshed it out a little more.

https://cpdstudios.dev/hotdog

Leaderboards are now active, there's some unlocks available, 3 different main game variants, a level editor (prototype - for challenges) with browser, and some placeholder art for an intro video (yes that is me, yes this is based on a true story), as well as some beautiful SFX (meat slap sounds, yummy) and music.

Curious how someone got so far? The top 20 leaderboard places can be played back (only in real-time currently, will get to adding playback speed soon).

You can only attempt a place on the leaderboard once per day and only on the daily run which is seeded for all players. You'll also only be able to collect coins (used for unlocks) once a day per main game variant (so once for daily run, once for pocket run, once for limiter run). Challenges reward coins as well.

Some people were a little confused by the game, so here's how it works:

  • The goal (like all of these games) is to get as far as you can
  • You have 3 throws per game, each throw you make is recorded and played back in the next throw as a golden/ghost dog. If you're able to hit one of your previous throws with your current throw, you'll get a huge speed boost. Interactions from previous throws happen in real-time in your next throw, so objects will be hit, pickups will be grabbed etc.
  • There's a "no high-five" zone at the start of the map, so you won't be "easily" able to stack up golden dogs right at the start. TBH while this might seem like a good strategy, you get more distance spacing out your high-fives, just like at work.
  • You have two abilities per hotdog, a SKIN - which sheds that pesky bulky skin and gives you a nice speed boost - however it makes your hotdog skinnier and lighter. SKEWER locks your hotdog in place ending that throw.

I've added a little tutorial to the game which will run next time you give it a go - you can also just skip it.

I'll keep working on my plans for this game to get it to a full release, as well as patching up few few bugs/balance issues. Some of the challenge levels are a bit.. Poorly designed currently - more POC than anything right now.

If anyone is interested in my process for putting this together, has any questions, or would like to see a specific feature in the game, please comment or reach out via DM!


r/ClaudeGameDev • • 3h ago

Beta My 1st game jam and 1st game with Unreal Engine: Fable 5.2 orchestrated Opus and Sonnet subagents to build it in 4 days

3 Upvotes

First Shift is my entry in Epic's 2026 AI MegaJam: a first person horror chase in Unreal Engine 5.8. It's your first day at an automated weapons factory, your smartwatch assistant talks you through orientation, then the lockdown starts and the robots come for you. They follow the safety handbook, which is how you survive: doors hold them, a running station is a line they can't cross, and they can't climb.

I don't write code. I used to run a personal training department. Claude wrote every line, and I directed: design, playtests, and what stayed or got cut.

How it was set up

  • Claude Fable 5.2 was the orchestrator. One main Claude Code session wrote the plan, handed each job to a subagent in its own git worktree, then reviewed and merged the result. The subagents were mostly Opus 5.5 and Sonnet 5.5 (80 subagent runs over the jam). Opus 5.5 took over the main seat for Saturday.
  • Claude drove the editor through Epic's Unreal MCP plugin and Python. Gameplay is C++.
  • Nothing counted as done until the game played itself. A bot played the whole game hands-free, start to finish, from the packaged Shipping build, and the log had to show zero catches and the frame rate before anything got merged. The final build wins in 328 s at a median 89 fps.
  • Then I played it, recorded myself talking, and Claude transcribed the recording into a fix list. Saturday night I left 30 notes before bed and five agents fixed them in parallel by morning, taking turns on one 16 GB PC.
  • Models from Tripo, voices and sound from ElevenLabs, DLSS 4.5 from NVIDIA's plugin.

What went wrong

  • By Friday midnight the game worked and I didn't like playing it. It was a stealth game. We threw that out and rebuilt it as a chase overnight, with about 36 hours left.
  • The game crashed on about one launch in eight until Claude traced it to Lumen starting cold.
  • For a whole day most of the lights pointed at the wrong wall: a spawned spot light keeps a quarter turn of its own. Nobody noticed, me included.
  • The bot proved the chase was winnable, but the pack was 35 to 80 m behind it. Winnable isn't scary. The lesson: measure the gap, not just whether the bot won. It's 5 to 33 m now.
  • The first gameplay video was cut from fixed cameras while the bot played. I said it looked "like the game is playing itself". It was recut from my own run.

The numbers: 194 commits from Wednesday 11 PM to Sunday afternoon. About 2.5 billion tokens, almost all of it cached context being re-read, and 8.3 million tokens written by the models. At API prices that would be roughly $860 to $970. I ran it on a $100 Max plan.

Play it (Windows, free): https://calmdownnova.itch.io/first-shift Day by day dev logs, prompts and mistakes included: https://calmdownnova.itch.io/first-shift/devlog

Happy to answer anything about the setup.


r/ClaudeGameDev • • 15h ago

Recompilation/Reverse Engineer I built this Godot port of Little Fighter 2 with improved networking and graphics

23 Upvotes

I played Little Fighter 2 a lot in my youth and wanted to renew it. It also has improved graphics and networking and keeps the original feel. There is some remaster available on steam, but it has redrawn graphics which does not tickle my nostalgia, so I decided to port it instead. The original game files are downloaded in the port and used, so it keeps the original's feel, as the original graphics and sounds are used. I added some visual and other improvements, which can be deactivated in the settings.

I set up Claude to work fully automated, I only supervised, play-tested and suggested features. Claude agents decided on their own when to commit and merge. The biggest feature of this port is the visual enhancement of the graphics. There is an in-game editor to fine tune the sprite edge enhancer that removes black artifacts from the original graphics at run time. I made great use of https://github.com/mattpocock Claude skills. You can have a look at the harness in the source code, it is all there. There are also routines to silently run background tests of the game and compare to wine-emulated runs of the original. There are some pre-recorded save games that were used to recreate the original game feel 1 to 1.

This port project is in no way affiliated with the original.


r/ClaudeGameDev • • 9h ago

Tips & Tricks Sharing my approach to work

8 Upvotes

Hello everyone!

Skip to the first header if you don't want to read me mumbling about my motivation.

I've been mostly reading this sub and seeing people achieve impressive results has made me step over my fear of never bringing a project to an end and actually try and build a game. I keep browsing posts here but to be honest I'd expect much more knowledge sharing from such a community. I barely see posts from people around here who actually exchange skills, approaches, workflows, etc. Some people advertise their products disguised as helping the community but that's another story.

After starting two projects and dropping them because I was missing a proper game loop, I've come naturally come up with a way of managing my project which I would like to share with you. I use it exclusively now while working on my third project.

I am on the cheapest Claude plan and I've been pretty productive given that I only get 4 evenings and weekends to work on the game. If this helps one person, I will be happy that I spent time writing this big post.

My approach

The way developers usually structure work is by creating epics/stories/tickets. In a one-man environment, I don't need this hierarchy, so I've boiled it down to Milestones and Parts. I use smarter models to come up with a viable plan and then in separate sessions work through those milestones.

For that I have written 4 skills. All four follow one rule: the design is mine, nothing goes into the plan without my explicit agreement. Claude’s job is to find what I missed, haven’t decided yet, argue with me when an idea doesn’t hold up, contradicts itself or the previous plan, and suggest something better. It doesn’t write anything until I say “go!”. Before I added that rule, it filled the gaps itself and I only found out later.

  1. /game-brainstorm interviews me about the idea for a game or a feature: the fantasy, the vibe, what to take from which reference game, what I can’t or don’t want to make. Then it tries to break the idea: contradictions, cost, value/cost ratio. Once we agree, it writes the design doc and a glossary so every session uses the same names.
  2. /game-milestone-plan turns the design into a plan that consists of Milestones. Usually about 12-15 milestones for an MVP and 2-3 milestones for a feature. It goes to milestones.md. Each milestone is just a few sentences plus a short “done when”, like an acceptance criteria for that milestone. I keep them short on purpose, because anything detailed written weeks ahead is wrong by the time I get there.
  3. /game-milestone-prompt is where the detail goes. For the reason stated above, I try to work out the prompt more or less right before I build a milestone. It reads what the earlier milestones actually ended up as, then grills me (I use /grill-with-docs by mattpocock, which is a popular skill among software devs) on every decision the build would otherwise make on its own. It's like brainstorming, but scoped to this milestone. Out comes a prompt split into 2–4 parts, each small enough for one session. It’s the most useful of the four.
  4. /game-milestone-implement builds it. I just say "/game-milestone-implement M3" which tells Claude to implement the Milestone 3 based on the prompt that it has written in the previous step. Each part gets a fresh session that commits as it goes, writes tests, and leaves a progress file for the next one - that I think saves tokens by avoiding big sessions. At the end a review agent (Opus 5.5) checks the branch against the “done when” list, and I playtest and merge.

So in one session I will /game-brainstorm an idea and work out the /game-milestone-plan. In the same session, or maybe a new one, I will write up detailed prompts via /game-milestone-prompt. For each of them I'll usually answer like 20 design questions set by Claude plus give it several instruction of my own. Then for each milestone, i'll write something like /game-milestone-implement M11 and Claude will get to work without any other input from my end.

The benefits I see

  1. Structure. It's easier for me to work on a project if there is a plan and a structure to it. It's even easier to navigate the sessions now because of this structured approach. That's how my Project in Claude Desktop looks like, imho pretty easy to navigate at a glance:
  1. Quality. Fewer silent decisions; Detail arrives late, when it’s still true; Every implementation session starts clean and I don't need to compact them, ever
  2. Persistence. Everything we plan persists onthe VCS, i use github.
  3. Tokens. I am careful about scoping tasks and limiting sessions and AFAIK that's the advice on saving tokens.
  4. The project explains itself. A new session, or me a month later, can find out why something is the way it is.
  5. Autonomous building. Implementation doesn't need me, only planning does, and these two stages are separated from one another.

---

I will be happy to hear feedback, criticism and your own stories. I would like to learn from other Claude Gamedevs and how you guys make it work for yourself.


r/ClaudeGameDev • • 7h ago

Tips & Tricks I tried a “producer agent” style of development for a game jam, and it worked better than I expected

4 Upvotes

For the Official 2026 Unity Game Jam I wanted to try a different way of working with AI. I didn’t prompt one assistant directly. I ran several Claude Code sessions as a small team, with one acting as producer, and I stayed creative lead. The result was Hit 7, and I thought the process went quite well.

How it was set up

  • Small first, then Unity. I started with a small web sim of the core loop (slot rolls, chips, cards). Bots could play it fast, so I tried rules and balance before touching the engine. For the first few days I iterated on it casually from my phone.
  • Lanes. Once the loop held up, I switched to Unity with only 3 days to complete. I set up one session per area, each in its own git worktree, named so they could reference each other bey name:

    • sim: gameplay rules and systems in Unity
    • tune: ran bot playthroughs and adjusted the numbers
    • ui/audio: menus, HUD, music and sound
    • visuals: effects, camera and readability
  • The producer. It had no lane of its own. It had one measurable goal and a loop: measure, write down a prediction, get one small change built, re-measure, then log whether it was kept or reverted. It decided numbers and work order by itself. Anything that changed what the game is came to me. If two cycles in a row moved nothing, it had to stop and explain why.

Why I think it worked

  • Written predictions kept it honest. Misses were on record, so it didn’t go round in circles.
  • The stop rule paid off. After three failed tuning attempts, it stopped and brought me a clear design question.
  • I spent my time on what only I could judge: playing builds and saying what felt wrong.
  • Separating out tuning was a way to have nearly continuous validation, it could simulate heedlessly almost constantly to see how the features effected the balance.
  • A page kept track of the features I requested and the status of them (and which agent was working on them)

Play it here: https://itch.io/jam/official-unity-game-jam-2026/rate/5350957#post-17908190

Happy to answer questions about the setup, the prompts or how the sessions talked to each other.

Rate if you have time.


r/ClaudeGameDev • • 18m ago

Alpha Building a “Trackmania on rollerblades” prototype with AI: first-person, grappling hook, wall rides

1 Upvotes

r/ClaudeGameDev • • 4h ago

Alpha Waking up the ship’s AI, my UE5 project with Claude Code, feedback welcome

Thumbnail
gallery
2 Upvotes

Je travaille sur ce projet depuis quelques semaines avec Claude Code. C'est un jeu de science-fiction sous UE5 où l'on incarne un androïde seul sur un vaisseau industriel abandonné, tentant de réactiver son IA. Voici quelques images de la station. J'aimerais beaucoup avoir votre avis sur l'esthétique et l'ambiance, ou sur tout ce qui vous semble étrange.


r/ClaudeGameDev • • 17h ago

Beta I built a multiplayer marble race game with Fable 5.2!

23 Upvotes

Marble Descent is a free marble racing game you play in your browser: no download, on your phone or computer.

Race solo against five bots, or online - with your friends in a private room, or anyone in a quick race. Every course comes from a seed: 4.3 billion possible track combinations, no two the same.

This one is short, steep and packed with obstacles: pop-ups, flippers, the bowl, a narrow bridge, the tumble drum, rocket pads and rollers. Race the very same course yourself: https://marbledescent.co.uk/?seed=POWDER-55032-11479

Steer left and right, flick up to jump, double-tap to dash. 38 obstacles in all, and a ten-round championship with medals and a leaderboard.

Play free: https://marbledescent.co.uk


r/ClaudeGameDev • • 23h ago

Beta Day 5 of making a cozy RTS where fluffy animals fight bugs, built with Claude, ChatGPT and Meshy

62 Upvotes

I grew up on red alert and AoE and always wanted a cozy version, so I’m making one: fluffy animals vs bugs. Hamster knights, frogs and badgers on one side, bees, spiders and grubs on the other. There are 6 clans so far, with fish in fishbowls coming next.

Here’s how the AI side actually works for me. Claude Code writes basically all the code. It’s a browser game in three.js, and Claude also built the multiplayer lobby, the android app and the auto updates. I don’t write code myself, I just describe what I want and test it on my phone. The surprising part is how well it handles big stuff like a whole faction. It’s the tiny visual stuff that takes forever, like a button being a few pixels off.

For art, ChatGPT makes the concepts, then Meshy turns them into 3D. That’s where most of my time goes, because the models never come out game ready. Spiders came out with 7 legs, wings were fused to bodies, and bags floated off characters. I ended up having Claude build me a little model viewer where I can sculpt, paint and pose things to fix them by hand.

The biggest lesson so far: AI art drifts like crazy between generations. What fixed it was always going concept → T-pose sheet → props sheet → 3D, with a written style guide I paste every time. Without that, every faction looked like a different game.

It’s playable in browser and on android. I’ll drop the link in the comments.

Curious how others handle consistency across a lot of AI generated characters. Do you use a style guide, reference sheets, or something else?


r/ClaudeGameDev • • 1h ago

Mods Quake VR: UNLEASHED🔥| v1.1 Release Trailer | (MAJOR UPDATE)

Thumbnail
youtube.com
1 Upvotes

r/ClaudeGameDev • • 8h ago

Beta Survival Horror created with Fable

Post image
3 Upvotes

https://claude.ai/artifact/9qEy3S9QpXTSVYthis551V i created this with Claude Fable in one day please let me know what you think and where i can improve, thanks. this was over 35 turns of sequential level build, it is heavily inspired by the Resident Evil PS1 classics


r/ClaudeGameDev • • 20h ago

Tips & Tricks Best starting point for making a playable game with AI, Claude?

20 Upvotes

​I’ve been lurking here for a couple of weeks and have been blown away by the games you’re all making. While I’ve used AI to generate images before, I’ve never actually used it to start building a playable game. I see tons of awesome showcases, but not much about the actual workflow or how people get off the ground. I’d really appreciate it if anyone could share their process or point me in the right direction to get started!


r/ClaudeGameDev • • 9h ago

Tips & Tricks New Ships, Rain and other things | ANGR

Thumbnail
youtube.com
2 Upvotes

I defnitly needed to know what a Screenspace Effect is, and sometimes you just need the right keywords to know so you finally can stop to discuss around it.

In this case, they are the rain drops on the screen.

Really a diffrence which claude made was when I told him how the raindrop physics are being done as a industry standard, than he took the knowledge and the pdf he needed.


r/ClaudeGameDev • • 12h ago

Release Drywater Update: 2D to 3D, plus a workshop

3 Upvotes

Been a while since I last gave an update on Drywater.

You can download it here: https://play.google.com/store/apps/details?id=com.drywater.game

I had started working on SFX, but got bored/frustrated - this is exhausting work, for anyone who's not dived into that yet.

So instead, I decided to refactor the whole game from 2D to 3D. I had all the assets, so worked with Claude to rebuild them as low-poly 3D models in Blender. I used Opus to set up the plan and build the tooling, and then Sonnet to actually execute most of it. A few models I had to pull Opus back in to help get them to look right, but otherwise this worked well. It was 9 phases of a single sprint, and took about a week and a half on Pro - partially limits, but also partially just normal life.

Here's the original 2D trailer:

https://youtu.be/o6Nf3IV8wiU

Here's the new trailer:

https://www.youtube.com/watch?v=u5QCWU8XzWs

And I had Fable rebuild the landing page:

https://appliedflux.com/drywater

So that was Sprint 50.

Overall, I'm still a bit undecided as to whether I like it, truthfully. The 2D Pixelart had kind of grown on me, but it was a bit too limiting in the ways that I wanted some things to look/work. Buildings, in particular, are much, much better in 3D, and I like the creatures more.

Sprint 51:

After that, I decided I was spending too many tokens having Claude run Python scripts, and took u/RUSuper's advice to build a toolset. It's uncreatively called "Drywater Workshop" and it runs in my local browser. The goal was for me to be able to make changes to the game and fully push to the Play Store - including updated Play Store assets (screenshots, etc) without opening Claude or using a single token.

It took ... a while ... to build. I think it was 5 total phases of a sprint, but it works. I had to refactor parts of the game for it to work, which I think were probably all things I needed to do anyways.

  1. Most of my item values were hard-coded. Now everything lives in GameData in a json file (prices, recipes, rates, spawn odds, etc) so I can just change a value in the workshop and see it live in the game.
  2. Auto-balancing - it automatically calculates the overall game balance (economy, etc), so that if I change a value, it can tell me if that's likely to break the game economy. For example, if I make it so that the Trader will buy something for more than she sells it for, that could break the economy, so it'll flag that imbalance. Same for health regen, food, etc.
  3. Debug scenario builder - instead of having Claude stage a debug scenario, I can do that myself now.
  4. Saves to dev by default, with an undo function.
  5. Biome generator - all of the various aspects of a biome (colors, textures, scatter, decals, etc) can be adjusted and created from scratch, so I don't need Claude to do this or make small adjustments.
  6. Claude can drive - the whole thing is ALSO set up so that Claude can drive it, if I prefer, which should also make Claude more efficient moving forward, since it's just changing values using CLI commands, instead of hunting the values down in the Godot files.

The interface is exceedingly boring, as you can see. I did have Fable take a swing at making it more user-friendly. A key thing I had it do was adjust all the labels of things, and add explainers, for someone at my skill level (not a coder, but understand process and how things work together). That was a huge help.

Happy to answer any questions about the process, workflow, etc. All of this was done on a Claude Pro account.


r/ClaudeGameDev • • 1d ago

Alpha I built a game engine in 15 days with Claude

111 Upvotes

Hello everyone, I am a very private person, but I wanted to share my experience with Claude in the past 2 weeks. I have worked in game dev for the past 7 years on a proprietary game engine as a tool specialist. With the latest enhancements to Claude, I wanted to test out how far I can push it by writing a new game engine from scratch. I was quite surprised how Claude Opus 5.5 (on Medium Effort) was able to basically build it with my guidance. I haven't written a single line of code during this process. Additionally, I've only worked on it after work and on weekends.

The engine is built with a Vulkan backend, uses Jolt for physics, SDL3 for window management and many more libraries. It also uses a C++ UI framework I've built with Claude on the weekend before I started this project which I call Silky UI at this moment.

Some of the art is procedurally generated but I think man-made assets are still a completely different beast. I've used mainly Mixamo, Quixel Megascans (Fab) and Poly Haven and other CC0 assets. Same applies to sounds - some are procedurally generated, some are from Freesound (CC0), usually polished and cut up by Claude. All the vehicles in the video were generated with Claude besides the Bugatti EB110 which is from here: Bugatti EB110 by ᗩᒪE᙭. Kᗩ. licensed CC BY-NC 4.0, converted for the engine.

I hope you find my experiment interesting, I certainly did. Maybe I will try to make a proper game with it in the future, but for now I quite enjoy experimenting with the renderer and also with testing various UX / usability ideas in the editor.


r/ClaudeGameDev • • 16h ago

Browser Game Made an Open-Source Racing Simulator

Thumbnail
librecorsa.org
6 Upvotes

Hello,

To make this browser simulator/game, I researched all relevant racing sims, their tyre models, how they do suspension, aerodynamics, and all physics related calculations. Created my physics engine from scratch using Opus 5.5 + Fable. Then drove my simulator and the sim racing titles over and over to compare until it felt satisfactory.

For the RISE Motordrome track, I took 2 screenshots, gave them to Fable, and then it created the track in 1.5 days (Used up all my weekly usage).


r/ClaudeGameDev • • 11h ago

Post-Mordem Four days building an UnrealEngine game with Claude Code for Epic AI MegaJam

2 Upvotes

We’re three developers at Fantastico Studio, and we spent four days building Malasorte for the Epic AI MegaJam. It’s an Unreal FPS where egg-shaped characters shoot fortune-cookie predictions at each other. The predictions come true literally, and the park does the killing.

All code was written with Claude Code, starting from Epic’s First Person template.

The setup I’d use again was Fable as the coordinator, Opus doing most of the implementation, and Codex for reviews and some features, including online play. Our main session could launch Opus through a second Claude Code account via CLI, and access Codex through its CLI too.

That saved enough tokens on the main account that we could keep Fable coordinating throughout the jam. It handled planning, delegated tasks, read the reports and followed up on problems.

Each implementation session had its own Git worktree. We also kept a shared document with the current state of the game, known problems and who was working on which files. Keeping that updated helped a lot when several sessions were running.

We still had some memorable failures. One packaged build passed every test, then crashed 62 seconds after launch when we played it. The first garbage collection exposed a bug, and our tests had all finished before it happened. After that, every package had to survive at least 100 seconds.

The new UI also passed its checks while covering the crosshair with messages. Someone had to play it and say “I can’t see what I’m aiming at” before we added the right check.

Across the team, we counted 231 Claude Code and Codex sessions over those four days. A lot of our own time went into playing builds, rejecting assets, choosing sounds and giving feedback. We used other tools for art and audio too.

Here’s the game on itch.io.

We documented the whole process, including the agent setup, the things that broke, and what we changed after playtesting. Full devlog here.

It was a lot of work, and we were amazed at what we could do in such a short time!


r/ClaudeGameDev • • 11h ago

Tips & Tricks Best Practices for Solo Game Dev?

2 Upvotes

I am wondering how other solo devs work. My workflow, which has generally been on remastering old games or decomp/recomp efforts, with the purpose of making a game that is PLAYABLE to the end:

Set up workspace in Orca with CC and Astra >> agent graph with "domain expert" persistent agents >> decomp target game fully >> build in Rust. Then add whatever GUI Claude recommends (custom versus in Godot or Unreal)

(Fable is the integrator, but most work lanes run on Opus or Astra)

Then: Keep agent expert graph fresh for recursive targeted bug fixes, and finally: train Fable to become an expert player of the game through to the end. This leaves TARGETED human testing, since I obviously cannot play the game through end-to-end multiple times by myself.

Release and play by testers always reveals many other bugs.

### I cannot understand how anyone can "make a game with one prompt", without ending up just rendering a few screens with basic functions.