Quick start: making your first game.

The power of the Cocos Creator editor is that it allows developers to quickly prototype games.

Let’s follow a guided tutorial to make a magical game named Mind Your Step. This game tests the player’s reaction ability, and chooses whether to jump one step or two steps according to traffic conditions.

You can try out the completed the game here.

cocos-play

New Project

If you still don’t know how to download and run Cocos Creator, please review the Installation and Starting documentation.

To start a new project:

  1. Start Cocos Creator and then create a new project named MindYourStep. If you don’t know how to create a project, please read the Hello World! documentation.

  2. After creating a new project, you should see the following editor interface:

    main window

Creating a game scene

In Cocos Creator, Scene is the center for organizing game content during development and the container for presenting all game content to players. The game scene will generally include the following components:

  • Scene objects
  • Roles
  • User interface elements
  • Game logic, in the form of scripts, attached to Scene Nodes as Components

When the player runs the game, the game scene will be loaded. After the game scene is loaded, scripts of the included components will be automatically run. Apart from assets, game scenes are the foundation of all content creation. Now, to create a new Scene:

  1. In the Asset panel, click to select the assets directory, click the + button in the upper left corner, select the folder, and name it Scenes. Example:

    create scene

  2. Click the Scenes directory first (the following pictures create some common folders in advance), click the right mouse button, and select Scene Files from the pop-up menu. Example:

    create scene

  3. We created a Scene file named New Scene. After the creation, the name of the scene file New Scene will be in the edit state. Rename it from New Scene to Main.

  4. Double-click Main to open this Scene in Scene panel and Hierarchy panel.

Adding a road

Our main character needs to run from left to right on a road composed of cubes (blocks). Let’s make the road by using a built-in cube.

  1. Right click on Scene Node in the Hierarchy panel, then choose Create -> 3D Object -> Cube

    create cube

  2. Clone the cube to make two more cube with the shortcut key Ctrl+D.

  3. Assign the Cubes each a unique position:

    • First one at position (0, -1.5, 0).
    • Second one at position (1, -1.5, 0).
    • Third one at position (2, -1.5, 0).

      The result is as follows:

      create ground

Add a main character

Create a main character node

First, create an empty node named Player.

Second, create a Model Component named Body under the Player node. For convenience, let’s use the built-in Capsule model as the body of our main character.

create player node

The advantage of being divided into two nodes is that we can use the script to control the Player node to move the main character in the horizontal direction, and do some vertical animations on the Body node (such as falling after jumping in place), the two are superimposed to form a jumping animation.

Third, set the Player node to the (0, 0, 0) position so that it can stand on the first square.

The effect is as follows:

create player

Writing a script for the main character

It is necessary for the main character to be affected when the mouse moves. To do this a custom script needs to be written.

Creating a script

  1. If you have not yet created a Scripts folder, right-click the assets folder in the Assets panel, select New -> Folder, and rename the newly created folder to Scripts.
  2. Right-click the Scripts folder and select New -> TypeScript to create a new, blank TypeScript script. For TypeScript information, you can view the TypeScript Official Website.
  3. Change the name of the newly created script to PlayerController and the double-click the script to open the code editor (in, for example, VSCode).

    create player script

    Note: the name of the script in Cocos Creator 3.0 is the name of the component. This name is case sensitive! If the capitalization of the component name is incorrect, the component cannot be used correctly by the name!

Writing script code

There are already some pre-set code blocks in the PlayerController script. Example:

  1. import { _decorator, Component } from 'cc';
  2. const { ccclass, property } = _decorator;
  3. @ccclass("PlayerController")
  4. export class PlayerController extends Component {
  5. /* class member could be defined like this */
  6. // dummy = '';
  7. /* use `property` decorator if your want the member to be serializable */
  8. // @property
  9. // serializableDummy = 0;
  10. start () {
  11. // Your initialization goes here.
  12. }
  13. // update (deltaTime: number) {
  14. // // Your update function goes here.
  15. // }
  16. }

This code is the structure needed to write a component. Scripts with this structure are Components in Cocos Creator. They can be attached to nodes in a Scene and provide various functionality for controlling nodes. For detailed information review the Script documentation.

