Here are some highlights:

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.

Using some video references it’s not too bad still needs tweaking

I want to share the game I have been working on since late July. It is a free beta, it still has rough edges, and I am looking for playtesters and honest feedback.

Graveharvest is a dark pixel-art idle game. You are a necromancer under a blood moon, cutting down the Living as they cross the field, or letting the Reaping do it for you. You raise the dead as Vassals who gather Souls every second, buy Rites that make every kill worth more, and when prices outrun your harvest you take the Long Death: the life ends, the Ichor you earned stays, and the covenants it buys make the next life climb faster. It is a long game, made to sit in the background and be come back to. Finishing it takes months, not an evening.

AI has been a life changer for me as a solo dev. I have always had more game ideas than time, and spending years on a single game was never something I could afford. Now I write the design, break it into tasks, and hand them to Claude. It feels like running a small team: a stronger model (Opus/Fable) plans and reviews, a cheaper one writes the code from tightly scoped briefs, and I make every design call and play every build. The engine is Godot 4.

Bugs constantly appearing, and especially thinking of ideas and aligning and visual assets usually needs me to step in. Two things kept the project from falling apart as it grew: over 1,600 automated tests that have to pass before anything ships, and a simulation kept separate from the visuals, so the economy can be tested and balanced without opening the game. I also learned that the AI does far better with something to look at. Even a rough mock-up beats a paragraph of description. Characters, icons and music come from asset packs (credited in the game). It is hard to believe how much game there is after less than four months.

I honestly do not understand all the hate AI-assisted games get. I think transparency matters, so I am open about how this one is made, and I will say so on the store page if it goes to Steam. But seeing the reaction some AI-assisted games get, I do have doubts about that. How do other devs here handle it?

What I would most like to hear about the game:

- the first ten minutes: is it clear what to do without being told?

- the pacing and the prices, early on and after your first Long Death

- any bug you hit, and anything that feels unpolished

It runs in the browser, and there is a Windows download too. It asks once whether it may share anonymous play statistics; that is off unless you say yes.

I look forward to your constructive criticism!

https://jbi2109.itch.io/graveharvest

My remaster of the Alien Breed 2 games now supports all four titles. You can play with a reasonably close emulation of the original or enable a bunch of modern features and graphics. Classic graphics only for Tower Assault, modern requires light placement on 50+ levels.

This is a Claude project that mostly used Opus Medium. One repo documents the game and produce an exporter to modern file formats, the other is the engine and consumer that imports the assets. DeepSeek was used a little early on when it was cheap but was not reliable. Claude has good knowledge of 2D graphics/systems and executed most of it without challenge. Adding netcode was quite painless but have to review occasionally for sources of desync. We agreed on LUA as a game engine such as Godot didn't give us anything we couldn't hand create/added more overhead then started with a skeleton of the game and slowly built up on top of it.

In hindsight starting with an emulator and dynamic loading might have been better but potentially I can do a lot more this way.

Lessons so far:
- Lock down comment and docs rules early. Enforce with tests,

- Agree structural scope as early as possible (e.g. netcode). Gameplay features and visual FX are easy to add on later but core systems take a lot of setup. We had to implement determinism and remove globals midway through the work.

- Optimization isn't too much of a problem with a repeatable benchmark but you start getting dead ends when the easy wins are done.

- Giving Claude a screenshot ability helps a lot with anything that touches visuals.

- Claude being able to read and understand every file type helps but it doesn't mean they won't still struggle to interpret things more abstract than code (misaligned sprites, audio pitch being wrong etc)

- Have a weekly check in with Claude about usage where it reads the session transcripts and tool usage to understand where you are inefficient.

Claude also edited this trailer from gameplay with suggestions from me! I titled the clips and gave it the main ideas.

https://vironi.itch.io/xenoblight

Original game files are required.

There is a new easy difficulty for Alien Breed 2 that reduces the amount of aliens and makes the first level more forgiving. Tower Assault gets a facility map to make it a bit easier to tell how the levels connect together. Restart Level rewinds back to your level start conditions so you can make another attempt without losing the whole game.

