I flipped a coin... and tails won. 😆 That means the Arcade Fighting Game officially wins the coin toss, and we're starting a brand new project for Create Games with AI. Honestly... I'm way more excited than I probably should be. For those of you who take the time to read this, I wanted to share some feedback from the AI I've been building games with for over a year. I started this journey with zero coding experience, learning by stumbling forward one project at a time. My goal is simple: Create an arcade fighter that feels retro, but polished, responsive, and genuinely fun. I want it to be the kind of game that's still calling you back after your first 10 minutes. I'm not even much of a fighting game player anymore, but growing up with Mortal Kombat, Street Fighter, Dead or Alive, Tekken, Marvel vs. Capcom, and countless anime fighters, there was always something that kept me coming back for just one more match. That's the feeling I'm chasing. If I can capture even a little of that spark, I'll consider this project a success. Ambitious? Absolutely. 😂 Anyway... here's the reality check my AI gave this madman before we started. [CHATGPT] If we were sitting in a coffee shop after a game jam, here's what I'd tell you. 1. First impression My first thought wasn't: "This is revolutionary." It was: "I could lose 20 minutes playing this." That's a compliment. There are two kinds of indie games. One says: "Look at this crazy mechanic." The other says: "That feels really good." The second category quietly makes money far more often. From everything we've built so far, Project Spirit isn't trying to reinvent fighting games. It's trying to make one that feels fast, readable, and satisfying in the browser. That's a legitimate goal. Would I play it? For five minutes? Absolutely. Would I come back? Only if you give me reasons beyond the first dozen matches. 2. The hook Here's where I think people accidentally describe the wrong hook. You said: Simple 90's fighting game with updated moves and visual effects.

Momma J's Pizzeria is a story-driven time management game where you work your way through increasingly hectic pizza shop shifts while experiencing a comedic narrative about life, customers, and working in a neighborhood pizzeria. Based on characters created by my friends. Who is it for? Players who enjoy casual games they can jump into for 10 to 30 minutes, fans of cooking and restaurant games, and anyone who likes humorous stories with satisfying, fast-paced gameplay. What's the core mechanic? Listen to customer orders, remember them, prepare the correct pizzas and drinks, deliver them before customers leave, and survive the growing chaos as each shift becomes faster and more demanding. I have the foundation down so far the voice acting and the storytelling is being built in

Hey I'm Fame, I'm working on Time Management game. My experience with coding is absolutely zero 😅 but my experience with video games is over 35 years lol. The game I want to ship.... well i can not because it will be the first of its kind 😅 so instead i'll focus on the time management game which will be a cooking simulation/restaurant management game where players race to prepare and deliver pizza orders while surviving the chaos of working at a neighborhood pizzeria 🤗

I've been experimenting with a different AI game development workflow and I'm curious if anyone else works this way. Instead of building an ugly prototype first and worrying about the UI later, I start by generating the actual game screens. I create a PRD, then use ChatGPT, Figma AI, or similar tools to generate screen concepts and even prompts for the content that should appear on each screen. Because everything is based on the PRD, the screens already reflect the intended gameplay and progression. Next, I have my coding AI recreate those screens as a working prototype using mock data. At this stage I'm not focused on databases, APIs, progression systems, or backend logic. I'm only testing whether the screens feel right, whether the user flow makes sense, and whether the game is actually fun to navigate. Once I'm happy with the experience, I simply replace the mock data with real systems and connect everything together. I'm currently doing this for a diablo-like idle-game. Below are a few of the AI-generated screen concepts, followed by the current prototype, which is still in the mock-data phase. 👉 https://idle-hero-loot.lovable.app/game So far I've found that this approach helps me spot UX and gameplay issues much earlier than when I start with functionality first. Has anyone else tried a screen-first workflow like this? Do you design realistic screens before implementation, or do you still prefer building the systems first and polishing the UI later? Would love to hear how others approach AI-assisted game development.

Pixel Power was created so fast in CHATGPT! Looking forward to what i can create!