Monitoring of mouse events needs to be added in the script to let the Player node move. Modify the code in PlayerController as follows:

  1. import { _decorator, Component, Vec3, input, Input, EventMouse, Animation } from 'cc';
  2. const { ccclass, property } = _decorator;
  3. @ccclass("PlayerController")
  4. export class PlayerController extends Component {
  5. /* class member could be defined like this */
  6. // dummy = '';
  7. /* use `property` decorator if your want the member to be serializable */
  8. // @property
  9. // serializableDummy = 0;
  10. // for fake tween
  11. private _startJump: boolean = false;
  12. private _jumpStep: number = 0;
  13. private _curJumpTime: number = 0;
  14. private _jumpTime: number = 0.1;
  15. private _curJumpSpeed: number = 0;
  16. private _curPos: Vec3 = new Vec3();
  17. private _deltaPos: Vec3 = new Vec3(0, 0, 0);
  18. private _targetPos: Vec3 = new Vec3();
  19. private _isMoving = false;
  20. start () {
  21. // Your initialization goes here.
  22. input.on(Input.EventType.MOUSE_UP, this.onMouseUp, this);
  23. }
  24. onMouseUp(event: EventMouse) {
  25. if (event.getButton() === 0) {
  26. this.jumpByStep(1);
  27. } else if (event.getButton() === 2) {
  28. this.jumpByStep(2);
  29. }
  30. }
  31. jumpByStep(step: number) {
  32. if (this._isMoving) {
  33. return;
  34. }
  35. this._startJump = true;
  36. this._jumpStep = step;
  37. this._curJumpTime = 0;
  38. this._curJumpSpeed = this._jumpStep / this._jumpTime;
  39. this.node.getPosition(this._curPos);
  40. Vec3.add(this._targetPos, this._curPos, new Vec3(this._jumpStep, 0, 0));
  41. this._isMoving = true;
  42. }
  43. onOnceJumpEnd() {
  44. this._isMoving = false;
  45. }
  46. update (deltaTime: number) {
  47. if (this._startJump) {
  48. this._curJumpTime += deltaTime;
  49. if (this._curJumpTime > this._jumpTime) {
  50. // end
  51. this.node.setPosition(this._targetPos);
  52. this._startJump = false;
  53. this.onOnceJumpEnd();
  54. } else {
  55. // tween
  56. this.node.getPosition(this._curPos);
  57. this._deltaPos.x = this._curJumpSpeed * deltaTime;
  58. Vec3.add(this._curPos, this._curPos, this._deltaPos);
  59. this.node.setPosition(this._curPos);
  60. }
  61. }
  62. }
  63. }

Next, attach the PlayerController component to the Player node. Select the Player node in the Hierarchy panel, then click the Add Component button in the Inspector panel, select Custom Script Component- > PlayerController to the Player node to add the PlayerController component.

add player controller comp

In-order to see the object at runtime, we need to adjust some parameters of the Camera in the scene, set the position to (0, 0, 13), and set the ClearColor to (50, 90, 255, 255):

camera setting

Now, click the Play button. Once running, click the left and right mouse buttons on the opened web page, you can see the following screen:

player move

For additional details please refer to the Project Preview Debugging documentation.

Adding character animations

The Player can be moved in a horizontal direction. This is a start, but not good enough. Player must become more life-like. This effect can be achieved by adding a vertical animation to the character.

Note: before proceeding, please read the Animation Editor documentation.

