We covered a lot in this chapter. You learned about a container in Construct 2, what its traits are, and how to make it. You also learned about two new behaviors: the Pin behavior to easily follow an object and the Pathfinding behavior to look for a path and move along on it. You also know that the Pathfinding behavior can evade obstacles on the screen, both the default kind of obstacles and the custom ones.

One more behavior that we covered in this chapter is the Turret behavior that can recognize targets and shoot them. You also know about the action to scroll the layout in the game without using a Scroll To behavior. You learned how to import sound files to Construct 2, which file type is good when importing, whether to import them to the Music or Sounds folder, and how to play them in the game with the Audio object. Finally, we used the value stored in an array in the gameplay, instead of simply using it to store the player's high score.

Try to expand this game yourself. What happened at the end of the game? Do you need a game-over screen? Is there a scoring system in place? Can you add your own leaderboard at the end of the game? There are a lot of possibilities!

That's really a lot of things, and we're starting to make a pretty complex game. However, all of the game developers know that all games contain bugs, or at least one. That's why they do a lot of testing and QA, or Quality Assurance—a process to prevent bugs or defects in the games—before they push their games out the door. Next, we will study about bug testing in Construct 2, and you will know what usually causes bugs.