• Twin stick controls with gamepad support or classic directional controls.

Multiplayer:

• Online multiplayer with rollback netcode for two players with UPNP port request.

• Two-player viewport with multiple camera modes including dynamic split screen or full size views.

• More options to share beyond just credits.

Modern mode provides:

• 640×360 virtual canvas scaled by an exact integer to the display (×2 at 720p, ×3 at 1080p = 1920×1080, ×4 at 1440p, ×6 at 2160p). Pixel-perfect, square pixels throughout. 2.8× more world area than classic's 320×256

• Fog of war to let you restrict your viewable area to approximately the original games area.

• Audio system emulates the original four channel behavior via rules while allowing additional channels to play to avoid cut offs. Stereo emulation and distance based falloff for sounds are also simulated.

• Lightweight deferred-lighting mode. Flashlight with real polygon shadow-casting occlusion (not a fake cone) and wall-spill lighting. Static light fixtures are real dynamic lights (falloff, shadows), not painted-on brightness. Props (barrels, etc.) cast their own projected shadows.

• Modern alien pathfinding AI if you want them to be much more aggressive.

Classic mode provides:

• Authentic 320×256 viewport, pixel-aspect-corrected by 16/15 (the real PAL Amiga ratio) so it displays 4:3 pillarboxed 1440×1080 at 1080p. The non square pixel ratio is critical to not requiring letterboxing at modern resolutions, a strange coincidence.

• The original's flat, unlit renderer (no flashlight/shadows at all).

• Original HUD but full speed updates instead of being restricted to one column at a time.

• Accurate 4-channel Paula-style audio, including the original's channel-stealing behavior.

• Original pathfinding.

Hello, community! I wanted to share a new map I’ve just added to Agentic Wars Conquest, my browser based multiplayer tactical shooter built with Three.js

The craziest part is that the entire Palm Beach map featuring a private tropical paradise, a mansion with a pool, and an iconic temple with a golden dome was designed and developed in just one day using Fable 5.2. It’s perfect for dynamic, mid range combat and controlling capture points.

You can play it for free, directly in your browser (no downloads required):

👉 agenticwarsconquest.com

What do you think of the result, considering it was built in record time? Let me know your thoughts and any suggestions for balancing! thanks in advance

As you can see, this has been quite a journey! I consume a lot of lofi on YouTube and wanted something on my TV that wasn't a repeating scene. The stream follows the life of Maple (the fox) who is the town Radio host. Claude simulates her day, what she does, who she chats with, and what happens in the town in general. I love being surprised/delighted by the little things that happen. The residents' conversations are also generated based on what's happening in their world, so it's not just a collection of scripted animations/words.

I have had SO much fun with Claude code and making charming additions like changing weather/seasons/decor. I gave everyone costumes on Halloween lol... Today I spent the day perfecting the menu and items in the town cafe.

Happy to answer any questions! If you're interested in checking out the live stream, you can find it here.

Hi! It's a recreation of the original Heroes of Dragon Age. Initially, I was doing it by hand because I wanted to write code myself again in my favorite language, C (idk, I just like the language's constructs, and I'm a big fan of Jonathan Blow, Mike Acton, Casey Muratori, Per Vognsen, etc.). I really enjoy the process. But then I got stuck on some model animation and shader code. It needed to match the original closely, and that's hard to achieve without deep knowledge of this stuff. I feared that, in the end, I wouldn't be able to finish the project myself and would waste a lot of time trying... So I switched to AI tools again. I started making a lot of progress by throwing Claude Code / Codex at the original APK and game cache I managed to recover back in July. The results were trash initially, but after quite a lot of iterations and manual interventions, I managed to get it to look and feel kinda as good as the original.

