Blog: May 2016
Welcome to my Blog! This is entry number one. There are so many people out there trying to make games, and I’ve decided
I’m going to join them. So here is my blog, a way of recording the journey I’m about to undertake. I have a feeling I’ll go off
on a few tangents but that’s what it’s all about. I start here, having given myself a basic grasp of how to make a game. Now to
see if I can actually make one...
I remember reading a blog some time ago, when I was just starting to learn how to code. It recommended that as a first test
to coding the budding new developer should make the game ‘Tetris’. Not just the principle game of shapes falling into place
and a score being generated, but the whole game - start screen, high scores, sounds - everything. This is good advice. Once
you get an idea of how to make games, it’s very easy to get bogged down in a hundred different ideas and never actually
finish anything. It becomes a habit.
So my first challenge is to finish a game. I don’t want to make Tetris though. I want to make something new, my own game,
my own puzzle game. It can’t be too complicated as it can’t take too long to make. A Tetris type game then. I have therefore
set myself the aim of making a puzzle game in three months. Given the amount of time I get to code each week it’s a
challenge, but the time limit is on.
I’ve called it ‘Square Pegs Round Holes’. The aim of the game is to score as high as possible and the game gets more
difficult the longer you play. Shapes in the form of circles, squares, stars and triangles fall down and the player has to collect
each falling shape in the right box. This involves moving four different boxes along the bottom, to collect the right shape.
Collecting the wrong shape or missing the shape will fill a junk meter. When the meter is full the game ends. Collecting the
shape in the right box will score some points!
The game engine is up and running and already it seems pretty fun to play! I had to put some thought into how the player will
control the boxes. Should the player controlled boxes jump over each other as they are moved, or could multiple boxes
occupy the same space? If they do occupy the same space, what happens if a shape hits more than one box? Does the
player score or do they get penalised?
After switching it around a few times I think I’ve finally settled on a method that seems fair. As long as the player isn’t
controlling the wrong box at the time a shape is collected, the player will score. This will mean the player will need to think
about bringing a box along the path of a falling shape, or accidentally collect it on the way.
Aside from making the game, I’ve been doing some writing for the website. If you’re reading this blog chances are you’re on
the website - in which case all has gone to plan and it’s up and running! I’ve also started thinking about making some tutorial
videos on how to make games with GameMaker. I have learnt a lot from other people’s videos and I feel I can probably add
some of my own which hopefully will be useful to someone.
I’m going to