We have just hit 500 members 🤯 ! To celebrate, I’m doing a game giveaway 🎉 If a free member wins: you get 1 game 🎮 If a Premium member wins: you get 2 games 🥰🥰🥰 The Games (You get to pick 1 (or 2)) - Resident Evil Village - SteamWorld Build - The Lord of the Rings: Return to Moria - Assassin's Creed Valhalla - Crysis 3 Remastered - Rogue Waters - Nordhold - Nice Day for Fishing (These are PC games, you will need STEAM) THIS IS HOW YOU ENTER THE GIVEAWAY👇👇👇 Drop your game idea in the comments. Funniest / weirdest / most playable idea wins!

Aww, we have new pic for @Morgan Page + new group name!! Exciting stuff!

I’ve created a Telegram game with 100k players, that generates thousands of dollars in revenue. With AI. If I were to coach you, what would you want me to help you with?

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.

Something for everybody! I probably haven't said it enough in here but I'm a massive OpenCode fan. Almost all my day to day is now done in OpenCode with GLM5.1(worth its own video) as my coding workhorse. So if you are interested in keeping your options, about as open as they can get, then checkout my OpenCode video below. However if you are thinking of doing a turn-based game at some point ( and if not, why not !? ), then check out my other video, it's very cool. Also there has been some interest in doing a community game together! Now how cool would that be? We could all share our workflows, learn from each other, argue about lore, mechanics, art direction... So here is a survey to gauge interest, if we get enough votes, we move to the next stage...