During last week’s Hangout we wrapped up our endless runner game development series by adding some final particle effect tweaks, dropping in Composer scenes, and adding collision audio. This week we are starting a brand new game development series that will give us a chance to understand how to programmatically add display objects in a grid, randomly assign images to be displayed, match touched items, and more. Download the code and follow along each week.
At the end of January, I talked about wanting to make plugins more open.
Today, we’re doing two things to make that happen.
Last week on Corona Geek Hangout 134, we continued working on our endless runner game by adding a third party particle library to spice up the look and feel of the player’s movement. We also added code to track the player’s progress and keep score as the player successfully avoids treacherous hallway corners. Here are video clips from the session.
Recently on Corona Geek Hangout 133, we continued working on our endless runner game by adding code to generate continuous hallways, add particle effects, and automatically restart the game when the player object runs into a wall. By the end of the Hangout our game was looking a lot like the original. Watch these clips to see highlights from the conversation. Download the code and follow along.
During last week’s Hangout we continued development on our endless runner game. We added code to generate continuous hallways, handle memory cleanup of previous wall segments, and automatically restart the game when the player collides with a wall. We also added particle effects to the player. This week we talked more about how the particle effects work, added code to keep track of player progress, and added an interface for the player’s score and speed.