Case 1.4

Case 1.4 / End Case

Final task of the year was to create a game. (as our study direction suggests we do).
The idea/concept of our game was something we’ve been working on the entire year.
The last three weeks of the year were the time we had to make the game.

I’m not going to go too much into detail about this one, as I’d probably be writing an entire
book if I did, but this task really showed a lot about how much an idea can change throughout
the year. Mainly because of limitations of ability or time, but also because you tend to
grow tired of ideas that otherwise seemed to be incredible to you. I think this is probably
one of the most important lessons learned from this year.
I didn’t manage to put everything I wanted into the game, but despite that, I’m quite proud
and happy with what I’ve achieved.

To give you a basic idea about the game I made, here’s the pitch:
To save the life of a dear friend, a boy (the player) gets pulled into a sort of watercolour world.
It this world he must collect pieces of her heart (Heart Pieces) by finding his way through a route
with the help of watercolour techniques. He must learn to use these in a simple but smart way.

It’s a simple game that mainly focuses on the calm atmosphere and story and wants to let the player
relax a bit. But of course he must sometimes think a bit about what would be the best way to reach
his goal.

1 Liamallicia

Naamloos Naamlooss


Game Engines Final

Game Engines

Task: Create a (short) game based on old arcade (or alike) type games.

Programming is, in a way, fun, but it’s also the subject I have most trouble with.
For this little game I chose to make something based of Space Invaders.
To explain the game;
There’s two lines & each has 5 holes that shoot bullets. One of the lanes is the enemy, which
randomly shoots one or more bullets out of its 5 holes. The other line is controlled by the player.
The player too can shoot bullets out of their 5 holes (by clicking on the a,z,e,r,t keys).
Now, what you basically have to do is shoot and destroy the bullets the enemy shoots at you. However
if the enemy hits your line and/or you hit the enemy line, it’s game over! With other words, you may
only hit the bullets. Try to keep up for as long as possible.

I was quite proud of this game. Unfortunately, for some reason, I couldn’t get the scoring system to
work. It helped me a lot programming wise though. I finally started to properly understand several
things. The game itself is actually also quite fun to play in my opinion.. (has both normal & hard mode)

Naamloos Naamloos2

Case 1.2

Our second important school project was also to be made in a group. And since we’re the
“Game Art & Design” group, our task was … to create a game! This time in a group of 3.
It had to be a game with “standard visuals” which means objects like cubes, spheres etc..
No complicated world with stylish characters or emotional storylines.

Our group made a game called “Tunnel Vision”. The player controls a ball rolling through
a tunnel and needs to collect points while avoiding obstacles. My strongest point is drawing
so I was in charge of making all of the artwork (from concept art to textures, buttons,
some level design etc..). Level design was mainly done by a second teammate though,
since he made the 3d levels in Blender. Our third member did all of the programming.
It might not be perfect but… seeing this game come to life and work was a big boost
for my “What are we really doing here” question.

dqfd Startscreen