Right now, I'm comfortably creating new content and fixing bugs using exclusively Opus 5.5 XHigh / Fable 5.2 with Medium / XHigh effort (without Ultracode mode), and I'm pretty happy that it can do stuff with minimal visual artifacts and logic errors, though I still control what it does and how it does things. I don't really look at the code anymore, except maybe a little for critical parts. I also generate some art in the game's style using GPT Image 2.6, as I have a Codex subscription too.

This project is completely open-source. I run an online server for the game, and it's completely free and will stay free forever. The server costs me like $5 a month, and the domain is like $10 a year or something, so... as a grown adult, I'm sure I can handle it, ahah.

I played this game when I was a kid. I spent a lot of my money on this laggy, trashy gacha game, but I liked its style and mechanics. Now, it feels great that I can modify it however I like, or however the players want, and make myself a billionaire in the game. But it kinda doesn't feel the way I wanted it to. Having developed it myself, I've unfortunately lost a lot of interest in it, but anyone who plays it can still get the full experience, I guess.

If anyone wants to try it, it's supported on macOS, Windows, and Linux. Soon, I'll start looking into making it playable in a browser too, but idk for now.

Anyway, you can find links to the repos, Discord, etc. on the project's website - https://hodareborn.com

Hey everyone! I wanted to share some progress on VELARIUM, an action game I’m developing in Godot 4.
I’ve been working on a development version called V-Next, focusing on the characters, weapons and interface. The game has six characters: Knight, Ronin, Wizard, Witch, ZAD and MECHA, with five evolution stages each. I’ve been working on character selection, the upgrade area, the Forge, the Rift Gate and other menus. Character effects have also been added, which is starting to give the game more personality.

The part that turned out to be much harder than I expected was getting everything to work together. For example, I discovered that some models downloaded in a batch came without bones, so they had to be exported again with rigs. Then came the other problems: capes deforming, stances that don’t suit the character, hands clipping through weapons or not really gripping them, and animations changing unexpectedly when switching weapons.
There have been some targeted improvements: Ronin’s grip, conflicting animation ownership on Knight, carry adjustments for MECHA, and fixes for some staff grips. These don’t solve every combination, and they haven’t all been verified in a full gameplay test. ZAD has an experimental rifle-grip solution that has been tested separately, but it isn’t integrated into the game yet.

What I want to tackle next is making each character feel unique in motion, not just in appearance: their idle, walk, run, weapon grip and transitions. I’m also investigating FPS drops and performance. I’d rather share the process honestly than call something finished before it actually works.

If you’ve worked with rigged characters and separate weapons in Godot, how did you approach matching the hands, weapon and animations? I’d also love to hear what you think of the overall direction.

MORS is a factory game on a 1:1 Mars: mine, smelt, belt everything together, then build trains, rovers and rockets and launch them yourself. The planet is real size, built from NASA's elevation data, so Olympus Mons is 21 km tall and a belt can run 98 km to the horizon.

Cost: free. Free demo on Steam now, and the full game will be free at release (4 Mar 2027): https://store.steampowered.com/app/4950970/MORS/

How I use Claude (Claude Code):

• Day-to-day coding in Godot: 61 of the 167 commits in the game's repo carry Claude as co-author. I design and review, Claude writes most of the GDScript, I play-test every change

• Performance: Claude wrote stress tests that lay belts kilometres long and measure frame cost. After the belt rewrite, 98 km of conveyor went from 26 fps to four lanes of it at 198 fps.

• Bug hunting: the drop pod's heat shield was floating a metre below the capsule. Claude traced it from a screenshot to the rig code and fixed it.

• Trailer and shorts tooling: Claude wrote scripts that play the game under Godot's Movie Maker (scripted cameras, flights, launches) and a Python assembler that cuts the footage and adds captions and narration.

Other tools:

• Godot (custom double-precision build)

• Blender for models

• ElevenLabs for narration in the shorts

• NASA elevation data for the planet

Mission 04, "Black Tide", from a VR island adventure. The whole mission was played in one go (about 10 minutes, plane to plane) and cut down to 1:45. Meta Quest / PC VR · in development.

In the clip:

- jump from the plane and steer the parachute with your hands