After reading and understanding the capabilities of the Animation Editor character animations can be implemented!

  1. Locate the Animation panel, at the bottom of the editor alongside the Assets Preview and the Console panels. Select the Body node in the Scene and click to add an Animation Component and then click again tp create a new Animation Clip. Give this new Animation Clip a name of oneStep.

    player move

  2. Enter animation editing mode in-order to add the position attribute. Next, add three key frames with position values ​​of (0, 0, 0), (0, 0.5, 0), (0, 0, 0).

    add keyframe

    Note: remember to save the animation before exiting the animation editing mode, otherwise the animation will be lost.

  3. Animation Clips can also be created using the Asset panel. Next, Create a Clip named twoStep and add it to the Animation component on Body.

    add animation from assets

    Note: the panel layout was adjusted for recording convenience.

  4. Enter the animation editing mode, select and edit the twoStep clip. Similar to the second step, add three key frames at positions (0, 0, 0), (0, 1, 0), (0, 0, 0).

    edit second clip

  5. Reference the Animation component in thePlayerController Component, as different animations need to be played according to the number of steps Player jumped.

    First, reference the Animation component on the Body in the PlayerController component.

    1. @property({type: Animation})
    2. public BodyAnim: Animation|null = null;

    Then in the Inspector panel, drag the Animation to the Body variable.

    drag to animComp

    Add the animation playback code to the jump function jumpByStep:

    1. if (this.BodyAnim) {
    2. if (step === 1) {
    3. this.BodyAnim.play('oneStep');
    4. } else if (step === 2) {
    5. this.BodyAnim.play('twoStep');
    6. }
    7. }

    Click the Play button. When playing, click the left and right mouse buttons, you can see the new jump effect in action:

    preview with jump

Upgrading the road

In-order to make the gameplay longer and more enjoyable, we need a long stretch of road to let the Player run all the way to the right. Copying a bunch of cubes in the Scene and editing the position of each cube to form the road is not a wise practice. We can, however, complete this by using a script to automatically create the road pieces.

A “Game Manager” can help

Most games have a manager, which is mainly responsible for the management of the entire game life-cycle. You can put the code for the dynamic creation of the road in this same manager. Create a node named GameManager in the Scene. Next, create a TypesScript file named GameManager in assets/Scripts and add it to the GameManager node.

Making a Prefab

For a node that needs to be generated repeatedly, it can be saved as a Prefab (prefabricated) resource. This means it can be used as a template when we dynamically generate other nodes of this same type.

Note: before proceeding, please read the Prefab Resources documentation.

It is necessary to make the basic element cube of the road into a Prefab, after which all three cubes in the Scene can be deleted.

create cube prefab

Adding the automatic road creation

A very long road is needed. The ideal method is to dynamically increase the length of the road, so that the Player can run forever. First, generate a fixed-length road with a length that is arbitrary. To do so, replace the code in the GameManager script with the following code:

  1. import { _decorator, Component, Prefab, instantiate, Node, CCInteger} from 'cc';
  2. const { ccclass, property } = _decorator;
  3. enum BlockType{
  4. BT_NONE,
  5. BT_STONE,
  6. };
  7. @ccclass("GameManager")
  8. export class GameManager extends Component {
  9. @property({type: Prefab})
  10. public cubePrfb: Prefab|null = null;
  11. @property({type: CCInteger})
  12. public roadLength: Number = 50;
  13. private _road: number[] = [];
  14. start () {
  15. this.generateRoad();
  16. }
  17. generateRoad() {
  18. this.node.removeAllChildren();
  19. this._road = [];
  20. // startPos
  21. this._road.push(BlockType.BT_STONE);
  22. for (let i = 1; i < this.roadLength; i++) {
  23. if (this._road[i-1] === BlockType.BT_NONE) {
  24. this._road.push(BlockType.BT_STONE);
  25. } else {
  26. this._road.push(Math.floor(Math.random() * 2));
  27. }
  28. }
  29. for (let j = 0; j < this._road.length; j++) {
  30. let block: Node = this.spawnBlockByType(this._road[j]);
  31. if (block) {
  32. this.node.addChild(block);
  33. block.setPosition(j, -1.5, 0);
  34. }
  35. }
  36. }
  37. spawnBlockByType(type: BlockType) {
  38. if (!this.cubePrfb) {
  39. return null;
  40. }
  41. let block: Node|null = null;
  42. switch(type) {
  43. case BlockType.BT_STONE:
  44. block = instantiate(this.cubePrfb);
  45. break;
  46. }
  47. return block;
  48. }
  49. // update (deltaTime: number) {
  50. // // Your update function goes here.
  51. // }
  52. }

Assign the Cube prefab that made previously to the CubePrfb property in GameManager Inspector.

