Table of Contents
You can create a game in Builda by starting a project, placing assets on a map, and connecting events to actions with blocks. Begin with one playable scene and one goal. Once movement and the goal work, add interface elements, progress data, and more levels.
Builda’s app listing describes its drawing, animation, community, and block-coding tools. The screenshots below show an editor layout; labels and available templates may differ by app version or language.
1. Start a small project

- Open Builda on your phone or tablet and select Create or the large + control.
- Start a new project and choose a template close to the game you want to make.
- Keep the first version small: one map, one player character, and a clear objective such as collecting an item or reaching an exit.

A working template is useful because you can inspect how its controls and events are connected before changing them. Save a separate copy when the app offers that option.
2. Find the main editor controls


The editor combines a map canvas, asset categories, scene settings, data, and a test control. Use Map for the level itself and switch to UI for screen elements such as buttons and score displays.

- Back: Return to the previous editor or project screen.
- Undo and redo: Reverse an accidental edit or restore an undone action.
- Search: Find assets rather than scrolling through the entire library.
- Menu: Inspect additional editor options. Read the available labels before applying a setting.

- Settings: Adjust the scene’s properties.
- Data: Define values the game needs to track.
- Save: Store your editing changes.
- Run: Test the project and check how its objects and blocks behave.
Saving the project and saving a player’s progress are separate tasks. The editor’s Save control stores your work; gameplay progress needs suitable variables and save settings.
3. Build the map with the right assets
Place objects on the grid so terrain fits together and the player has a navigable route. Check the active layer before placing an asset: layer order affects which objects appear in front of others.
| Category | Typical use |
|---|---|
| Tile | Ground, floors, walls, and other level structure |
| Deco | Visual decoration; check its properties before assuming it blocks movement |
| Actor | Characters, enemies, and other objects with behavior |
| Prop | Interactive scene objects such as doors or movable boxes |
| Item | Collectibles such as coins, keys, or power-ups |
| Weapon | Combat equipment and related objects |
Choose an asset thumbnail and place it on the map. The asset palette’s + control lets you add or create an asset. Open an object’s gear or property control to inspect its settings and attached blocks.
Do not assume artwork alone defines behavior. A door needs an interaction, a coin needs collection logic, and a floor needs the appropriate collision properties.
4. Configure the scene and its events

In the map settings, give the scene a recognizable name and choose its width, height, and background color. Keep the first scene compact enough to test quickly.
- Reset map after exiting: Check how this option affects collected items and changed objects when you leave and return. Choose the behavior your game needs, then test it.
- Mirror mode: Useful when placing a symmetrical layout. Turn it off when editing only one side.
- Camera and zoom: Adjust the view so the player can see the area needed for the next action.
Use Confirm to apply settings. Save the project afterward rather than assuming that closing a settings window stores every edit.
Choose the event that matches the action
Event blocks tell the game when to run a sequence. The scene settings shown here include map creation, player entry, player exit, and receiving a broadcast.
- When map is created: Put initial scene setup here, such as preparing objects for the level.
- When player enters map: Use for actions needed on entry, such as showing a message or positioning the player.
- When player exits map: Use for transition-related actions.
- When receiving broadcast: Respond to a named signal sent by another object.
For example, collecting a required item could send a win signal. The scene could respond by showing a victory panel. Keep the signal name identical at the sending and receiving ends, and test that one interaction before adding others.
5. Track scores and progress with Data

Open Data and create a player variable for a value that changes during play. A score, health value, coin balance, or unlocked-level value each needs a clear name and an appropriate initial value.
The example project includes values for level stars, unlocked levels, and the current level. An array can hold several related values; a single numeric variable can track one count or level number. Choose the type that matches what you actually need.
Inspect each variable’s settings for storage options. Do not assume every value is saved between sessions. Test leaving a map, returning, and reopening the game to check the persistence you intended. Avoid resetting saved progress in an entry event unless that reset is deliberate.
Use the Config table for reference data such as item prices, enemy starting attributes, and level limits. Keeping these values together makes balancing easier than changing the same number in several block sequences.
6. Add interface elements that respond to the game

Switch from Map to UI to place text, images, buttons, and bars. Use UI layers to keep a dialog and its buttons in the correct visual order.
A score label needs to display the score variable. A button needs a press event and an action. A health bar needs to reflect the tracked health value. Adding the graphic does not complete the connection.
Templates such as YOU WIN, YOU LOSE, RETURN, and CONTINUE provide starting graphics. Decide what each control should do and attach that behavior. Lock icons and star displays also need conditions that match the player’s progress.

7. Test a complete playable loop
- Save and select Run.
- Check that the player starts in a reachable location and can move through the map.
- Trigger the objective and confirm that the score, item state, or win screen changes as intended.
- Try the restart, return, and continue controls.
- Leave and re-enter the scene to check reset and progress behavior.
Change one failing interaction at a time, then run it again. A single finished level is a better starting point for expansion than several scenes whose logic has not been checked.
For ideas about a catch-and-upgrade loop, see the Builda fishing guide. If event blocks and variables are new to you, the simple Scratch game tutorial provides another introduction to those concepts; its controls and blocks belong to Scratch, so they are not Builda instructions.
Reader Comments 0
Sign in with email or Google to join the discussion.