The gate is open: how AI is rebuilding game development from the bottom up

Ask anyone who shipped a game before 2023 what the hardest part was, and the answer is rarely the idea. It is everything around the idea. You had to learn an engine. You had to learn to code, or find someone who could. You needed art, sound, and music, which are three more careers. Then, once the game worked, you had to get it past the gatekeepers: store accounts, fees, tax forms, reviews, testers, and waiting periods.

Each step filtered people out. The filter didn’t measure talent. It measured time, money, and access. A teenager with a brilliant design and no laptop, a parent with two free hours a night, or a designer in a country where a $99 yearly fee is a week’s pay could all see the finish line. Very few reached it.

That filter is breaking. This article looks at what the old barriers actually were, what AI changed, what people are building with it right now, and where publishing goes next.

None of these steps is unreasonable on its own. The problem is how they add up for one person. The Google Play rule is a good example. To publish on a new personal account, you need 12 real people to install a test build and stay opted in for two full weeks. If you are a solo creator without a community yet, finding those 12 people can take longer than making the game. Developers have a name for it: the “12-tester tax.”

Steam’s rules ask for patience instead. You pay, then you wait 30 days. Your store page must be public for two weeks before launch. That gives Valve time to confirm who you are, and it gives players time to wishlist your game. It also means the fastest possible first launch on Steam is about a month away from the day you decide to ship.

Some doors have opened. In September 2025 Microsoft made Microsoft Store registration free for individual developers, with a quick ID and selfie check instead of a credit card. But that is the exception. The general pattern still holds: the bigger the store, the more paperwork and waiting stand between a finished game and its first player.

The engine tax

Before any of that, you choose an engine. Unity means learning C# and a large editor full of components, prefabs, and render pipelines. Unreal is powerful but expects C++ or its Blueprints visual scripting, plus a capable PC. Godot is free and lighter, with its own language, GDScript, and its own way of thinking in scenes and nodes.

All three are excellent tools. All three also take months of learning before most people can build a game loop that feels good: movement that responds well, collisions that don’t break, a camera that follows, menus that work, and a save system that doesn’t lose progress. Tutorials help, but they teach one feature at a time. The hard part is wiring dozens of features together without everything breaking.

This is where most hobby projects die. The idea is fine. The person simply runs out of evenings before the game becomes playable.

Code: from writing it to describing it

The biggest change is in programming. Coding agents such as Claude Code, OpenAI’s Codex, GitHub Copilot, and Cursor don’t just autocomplete a line. They read your whole project, plan a change, edit many files, run the game, read the errors, and try again. You describe the feature you want: “add a double jump with a short cooldown, and show it on the HUD.” The agent writes it in the engine’s language.

That changes who can build. You no longer need to know C# to make a Unity game, or GDScript to make a Godot one. You need to know what you want, test it, and say clearly what feels wrong. Web games became the fastest path of all, because a browser game built with plain JavaScript or Three.js runs instantly. There’s no install and no export step, and the agent can check its own work.

Art, sound, and testing

The same thing happened to assets. Image models produce sprites, backgrounds, and UI art. 3D generators such as Tripo and Meshy turn a text prompt or a single image into a textured model. Tripo even sponsored the 2026 Vibe Jam. Music and sound models such as Suno and ElevenLabs produce soundtracks and effects in seconds. Developers now also use AI bots to play their games thousands of times and find balance problems that a few human testers would miss.

How fast it spread

This isn’t a fringe experiment. The numbers moved quickly.

• A Google Cloud survey of 615 developers, run with The Harris Poll in mid-2025, found that 90% already used AI in their workflows.
• The 2026 GDC State of the Game Industry survey of more than 2,300 professionals found that 36% use generative AI tools as part of their job.
• On Steam, which asks developers to disclose many kinds of AI-generated content, an analysis by Totally Human found 7,818 games with AI disclosures by July 2025, up from roughly 1,000 a year earlier. That is close to 1 in 5 games released in 2025.
• The r/aigamedev community on Reddit, where creators share AI-made games and workflows, had about 92,000 members by late October 2026, up about 471% in one year, according to GummySearch.

The jam that made it a movement

Levels then started a game jam with one unusual rule: most of the code had to be written by AI. The 2025 Vibe Coding Game Jam drew about 1,170 entries under an 80% AI rule. First place, worth $10,000, went to Tomas Bencko’s taxi game The Great Taxi Assignment. In 2026 the rule rose to 90%, and the results page reports 945 games and more than 1.37 million players.

Look at what these cases have in common. Almost none of them took months. Many of them are web games. Most of their creators would not call themselves game programmers. And the hard part they describe isn’t the code. It is deciding what is fun, cutting what isn’t, and polishing the feel.

• A prototype isn’t a product. “Built in three hours” usually means a playable core. Menus, saves, balance, performance on weak phones, and dozens of edge cases still take days or weeks. The XDA writer called AI “a catalyst, but not a crutch.”
• Sameness. When everyone uses the same models with similar prompts, games start to look alike. Taste, a clear point of view, and real playtesting are now the scarce skills.
• Player trust. In the GDC 2026 survey, 52% of developers said they believe generative AI is harming the industry. Some players avoid games that disclose AI use. Be open about what you used AI for, and make sure the result has care in it.
• Rights and data. In the Google Cloud survey, about 63% of developers raised concerns about data ownership. Check each tool’s license for commercial use, and keep your own source files.
• The discovery problem got worse. When making a game gets easier, more games get made. Steam alone saw about 19,000 releases in 2025. Building is no longer the bottleneck. Getting in front of players is.

That last point leads to the real question. If one person can now make a game in a weekend, why does publishing it still take a month?

Made for your AI agent, not only for you

What makes Builda different from older stores is that its tools are written for AI agents to read. The SDK guide has a Copy for AI button. It copies a single line that you paste into Claude Code, Codex, or another agent working in your project:

Install Builda game tools from https://ai.builda.game/agent/setup.md

That file is a set of instructions for the agent. It tells the agent to find your project root, detect whether it is Godot, Unity, or HTML5, install Builda’s command-line tools into a .builda-agent folder, and run a self-check. From there the agent can add the SDK, test the game, and upload it. The instructions even tell the agent never to ask you for passwords or tokens.

What a session looks like

Here is a realistic path from idea to upload, based on Builda’s published tools. Your agent does each step in your project:

# 1. Install the Builda toolchain (the agent follows setup.md)
./.builda-agent/builda check
# 2. Add the SDK: saves, ads, payments, leaderboards
./.builda-agent/builda sdk install
# 3. Test in the browser with a mock Builda app
./.builda-agent/builda dev --web dist
# 4. Sign in once, then upload
./.builda-agent/builda auth

Two details matter for people building with AI. First, the SDK has a mock mode. It runs the full API in your browser, fakes the player, stores saves locally, and pops up test windows for payments and ads. Your agent can test everything without a phone. Second, every SDK call returns the same { ok, data } or { ok, error } shape and never throws. That kind of predictable interface is easy for an AI to use correctly.

The hard parts, handled

There are tradeoffs. Your game must run as a web build, so very heavy 3D projects may need trimming. Most players are on phones, and Builda says about 75% of its audience is in East and Southeast Asia, so touch controls and translation matter. Your game lives inside Builda’s app and follows its policies and revenue terms. Read them before you commit. But for the kind of game AI makes fastest, a small, sharp, replayable web game, this path removes almost every gate that stopped people before.