assign cube prefab

The length of the road can be changed by modifying the value of roadLength in the Properties panel for the GameManager.

When previewing, the road is now automatically generated, however, because the Camera does not follow the Player, the road behind cannot be seen. Changing the Camera in the Scene to be a child node of the Player can help solve this.

drag camera to player

Now, the Camera will follow the Player’s movement.

Adding a start menu

The start menu is an indispensable part of most any game. Add the game name, game introduction, production staff and other information here. Creating a simple start menu starts with some basic steps:

  1. Add a button called Play

    create button

    This operation creates a Canvas node, a PlayButton node, and a Label node. Because the UI component needs to be displayed under the parent node with Canvas, the editor will automatically add one when it finds that there is not a node with this component in the current Scene. After creating the button, change the String property of cc.Label on the Label node from Button to Play.

  2. Create an empty node named StartMenu under Canvas and drag PlayButton under it. We can switch to the 2D editing view for UI editing operations by clicking the 2D/3D button on the toolbar.

    Note: 2D View is this toolbar button 2d-view.

    Note: before proceeding, please read the Scene Editing documentation.

  3. Add a background frame by creating a Sprite node named BG under StartMenu. Adjust BG‘s position to above the PlayButton, setting the W(width) and H(height) of ContentSize to (200, 200), and setting its SpriteFrame to internal/default_ui/ default_sprite_splash.

    create bg sprite

    change spriteFrame

  4. Add a Label called Title for the title of the start menu.

    add title label

  5. Modify the text for Title and adjust it’s position, text size and color.

    modify title

  6. Adjust the position of the PlayButton. The layout of a simple start menu is complete.

    modify title

  7. Add game state logic, generally it can be divided into three states:

    • Init: display the game menu and initialize some resources.
    • Playing: hide the game menu, players can operate the game.
    • End: end the game and display the ending menu.

      Use an enum type to represent these states.

      1. enum BlockType{
      2. BT_NONE,
      3. BT_STONE,
      4. };
      5. enum GameState{
      6. GS_INIT,
      7. GS_PLAYING,
      8. GS_END,
      9. };

      Add a private variable that represents the current state to the GameManager script

      1. private _curState: GameState = GameState.GS_INIT;

      In-order not to let the user operate the character at the beginning, but to allow the user to operate the character while the game is in progress, we need to dynamically turn on and off the character’s monitoring of mouse messages. This can be done with the following changes to PlayerController:

      1. start () {
      2. // Your initialization goes here.
      3. //input.on(Input.EventType.MOUSE_UP, this.onMouseUp, this);
      4. }
      5. setInputActive(active: boolean) {
      6. if (active) {
      7. input.on(Input.EventType.MOUSE_UP, this.onMouseUp, this);
      8. } else {
      9. input.off(Input.EventType.MOUSE_UP, this.onMouseUp, this);
      10. }
      11. }

      Next, reference PlayerController in the GameManager script. Drag the Player variable in the Inspector panel.

      1. @property({type: PlayerController})
      2. public playerCtrl: PlayerController = null;

      In-order to dynamically open/close the open menu, the StartMenu needs to be referenced in the GameManager. Drag the StartMenu of the scene into this variable in the Inspector panel.

      1. @property({type: Node})
      2. public startMenu: Node = null;

      add player to game manager

      Modify the code in the GameManager:

      1. start () {
      2. this.curState = GameState.GS_INIT;
      3. }
      4. init() {
      5. if (this.startMenu) {
      6. this.startMenu.active = true;
      7. }
      8. this.generateRoad();
      9. if (this.playerCtrl) {
      10. this.playerCtrl.setInputActive(false);
      11. this.playerCtrl.node.setPosition(Vec3.ZERO);
      12. }
      13. }
      14. set curState (value: GameState) {
      15. switch(value) {
      16. case GameState.GS_INIT:
      17. this.init();
      18. break;
      19. case GameState.GS_PLAYING:
      20. if (this.startMenu) {
      21. this.startMenu.active = false;
      22. }
      23. // Directly setting active will directly start monitoring
      24. // mouse events, and do a little delay processing
      25. setTimeout(() => {
      26. if (this.playerCtrl) {
      27. this.playerCtrl.setInputActive(true);
      28. }
      29. }, 0.1);
      30. break;
      31. case GameState.GS_END:
      32. break;
      33. }
      34. this._curState = value;
      35. }
  8. Add event monitoring to the Play button. In-order to start the game after clicking the Play button, the button needs to respond to click events. Add code that responds to the button click in the GameManager script, and click to enter the game’s Playing state:

    1. onStartButtonClicked() {
    2. this.curState = GameState.GS_PLAYING;
    3. }

    Next, add the response function of Click Events in the Inspector panel for the Play button.

    play button inspector

