Skip to content

Make a little game. Learn a lot.

Learn to Create Your First 2D Game | CuitPlay Tutorials

A practical path from the robot starter scene to a small adventure with coins, an enemy and a second level. Keep the editor open alongside these steps.

These are written, practical tutorials using the existing editor. There are no video lessons on this page. Follow them in order or choose the task you need.

LESSON 01

Create your first 2D game

Start with one scene and a clear goal.

  1. Choose Create a Game. The starter opens with a robot, platforms, coins, an enemy and a flag; it is a starting scene, not an empty canvas.
  2. Change the game name in the top bar. Try a simple name such as Coin Garden.
  3. Find the Asset Library on the left, Game World in the centre and Properties and Rules on the right. Select an object to see its settings.
  4. Press Play to try movement. Return with Back to editor and change one platform position.

Check your result: You can identify the player, move a platform and return from Play without losing the editable scene.

LESSON 02

Design a player character

Keep the first character simple and recognisable.

  1. Select the player and choose Draw / replace picture. Use + Create / import sprite when you want a new sprite instead.
  2. In Sprite Studio, draw a few shapes or import artwork. Use artwork layers to arrange the parts.
  3. Create frames and an animation sequence if you want animated artwork. A single frame is enough to begin.
  4. Save the artwork back to the game. Select it and adjust Position & size in Object Details.

Check your result: Your picture appears on the intended player, and you can still select and reposition it.

LESSON 03

Add backgrounds and game objects

Build a small scene before adding more mechanics.

  1. Open Backgrounds in the left library and choose a setting. To use your own image, choose + Upload / import background and apply the imported item.
  2. Open Assets, choose a category and add a platform, collectible or enemy.
  3. Drag the object into position or edit its X and Y values. Use Grid and Snap for regular spacing.
  4. For overlapping objects, use Object menu ordering commands to bring an object forward or send it behind. Ordering changes appearance; it does not switch collision on or off.

Check your result: The background fills the scene and the objects appear in the intended order.

LESSON 04

Create keyboard movement

Use the built-in controls first, then learn input events.

  1. Select the player. Under How does it move?, choose Use game controls. Set a move speed and a jump speed.
  2. Enable Falls with gravity. Make the floor a Solid surface. Jumping needs a surface to stand on.
  3. Open Game → Game controls. Check the bindings for moving left, moving right and jumping; assign Left Arrow, Right Arrow and Space if those are the controls you want.
  4. Press Play and try each control. Built-in movement already handles these actions, so do not add competing movement rules for the same player.
  5. For additional behaviours, add an input action and use it in a rule. Pressed fires once on a press, Held reads whether it stays down, and Released fires on release.

Check your result: The player moves in both directions and can jump from the solid floor.

LESSON 05

Configure events, conditions and actions

Make one coin change the score.

  1. Choose + Add Rule in Properties and Rules. Give it a descriptive name such as Collect the first coin.
  2. Set When / Condition to Objects touch. Choose the player as This object and the coin as Touches.
  3. Use IF — once when it becomes true. Under THEN choose + Add action, category GAME, action Change score, and amount 1.
  4. Add a second action: category OBJECTS, action Remove / Destroy object. Choose that same coin.
  5. Close the rule editor and test. THEN actions run in order. ELSE is the alternative branch for supported conditions; press/release events do not use an ELSE branch.

Check your result: Touching the coin adds one point and removes only that coin for the play session.

LESSON 06

Configure collisions and solid platforms

Appearance and physical support are different settings.

  1. Select a platform and enable Solid surface. Select the player and enable gravity for a normal platform game.
  2. Review Artwork in this game → Collision shape. Visible artwork ignores transparent regions; the Sprite Studio box uses the saved collision rectangle when available.
  3. Keep object collisions enabled for objects used by contact rules. No object collisions skips those contacts.
  4. Test landing from above, approaching from the side and jumping beneath the platform. If an interaction looks wrong, inspect the artwork bounds, collision setting and placement before adding more rules.

Check your result: A normal landing supports the player; the coin or enemy contact rule still responds.

LESSON 07

Add enemies and health

Use a property for health and protection to control repeated hits.

  1. Select the player. Under My object’s properties, add a Number property named Health and set its starting value to 3.
  2. Add an enemy from the library and position it where the player can reach it.
  3. Create a rule with Objects touch: player touches enemy. Choose IF for one hit on entering contact.
  4. Add a THEN action with category PROPERTIES and action Damage health. Select the player’s Health property, damage amount 1 and protection after hit of 1 second.
  5. Add a separate rule checking the Health property is at most 0. Choose GAME → Game over as its action.
  6. Test one hit, move away and return. If you choose WHILE for continuing contact damage, keep a protection interval; repeated property subtraction every tick can remove health too quickly.

Check your result: The player loses health on contact and the game ends at zero. Restart restores starting values.

LESSON 08

Create additional levels

Keep a clear entrance and exit for each scene.

  1. Open the Level dropdown and choose + Add Level. Give the level a clear name.
  2. Select a level to edit its scene. Add its background and platforms. Use the Screen dropdown to add connected screens inside that level when needed.
  3. In Scene properties, configure Level exit: reaching the final screen’s right end or touching a chosen exit object. Choose an available transition.
  4. Test travel from the earlier level. The existing travel system carries the player; test the arrival position before placing obstacles near the entrance.

Check your result: You can switch levels in the editor and reach the next one during play.

LESSON 09

Run, test and save

Test a short checklist after each change.

  1. Press Play. Try left, right and jump, collect a coin and approach an enemy.
  2. Check score, health, platform landings and the exit. Use Pause or Restart when needed.
  3. Return to the editor and correct one issue at a time. Play Mode changes are separate from the original editing layout.
  4. Press Save for the browser slot. Use File → Open / import / export for an editable JSON backup, or File → My cloud games for signed-in cloud projects.

Check your result: You have a working test run and a saved editable copy. Saving another game in the browser replaces the single browser slot.

LESSON 10

Debug common game problems

Start with the smallest explanation you can test.

  1. Player does not move: click the game area, check pause state, movement mode and the configured control bindings.
  2. Player does not jump: check gravity, jump speed and whether it is standing on a solid surface.
  3. A rule does nothing: check Enabled, selected objects, the condition and any extra property checks. Disabled action choices may need an object property or animation first.
  4. Health falls too quickly: look for WHILE contact rules and repeated number changes. Use Damage health with protection when appropriate.
  5. The wrong object disappears: check the action’s target. A contact condition and an action can refer to different objects.
  6. Test one correction, then save or export again. If the problem remains, note the exact steps that reproduce it.

Check your result: You can explain the cause of one problem and show the change that fixed it.

Open the broader guide for saving, publishing, machines and AI imports. Read the FAQ for quick answers.

Your next step is a small experiment.

Build one screen, try one rule and press Play. Every test teaches you something.

Open Game Maker →