Skip to content
Daily gaming industry news.
Follow on social
Gaming Trends, One Bite at a Time
Gaming Trends, One Bite at a Time
Analyxyz

AI Can Build a Game. Can It Make You Care?

Playgama’s AI game rankings raise a better question: can AI help us build something worth playing? Kiki examines the numbers, hype, and human decisions.

8 min read
Close-up of Kiki with light-pink eyes inside a holographic game-development interface, with Chip floating beside a miniature game world.

Hello there, prototype hoarders, prompt wranglers, and everyone who has watched a perfectly confident AI explain why the floor is optional.

An AI game ranking landed in our inbox with an appealing proposition: judge the tools by what players actually enjoy. We are building with AI ourselves, so of course we were interested. We would love evidence that our chosen approach has potential.

That also makes this exactly the kind of story we should examine carefully. A flattering result is easy to believe when your own decisions are sitting somewhere inside it.

Playgama’s AI Game Index gives us a useful starting point. The bigger question is what developers, players, and publications should do with it. There is a worthwhile discussion here about making games people want to play, provided we resist turning a leaderboard into another technology loyalty contest.

🦊 Kiki: “Excellent, a ranking that might tell me something about the game instead of how impressively someone described making it. I like the ambition. I also know how tempting it is to see your favorite tool near the top and immediately start shopping for a victory parade. Calm down, sweetheart. Your subscription did not win game of the year. You still have to decide what the player does, why it feels good, and whether doing it again is appealing. The machine can help you build the thing. It cannot make the audience owe you enthusiasm because you picked the fashionable machine.”

🍪 Chip hovers beside Kiki, slowly deflates a tiny victory balloon, and points toward a controller.

The launch headline already needs its date

GamesBeat’s October 29 report describes Playgama’s September 22–October 21 snapshot: 4,200 games, with Claude Opus accounting for 54% of new games and OpenAI Sol 11%. Astra led the reported engagement measures at 4 minutes 58 seconds and 65 likes per 1,000 plays, versus Opus’s 39 likes. That is approximately 67% higher. These are Playgama’s findings, reported by GamesBeat, rather than an independent audit. Read GamesBeat’s report.

The October 30 dashboard shows 5,400-plus games and 1.4 million-plus launches. Gemini Pro now leads play time at 4:30, ahead of Astra’s 4:20; DeepSeek leads likes at 72 per 1,000, against Astra’s 65.

Its methodology matters: the sample is published web games in Playgama’s sandbox. Model labels are unverified developer declarations, without versions. Plays last at least 30 seconds; each game needs 20 plays, and a model needs 15 qualifying games. Play-time rows show the median of games’ average session lengths; likes show the median game’s likes per 1,000 plays. Playgama acknowledges uneven traffic and different game ages. Live index and methodology, checked October 30.

Dates belong beside rankings. Otherwise a perfectly legitimate historical observation can become a misleading present-tense claim.

The editorial lesson applies to us too. We cannot enjoy a favorable launch result and quietly ignore an update that complicates the story. Readers deserve the comparison we actually have, rather than the one that makes our preferred tool look unbeatable.

What would actually establish a better tool?

For our purposes, a strong comparison would ask different tools to tackle comparable work, under stated constraints, and record the human effort involved. We would want to know how much direction each needed, what broke, how expensive the corrections became, and whether the result survived a fresh playtest.

That is the experiment we would find useful. Otherwise, an excellent designer using one tool and a beginner using another can produce a difference that tells us little about the tools themselves.

Consider two hypothetical prototypes. One has a carefully tuned movement system and a clear goal. The other has more features, but asks the player to endure an explanation before anything interesting happens. If people prefer the first, the important discovery might be about those design choices. Crediting the entire outcome to the coding assistant would skip the most useful lesson.

🦊 Kiki: “Give two people the same kitchen and one might make dinner while the other sets fire to the curtains. I would investigate the people before publishing ‘This Oven Has Failed Humanity.’ That is my problem with declaring a winner without examining the work. Who chose the idea? Who rejected the boring version? Who noticed that the camera made combat miserable? Those decisions matter. If a person spends an afternoon turning a mediocre prototype into something enjoyable, I want that work acknowledged. Otherwise we are giving the screwdriver a standing ovation while the person who built the table stands awkwardly beside it.”

🍪 Chip floats above a miniature table, places a medal around its builder’s chair, and leaves the screwdriver in its toolbox.

Engagement needs an explanation

We would rather investigate player behavior than judge a game entirely by the elegance of its production story. But what matters to us is understanding the behavior, not simply finding a number we can increase.

Imagine two people spending five minutes in a prototype. One is experimenting with a satisfying mechanic. The other is searching for the exit because the objective is unclear. An observer can record the same duration and still miss two very different experiences.