- climb a tree and snipe the beach guards from the top

- climb the submarine's tower ladder, holding on with one hand and shooting with the other

- dual-wield below decks and find out what happened to Ethan

- scan the beach through the periscope

- flood the escape trunk and swim out under the hull

- fire a flare so the plane picks you up

How Claude fits in:

It's a Unity project, and Claude Code (Opus 5.5 / Fable 5.2) works right inside it, writing C# and building levels from code. In this mission that's the submarine and its escape trunk, the periscope, the guards' sight and hearing (they can't see you through leaves, they hear your footsteps), the hit zones and the hand-steered chute.

What made it work:

- Claude can't wear the headset, so the loop is: I play, describe in plain words what felt wrong, Claude changes the code and tells me what to check next.

- For most features it also writes itself a test tool (a compile check that runs outside Unity, review scripts that load a level and report back), so it can test its work before I put the headset on.

- It keeps notes of the project's rules between sessions (like "you pick things up with grip, never the trigger"), so the next session already knows them.

Even this video was cut by Claude Code: ffmpeg on the raw NVIDIA recording, caption cards drawn by a PowerShell script, no video editor.

Happy to answer questions about the workflow.

Hallucination Inc. is a free browser game: you run an AI lab for 24 quarters, one crisis card and one bet per quarter. A run takes about 12 minutes and usually ends in bankruptcy, a coup or an indictment.

https://hallucinc.com (phone or desktop, no install, no sign-up, no ads)

I wrote no code. I directed Claude Code: one main session that planned, briefed sub-agents, read their reports and merged, and sub-agents that each worked in their own git worktree. Kick-off was November 11, launch November 15.

What worked

• Gates the agents can't argue with: deterministic replays of the simulation, a content lint, bots that play thousands of runs for balance, and 58 browser checks on every push.

• A second agent as reviewer for anything that guards data. Reviews caught real things, including our own scripts sending an access token to the wrong host.

• An agent playing the game as a first-time player. On launch day 9 of 10 visitors left on the first card. It walked the first run, named why, and a guided tutorial shipped the same evening.

What didn't

• The comedy is unrated. I'm still reading the 850 pieces of text.

• One balance target still fails: too many responses that players rarely or always pick.

• Launch day brought almost no players. Building was the easy part.

Tell me where it stops being funny, or ask anything about the process.

I made LEVEL ZERO, a procedural Backrooms horror game that runs in the browser. Play it here: https://synapcore.itch.io/level-zero

HOW I USED CLAUDE

I built the whole game in conversation with Claude Code (desktop app, Claude Opus 5.5). I'm not a programmer: I did the creative direction, playtesting and feedback, and Claude wrote and debugged all of the code.

- Initial build: I asked for "something like the Backrooms, procedurally generated". Claude wrote the game as a single HTML file using Three.js:

- an infinite chunked maze generated from a seed;

- custom shaders for the lighting, fog and VHS look;

- procedural textures drawn in code;

- Web Audio for the fluorescent hum, footsteps and the entity's drone.

- Design iterations: I'd play, then describe what felt wrong. Some examples:

- "the sanity effect isn't noticeable enough" → Claude added colour drain, chromatic aberration, screen warping, VHS tearing, fake footsteps, hallucinated words and images, and music that degrades in stages (muffled, overdriven, then skipping like a broken tape).

- "sanity barely drops, there's too much almond water" → Claude rebalanced the drain rates and made bottles rarer.

- "it's too easy, add events, puzzles and lore" → Claude added:

- blackouts, a voice calling your name behind you, looping corridors and ringing phones;

- a code split into digits painted on the walls;

- a "lights out" breaker-box minigame and a radio you tune to get directions;

- 6 notes and 2 VHS tapes that teach the survival rules and unlock a true ending.

- Testing: Claude playtested in the Claude desktop app's built-in browser. It used temporary debug hooks to teleport to spots and trigger every ending and event. It also flood-filled 20+ seeds to make sure all items and the exit can always be reached.

- Bug fixing from my reports:

