Tyrbo Make your game

An AI game engine where the AI is the builder, and the parts are tested

In most engines, a person sits between the parts and the game. They choose a physics setting, attach a script to a sprite, connect a button to a scene, and test whether it all holds. In an AI game engine, that seat is taken by the AI. It reads what you want, decides which parts the game needs, connects them, fills the gaps with new code and checks the result.

That is what Tyrbo means by the AI game engine. The AI does not invent everything from nothing for each request. It works like an experienced builder with a well-stocked shelf: most of what it reaches for has already been proven, and its own effort goes into the parts that are new to your idea.

Make your game

Sign in to get the plan and its concept art. Both are free.

  • Match-3 puzzle game concept art in the bright and bold lookMatch-3 puzzle · Bright and bold
  • Survivors game concept art in the 16-bit pixel lookSurvivors · 16-bit pixel
  • Platformer game concept art in the 16-bit pixel lookPlatformer · 16-bit pixel
  • Top-down adventure game concept art in the 16-bit pixel lookTop-down adventure · 16-bit pixel
  • Tower defense game concept art in the bright and bold lookTower defense · Bright and bold
  • Runner game concept art in the bright and bold lookRunner · Bright and bold
  • Cozy farm and garden game concept art in the cozy cartoon lookCozy farm and garden · Cozy cartoon
  • Card battler and autobattler game concept art in the gilded fantasy lookCard battler and autobattler · Gilded fantasy
Looks Tyrbo starts games from. Every game ends up with a look of its own.

Where the AI sits in the engine

Think of the engine in three layers. At the bottom are the tested bricks: grid board, free movement, side-view bodies, cards interface, currency and HUD displays, level progress, world maps and a world grid, plus map recipes for arenas, dungeons, caves, side-view levels, race tracks and tower-defense lanes. At the top is your game: its rules, its world, its look.

The AI lives in the middle. It translates the top into choices about the bottom. "A frog that hops between lily pads" becomes a world grid, a hop movement, a level progress track and perhaps a light physics body for the splash. You never have to name any of that; you only have to say what the frog does.

From your sentence to a parts list

Assembly starts with a conversation. The AI asks a short round of questions, each with a guess already selected, about how a round ends, whether play is calm or frantic, which orientation suits it and which look fits. Your answers narrow the parts it will need.

Then it writes a plan: a title, a pitch, every part of the game listed out, and concept art. The plan is effectively the engine's parts list in human words, and you read it before anything is assembled. Signing in to see it costs nothing. Changing a line here is far cheaper than changing a built game, which is why the AI shows it to you first rather than building on its own assumptions.

Writing only what the shelf does not have

No library covers every idea. When the plan includes something the bricks lack, a gravity flip, an enemy that copies your last move, a combo rule unique to your board, the AI writes it as clean code that belongs to that one game. It is attached to the tested parts rather than replacing them, so a new rule for scoring does not disturb a movement brick that already works.

This is the main difference from asking a chatbot for a game. A chat window produces one long file with nothing proven inside it. An engine assembled this way keeps the proven parts proven, and confines the unknowns to the small amount of code your idea actually needed.

Art fitted to the engine, not pasted on

An AI that generates art without knowing the game ends up with sprites at the wrong scale and models that fight the camera. Because the AI here also assembled the engine, it knows the camera angle, the screen orientation and which objects animate. The art is made for those facts.

Each game gets one look from 24 directions and a UI skin of fonts, palette, frames and buttons cut to match. Art comes from curated packs first and is generated where they run out, with 3D models rigged and animated so characters move rather than slide. The AI can also add tools just for you inside the game, such as a cheat that skips a level or a slider for enemy health, so tuning is something you do with your own hands.

Why the engine checks the AI before you see the game

An AI can be confident and wrong. So the engine does not take the assembly on faith. Before a game leaves, it must pass checks: no soft-locks, smooth play on a low-end Android phone, ads and purchases wired, leaderboards live, and a signed build you own outright.

That is the promise behind the phrase. The AI does the assembling, and the engine holds it to account. For the broader explanation of how this compares with coding assistants and asset generators, read what an AI game engine is. For the hands-on version from idea to phone, see make a game with AI or the AI game maker.

Ideas you could type

  • A frog that hops between lily pads catching fireflies, while a heron circles overhead
  • A shop on a mountain pass where you trade goods with travelers before a snowstorm closes the road
  • A tiny robot that sorts parcels on a conveyor belt that keeps speeding up
  • A garden defended by sunflowers that fire seeds at slugs crawling down three paths

From a sentence to your phone

  1. 1

    Describe it

    One sentence is enough. Say what you tap, what you dodge, what you win.

  2. 2

    Answer a few questions

    Each comes with our best guess picked, so most of the time you just tap Continue.

  3. 3

    See the plan

    A title, a pitch, every part of the game, and concept art, before anything is built.

  4. 4

    Play it today

    Scan the code and it runs on your phone. Change it by talking to it.

Built to ship, not just to prototype

Every game leaves the pipeline with all of this checked, not hoped for.

  • No soft-locks
  • Runs on low-end Android
  • Ads and purchases wired
  • Leaderboards live
  • A signed build you own

Questions people ask

What makes an engine an AI game engine?

The AI is the one choosing and connecting the parts. In Tyrbo, it plans the game with you, picks tested bricks and map recipes, writes new code where the library ends, makes art for the game it assembled, and the engine checks the result before you get it.

Does the AI write the whole game from scratch?

No, and that is deliberate. Most of a game comes from bricks that were tested on their own. The AI writes fresh code only for what your idea adds, which keeps the unproven part of the game small and the familiar parts dependable.

Can the AI get my game wrong?

It can guess wrong, which is why every guess appears as a question you can change and the plan comes to you before building. After the build, you correct anything by describing it, and the checks catch problems such as soft-locks before the game reaches you.

Who owns a game the AI assembled?

You do, with full ownership and commercial rights. You receive a signed Android build to put on Google Play under your own account, and the code written for your game belongs to your game.

Your game is one sentence away.

Make your game

Sign in to get the plan and its concept art. Both are free.