Now, preview the scene by clicking the Play button to start the game.

Adding game end logic

The game character is just running forward, with no purpose. Adding game rules to make the game play more challenging would make the game more playable and give it a purpose.

  1. The character needs to send a message at the end of each jump. This message should record how many steps the character jumped and its current position. This can be done in PlayerController.

    1. private _curMoveIndex = 0;
    2. // ...
    3. jumpByStep(step: number) {
    4. // ...
    5. this._curMoveIndex += step;
    6. }

    Send a message at the end of each jump:

    1. onOnceJumpEnd() {
    2. this._isMoving = false;
    3. this.node.emit('JumpEnd', this._curMoveIndex);
    4. }
  2. Monitor the character’s jumping end event in GameManager, and judge the winning or losing of the game, according to the rules.

    Increase the failure and ending logic to judge how the game is being played.If Player jumps to an empty square or exceeds the maximum length value, the game will end:

    1. checkResult(moveIndex: number) {
    2. if (moveIndex <= this.roadLength) {
    3. // Jump to the empty square
    4. if (this._road[moveIndex] == BlockType.BT_NONE) {
    5. this.curState = GameState.GS_INIT;
    6. }
    7. } else { // skipped the maximum length
    8. this.curState = GameState.GS_INIT;
    9. }
    10. }

    Monitor the character’s jump message and call a function to decide:

    1. start () {
    2. this.curState = GameState.GS_INIT;
    3. this.playerCtrl?.node.on('JumpEnd', this.onPlayerJumpEnd, this);
    4. }
    5. // ...
    6. onPlayerJumpEnd(moveIndex: number) {
    7. this.checkResult(moveIndex);
    8. }

    If you preview playing the game now, there will be a logic error when restarting the game. This is because we did not reset the _curMoveIndex property value in PlayerController when the game restarts. To fix this, add a reset function in PlayerController.

    1. reset() {
    2. this._curMoveIndex = 0;
    3. }

    Call reset() in the init function of GameManager to reset the properties of PlayerController.

    1. init() {
    2. // ...
    3. this.playerCtrl.reset();
    4. }

Step counting display

We can display the current number of steps jumped in the interface. Perhaps watching the continuous growth of steps during the jump will be very fulfilling to the player.

  1. Create a new label named Steps under Canvas, adjust the position, font size and other properties.

    steps label

  2. Reference the Steps label in GameManager

    1. @property({type: Label})
    2. public stepsLabel: Label|null = null;

    steps label to game manager

  3. Update the current Step data to appear in new Steps Label. A game ending interface has yet to be created, for now, reset the number of steps to 0 when restarting playing.

    1. set curState (value: GameState) {
    2. switch(value) {
    3. case GameState.GS_INIT:
    4. this.init();
    5. break;
    6. case GameState.GS_PLAYING:
    7. if (this.startMenu) {
    8. this.startMenu.active = false;
    9. }
    10. if (this.stepsLabel) {
    11. // reset the number of steps to 0
    12. this.stepsLabel.string = '0';
    13. }
    14. // set active directly to start listening for mouse events directly
    15. setTimeout(() => {
    16. if (this.playerCtrl) {
    17. this.playerCtrl.setInputActive(true);
    18. }
    19. }, 0.1);
    20. break;
    21. case GameState.GS_END:
    22. break;
    23. }
    24. this._curState = value;
    25. }

    Update the Steps Label in a function that responds to the character jumping. It should make sense that recording the number of Steps would take place after each and every jump for accuracy.

    1. onPlayerJumpEnd(moveIndex: number) {
    2. this.stepsLabel.string = '' + moveIndex;
    3. this.checkResult(moveIndex);
    4. }