- camera jumps with the mouse → raw pointer-lock input plus spike filtering;

- fake doors standing alone in rooms → moved onto real walls;

- title cut off inside the itch.io frame → menu layout fix.

- Release: Claude added the English/Spanish language system and translated all the text and lore. It also packaged the itch.io zip, captured the screenshots by driving a headless browser from a script, and composed the cover art.

OTHER TOOLS

- Suno Pro: the 4 soundtrack tracks, made by me.

- ffmpeg: converting the music to MP3 (Claude ran it).

- Three.js r128 (MIT), VT323 and Special Elite fonts (Google Fonts).

- itch.io for hosting.

Feedback welcome, especially on difficulty!

I came into this one feeling really strong because of my work in Unity this year, and was completely unprepared for how much worse Opus would be in UE5 with C++. I scoped for a project I could finish in roughly 18 hours for a 4 day game jam. I spent more than a day fighting Opus on a single VFX and more than a day on combat animations, and both still aren’t right. Bugs I had night one are still in the build after handholding and vibe coding and fixing and it showing back up, etc. Really obvious bugs like ‘the player bends over awkwardly, gets stuck, and can’t move until they’re attacked.’ Game breaking bugs I’ve never seen from Opus in Unity.

Is Opus just not as good at C++ Unreal projects as it is in Unity? I figured it would probably be great considering the AI game jam and Anthropic sponsorship…

May post the game/trailer later for reference because I’m real disappointed and frustrated and need to vent :/

Here is some quick gameplay from my entry for Unreal Engine AI megajam. Its my take in classic tycoon genre. It covers 7 decades and has lots of trains, cars and aircraft inspired by real ones from the era it covers.

Developed over three days. I managed to get quite a lot of stuff in, but there are lots I'd like to add as well!

Game was fully made with Claude Code - it handled all coding and 3d modeling (with Blender).

Music and sounds came from Elevenlabs, but it was also Claude Code that prompted them via their API. Textures are from locally run Qwen-Image and in small parts also OpenAI Images.

If anyone wants to try it out, the gamejam build is available for free at https://jazzkissa.itch.io/tetsudo

I'm a solo dev from Switzerland and just released Moundlings, a strategy game for iPhone and iPad. You lead a blue ant colony, swipe from mound to mound and try to take the garden before the red colony does. Everything looks like it's made of clay.

How I built it:

* Brainstormed the idea with ChatGPT and defined the first game assets.
* Wrote a developer briefing for Claude, which did the implementation in Swift with SwiftUI and SpriteKit.
* Made more assets with Grok Image and ChatGPT Image through WaveSpeed.
* Pulled the sounds straight from Envato Elements through their MCP.

The biggest challenge was playtesting. I needed enough rounds on every device to answer the questions that matter: does it feel good, does it stay varied, and how should the opponent get harder over time. My 8-year-old son loves it, and I also widened the test group through TestFlight. Getting other kids to test it on purpose was harder than expected, partly because the adults liked it a bit too much ;)

Classic is free, the full version is a one-time purchase. No ads, no subscription, no tracking, and it works offline.

