Notes from building a studio where the brief is a sentence and the output is a playable build: what to put in a prompt, what the agent needs around it, how a build gets tested before you see it, and where the line sits on other people's worlds.
We built a game engine for one reader: the agent. It runs in the browser and on desktops, builds in seconds, tests its own games, and loads a fraction of the size of the same game in Godot.
Epic takes the Windows build, any engine welcome. The studio now uploads and labels it for you; the organisation, the store page and the review are still yours.
Yes, and unlike Steam, Epic has published no AI disclosure rule. What its CEO has said instead, and the rules that apply whether or not AI made the game.
The studio can now profile a game on a cloud GPU in real time: frame rate, the 1% low, the worst frames and where each frame's time goes. We gave two games one performance turn each. One had a ten-second freeze nobody had seen.
Forge now makes 2D art: painted art in place of GPT Image and pixel art in place of PixelLab. We built the same two games with and without it, and here is how an early alpha compares with the state of the art.
Forge is the studio's own 3D asset pipeline. It rigs any humanoid onto one shared skeleton with a 170-clip animation library, and it can make the models too. It's an early alpha; here it is side by side with the Meshy rigs it replaces, and a whole game built both ways.
The studio now renders Pro games on cloud GPU machines. The agent checks its desktop graphics properly, gameplay videos come back in minutes, and you can play the full desktop build in a browser or share it with a link.
The Marketing kit now makes the App Store's new product page header and search art, iPhone Duo and 6.3-inch screenshots, Google Play's tablet set and alt text, and the videos: App Store previews, animated header and search loops, and 4K. Shown with one real kit.
Google AdMob ads and in-app purchases for the Android and iOS versions of your game. Pick the ad formats, say where they go and the agent wires them in. The browser version stays exactly as it was.
Epic has delayed its Disney shooter and told the team there will be no more hand-written code. Every vbgnt game is already made like that. Here is what works and what does not.
A lighter vbgnt you add to Claude, ChatGPT or a coding agent. Your assistant writes the game; arcadegnt builds it, plays it on a desktop and a phone, and puts it online. Free, with no API keys.
I always wanted to make horror games. In thirteen days I made four, set at night in the mountains of western North Carolina, each one a fork of the game before it. How they were built, what broke, and the desktop version with volumetric fog.
Two product launches, a warehouse safety course, a trade-show game and a portal of six games for a children's hospital, each built from a short brief for a made-up client. What each one does, why, and how to get one.
The Pawn Who Would Be King is a live-action fantasy series starring the heroes of a chess battler, with every episode ending on real gameplay. How the cast, the voices and the talking shots were made, what went wrong, and how to ask Promote for one.
Tick Pro and the studio builds your game for Windows, macOS and Linux on Godot's desktop renderer: real-time global illumination, volumetric fog, reflections. The browser version stays as the preview you test with.
Say what the campaign is about and how long it runs, and the agent cuts vertical shorts from your real gameplay, writes every post, checks which subreddits will let you post, and lays it out day by day. Four games, four campaigns, and what it refuses to fake.
A coding agent builds every game in the vbgnt studio. Here is which engine to give it, how to set it up, and the failures that only show up in production.
Rosebud, Star, Astrocade, Google Playground, Tesana, GDevelop, Replit and vbgnt, judged on the same five questions, with every price taken from the vendor's own page.
Yes, if it is small. Two Vibe Jams and nearly 2,000 games show what vibe coding makes, where it breaks, and how to do it so the game works.
Godot has no AI assistant of its own. Here is what the MCP servers, editor plugins and studios actually do, and how to tell a useful one from a chatbot.
Between nothing and $100 up front, then a share of sales. Every store's fee in one table, and the costs that are not on any pricing page.
Three routes, ending in three different places: a game inside an app, a web game on any phone, or a real app on Google Play and the App Store.
A new model is now live in the studio model picker. On day one we used it to build Kartropolis, Cat Person, and Fat Bear Week.
Potion Pile and Nine Heavens Ascent were written, illustrated, playtested, packaged and listed by the studio, then submitted by one person who wrote none of their code. Here is the division of labour, the step that still needs a Mac, and the one thing the agent refused to fake.
Tick the stores you want and the agent plays your game, captures real screenshots at every size they demand, composes the icons, capsules and feature graphics, and writes the listings within their limits. Browse the kit in the studio, download it as one zip, or publish the game's own page from it.
games.vbgnt.com now lists the games players starred across every arcade, ranked by what is being played this week, with search over titles, descriptions and styles. Opt-in per game, and your arcade stays exactly as it was.
Connect any assistant that supports MCP to your studio, sign in once, and your own agent can create games, follow the builds, manage your arcade and export the results from wherever you already talk to it.
Views, players, plays and playtime for every game on your arcade, split by platform, visible only to you. No cookies, no addresses kept, and nothing shown in public. Plus online high score tables for the games that keep score.
Ask for co-op or versus and the studio builds the lobby, the four-letter room codes and the invite links. One player hosts, the rest click a link, and the match runs browser to browser.
The arcade plays the web build. Everything else starts in the Publish pane: tick the platforms, press Export, and a build machine does the rest while you keep working on the game.
We read back every prompt that built the games in the gallery: 236 of them across 33 projects. Here is the order that worked, and what to say at each step.
The five games on the homepage started as concept art with nothing behind it. We had briefs written from the images, ran them through the studio, and published the results at demo.vbgnt.com.
Four unrelated technologies are sold under one name, which is why the demos look impossible and the free tools feel like toys. Here is the actual taxonomy.
Three genuinely different routes now exist, and picking the wrong one for your project is the most common reason people give up in week two.
In June 2026 Godot banned AI-written code. It banned it from the engine's own repository, not from your project, and the distinction is the whole answer.
Generating a good asset is easy. Generating a coherent set of four hundred is hard, and a game is made entirely of sets.
Yes, with disclosure, and since January 2026 the rules no longer ask about the tools that wrote your code. What that means, and what it still covers.
Steam will not take the web build, so the job starts with a desktop export. Then a $100 fee, a 30-day wait, and a store page that matters more than the game does.
The export is routine. The review is not. Apple's guidelines are pointed at exactly the kind of small, quickly-made game a generative studio produces.
Twenty-five dollars, once, and no Mac required. Then the obstacle nobody sees coming: twelve real testers, for fourteen continuous days, before you can ship.
The only one of the four the studio can finish for you. No native build, no signing, no review, no fee. Create the page, tick a box, and the Publish pane pushes the build.
For twenty years the interesting problem was finding something to play. The interesting problem now is that making one has become faster than searching.
A machine good enough to build the game you're nostalgic for is good enough to build it too faithfully. That is a product decision long before it is a legal one.
Your games land at your own address, laid out like a console dashboard. No feed decides who sees them, and that is a design decision, not a missing feature.
A game you have to install is a game nobody plays. The web build is the only target where "here, try this" is a link and not a favour.
A generated game that doesn't boot is worse than no game at all, because it costs you the ninety seconds it took to find out. So every build gets playtested first.
Every model can write a game loop. Almost none of them can hand you something that runs. The gap between those two facts is the entire product.
The difference between a generated game worth playing and a generated shell is almost entirely in the first two sentences. Here is what belongs in them.
The console I actually wanted didn't exist: one where the library is written on demand, in the fifteen minutes between having an idea and wanting to play it.
Everything here is how the studio works. The shorter version is: say what you want to play, and a few minutes later play it.