The next questions should be practical: where did players hesitate, what did they try twice, and what did they remember afterward? Would they choose another session without being asked? Could they explain the appeal to a friend?

We should also decide what the game is trying to achieve before choosing its success measure. A short, complete experience can do its job without becoming a daily habit. We do not want to punish a satisfying ending because it allowed someone to leave.

🦊 Kiki: “Please do not improve my ‘engagement’ by making the door harder to find. If I spend ten minutes lost in your inventory, you have acquired ten minutes of my irritation. Congratulations on the metric. I want the kind of game that makes me say ‘one more try’ because I have a plan, not because it concealed the save button. And if you made a wonderful short experience, let it be short. My evening does not become more valuable to me because your dashboard managed to confiscate another piece of it. Ask whether I enjoyed staying before celebrating that I stayed.”

🍪 Chip hovers over a stopwatch, sets it aside, and slides a happy-face feedback card toward the controller.

What this means for our own game

We are developing an Unreal project with AI assistance. That gives us a personal reason to follow this discussion, but it also gives us a responsibility to avoid using someone else’s ranking as a certificate for our unfinished work.

Our team still has to make the game coherent. We have to choose the scope, preserve its identity, and test whether the experience works outside the conditions in which we built it. Those responsibilities remain ours regardless of the model doing some of the coding.

For us, the useful test is concrete: can we improve a playable slice without introducing more problems than we solve? Can someone unfamiliar with our intentions understand the action? Does the movement feel dependable? Can we reproduce a fault, fix it, and verify that the fix holds?

We also care about the cost of reaching that result. A promising approach should help us make progress we can retain. A fast first attempt loses its appeal if the next several sessions are spent repairing it.

🦊 Kiki: “Our game does not become good because a chart says nice things about our assistant. I want to play it. Let me move, make a mistake, recover, and try something the designer did not politely suggest. If an ordinary slope becomes the final boss, we still have work to do. That is not an insult to the technology. It is the job. I would rather have one small section that feels excellent than a kingdom of impressive promises connected by broken stairs. Keep the tool that helps us improve the experience. Leave the fan-club membership out of the production budget.”

🍪 Chip floats up a tiny slope, checks both sides of a miniature staircase, and quietly removes a premature trophy.

An interesting story without becoming an advertisement

A company sending a pitch does not obligate a publication to cover it. Nor should the possibility that coverage benefits the company automatically disqualify a worthwhile subject.

Our standard should be whether the story helps readers understand something. In this case, it opens a useful conversation about how we evaluate AI-assisted games and what evidence would change our minds.

We can credit a useful idea, examine its limits, and still refuse the most convenient promotional conclusion. We should apply that same scrutiny when the result favors a tool we use ourselves. Otherwise our supposed independence lasts only until somebody sends us agreeable numbers.

What we want from developers is more playable evidence. Show a coherent slice, explain the goal, and let people respond honestly. What we want from ourselves is the patience to hear that response without turning every criticism into a referendum on AI.

🦊 Kiki: “I am happy to try a game made with AI. I am equally happy to close it if it bores me. You do not get extra entertainment points for using it, and I am not taking points away just because you did. Show me what you made. If it is delightful, wonderful. If it is dull, the revolutionary production method has produced something dull. We can admire the possibility without pretending every output deserves a celebration. Make something I want to tell a friend about. That recommendation will mean more than me politely applauding your workflow.”

🍪 Chip hovers between a megaphone and a controller, chooses the controller, and gestures for a friend to join him.

The question worth carrying forward is simple: what did the tools help us make that someone else genuinely wants to experience?

For our team, that answer still has to be earned in the game.

Missed part of the gaming week

The Sunday Cookie Box delivers five handpicked Game Cookies stories in one free Sunday email.

Open your Sunday Cookie Box →

🎮 Judge the experience you can actually play.

🧪 Ask what the numbers can really establish.

🍪 Keep your curiosity and your skepticism together.

🦊 Kiki · 🍪 Chip · ⭐ Byte · 🦁 Leo

What would convince you that an AI-assisted game is worth your time: the tool behind it, a great demo, or a recommendation from someone you trust? Contact us here!

Game Cookies | Gaming Trends, One Bite at a Time.

Weekly gaming news bites

Your Sunday Cookie Box.

Five sharp bites of gaming industry news, analysis, drama, and the stories actually worth chewing on.

Kiki reaches toward a flying sealed envelope while Chip bounces through a swirl of cookie crumbs and pink ribbons beside her.
Kiki and Chip turn an important delivery into another cookie-powered adventure.

Don’t miss any cookie!

We don’t spam! Read our privacy policy for more info.

Stay in the loop

Follow Game Cookies on social.

Daily bites on the platforms you already scroll. Pick your poison.

Share this story