Us mods are working on some tooling to keep track of resources that devs should know about. Lets get a big list down below of resources everyone here finds useful:
Friendly reminder that we have a discord server you can all hang out at. The discussions there are much more in depth, and nothing beats being able to chat to other like minded devs in real time (or close to). Hop on this weekend and say hi.
I get it, the AI excitement is real when you make something playable in 1-3 days, but please stop coming on here and proclaiming you’ve made a game. You haven’t. You’ve made a tech demo or prototype. The real building will be in the coming months or even years if you hope to make something memorable, yes even with AI.
I’m not trying to discourage building with AI but the I built X in some ridiculous amount of time posts are getting ridiculous.
I'm 49 years old and live in Sweden. I've never developed a game before, but gaming has been a big part of my life for as long as I can remember.
I grew up playing games like Zelda, and as I got older, games like Diablo and Baldur's Gate really stuck with me. Those are the kinds of games that made me fall in love with gaming, and they're a big part of what inspired me to start making my own game, The Last One: From Ashby.
It's a fantasy RPG with turn-based combat, inspired by the games I grew up loving.
Since I had no previous experience in game development, I've been using AI tools to help me along the way. Without them, I probably wouldn't have been able to take on a project like this. It's been a lot of experimenting, learning new things, and figuring stuff out as I go.
So far, I've spent around 1,000 hours working on the game. There have been plenty of mistakes, frustrating moments, and late nights, but I've genuinely had a great time building it.
The game is completely free to play and runs directly in your browser. You don't need to download anything or create an account. Just choose to play as a guest and you're good to go.
I never really imagined I'd be making my own game at 49, but here I am. It's pretty amazing what you can create these days with an idea, some patience, and the help of AI tools.
I'd love for people to give it a try, and I'd really appreciate any feedback, good or bad. I'm still learning, and there's always something I can improve.
Most importantly, I hope some of you have as much fun playing it as I've had making it!
I used AI for Art, Code and sound. The rest is my own
Hi! I'm a solo dev, and Magemind is my first paid game: a pixel-art castle defense where you type (or say) any spell, like "turn the ogres into chickens" or "summon a war tank", and the wizard casts it. Since this sub cares about how AI is actually used, here's the honest breakdown.
Where AI was used
Almost all of the code (Godot 4.7, GDScript) was written with Claude Code. I direct, design, test and make the calls; Claude writes and fixes. The project keeps a long CLAUDE.md with my rules and known engine pitfalls, and test scenarios run the real game and save screenshots, so it checks the result instead of guessing.
The translations into 6 languages were made with AI help. Music, many sound effects and the trailer narration come from ElevenLabs. The rest of the sound effects are synthesized from code.
Where it wasn't
The pixel art isn't from an image model. Every sprite sheet is painted pixel by pixel by GDScript tools with a fixed palette. A nice side effect: changing a sprite means editing code, so the art can evolve with the game.
How the game understands spells
This is the part I'm proudest of. By default there's no LLM involved. A sentence goes through two small local pieces.
The first is a keyword grimoire: hand-written rules in several languages. "Rain of fire" is fire, not water. "Freeze the wolf" makes the wolf the target, not a summon. It also reads counts, colors and creature traits.
The second is a tiny classifier embedded in the game, fastText-style. The sentence is split into words, word pairs and 3 to 5 letter chunks, which are hashed into 131k buckets. The average of those vectors goes through one hidden layer and then into separate outputs, one per field: spell shape, element, creature, building, effect, range, target, size, which animal to turn enemies into, and "is this even a spell?". It's 9 MB (int8), loads in about 4 ms and runs in about 1.4 ms in plain GDScript, doing exactly the same math as the Python training code.
The rules decide when they find something clear. The classifier decides when they find nothing or only a weak hint, and that's where it shines: synonyms ("fry these goblins"), typos ("fierball"), voice mistakes ("idra" for hydra), slang, and sentences that aren't spells at all.
It was trained on 240k synthetic sentences generated from vocabulary lists, with typos and speech errors mixed in (the training code was written with Claude Code too). On a hard test set I wrote before training, 254 sentences with synonyms, typos and slang in 6 languages, the rules alone got 145 right. Rules plus classifier get 250. With words it never saw in training, it still picks the right spell shape 92% of the time.
What comes out is a recipe: one of 108 spell shapes, plus element, creature, count, colors and effect. The game, not the model, sets damage and mana from fixed rules, with hard caps: power 1 to 5, at most 12 projectiles or creatures, speed bonus at most 1.6x. Type "kill all the monsters" and the wizard gives it a try and faints. Nothing you type can break the balance.
Earlier versions used a local LLM (Qwen3 on llama.cpp). It understood well, but every spell took seconds and it needed a 5 to 18 GB download. The classifier replaced it and casting became instant.
The optional LLM
If you paste your own OpenAI key, a GPT model fills that same recipe through a strict JSON schema, with a spell name and a one-line description. Same caps, same damage rules, and any error falls back to the local path. Voice mode runs whisper.cpp on your own machine (Windows only for now).
a quick 10 mins playable concept of a hack n slash/open world game concept i've had for a while! made this in under 4 days and curious what yall feedback are on how i can improve! i was given a time limit of 4 days to make this for a game jam and i thought it would be fun to join and try to make something as a beginner who just started. this is my 3rd project i have ever made.
MARROW was made in 4 days by just me working with claude, meshy, tripo and fal. I directed the idea, the design, the look, the feel, and every decision about what went in and what got cut. The AI tools did a large part of the hands-on work under that direction.
all of the game's C++ was written by Claude Code (Anthropic) running in my terminal, inside Unreal Engine 5.9.
- Claude also drove the Unreal Editor directly through Epic's Unreal MCP and Python: importing assets, building parts of the level, setting up lighting and materials, and running automated screenshots to check its own work and show me previews.
- Every change was tested in game by me, and I sent it back with notes until it felt right.
3D MODELS: MESHY, TRIPO, FAL
- The hero, the enemy swarm and the girl at the camp started as AI-generated 3D models (Meshy and Tripo), made from my concepts and descriptions.
- Concept images and image edits were made with fal (nano-banana).
- The raw models were cleaned up, cut, decimated, re-textured and rigged in Blender, mostly through Python scripts written by Claude and some help from Codex.
ANIMATION
- The hero's attack swings and the beast's attacks were keyed in Blender through scripts written by Claude, then imported into Unreal.
- Running and movement use Epic's Game Animation Sample, retargeted onto our characters with claude.
UI AND EFFECTS
- The spine health bars are based on real life anatomy images, turned into game textures by scripts Claude wrote.
- The menu text, quest marker and other UI images were also generated by scripts.
- Effects like the ink splashes, sparks, wind lines and the PS2-style pixel look were built in Unreal by Claude to my direction.
SOUND AND MUSIC
- Hit sounds are my own chosen free assets sfx NOT made by ai, layered and mixed in with claude.
I still read all of the code that goes into my game. It is a slow and mentally fatiguing process. I even still write or edit about 20-30% of it myself. In fact, I think I'm working slower than I ever have now that I use AI tools. I've experimented and evolved my AI workflow a lot over the past 3 years, and this is the approach I've settled on recently, but I don't hear a lot of game developers talk about working this way.
Some background: in my day job I'm a senior software engineer with 10+ years experience. For that work, I exclusively stick to vibe coding--if it works, it's good enough, I can't be assed. There's too much pressure not to, and things move too quickly for well-crafted code to matter.
But for my game, I historically have dismissed AI tools because they make the code an unmaintainable mess, and I actually LIKE crafting the code for the game. I would try again every 3 or 4 months, but until the more recent frontier models, they all felt too unreliable and stupid to help me. That all changed with GPT 6 Astra. It was so effective and reliable when I used it at my day job, I decided to try using it to vibecode my game for a bit.
Well, the results were superficially very good, but it was still an absolute explosion of chaos in the codebase. And before you dismiss it as a skill issue, remember I do vibe coding for a day job, I know how these tools work and how to steer them. But still, an 8 year old codebase grew 2x in 1 month of vibe coding. Because I love this project, I AM looking under the hood at how things fit together, and the AI code was a disaster. Not a single system it built was reusable or modular. Maybe you are of the opinion that that doesn't matter anymore, and it doesn't for quick projects. But for a project you want to keep growing and adding to, this only makes things exponentially harder. Even if you have unlimited funds for tokens, eventually even the AI will have trouble working in a mess like that. So the past month or so I've been cleaning it up.
I'm still using AI tools to do this, but I'm back in VSCode reading through the actual scripts as I go. And I have to say, I really love this workflow. There will always be economic pressure to cut corners and rush out slop, but if you are in a position to ignore that pressure, this is the way. I am whittling the codebase down to well-defined primitives that are fun to compose and play with, and at the same time I'm not giving up the seeming omniscience AI provides us with. And if I need to prototype a feature, it's super easy to plan, to get a full picture of how it will interact with other features, build a sloppy first draft, and then refine/clean up. Additionally, now that Unity and Blender have really good integration with these tools, a lot of editing tedium has been eliminated as well.
I just wanted to post about this because sometimes it seems like the anti-AI camp says "ai leads to unmaintainable slop", which can be true, and the pro-AI camp says "you don't have to read code anymore", which can be true, but I rarely hear about people talking about how AI helps them make well-crafted, small, maintainable code much more effectively than ever before.
I started a game studio to see how far I can push AI game development. Not just one-shots or demos either, complete games from my extensive idea backlog!
KILLFACTION is my first project!
The game is a micro-extraction shooter that works a bit like a rogue-lite:
Carry out short missions on procedural maps
Earn money if you succeed
Buy equipment and cosmetics
Extract with your stuff in between missions
If you fail or die, you loose it all
Simultaneously, you can play 5v5 PVP mode online!
It's not just a demo, it's basically done (first round of cosmetics and all) - I'm at the network optimization phase, and just beginning marketing.
HOW IT WAS MADE:
Took about 2-3 months to get it to this point.
It was done with heavy ChatGPT usage - mostly Astra.
Godot (no MCP, the AI can just edit godot files!)
Local AI for the player model generation (Trellis 2 I believe).
Some of my own techniques for achieving consistency and clean rigging too.
I originally made this with Astra 6, but now that Astra 6.2 is out, I went back and polished it up a bit using Max reasoning.
Everything except the rabbit character itself was done by Astra — including the modeling, textures, the rabbit's animations, the mech's mechanical movement, and the VFX.
If your game trailer got more than 10 likes there’s already a chance someone might vibecode it in Roblox and add ton of microtransactions.
Since this phenomena has gotten insanely viral, it’s safe for you to assume that your game IS going to be copied, if you believe it’s a good game at least.
How to combat this?
Simply be you the guy who creates the Roblox slop version of your own game. When you are ready to deploy the official game you should already have done the slop one on Roblox studio, and release the Roblox version shortly after announcing to the public the original game.
Castle Defense: Medieval is a village builder mixed with tower defense. By day, you gather wood, stone and food and build your town. At dusk, your villagers take up arms. By night, you hold off raider waves with towers, siege engines, soldiers and arrow volleys.
How AI was used
Started as a prototype in a Claude chat, then moved into Claude Code for ~ 1k commits
All the 3D models, animations, maps and UI are code-generated with three.js, with no art packs
I designed each stage as a 2D sketch first, then had it built in 3D from the sketch
Playtesting was just me on my phone, sending screenshots with arrows and circles drawn on them
So far Godot has had very much anti-AI attitude, just a few months ago in June of this year they made a statement that basically LLM-assisted submissions are not allowed (on their blog and in their contribution rules):
"No autonomous AI agent use or vibe coding", "No use of AI to generate substantial pieces of code" and so on.
It'll never be publicly available though as i don't need Disney on my back lol. This is a personal project and i obviously own no rights to Star Wars. But i wanted to share some screenshots at least.
What’s in it: 8 missions across time (1953 Naples mafia, Maya jungle, Siberian base, Neo Hong Kong 2337, the Cretaceous, the Alps, medieval France, Hell → Heaven), ragdoll physics, kicks and slide-kicks, enemy pathfinding with different “intelligence” levels, an arcade challenge league, and a hub where you meet your characters.
How it was made: I put in all my ideas of what a fun FPS should be (bullet time, big kicks, skill shots, EXPLOSIONS). It took 100 published versions to get here. I started with one level in 1953 Naples and a pizza launcher, then kept iterating with Claude Opus 5.5 with Babylon.js which is in fact far less popular than Three.js.
I wanted to test direct character modelling in Blender. Headless, 30 minutes time limit. All four models have the same prompt - model this rat in Blender, time limit 30 minutes.
The results are pretty interesting.
Opus 5.5 Extra
Fable 5.2 High
Sol 6.2 High
Astra 6.2 High
A few interesting observations about Astra:
It was the only model that discovered I had the Tripo CLI installed and decided to start by generating the character with Tripo. I had to stop it and explicitly ask it to use Blender only.
After that, it discovered that the workspace already contained a version modeled by Sol 6.2 and decided to use it as a starting point rather than start from scratch. I had to stop it again.
It was also the only model that worked for the full 30 minutes without stopping. Every other model stopped twice, either asking for guidance or declaring the job done, and I had to encourage them to continue.
Which model do you think produced the result closest to the reference?
I can't code. I make browser games with Claude, and about five weeks ago I started a small Discord where people who make games with AI play each other's games and leave notes. It has 87 members and 37 games posted now, which is more than I expected. Here is what I learned so far and what I'm changing.
What worked
Asking one question. When a maker asks one thing, like is the first room too dark, the notes are much more useful than when they ask for thoughts.
A simple note format. What you did, one thing that worked, one thing that confused you, and an answer to the maker's question. It's short and the maker can act on it.
Notes turn into changes fast. Someone left a note on my jam game last weekend and I had the fix built two and a half hours later. My dungeon crawler has had 17 notes and most of what I changed in it came from them.
Saying which AI tools you used. Everyone does it, so nobody gets judged for it, and the notes get better because people can say things like the AI dialogue repeats.
What I'm changing
Sharing the playing. I still write most of the notes, and a few members now give notes without being asked. Getting more people to play each other's games is the next thing I'm working on.
One game per round for me. Last weekend I entered four of the ten games in our weekly feedback round, and the notes from members went to my games. Next time I enter one and leave the room to everyone else.
Less to read. The pinned post for sharing a game had a template, twelve tags and three more paragraphs. I cut it down.
Overbuilding. I added a login and game uploads to the site before anyone asked for them. I couldn't help myself, I like building things. This week the first person who isn't in the Discord added a game with it, so it wasn't for nothing. I'm still trying to wait until someone asks and I don't always manage.
If I started again I would do the same thing in the first weeks and play every game myself. It's the part I enjoy most, a new game every few days and then seeing it change after a note.
If you run or use a feedback group, how do you get people to play each other's games and not only post their own?
I made this game for Epic AI MegaJam 2026, and I got several positive feedback, but they was just one-liners, and It would be nice to get more deep feedback, recommendations what could be done better. I see a lot of things that should be improved, and I already have plan, but its really important for me to see some other perspectives, I would really appreciate your time and effort.
Characters sprites/animations was done by fal.ai (I have intentionally kept that small amount of frames for animations, and overall it looks a bit slop but it kinda fits in game art style in my opinion)
Sounds was fully done with claude and I fill that I don't like some detail about how it sounds, but I'm not sure what exactly. Maybe background noise should be tweaked a bit.
All other visual details (beside characters), was done entirely with code (Claude), procedural textures/sprites, a lot of shaders for fire distortion and visual artifacts for example.
This is almost entirely vibe-coded by Claude. As one of my earliest Claude projects, I wanted to do something as basic as a match-3 to see what could be done with it.
Starting with a simple, familiar concept proved to be a pretty strong foundation for something larger, as I developed new ideas and mechanics. My prompts haven't been anything extravagant; a conversational method of interacting with Claude has gone a long way.
At the very least, the code hasn't collapsed upon itself yet, which I'm considering a good sign.
The core idea is that every single swap drops a piece of loot. If you're like me and you're a "I like it when the numbers go up" kind of gamer, there is plenty of that.
In 20-40-minute runs (with an unlockable Endless Mode), you'll face off against 40 enemies, each with their own Traits and methods of messing with you and the board, plus additional Elite Traits that make things even more challenging.
Thus far, the loot system is pretty robust - I've implemented over 160 item properties, 6 rarities, 27 socketable Shards, nearly 70 Uniques, and a variety of ways to customize your gear.
There are 21 classes with different Traits, Weapon Affinities, and Paths, plus 140 Spells, all of which help you refine your builds.
Right now, there are over 120 Unlocks for new content - horizontal progression only.
Art was an uphill battle to get it consistent using ChatGPT, but through trial and error (and prompt help from Claude), I got it to create a few reference images where the style seemed to fit well and I built off those initial images and prompts over and over to get each piece of art fairly consistent (and hopefully not too sloppy).
I've put tons of hours of work in already and I'm constantly refining. My current goals for the next release are to add more Spells, enemies, and ways to more directly influence your build and create synergies.
This is a beta and it will remain free as long as it remains so. Would love to know what people think!
First of all, a big thank you to everyone who responded to my previous post! I honestly didn't expect so much advice, feedback, and encouragement. 🙏
One of the biggest discussions was whether I should move to Godot or keep building on my custom Three.js setup. I actually explored both directions and ended up leaning toward the latter. So here's a little update, along with some before-and-after images.
For those who missed it: I'm an art director, not a developer. What started as a simple 2D canvas experiment with Claude has slowly turned into Over The Edge, an isometric rally game built with Three.js. Inspired by classic Colin McRae, but focused more on arcade fun, ridiculous corners, and pushing friends off cliffs.
So, about that Godot port... Following some of your suggestions, I decided to give Godot a proper try. Surprisingly, it went really well. I built a way to export the generated stages into Godot, and before long, most of the game was running there.
But maintaining two versions quickly became a headache. Meanwhile, I also followed the advice to keep improving the custom Three.js engine, and many of the performance issues turned out to be fixable.
The biggest performance improvement actually came from rethinking anti-aliasing. Instead of relying on how Three.js was handling it, I experimented with a custom approach that turned out to be much more efficient for this particular game. It made a surprisingly big difference to how smoothly everything runs. I only discovered this thanks to Fable 5.2. and continuous tries to optimize.
So for now, I'm sticking with Three.js. Not because Godot didn't work, but because improving what I already had made more sense. And being able to share the game instantly through a browser is still a huge advantage. Plus I didn't feel like the performance took a giant leap compared to Three.js
The cars are still generated through code but different. Multiple people asked me how assets are made. (cars in this case) I've started using ChatGPT to generate blueprints based on real rally cars, then direct Claude to turn those references into 3D geometry using JavaScript. Before this method I had an example car and moved from there to generate more cars. The new way still isn't one-shotting cars through the pipeline.
There's a lot of comparing proportions, tweaking details, and iterating. Some cars still look questionable, but the newer ones are actually more detailed while using fewer polygons. Claude really doesnt like clean 3d models it seems. But it's slowly learning how to better itself based on past iterations. 😄
The cars became a lot more smooth and complex while at the same time lost 60% of the polygons. (cars now sit around 15k polygons)
Procedural stages need a human touch Just letting AI generate roads and environments doesn't necessarily result in something fun to drive.
I've directed Claude to build a system using building blocks I've designed, like different corners, elevation changes, villages, and obstacles.
I've let Claude create a stage editor to easily check what it generates
The endless mode generates new stages live using those blocks. But the regular stages still require lots of manual tweaking and testing to get the flow right.
A stage can look great from above and be absolutely terrible to drive.
@taisui asked me why I limited the camera angle to an isometric perspective. I tried to do it different. But I havent felt more nauseous in my life. Looks pretty though.
Making the world feel more alive I've connected ElevenLabs to create a co-driver who calls out pace notes and occasionally comments when you crash. That worked way better than I expected. I took a lot of inspiration from the Colin McRae series regarding the voice.
The rest of the soundscape was a combination between Claude generating basic audio and some sounds from an online Folio platform. So this has improved quite a bit, with cheering crowds, wind, gravel, dirt rubbing against the car, and the first proper crash and scrape sounds.
I use claude to compare different styles. And then review them first before making a decision.
The biggest thing I've learned Even though Claude does all the coding, I've spent a ridiculous amount of time directing everything.
Testing, tweaking, providing references, reshaping systems, and making sure things actually look and feel right.
As an art director, it's a familiar process, but AI can build something incredibly quickly without necessarily understanding what makes it good.
The procedural stages are probably the best example. Generating a road is easy. Making one that's genuinely fun to drive takes a lot more thought.
It's still pretty wonky and far from finished, but I'm happy with how much has changed.
For the people asking how much time this has taken. Ive tracked every minute of it. 😅
I'm curious if others working on bigger AI-assisted projects have experienced the same thing. Does AI actually save you time, or do you end up spending that time directing and refining instead?
Thanks again for all the feedback last time. It really has helped! For anyone curious to try the current version, it's playable directly in your browser:
Hey everyone! Back with another AutoSprite update. I've been working on this almost every day for close to a year now, and it's been pretty crazy seeing how far it's come.
I originally started building this because I always wanted an easier way to make characters for my own games. The idea was simple: take one character image, turn it into animations, and actually be able to play with it instead of spending hours putting spritesheets together.
Lately I've been really focused on isometric and 2.5D cozy games. Getting a character to look consistent while walking, farming, and dancing in 8 different directions is surprisingly difficult.
Some of the things I've added and improved recently:
8-direction isometric spritesheets for farming sims, life sims, and cozy games
Better character consistency across different animations and directions
Idle, walk, run, farming, dancing, and custom animations
Equipment and character customization workflows
A playable browser preview so you can actually test your character
MCP integration with Claude Code and Codex to help build games with your generated assets
My goal is still the same: one character image in, a complete playable character out.
It's definitely not perfect yet. Getting animations to loop smoothly, keeping equipment consistent, and making farming actions look good from every angle are all things I'm still working on.
But I feel like we're getting closer to making it possible for anyone with a cozy game idea to actually bring their characters to life.
I'd love to hear what you guys think, especially anyone working on an isometric cozy game. What's the biggest pain point you still have with character animations?
Thanks everyone for all the feedback over the past year. It's genuinely helped me figure out what to build next!
Key info: - We have an incredible panel of 20+ judges from the tech, AI and gaming communities. - ElevenLabs, fal, and Meshy are kind enough to be sponsoring the event and giving out free starter credits to participants. They are also giving out lots of credits to dedicated track-winners for "Best use of [their tool]". Sponsor prizes are separate from the $100k cash prize pool (which is funded by our platform). - You can use whatever tools you typically use to build and any major game engine that exports to the web, including ThreeJS, Unity, Unreal 5.9, Godot, Kaigen, and more - Browser games only targeting desktops (mouse/keyboard) with optional controller support. No mobile gameplay. Custom and proprietary engines are also permitted, provided the final game runs in a desktop web browser. Native desktop executables, Steam downloads, mobile games, touchscreen-only games, and games requiring specialized hardware aren't eligible. - This is beginner-friendly. Anyone can now create incredible, immersive games and experiences. Humans are the artists; models are just paintbrushes! - Games must be created during the jam. Pre-existing games or projects already in development are not eligible. Reusable assets, libraries, tools, and general-purpose frameworks are permitted, but pre-existing game-specific gameplay, levels, and substantial completed game systems are not. - We're looking for thoughtfully crafted games, not one-shot generations. We believe gaming is the ultimate form of art. Submissions must be complete, playable experiences rather than unfinished prototypes or technical demos. A complete game can be short or simple, but should deliver a cohesive, polished gameplay experience with a clear objective or replayable gameplay loop. Participants can submit up to 2 games; we value depth, creativity, and polish over quantity! - 18+ years old, individuals only (no teams). Open worldwide except where prohibited by law or applicable sanctions. Winners must complete required identity, eligibility, and tax checks before receiving prizes. Prizes are subject to applicable taxes and withholding. See official rules at opengame.io/jam for details. - To ensure fairness, we operate on an honor system supported by community reporting and verification of potential winners. We reserve the right to request development history, source code, or other evidence that a game was created during the jam, and to disqualify submissions that violate these rules. - The jam will be hosted on opengame.io. All submissions must be uploaded to and playable directly on the platform. - There is no required theme, but each game must fall into one of the 10 genres below.
Exact prize pool is as follows (i) Best Game Overall: $50,000 prize pool: 1st place receives $25,000, 2nd place $17,500, and 3rd place $7,500. All games are automatically considered, regardless of genre. (i) Top 3 in Each Genre: $50,000 total prize pool: Each of the 10 genres has a $5,000 prize pool ($2,500 for 1st, $1,500 for 2nd, and $1,000 for 3rd). Genres include Shooter & Survival, Action & Adventure, RPG, Platformer, Strategy, Simulation & Management, Racing & Sports, Fighting, Puzzle & Casual, and Party, Social & Sandbox.
*Prizes displayed are gross amounts. Payouts are net of any tax we are required by law to withhold. Each participant selects one primary genre for their game. We reserve the right to reclassify submissions that do not reasonably fit their selected genre. Each game can win only one cash prize, but may also win sponsor-specific credit prizes. Games awarded Best Game Overall cannot also receive a genre-specific cash prize.
This was a fun experiment I started 2 weeks ago. I was tinkering with AI-assisted workflows in Unreal Engine. I thought it would be really funny if someone tried to make GTA Manila before GTA 6, right before the meme ends.
The project is unfinished. I only have a single $100 Claude Max subscription and a $20 ChatGPT subscription. I did not use Tripo 3D, Meshy, or Hunyuan. I knew making an open-world game with realistic graphics set in the entirety of Manila within 2 weeks was unrealistic. I settled with the following assumptions and compromises:
Single-player only
Used free assets from Unreal Fab, and assets that I already owned. With limited token budget, it was impractical to create all the 3D models and animations from scratch using AI. I found a bunch of useful shaders, character animation, and vegetation assets that are worth it.
For custom 3D models, limited review loops to only 1-2. Claude as the 3D modeler while GPT-6.1 Sol Xhigh as the critique. This did not produce the results I wanted, but hey, I gotta work with what I have. Too many loops would burn through my tokens fast.
Only selected iconic locations of Manila will have high details while everything else is low-poly.
Moreover, I was working on other projects besides this one. Not all of the Claude Max subscription was used here. In the end, I was not able to implement the features I wanted. There are still many missing systems.
Lessons learned:
Having a good prompt and excellent reference images can carry the quality of the output by a lot.
Probably sounds obvious to most of you, but to me the biggest mistake I did were the lousy skills and references I was using during the early stages. I made the mistake of adding too many rules which prevent Claude from trying different approaches. Use /doctor and double check that your setup follows the Claude Opus and Fable prompting guide. Regarding reference images, the reasoning is in the next item below.
2. Art Direction > Realism.
This applies especially to lighting, post-processing, and visual effects. A wise 3D artist once told me, "Great lighting and post-processing can make mediocre 3D models look good". It's certainly possible to get great 3D models by giving Opus a lot of reference images and have it undergo multiple review loops with itself or GPT-6.1 Sol. However, when putting all the objects together and assembling the scene in Unreal, my initial results looked bad because Claude was taking inspiration from real-world location lighting. I recommend gathering references of lighting setups in modern video games, film, or edited photographs to deliver the mood and atmosphere you're trying to achieve.
3. Fable 5.2 is INSANE, but deym is it a token furnace.
I know Fable can one-shot entire games that look amazing. However, with the limited amount of Fable tokens I have, I used it primarily on lighting, post-processing, cutscenes, and character animations.
4. Start building your personal 3D asset library.
Lots of free high-quality assets out there. Create your own asset browser tool and have your agents scan through it recommend you assets before attempting to create something.
5. Texture shimmering, light and shadow flickering, z-fighting, Lumen splotches.
These things can sometimes go under the radar without getting fixed because Claude only analyzes a couple of frames not in a sequence.