Corona SDK: Build a Concentration Puzzle Game

In this tutorial I'll be showing you how to create a concentration puzzle game with the Corona SDK. You'll learn more about timers, touch controls, and sounds. The objective of the game is to quickly tap on the correct button before runnig out of time. Read on!


1. Application Overview

App Overview

Using custom graphics we will code an entertaining game with Lua and the Corona SDK API's.

The player will be able to use the touch screen on the device to select the correct button, and you can modify the parameters in the code to customize the game.


2. Target Device

Target Device

The first thing we have to do is select the platform we want to run our app within. This way we'll be able to choose the size for the images we will use.

The iOS platform has these characteristics:

  • iPad 1/2/Mini: 1024x768px, 132 ppi
  • iPad Retina: 2048x1536, 264 ppi
  • iPhone/iPod Touch: 320x480px, 163 ppi
  • iPhone/iPod Retina: 960x640px, 326 ppi
  • iPhone 5/iPod Touch: 1136x640, 326 ppi

Because Android is an open platform, there are many different devices and resolutions. A few of the more common screen characteristics are:

  • Asus Nexus 7 Tablet: 800x1280px, 216 ppi
  • Motorola Droid X: 854x480px, 228 ppi
  • Samsung Galaxy SIII: 720x1280px, 306 ppi

In this tutorial, we'll be focusing on the iOS platform with the graphic design, specifically developing for distribution to an iPhone/iPod touch, but the code presented here should apply to Android development with the Corona SDK as well.


3. Interface

Interface

A simple and friendly interface will be used. The interface will involve multiple shapes, buttons, bitmaps and more.

The interface graphic resources necessary for this tutorial can be found in the attached download.


4. Export Graphics

Export Graphics

Depending on the device you have selected, you may need to export the graphics in the recommended PPI. You can do this with your favorite image editor.

I used the Adjust Size... function in the Preview app on Mac OS X.

Remember to give the images a descriptive name and to save them in your project folder.


5. App Configuration

An external file will be used to make the application go fullscreen across devices, the config.lua file. This file shows the original screen size and the method used to scale that content in case the app is run in a different screen resolution.


6. Main.lua

Let's write the application!

Open your prefered Lua editor (any Text Editor will work, but you won't have syntax highlighting), and prepare to write your awesome app. Remember to save the file as main.lua in your project folder.


7. Code Structure

We'll structure our code as if it were a Class. If you know ActionScript or Java, you should find the structure familiar.


8. Hide Status Bar

This code hides the status bar. The status bar is the bar on top of the device screen that shows the time, signal, and other indicators.


9. Background

Background

A simple graphic is used as the background for the application interface. The next line of code stores it:


10. Title View

Title View

This is the Title View. It will be the first interactive screen to appear in our game, and these variables store the components.


11. Credits View

Credits View

This view will show the credits and copyright of the game, this variable will be used to store it.


12. Game Background

Game Background

The level background. This will also add the score textfield.


13. Instructions Message

Instructions

An instructions message will appear at the start of the game, it will be tweened out after 2 seconds.


14. Buttons

Buttons

The buttons. The objective of the game is to tap the black square before running out of time.


15. Alert

Alert

This is the alert that will be displayed when the time reaches zero. It will show the score and end the game.


16. Sounds

Sounds

We'll use Sound Effects to enhance the feeling of the game. The sounds used in this game were created in as3sfxr.


17. Variables

These are the variables we'll use. Read the comments in the code to learn more about them.


18. Declare Functions

Declare all the functions as local at the start.


19. Constructor

Next, we'll create the function that will initialize all the game logic:


20. Add the Title View

Now we'll place the TitleView on the stage and call a function that will add the tap listeners to the buttons.


21. Start Button Listeners

This function adds the necesary listeners to the TitleView buttons.


22. Show Credits

The credits screen is shown when the user taps the about button, a tap listener is added to the credits view to remove it.


23. Hide Credits

When the credits screen is tapped, it'll be tweened out of the stage and removed.


24. Show Game View

When the Play button is tapped, the title view is tweened and removed revealing the game view. There are many parts involved in this view, so we'll split them in the next steps.


25. Instructions Message

The following lines add the instructions message.


26. Add Buttons

This part places the buttons on the screen and groups them to handle them easier.


27. Display Time

Now we create a TextField that will display the time remaining.


28. Game Listeners

This function adds the necessary listeners to start the game logic.


29. Start Timers

Next we initiate the timers. They will handle the time left and the current bonus time that will be added when the correct button is pressed.


30. Add Bonus Time

If the Black button is selected the bonus time is added to the total.


31. Change Squares Position

Then we move the buttons to a different position using the values set in the previously created Table. We also play a sound and add the score:


32. Incorrect Button

If the button pressed is red, time is subtracted.


33. Check for Time Over

This function reduces the total time and checks if it reaches zero to call an alert.


34. Reduce Bonus

The following code decreases the bonus added when the correct button is pressed. It displays a message to alert the player.


35. Alert

The alert function creates an alert view, animates it, and ends the game.


36. Call Main Function

In order to start the game, the Main function needs to be called. With the above code in place, we'll do that here:


37. Loading Screen

Loading Screen

The Default.png file is an image that will be displayed right when you start the application while iOS loads the basic data to show the Main Screen. Add this image to your project source folder, it will be automatically added by the Corona compiler.


38. Icon

Icon

Using the graphics you created before you can now create a nice and good looking icon. The icon size for the non-retina iPhone icon is 57x57px, but the retina version is 114x114px and the iTunes store requires a 512x512px version. I suggest creating the 512x512 version first and then scaling down for the other sizes.

It doesn't need to have the rounded corners or the transparent glare, iTunes and the iPhone will do that for you.


39. Testing in the Simulator

Testing

It's time to do the final test. Open the Corona Simulator, browse to your project folder, and then click open. If everything works as expected, you are ready for the final step!


40. Build

Build

In the Corona Simulator, go to File > Build and select your target device. Fill the required data and click build. Wait a few seconds and your app will be ready for device testing and/or submission for distribution!


Conclusion

In this series, we've learned about timers, tap listeners, and other skills that can be really useful in a wide number of games.

Experiment with the final result and try to make your custom version of the game!

I hope you liked this tutorial series and found it helpful. Thank you for reading!

Tags:

Comments

Related Articles