At the begining of 2013 I was working as part-time web developer which gave me a fair bit of free time. To fill this time I challenged myself to make a game a month.
My goal was just to remake a classic game and write a post explaining how I made it. Seeing as I was remaking games that had been make a million times I went with titling them “Just Another [Insert Title] Game”.
I managed to make two games before I got invovled in a 10 day Game Jam. Once we finished the Jam I went from working part time to full time as a Junior Software Developer and just ran out of free time to build a game a month.
Hello!How you been? I can’t believe it’s been another month.
So this month has been a bit of a mess. I started out making a game and, well, got caught up with a GameJam. At the start of this month, GameJolt start a GameJam from the 1st to the 11th, so as a studio we thought this would be a fun thing to take part in.
The theme for the jam was chaos. We played around with multiple ideas but end up going with a first person Unity game about causing chaos at work. The main goal of the game was to basically kill your boss. There was going to be multiple ways of doing this and typical office stereotypes to help/intervene with you achieving your goal.
I current don’t have a link to the game but most of the jam was recorded on our studio Twitch channel
Anyway I’m sorry about the late post and the lack of content but next month, well this current month, I’m moving up from ActionScript 2 to ActionScript 3. I’ve been putting it off for a long time but I’m manning up and just jumping into the deep end.
Thanks again for reading and I’ll see you in just under a month :]
Game Number 2! So this month I have somewhat stuck with the “in space” theme and have remade Asteroids. I haven’t had as much time this month to work on the game, due to the fact that I got a programming apprenticeship. First 9 – 5 job (Well 8:30 – 5:30) so finding enough time to keep up with everything I used to do has been a bit of a struggle but I JUST managed to finish this month’s game. 😀
I haven’t really got much time to write an epic summary like I did last time but I can break it down a little.
Doing things as I usually do, I planned out what the core gameplay would require. This was Player, Bullets, Asteroids, Asteroids manager and a HUD to display score, lives and the current level.
I started off by copying Player.as and HUD.as from the last game. Obviously these classes are going to be very similar in Asteroids as they were in Lunar Lander, so there’s no point in completely recoding them. (The lists bellow are in no real order)
From Player.as I:
– Removed Gravity and added friction
– Changed appling thrust from space bar to W or Forward Arrow
– Removed the Thruster Image
– Made space bar now fire bullets when pressed
From HUD.as I:
– Removed all fuel related functions
– Removed end of level screens and effects
– Adjusted the game over function to deal with outputting the level at the end
– Added an effect for the level text on the HUD
I did all the changes to the player class first and then created a parent class for the bullets and asteroids (They have basically the same functionality so there’s no reason to duplicate code). This handled movement, flying off screen, seting properties and just basic functions to get variable values.
Asteroid manager was created next. This class creates and destroys asteroids and levels. It also handle collisions between objects and all asteroids on stage.
Once I had the manager and the parent class, it was time to make the asteroids. The asteroids class really doesn’t do much. It just looks after the size of the object a calls back to manager if it needs to be destoryed.
Last up, as per usual, I created the menu screens (and adjusted the HUD). I seem to leave these two things to last due there simplicity (Well the menu at least) and becuase gamplay mechanics are kind of key to a game.
Sorry that this months artical doesn’t contain much detail, I have really been short on time! Anyway, for now, thanks for reading and I shall see you next month :]
First month, first game. For this month I’ve decided to remake Lunar Lander. Why did I chose this? Well, because it’s simple and addictive game. I think the fact that I’ve wasted hours/days of my childhood playing it (Just like all the other games I’m planning to do this year) may have helped towards choosing this game.
I started, as I usually do, with programming the most important object, the player’s ship. I first created a simple movie clip with a basic image of space ship and attached a new class file to it. In the new class file I programmed in a simple key listener for allowing the player to rotate and thrust the ship. After flying the ship around I decided the next step was to add in the collision checks. These first checks were simple ones; if the player flies off either the left or right side of the screen they should reappear on the opposite side with the same velocity and if the player tries to go off the bottom or top of the screen they simply just get pushed back. Now I’m left with a ship that can fly endlessly around the screen. Seeing as lunar lander is based on the moon and not in space, this just simply wouldn’t happen. I sorted this issue by adding resistance to the ships position update, a max velocity and obviously gravity to the ship.
With the basics of the ship done I next moved on to setting up the landscape for the ship to crash and land on. I first thought about having separate movie clips for each level but the collision checking would become far too complex so instead I opted for drawing the level using an array of coordinates. This works by drawing a line between two coords and placing it in an empty movie clip. When the loop is setting up the level there’s a check to see if a landing pad needs to be drawn. The positions of the landing zones for each level are stored in another array. LevelManager.as handles all these function for creating and destroying the level.
Next up, the collision checks between the land and the player. This for me was a big deal. I haven’t done collision for single lines before, only simple rectangle and circular collision checks. I tackled this problem by first getting a piece of paper and drawing/working out how I know if the line and the player had collided. After a few minutes I simply worked out that the line had to create a tangent or a segment to be colliding with the player. My first assumption was that I needed to check if the collision circle of the player and the line had similar coordinates. This system was flawed because of the number of calculation that would have to be done. My next idea was using the three coordinates I have (the start and end of the line and the player’s centre) to create a triangle. The height of this triangle would then be compared against the radius of the player’s collision circle. If the height was less than or equal to the radius, the two object had collided. To work out the height of the triangle I rearranged the cosine rule (a² = b² + c² – 2bccos[?] to ? = arcos[(a² + c² – b²)/(2ab)] ) to find the angle between the top coord of the line and the centre of the player. I then rearranged sin(?) = opposite side / hypotenuse to opposite side = hypotenuse / sin(?). Putting these two together with all the values I have provides the height of the triangle. The only problem with this is when the player’s coordinates create an obtuse triangle. This means a right angle triangle can’t be made inside and thus breaks the previous formulas. I solved this by putting checks on the angles created making sure that they are less than 90 degrees. This does however create a blind spot which is corrected with simple distance checks from both the top and bottom of the line to the player. Below is my working which should help explain everything a bit more. Sorry that it’s a mess and for the random doodles by my sister. It’s my own fault for leaving it out on the desk -.- .
Now I had the basics and a playable version of the game set up, I moved onto creating the HUD. The HUD handles the start and finish of the game as well as keeping track of score, fuel and lives. I started off making a movie clip with a score counter, a fuel bar and little images of lives. Next I attached a new class to the movie clip and set up variables and functions to deal with the score counter, fuel bar and lives. I then realised I needed a score counter at the end of each level to show what the player had achieved. This was just another simple movie clip with text fields in that gets attached. I later added an effect to make it look as if the score was counting up. After setting the game over screen I wasn’t happy with everything just suddenly being on stage. This lead to making things fade in and out. Adding this in after I had completed the bulk of the code made everything a bit messier and I really should have thought about doing it in the beginning.
The last thing I didn’t was create the main menu, not really much code used for this I just set up movie clips with buttons in that called functions from the HUD. And, well, yeah, that’s about it.
Thanks for reading and sorry about any poor grammar. I shall hopefully see you in a months’ time :]