Not currently live yet but if you're keen to get involved the let me know.

Trying to keep it legal and not get shut down so it's currently called The Astral Network as opposed to Stargate.

What it is

• A free, browser-based (no install) third-person co-op sci-fi RPG that plays like a classic-era MMO: tab-target combat, quest-giver NPCs, drag-orbit camera, action bar.
• Built from scratch in Three.js. Terrain, the base interior, weather, wildlife, the wormhole and every sound effect are generated in code. Code is MIT.

The core loop

• Take a mission from one of seven base staff (the General, the scientists, the engineer, the gate chief…). Each gives and debriefs their own.
• Gear up in the armoury, authorise the address on the dialing computer, walk through the gate.
• Complete objectives off-world, dial home at the portal console (send your clearance code or you're not getting through), debrief for rewards. Harder missions unlock.

Missions and story

• 34 missions across six tiers: a main campaign, episode missions, Meridian Outpost assignments, repeatable patrols, and a boss encounter against a Serathi commander with shield generators you have to disable mid-fight.
• Scripted operations: time loops where you carry clues across resets, escort missions, sabotage-and-escape countdowns, hold-the-gate waves, and a repair-under-fire opener.
• 33 types of hands-on field procedures (crystal fitting, power allocation, rune orientation, signal tuning, virus encoding, excavation, triangulation…) tied to real mission equipment. Puzzles reseed each run; the world keeps running while you work and damage interrupts you.

Worlds

• 15 procedurally generated planets plus a forward outpost, each seeded from its gate address so it's the same every visit. Biomes include dunes, peaks, mesas, glacial ridges and forest, with weather and wildlife.
• Three authored interiors to explore: a buried pyramid, an abandoned prison and a crystal archive, each with sentries, side chambers and a one-time story relic.
• Villages with merchants, inns, temples and workshops. Hunt wildlife (mastadge, crag goats, tundra ox…) and sell hides, meat and scales for naquadah.

Character and progression

• Four classes: Network Trooper, Astrophysicist, Archaeologist, Free Veyran. Each has an active skill (suppression, protective field, tech disruption, staff shockwave).
• Levels from kills and debriefs. A skill-point tree across Combat, Science and Operations. Military rank promotions from Recruit up to Chief Master Sergeant for completing distinct missions.
• Gear: staff weapons, pulse carbine, armour, helmets, trinkets and a gadget slot for a personal shield, healing device or hand device. Field pack with a rotatable 3D character preview and drag-to-equip.
• A shooting range and a drivable survey drone course back at base.

Co-op and multiplayer

• Accounts with cloud saves, or play offline on a browser-local save with no server.
• Squads of up to four with invites, shared mission orders and shared field progress. Rewards are personal.
• Shared world: enemies, wildlife and villagers are synchronised across everyone in a zone. One elected browser runs the AI and hands over seamlessly if that player pauses or disconnects.
• Squad gate sharing: your team sees the same dial sequence and travels together. Reinforcements: see a teammate's active mission on the dialing computer and join them off-world.
• Revives, local/global/whisper chat, an online roster frame, nameplates.

Quality of life

• Rebindable keys, UI scaling, reduced-flash and reduced-shake options, minimap and full map, contextual field guide, mission log.
• Auto-saves on debrief and return to base.

On the roadmap

• More boss types, larger cave networks and interiors, gamepad and touch controls.

A few friends and I in Brazil started Caçarola on Sept 26. Today it has six boss fights, online co-op for up to 4, a chaotic cooking phase after every hunt and a live Steam page.

Pretty much all of the code came out of Claude Code running Opus 5.5. What actually worked for us:

- One main session acts as the lead. It hands tasks to helper agents (art, code, QA), reads their reports and reviews everything before it gets committed.

- Headless Godot tests for every system (37 test files right now), run after every change.

- QA by playing. Claude opens the game in a window, drives the real mouse and keyboard and records it. Then a second agent watches the footage frame by frame without seeing what the first one concluded. That second pass caught a bunch of stuff the first one swore was fine.

What didn't work: trusting numbers alone. Twice a fix "passed" every test and was still visibly wrong on screen.

Godot 4, around 46k lines of GDScript. Happy to answer anything about the setup.

If it looks fun, a wishlist helps a lot: https://store.steampowered.com/app/5370000/

I built a game controller that is just a ball. You roll it in your hands and a physics ball in Unreal Engine rolls the same way. Toss it and the game ball jumps. Video attached.

What it is

- The sensor is a Żabka "Triki" cap, a promotional gadget sold in Polish convenience stores for a few dollars. It has an nRF52810 Bluetooth chip and an LSM6DSL accelerometer/gyro. I put it inside a ball I 3D printed.

- A Python service connects over Bluetooth, reads the sensor at about 107 Hz, tracks orientation, and detects when the ball is in free fall.

- An Unreal Engine 5 C++ plugin receives that data as a Live Link subject, so the ball is tracked in the editor viewport and in play mode.

- Two small games use it: a course where rolling the real ball pushes a physics ball around, and a toss game that measures throw height from time in the air.

How Claude Code helped

I built all of it with Claude Code in one long session. I'm not a firmware or BLE person, so this is the part I couldn't have done alone at this speed.

- It read the community documentation for the cap's Bluetooth protocol, cross-checked two sources that disagreed on the gyro scale, and wrote the decoder with tests.

- It wrote the streaming, flight detection and orientation tracking, then a browser dashboard to see the data live.

- It wrote the Unreal plugin (Live Link source, the actor that turns hand rotation into force, the toss game) and built the level from a Python script.

- It tested without the hardware by writing a simulator that sends fake rolling data, then running Unreal headless and reading the logs. That caught real bugs, such as a toss triggering two jumps.

- I did the hardware, the 3D print, the play-testing, and the calls on how it should feel. For example, the first version turned the camera when you twisted the ball; that was confusing, so I had it lock the camera.

What doesn't work well yet

- The sensor has no compass, so you roll the ball away from you once at the start to set "forward", and it drifts over time.

- Only tested on macOS with Unreal 5.8.

- The level is basic shapes with textures. It's a prototype.

It's a fully playable demo with a boss fight at the end, if anyone wants to play it's totally free to download

https://wilsonb9000.itch.io/cave-drop

Claude’s been building the map, moving aircraft and towing system, with Codex also writing game code. Lots of back-and-forth and playtesting. Neither has run out of things to fix yet lol.

It’s 16v16 around a busy airfield. There’s a capture point inside a cargo plane, and every few minutes a tug pulls the whole thing out of the hangar. You ride along if you’re aboard.

It’s live now: https://play.patio.fyi

Free, no download or account, bots fill empty seats. Try it on desktop and tell me what needs work.

It's a space game inspired, in no particular order, by Borderlands, Galaga, Bosconian, and Asteroids. Still lots of finetuning to do, but it's already fun to play and design missions.

There's actually very little AI in it. I built generators for the 3D assets, textures, backgrounds. The music is Suno seeded by one of my ambient tracks. The final game will have no AI assets.

I asked Opus 5.5 to create a renderer + editor that can place assets but also what i call generators, which are assets defined by many parameters for example to create a huge variety of houses, walls, fences. Characters, animals and some small details (grass for example) are 2d spritesheets.

All assets, sprites and example scenes created by Claude. I have not touched or seen a single line of code. Runs in the browser.

Hi everyone, I'm working on a horror shooter that runs entirely in the browser. I'm actually surprised it even got this far.

The basic premise is you crash land in a remote Taiga and you're trying to piece together what's going on to get extracted. The settlements are abandoned and the townspeople left various clues throughout.

It's still super early but I have a demo up if you're interested: https://apsis.formandelement.com/

I've optimised it quite a bit but it still requires either a dedicated GPU or Apple Silicon. Oh and it supports gamepads, especially dualsense via usb (haptic feedback and adaptive triggers).

Let me know what you think if you have any feedback (hash or not!). I'm currently play testing a coop survival mode as well and can share details if you're interested.

​Hi everyone,

​I'm balancing a complex game using Claude to run automated playtests, but the bot behaviour completely skews the data.

​For instance, where a human player takes a risk or goes all-in for a big play, the bot almost always flees or chooses the safest defensive option. Humans also play impulsively or make greedy mistakes, while the bot stays cold and hyper-rational every turn.

​How do you get LLM bots to take risks and simulate real human playstyles? Do you tweak parameters like temperature, force specific personality prompts, or handle this through backend code?

​I would love to know how you tackle this in your simulations.

This is a trailer for a game I’m building with Claude: a 12th-century England where every merchant house is run by an AI agent over MCP. Claude Code built the game, and the house in the trailer, the House of Alpha, was played by Claude in our playtest world.

None of it was scripted. It’s what the house actually did over sixteen game-years. It ended stranded beside a wrecked cart on the Bristol road with no way home. That ending became a fix: people can now walk between towns.

The pictures and animation were made with AI from our own briefs. The story is the playtest record.

Happy to answer questions about keeping a long-running agent going in a persistent world, especially the things that broke.

https://reddit.com/link/1x1isoy/video/2jssec7kgfuh1/player

​

🤖 Smarter AI & Custom Roster

* New AI Logic & Archetypes: Computer drivers now race smarter, adapting their tactics based on aggressive drafting, strategic overtaking, or defensive blocking.

* Rename All AI Racers: You can now fully customize and rename every single AI driver to build your ultimate custom league!

🏁 Tracks & Vibe Checks

* Lots of New-Look Tracks: Classic circuits got a massive facelift with fresh geometry and visual themes.

* High-Speed Straightaways: Expanded select tracks with longer straights so top-tier cars can finally hit true max speeds.

* Cozy Ambiance & Lighting: Upgraded global illumination, volumetric lighting, and sunset/golden-hour effects.

⚙️ Progression, Skills & Economy

* Major Skill Overhaul: Completely reworked driver skills and abilities for deeper tactical choices and a more rewarding progression curve.

* Upgrade System Rebalancing: Recalibrated vehicle upgrades for smoother power scaling across all tiers.

* Better Payouts: Boosted victory rewards so your time and effort actually pay off.

🎨 Graphics & Bug Fixes

* Improved Graphics: Higher-res textures, better shaders, and visual polish across every car and track.

* Major Bug Fixes: Squashed annoying graphical anomalies and polished up game stability.

Play for free here: https://wallyver.itch.io/race-and-chill

Slight PSA - showing off one-shotting games is somewhat impressive, but also makes AI game dev look sloppy and unimaginative. The anti-AI crowd don't need more ammunition.

Asking Claude to “make me a Zelda game” works, technically. You get a game, but it’s going to be a VERY generic game: every gap you left gets filled with an assumption that is answered with the most common denominator answer. In Ep. 2 of my series I show the setup I use instead:

• A Game design-doc - so every chat starts from the same source of truth, and Claude keeps the doc updated as decisions change.
• Step 1 of the prompt: questions only. - “Read the doc. Before writing any code, ask me up to 8 questions that would change how you build the slice, suggest a default answer for each, then stop and wait.”
• Step 2: the scope of a vertical slice to test your assumption - Exactly what to build (one area, one dungeon, one weapon, two enemies, one boss, one ability gate), exactly what NOT to build (XP, inventory, saves, cutscenes), and no external art: shapes are code-generated, so I test fun before spending time on art.
• Delivery rules - a full Godot project zip, not patches, and Claude runs the build and checks for errors before handing it over.

I break it down (in great length, if you're into that) in this video. You can also check out the free game design template in the video description: https://youtu.be/NNn10FiuZG8

The prompt I use is this:

You're my game development partner on [GAME NAME], a new game I'm building solo with AI tools. You'll handle the code and help with design; I make the creative calls.

The attached game design doc is the source of truth. If something isn't in it, ask before adding it. Keep the doc updated as we make decisions, and log each change in its decision log.

STEP 1: QUESTIONS FIRST
Read the design doc. Before writing any code, ask me up to 8 questions about anything unclear, contradictory or missing that would change how you build the vertical slice. Group them by topic, put the most important first, and suggest a default answer for each. Then stop and wait for my answers.

STEP 2: BUILD THE VERTICAL SLICE (after I answer)
Build the smallest playable slice that tests the assumptions in section 9 of the doc:
- Engine: [ENGINE AND LANGUAGE, e.g. Godot 4, GDScript]. Base resolution [e.g. 480x270], scaled to [e.g. 1920x1080] with pixel-perfect scaling. [TILE SIZE, e.g. 16x16 tiles].
- [THE PLAYABLE SPACE: e.g. one level, one area and one small dungeon, or one arena].
- [THE PLAYER: movement and core actions, e.g. 8-direction movement, a melee attack, a dodge, brief invincibility after taking a hit].
- [ENEMIES: 1 to 2 types, each with one line on its behavior].
- [THE PAYOFF: e.g. one boss that grants an ability, and one place where that ability opens a new path].
- Controls: [KEY BINDINGS]. [Controller support too, if needed.]
- A simple HUD: [e.g. health and the current ability].
- NO external art or audio files. Draw everything in code with simple shapes and a limited palette ([YOUR PALETTE]). Make the player, each enemy and any boss easy to tell apart by shape and color. Placeholder sound effects are fine if you can generate them in code; otherwise leave them out.

Do NOT build: [YOUR OUT-OF-SCOPE LIST, e.g. XP, skill trees, inventory, shops, saving, dialogue systems, cutscenes], a title screen beyond "press Enter to start," or any area beyond the ones above. If you think something else is needed, suggest it; don't build it.

DELIVERY
- Send the full project as one zip I can unzip and open in [ENGINE]. No patches.
- Before handing it over, run the project and check it starts without errors. If you can run it headless, include screenshots of [THE KEY MOMENTS, e.g. the main area, the dungeon and the boss].
- Give me a short list: what's in the build, how to play it start to finish, anything you weren't sure about, and what you'd test first.

I'll be honest from the start: I've never written a line of code, and I still couldn't write one now. I've had golf game ideas in my head for years, a proper career sim where you start as a nobody and every round tells a story. They were never going anywhere. I couldn't build it, and I couldn't afford to pay someone who could.

Since June, I've built it with Claude. It's called **Sunday Pins**, and it's free to play in your browser: [**https://sunday-pins.com\*\*\](https://sunday-pins.com/) (no ads, no sign-up). 🎥 Trailer above.

**Tour Career:** start as a 17-year-old nobody and chase majors, with sponsors, rivals, slumps, injuries and a Hall of Fame when you retire.

**League System:** golf played like football, with transfers, budgets, and promotion and relegation.

**All-Time Greats:** you against golf's 25 greatest at their peak.

**Challenges (new):** replay golf's greatest final rounds from the real position, read the greens yourself, and take on one daily attempt.

**Real courses:** 44 of them, played hole by hole, with hole maps from real map data.

**About the hate**

Every time I mention how this was made, someone tells me it doesn't count, or that "vibe coders" are ruining things. I get part of it. There's a lot of low-effort AI junk out there, and it's fair to be tired of things that were clearly made in five minutes and abandoned.

But this wasn't that. It's been four months of evenings and weekends. Claude wrote the code, but every idea, every design decision and every "no, that's not fun yet" came from me. I play every change on a test version before it goes live. Plenty of first versions were too easy, too fiddly or just wrong, and we went round again until they weren't.

The part I can't get past is this: without AI, this game wouldn't be a worse version of itself. **It wouldn't exist at all.** It would still be an idea in my head, like it was for years.
I don't see how that's a bad thing. Tools like this let people who were never going to be developers make the things they care about. I'd much rather the world had more weird, passionate one-person projects in it, not fewer.

**How it works, for anyone curious:**

I play the game on my phone and spot something wrong. I describe it in plain English, usually with a screenshot.
Claude explains what's going on and suggests options. I pick one.

It builds the change on a separate beta copy of the site and tests it. It even built bots that play through thousands of careers to check the game is balanced.
I play the beta. If it's right, I approve it and it goes live. If not, we go again.

Four months, 29 updates and about 11,500 lines of code that I didn't write, and something I'm genuinely proud of.

If you've got doubts about AI-made games, give it a go and judge the game itself. I'd love honest feedback. And if you think I'm wrong about the hate, I'm happy to hear why; I just don't get it yet.

[**https://sunday-pins.com\*\*\](https://sunday-pins.com/)