[apps.apple.com/app](https://apps.apple.com/app/id6826520840)

If you want the full version, the code TGDFANPHR unlocks it for free until Nov 27:
[apps.apple.com/redeem](https://apps.apple.com/redeem?ctx=offercodes&id=6826520840&code=TGDFANPHR)

How do you handle playtesting? And how do you tune an AI opponent so it gets harder without feeling unfair?

After 500 bug fixes and 4800 messages with game community version 1.5 is now released!
P.S. Just released 1.5.2 which now works 3x faster than any other version.

Razdor is an open-source engine for Discord Times (Aterdux, 2004), a turn-based strategy/RPG. It plays the original campaign, community maps and mods by the original rules, and then adds the things a 2004 engine couldn't do.

How it was built

• Clean-room reverse engineering. The original executable was taken apart in Ghidra; every rule that maps and mods can see (battle, AI, map scripts, events, saves) was written up as a spec first and then implemented. The code cites the original's addresses.

• Diff tests against the original. The original runs under Wine, and a script mode replays the same inputs in both and compares the state step by step. By default Razdor matches the original exactly, bugs and imbalances included; every deviation sits behind an experimental switch that's off by default (16 of them right now).

• Rust + macroquad, about 190k lines, GPL-3.0. The game rules live in a separate module with no graphics dependency and are unit tested; the original's file formats (ini data, .DTm maps, its own picture formats, sounds) are read at runtime.

• Deterministic simulation: every game is recorded and can be replayed at up to 16×. The same determinism let us record the trailer's split screens twice with different graphics presets and get the same frames.

What you get

• ~11× the frame rate on the same GPU (RTX 4060, 1024×768, unlocked): about 2,000 FPS against about 176 for the original under Wine. A 200×200 map with 61 armies costs the game about 0.3 ms a frame. Load to first frame is about half a second.

• Any resolution and aspect ratio (the trailer is 21:9), refresh rates up to 180 Hz, a graphics preset ladder from "Original" (pixel-for-pixel the 2004 look) to "High" (light, shadows, water, weather, clouds instead of black fog of war, a living map), and a 2.5D view.

• Linux, Windows and macOS; Android and iOS are experimental, with a touch layout, graphics presets for weak phones and a battery saver.

• An in-game hub with the community's work: 327 maps, 29 campaigns and 25 mods.

Links

• Site and downloads: https://indicozy.github.io/razdor/

• Source: https://github.com/indicozy/razdor

• Wiki (English): https://indicozy.github.io/razdor/wiki/en/

• Trailer (Russian, YouTube): https://youtu.be/kHvM7Yv-2_4

I’m a solo developer from Ukraine building Nebulife. I direct the project, and Claude has written almost all of the code and tests. The game uses TypeScript, PixiJS 8 for 2D, Three.js for 3D, React 19 and Vite for the interface, and Capacitor to bring the same codebase to iOS and Android. It’s also available on the web.

Nebulife’s shared universe grows from one seed, while the server persists changes made by players. Its planets are fully procedural and use no textures. Players can explore star systems and planets, seed life, watch it evolve, and build colonies.

The attached gameplay clip follows a journey from a galaxy view toward a star system and a planet. It shows the change in scale, but it does not demonstrate persistence or evolution.

I’d be interested in design feedback: what would help players understand that a change they encounter in a shared world was made by another player?

For cost transparency, the US iOS app is a free download with optional purchases: Pro is $4.99 monthly, $34.99 yearly, or $99.99 lifetime, and Quark packs range from $0.99 to $12.99. The Android listing says it is free to play with ads and in-app purchases; prices vary by store and region.

https://nebulife.space

Three weeks ago today I started Tierra Firme, a naval MMO set in the 1720 Caribbean. You trade between 49 ports, fight pirates in real-time battles, build your fleet and sail with other players. It runs in the browser, no download:

Some numbers after 3 weeks:

~31,000 lines of code (a single-page client, a Node server for the shared world and real-time battles, Python for the game data and balance)

37 ship classes, 70 trade goods, a living economy where prices react to what players buy and sell

Ships can sink for good (with insurance), squadrons to hunt with friends, optional PvP

Payments, accounts, English and Spanish, about 215 deploys

How we split the work: I do the design, the balance calls and all the illustrations. Claude writes the code, tests it in a headless browser before every push, and deploys. I'm not a professional programmer. Most days I play, find something broken or boring, describe it, and we fix it in the same session.

Things that surprised me:

Balance is the hard part, not code. Changing one chest drop chance touches 5 other systems.

Real players find bugs in hours that I'd never find. The best feature ideas came from the first 20 players.

Keeping the server authoritative early saved us when people started poking at it.

Happy to answer anything: workflow, prompting, architecture, costs, what Claude is bad at, how to get your first players. And if you like ships, come sail with us.

Here are the most popular posts from the last week!

1. I don’t know who needs to hear this, but never EVER disclose that you used AI for your game

By: u/Icy_Masterpiece_4414 Karma: 299 | Comments: 314 | Flair: Tips & Tricks

View Post

2. AssetCat: free & open source tool to search & browse game asset packs

By: u/digitalhobbit

Post Thumbnail

Karma: 127 | Comments: 21 | Flair: Release

View Post

3. AI game development is moving so fast that I'm starting to wonder if I'm wasting my time building something ambitious. Anyone else feeling this?

By: u/DANAMITE Karma: 127 | Comments: 69 | Flair: Alpha

View Post

4. Tips for better looking games? Bonus: Screenshot of what Claude is doing for me currently

By: u/Reading_at_work

Post Thumbnail

Karma: 123 | Comments: 58 | Flair: Tips & Tricks

View Post

5. Building a Spore-inspired evolution and tribe game in Godot 4

By: u/Ouvolk

Post Thumbnail

Karma: 111 | Comments: 29 | Flair: Alpha

View Post

6. A game that's been stuck in my mind for years - Hotdog!

By: u/denzmilk

Post Thumbnail

Karma: 94 | Comments: 40 | Flair: Beta

View Post

7. Streets of Nice - my arcade beat 'em up, playable on phones and desktop

By: u/gwendalle

Post Thumbnail

Karma: 94 | Comments: 11 | Flair: Browser Game

View Post

8. I packaged my whole “concept art → Blender → Godot → shipped build” workflow as a Claude Code skill. The goal is AI-made games that aren’t slop

By: u/Any-Blacksmith-2054 Karma: 64 | Comments: 11 | Flair: Tips & Tricks

View Post

9. Fable 5.2 filmed and edited my game's trailer by itself. Here is the setup that made it possible

By: u/shurido

Post Thumbnail

Karma: 56 | Comments: 14 | Flair: Beta

View Post

10. I’m creating my own game with the help of Claude, and you can already play a very early version of it.

By: u/FeelingGrape94

Post Thumbnail

Karma: 55 | Comments: 14 | Flair: Alpha

View Post

I'm making a sall fantasy game and needed three shopkeepers for the same village. A potion seller, a blacksmith, and a general store owner. Simple enough, right?

I had the concept art ready, and they all looked like they belonged in the same game. I used Claude to help plan the AI character generation workflow before running them through Meshy's Image to 3D and dropping them into Unity.

Apparently, my village has no consistent anatomy rules.

The potion seller had a massive head, the blacksmith's arms barely reached his waist, and the general store guy looked like he'd wandered in from a completely different art style. Each model looked decent on its own, which somehow made it more annoying.

My first instinct was to open Blender and start fixing proportions. Then I compared the original drawings and realized I'd basically given the generator three different sets of instructions. Different camera angles, inconsistent head-to-body ratios, and poses that made the silhouettes harder to interpret.

So instead of spending the evening dragging vertices around, I went back and cleaned up the reference sheets. Same proportions, neutral poses, consistent framing, with front and side views that actually matched. I used Meshy's Multi-View option for the next pass so it wasn't guessing the depth from a single drawing.

There's still some cleanup to do, especially around clothing and accessories, but at least I'm approaching it with references that make sense now.

Turns out AI is pretty good at preserving the mistakes you didn't realize you put in the input.

Anyone making batches of stylized characters? How strict are you with reference sheets before generating, or do you just accept the Blender cleanup as part of the process?

Playable free in the browser: https://kedikatstudios.itch.io/royal-flush

The inspiration behind the game: https://variety.com/2022/film/news/titanic-crew-members-drugged-pcp-clam-chowder-1235465618/

This game was originally meant for a mobile submission for Epic's MegaJam, but we ran out of time. I'm quite proud of it anyway and would love to hear your thoughts!

Some stats:

- About 15 hours from empty folder to public itch.io page

- 49 prompts from me. Roughly a third were just "yes, upload it"

- 1,151 tool calls by the agent, 32 commits

- 6,197 lines of JavaScript (Three.js + GSAP), none typed by me

- 0 image or audio assets. Every texture is drawn on a canvas in code: the PS1 dithering, vertex wobble and 240p render are shaders, and the music is synthesized live including a public-domain hymn for level 3 (The song the band played as the ship was going down in the movie!)

- ~706k output tokens; ~278M tokens read, 99% of that cached context

Things that worked:

- Keeping one quality bar written down: "AAA game feel in a PS1 graphics package." Whenever something felt stiff (blocky shoulders, poses snapping), I pointed back to it, and the fix applied across every level.

- Having it build a headless autoplay bot early. Every level change was checked by the bot playing through it, which caught impossible obstacle layouts before I did.

- Giving feedback with reference images instead of adjectives. "Make the comics look like 1996 low-poly games" plus three screenshots beat any amount of describing.

Things that didn't:

- The first comic cutscenes looked amateurish and had to be rebuilt as 3D renders.

- Physics on the tilted level 3 took several rounds before objects slid in a way that felt fair.

Happy to answer questions about the workflow!

Hi, this isn't really a playable game in the traditional sense, but uses from Claude assisted game development ideas. I have had thoughts to turn it into a playable game, any suggested directions would be most welcome.

I love watching (Australian Rules Football)[https://en.wikipedia.org/wiki/Australian_Football_League] and sports analytics. I've always had this dream wanting to build a software that could learn to play the game (basically like doing AlphaGo but for AFL) to come up with positional strategies that have never been seen (AFL has no offside rule and 18 players on the ground each side so position and structure matter's a lot).

Turns out that is really hard lol. But with Claude I've recently made some cool progress toward that goal.

- First I made a stochastic game engine that simulated the game for 8v8 players. This is nothing new, but it encodes a lot of the macro logic that I wanted like kicking, marking, running, handballing, goal, point, pressure etc. Individual players can have different attributes (like speed, accuracy etc) which impact the play. I designed it in such a way that it could be playable by a Python program (a "team" if you will). In other words, the program would accept the current position and state of the game and then output what each player would do next. The game engine would then take that (from each team), simulate forward a second and then repeat.

- Then I experimented with "evolving" good python teams. I set up a Claude code session in a Docker container and allowed it to experiment with different python programs to "get good". It ended up playing itself a bunch of times, running analysis on the games it played with itself, and then repeating until it's strategy evolved. I did this 6 times in 6 different containers, all with different player profiles (some players were good at kicking but slow, others had excellent endurance, others had very good speed, others were good at getting contested possession etc.). What ended up happening was 6 very different teams emerged.

- Then I made the teams play each other! The rules were that there were 4 quarters of 4 minutes each. Each "coach" (Claude code instance) would get to analyse the game progress after every quarter and make small adjustments to the program based on what was happening during the game. Importantly the Claudes were isolated from each other (hence the Docker container) so they couldn't inspect the code of other teams. They could only guess what the other team was doing. Each coach had about 20-30 minutes between quarters to change their strategy before they needed to play again.

- Finally, I wrapped it up in a full broadcast. I had a series of characters that were presenters who hosted various shows. They would conduct interviews with the coaches after every quarter and run analysis on certain highlights of the play. They would also commentate the game as it was happening. I used the game state history to animate the play using a Super Nintendo style view (my favourite), used image generators and voice generators to help with the broadcast and then Claude to stitch it all together in a "show".

The result is actually quite amazing. The commentary still feels AI, but still it's genuinely entertaining. The stochostic nature of the game means that nothing is certain and any team can beat any other team. There are very clearly different styles of play emerging and very obvious in-game tactics that change to combat what happens.

I've attached an excerpt from one of the "Round Review Shows" where one of the analysts (Rusty Kneebone lol) is going over a Comet's play to give you an idea of how it plays out. Anyway if you guys are interested the full season is being hosted here: https://www.youtube.com/@AIFL-l3b/videos. Also, I've open sourced the game engine so other people can contribute programs if you wish: https://github.com/AFLgains/AIFL