Lights and shadows

Where there is light, there will be a shadow. Light and shadows create a 3D world where light and dark intersect. Next, let’s add a simple shadow to the character.

Turning on shadows

  1. In the Hierarchy panel, click the Scene node at the top, check Enabled in the shadows property, and modify the Distance and Normal parameters

    planar shadows

  2. Click the Body node, under the Player node, and set ShadowCastingMode under MeshRenderer to ON.

    model shadow

A patch of shadow can be seen in the in the Scene editor. However, this shadow cannot be seen when previewing because it is covered by the capsule body that is directly behind the model.

player shadow

Adjusting the light

When creating a new scene, a DirectionalLight will be added by default, and the shadow will be calculated from this parallel light. The direction of this parallel light can be adjusted in-order to display the shadow in another position.

In the Hierarchy panel, click to select the Main Light node and adjust the Rotation parameter to (-10, 17, 0).

main light

Preview the game and you can see this effect:

player shadow preview

Adding a character model

Using the capsule body as the character is a bit shabby, we can change this to make a Cocos character.

Importing model resources

Copy the cocos folder under the assets directory in Project Engineering to the assets directory of your own project.

Adding to the scene

A prefab called Cocos has been included in the cocos file, drag it to the Body node under Player in the scene.

add cocos prefab

Remove the Capsule model at the same time.

remove capsule

The model is a little dark and a spotlight can be added to highlight its shiny brain.

add cocos light

Adding a jumping animation

When previewing the game, the character will initially have a standby animation, but a jumping animation needs to be used during a jump.

First, add a variable in the PlayerController class that references the model animation:

  1. @property({type: SkeletalAnimation})
  2. public CocosAnim: SkeletalAnimation|null = null;

Then, in the Inspector, drag the Cocos node into this variable.

assign cocos prefab

The jump animation needs to be used in the jumpByStep function.

  1. jumpByStep(step: number) {
  2. if (this._isMoving) {
  3. return;
  4. }
  5. this._startJump = true;
  6. this._jumpStep = step;
  7. this._curJumpTime = 0;
  8. this._curJumpSpeed = this._jumpStep / this._jumpTime;
  9. this.node.getPosition(this._curPos);
  10. Vec3.add(this._targetPos, this._curPos, new Vec3(this._jumpStep, 0, 0));
  11. this._isMoving = true;
  12. if (this.CocosAnim) {
  13. // The jumping animation takes a long time, here is accelerated playback
  14. this.CocosAnim.getState('cocos_anim_jump').speed = 3.5;
  15. // Play jumping animation
  16. this.CocosAnim.play('cocos_anim_jump');
  17. }
  18. if (this.BodyAnim) {
  19. if (step === 1) {
  20. //this.BodyAnim.play('oneStep');
  21. } else if (step === 2) {
  22. this.BodyAnim.play('twoStep');
  23. }
  24. }
  25. this._curMoveIndex += step;
  26. }

In the onOnceJumpEnd function, change to the standby state and play the standby animation.

  1. onOnceJumpEnd() {
  2. this._isMoving = false;
  3. if (this.CocosAnim) {
  4. this.CocosAnim.play('cocos_anim_idle');
  5. }
  6. this.node.emit('JumpEnd', this._curMoveIndex);
  7. }

When previewing, the results are as follows:

cocos play

Final Code

