Creating a game takes three steps: say what should be practised, read and adjust the plan, then build. The plan step exists so you can reject an idea for one credit instead of twelve.
1. Say what learners should practise
Open Games in your classroom and start a new game. Describe the practice objective in your own words, the way you would describe it to a colleague:
A game where learners fix a broken sorting algorithm step by step and watch the array reorder.
Words fall from the top of the screen and the player catches the one matching the definition, for beginner vocabulary review.
Aim at what learners should get better at, not at the game mechanics. The mechanics are what the plan is for.
2. Read the plan
TutorFlow drafts a plan before it builds anything. It takes about a minute to read and covers what kind of game it is, what the player does, and how a round is won or lost.
This is the cheapest point to change your mind. Adjust the objective, the levels, or the win condition, or discard the plan entirely. Editing here costs nothing; discovering the same problem after the build costs a rebuild.
3. Set how it should play
Alongside the plan you can set how the game is built:
| Setting | Options | What it changes |
|---|---|---|
| Dimension | 2D, 3D | Whether the game renders flat or in three dimensions |
| Play length | Short, Standard, Deep | How long a single round runs |
| Visual style | Minimal, Cartoon, Pixel, Low poly, Neon | The art direction of the generated game |
| Persistence | Session, Local | Whether progress survives closing the tab |
| Audience | Free text | Who the game is for, in your words |
Persistence is the one worth a thought. Session means a learner who closes the tab starts over, which suits a five-minute drill. Local keeps their progress on that device, which suits something they come back to.
Title and description are yours to set here too, and both can be changed later.
4. Build and play it
Building takes a few minutes. When it finishes, the game opens in the editor and you can play it on the spot, exactly as your learners will see it.
Play it through once before sharing. TutorFlow has already confirmed the game runs and responds to its controls, but nothing has judged whether the difficulty is right for your class or whether the questions say what you meant. That part is yours.
If something needs changing, you do not start over. See Edit and Share a Game.
If the build fails
A version that will not start, or that freezes partway, is rejected and rebuilt rather than handed to you. If a build fails repeatedly, the objective is usually asking for something the generator cannot express yet. Narrowing it helps: one mechanic, one topic, one clear win condition.
Game generation is newer than the rest of TutorFlow and the range of what it can build is still growing.