Tips and troubleshooting
The game does not do what I want
- Preview and test the event on its own.
- Check the object's name is right and that no other object has a similar name.
- Check the layers: the object may be hidden behind another.
- If an action deletes or changes "everything", a condition is missing to pick only the right objects.
- Remember the event runs every frame: an add action with no "only once" condition adds 60 times a second.
Common mistakes
| Symptom | Likely cause |
|---|---|
| The character falls through the floor | The floor is missing the Solid behavior, or the character the Platform one. |
| The character does not jump with the space bar | The Platform behavior's jump uses the up arrow. |
| The score keeps rising | The event has no "only once" condition. Use Key just pressed, or delete the object on collision. |
| A created object does not show | It is on the wrong layer or was created offscreen. |
| The text does not show | Quotes are missing around fixed text, or the object is on a layer without a camera. |
| Changing layout fires the wrong event | Use Key released for keys that change screens. |
Event limit
Each condition and each action counts as one event. Comments do not. The sheet's footer shows "Events: 8 / 100". To free up room:
- Use behaviors instead of events.
- Use families to handle several objects in one event.
- Use sub-events, which share common conditions.
See your plan's limits in Getting started.
Keeping a high score
Add the Local storage object to the project. It writes values to the player's browser, and you can read them back in the next run. The high score stays on the player's computer, not in the cloud.
Teamwork and the classroom
Teachers create classes and student accounts, and send a project to everyone at once. See For teachers.
Getting help
Open an example close to what you want under Explore examples: its events show how the problem was solved.