The final code for PlayerController.ts should look like this:

  1. import { _decorator, Component, Vec3, input, Input, EventMouse, Animation, SkeletalAnimation } from 'cc';
  2. const { ccclass, property } = _decorator;
  3. @ccclass("PlayerController")
  4. export class PlayerController extends Component {
  5. @property({type: Animation})
  6. public BodyAnim: Animation|null = null;
  7. @property({type: SkeletalAnimation})
  8. public CocosAnim: SkeletalAnimation|null = null;
  9. // for fake tween
  10. private _startJump: boolean = false;
  11. private _jumpStep: number = 0;
  12. private _curJumpTime: number = 0;
  13. private _jumpTime: number = 0.3;
  14. private _curJumpSpeed: number = 0;
  15. private _curPos: Vec3 = new Vec3();
  16. private _deltaPos: Vec3 = new Vec3(0, 0, 0);
  17. private _targetPos: Vec3 = new Vec3();
  18. private _isMoving = false;
  19. private _curMoveIndex = 0;
  20. start () {
  21. }
  22. reset() {
  23. this._curMoveIndex = 0;
  24. }
  25. setInputActive(active: boolean) {
  26. if (active) {
  27. input.on(Input.EventType.MOUSE_UP, this.onMouseUp, this);
  28. } else {
  29. input.off(Input.EventType.MOUSE_UP, this.onMouseUp, this);
  30. }
  31. }
  32. onMouseUp(event: EventMouse) {
  33. if (event.getButton() === 0) {
  34. this.jumpByStep(1);
  35. } else if (event.getButton() === 2) {
  36. this.jumpByStep(2);
  37. }
  38. }
  39. jumpByStep(step: number) {
  40. if (this._isMoving) {
  41. return;
  42. }
  43. this._startJump = true;
  44. this._jumpStep = step;
  45. this._curJumpTime = 0;
  46. this._curJumpSpeed = this._jumpStep / this._jumpTime;
  47. this.node.getPosition(this._curPos);
  48. Vec3.add(this._targetPos, this._curPos, new Vec3(this._jumpStep, 0, 0));
  49. this._isMoving = true;
  50. if (this.CocosAnim) {
  51. // The jumping animation takes a long time, here is accelerated playback
  52. this.CocosAnim.getState('cocos_anim_jump').speed = 3.5;
  53. // Play jumping animation
  54. this.CocosAnim.play('cocos_anim_jump');
  55. }
  56. if (this.BodyAnim) {
  57. if (step === 1) {
  58. //this.BodyAnim.play('oneStep');
  59. } else if (step === 2) {
  60. this.BodyAnim.play('twoStep');
  61. }
  62. }
  63. this._curMoveIndex += step;
  64. }
  65. onOnceJumpEnd() {
  66. this._isMoving = false;
  67. this.CocosAnim.play('cocos_anim_idle');
  68. this.node.emit('JumpEnd', this._curMoveIndex);
  69. }
  70. update (deltaTime: number) {
  71. if (this._startJump) {
  72. this._curJumpTime += deltaTime;
  73. if (this._curJumpTime > this._jumpTime) {
  74. // end
  75. this.node.setPosition(this._targetPos);
  76. this._startJump = false;
  77. this.onOnceJumpEnd();
  78. } else {
  79. // tween
  80. this.node.getPosition(this._curPos);
  81. this._deltaPos.x = this._curJumpSpeed * deltaTime;
  82. Vec3.add(this._curPos, this._curPos, this._deltaPos);
  83. this.node.setPosition(this._curPos);
  84. }
  85. }
  86. }
  87. }

