Tyrbo Make your game

A no-code game engine where a sentence takes the place of the script

Every engine needs some way for you to say what should happen. Traditional engines use scripts in a programming language. Visual tools swap the language for node graphs, blocks or event sheets, where you connect boxes and conditions instead of typing. Those are real improvements for many people, but they are still programming: you have to learn the vocabulary and think in the engine's logic.

Tyrbo is a no-code game engine with a different input. You write what should happen in an ordinary sentence. The engine turns it into a plan, chooses tested parts to carry it out, writes new code where needed, and lets you check the result on your phone.

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.

Three ways to tell an engine what to do

Take one rule: when the hero touches a coin, add one to the score and play a chime. Here is how different engines want it expressed.

  • A script. You write a function that listens for a collision, checks that the other object is a coin, increments a variable, plays a sound and removes the coin. Exact and flexible, but you need the language and the engine's conventions.
  • A node graph or event sheet. You drag out a collision event, connect it to a condition, then to actions for the score, the sound and the removal. No typing, but the same logic in visual form.
  • A sentence. "Coins add one to the score and chime when the hero grabs them." Tyrbo works out the collision, the counter, the sound and the cleanup.

All three produce a working rule. Only the last one asks nothing of you beyond describing the game.

What happens to your sentence inside the engine

A sentence is vaguer than a script, so the engine has to resolve it. Tyrbo does that in stages. First it asks short questions where your words leave room, each with a guess selected: does the coin count reset per level, should the chime change pitch in a combo? Then it writes a plan listing every part of the game, which you approve.

During the build, the sentence maps onto bricks: the currency display shows the score, the movement or side-view body brick handles the touch, and any unusual rule, such as coins that turn into bees after dark, is written as new code for your game alone. You never wire the pieces; the engine connects them.

Changing a game by saying what is different

In a scripted engine, a change means finding the right file and editing it. In a node editor, it means finding the right graph and rewiring it. In Tyrbo, it means describing the difference: "make the boss slower in the second phase", "add a double jump", "let the shop sell a shield". The engine applies the change to the game you already have.

You can even ask for tools that a developer would normally build by hand. A button that spawns an enemy, a cheat to skip to the last level, sliders for gravity or enemy health: the AI writes them into the game for you, so you can tune values with your thumb instead of typing numbers into a panel.

What you trade, and who it suits

Sentences are not free of trade-offs. A programmer in a general-purpose engine can control every line, which is the right fit for people who want to program and enjoy it. With Tyrbo you give up that line-by-line control in exchange for never needing it. You steer by design decisions rather than implementation details.

That suits people who have ideas and limited time: designers, artists, hobbyists, teachers, anyone whose first game has been stuck behind a tutorial. It also suits mobile games in particular, where the hard parts beyond the rules (running on low-end Android, no soft-locks, ads and purchases, leaderboards, a signed build) are things the engine checks rather than things you assemble.

Getting started without a script

Open the workbench in your browser, write the game in a sentence, and answer the questions. Signing in to see the plan and its concept art costs nothing; building runs on paid plans with monthly credits.

For help phrasing that first sentence, read how to write a game prompt. The no-code game maker page compares this approach with block tools from the maker's side, and make a game without coding walks a first project from start to finish.

Ideas you could type

  • Coins chime when the hero grabs them, and every hundred coins buys a new hat in the shop
  • A pirate ship that fires cannons left or right with a swipe while sea serpents rise from the waves
  • A library where books fly off shelves and you tap to catch them before they hit the floor

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

How is a no-code game engine different from a visual scripting tool?

Visual tools replace typed code with nodes, blocks or event sheets, but you still build the logic yourself. In Tyrbo you describe the behavior in a sentence, and the engine decides which parts and code carry it out.

What if my sentence is ambiguous?

The engine asks. Before building, it turns open points into short questions with a suggested answer selected, and the plan shows every part of the game for you to approve or correct.

Can I still make complex rules without code?

Yes. Rules the tested bricks do not cover are written as new code for your game. You describe the rule, such as enemies that split when hit by fire, and then play it to check it behaves as you meant.

Do I need to understand programming concepts at all?

No. Words like variable, event or collider never come up unless you want them to. You talk about the game: what the player does, what stops them and what counts as winning.

Your game is one sentence away.

Make your game

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