The final code for GameManager.ts should look like this:

  1. import { _decorator, Component, Prefab, instantiate, Node, Label, CCInteger, Vec3 } from 'cc';
  2. import { PlayerController } from "./PlayerController";
  3. const { ccclass, property } = _decorator;
  4. enum BlockType{
  5. BT_NONE,
  6. BT_STONE,
  7. };
  8. enum GameState{
  9. GS_INIT,
  10. GS_PLAYING,
  11. GS_END,
  12. };
  13. @ccclass("GameManager")
  14. export class GameManager extends Component {
  15. @property({type: Prefab})
  16. public cubePrfb: Prefab|null = null;
  17. @property({type: CCInteger})
  18. public roadLength: Number = 50;
  19. private _road: number[] = [];
  20. @property({type: Node})
  21. public startMenu: Node|null = null;
  22. @property({type: PlayerController})
  23. public playerCtrl: PlayerController|null = null;
  24. private _curState: GameState = GameState.GS_INIT;
  25. @property({type: Label})
  26. public stepsLabel: Label|null = null;
  27. start () {
  28. this.curState = GameState.GS_INIT;
  29. this.playerCtrl?.node.on('JumpEnd', this.onPlayerJumpEnd, this);
  30. }
  31. init() {
  32. if (this.startMenu) {
  33. this.startMenu.active = true;
  34. }
  35. this.generateRoad();
  36. if (this.playerCtrl) {
  37. this.playerCtrl.setInputActive(false);
  38. this.playerCtrl.node.setPosition(Vec3.ZERO);
  39. this.playerCtrl.reset();
  40. }
  41. }
  42. set curState (value: GameState) {
  43. switch(value) {
  44. case GameState.GS_INIT:
  45. this.init();
  46. break;
  47. case GameState.GS_PLAYING:
  48. if (this.startMenu) {
  49. this.startMenu.active = false;
  50. }
  51. if (this.stepsLabel) {
  52. // reset the number of steps to 0
  53. this.stepsLabel.string = '0';
  54. }
  55. // set active directly to start listening for mouse events directly
  56. setTimeout(() => {
  57. if (this.playerCtrl) {
  58. this.playerCtrl.setInputActive(true);
  59. }
  60. }, 0.1);
  61. break;
  62. case GameState.GS_END:
  63. break;
  64. }
  65. this._curState = value;
  66. }
  67. generateRoad() {
  68. this.node.removeAllChildren();
  69. this._road = [];
  70. // startPos
  71. this._road.push(BlockType.BT_STONE);
  72. for (let i = 1; i < this.roadLength; i++) {
  73. if (this._road[i-1] === BlockType.BT_NONE) {
  74. this._road.push(BlockType.BT_STONE);
  75. } else {
  76. this._road.push(Math.floor(Math.random() * 2));
  77. }
  78. }
  79. for (let j = 0; j < this._road.length; j++) {
  80. let block: Node = this.spawnBlockByType(this._road[j]);
  81. if (block) {
  82. this.node.addChild(block);
  83. block.setPosition(j, -1.5, 0);
  84. }
  85. }
  86. }
  87. spawnBlockByType(type: BlockType) {
  88. if (!this.cubePrfb) {
  89. return null;
  90. }
  91. let block: Node|null = null;
  92. switch(type) {
  93. case BlockType.BT_STONE:
  94. block = instantiate(this.cubePrfb);
  95. break;
  96. }
  97. return block;
  98. }
  99. onStartButtonClicked() {
  100. this.curState = GameState.GS_PLAYING;
  101. }
  102. checkResult(moveIndex: number) {
  103. if (moveIndex <= this.roadLength) {
  104. if (this._road[moveIndex] == BlockType.BT_NONE) {
  105. // ump to the empty square
  106. this.curState = GameState.GS_INIT;
  107. }
  108. } else {
  109. // skipped the maximum length
  110. this.curState = GameState.GS_INIT;
  111. }
  112. }
  113. onPlayerJumpEnd(moveIndex: number) {
  114. if (this.stepsLabel) {
  115. this.stepsLabel.string = '' + moveIndex;
  116. }
  117. this.checkResult(moveIndex);
  118. }
  119. // update (deltaTime: number) {
  120. // // Your update function goes here.
  121. // }
  122. }

The end!

Congratulations on completing your first game made with Cocos Creator!

The complete project can be downloaded on our GitHub. The hope is this quick start tutorial will help you understand the Cocos Creator game development process, basic concepts and workflow.

Next, you can continue to improve all aspects of the game. Here are some ideas for improvement:

  • Increase the difficulty of the game, when the character stays in place for 1 second it fails.
  • Change to infinite runway, dynamically delete the runway that has been run, and extend the runway behind.
  • Add game sound effects.
  • Add an end menu interface to the game, and count the number of jumping steps and time spent by the player.
  • Replace characters and runways with prettier assets.
  • Can add some pickable items to guide players to “make mistakes”
  • Add some particle special effects, such as trailing when the character moves, dust when landing
  • Add two operation buttons for touch screen devices instead of left and right mouse button operation

Lastly, why not share this game with your friends? You can publish the completed game to a server of your choice using the Publishing Workflow documentation.