Last Signal – Week 1 + 2
|
New course and a new project to work on. Due to various students dropping off, there was an unbalace with the groups and team 14, the team I was part of, was divided up into other teams. Me and two others from team 14 were placed in team 5, where we luckily fit in nicely. The project started by choosing a concept that another team had developed during the previous design course and develop it into a fully funtional game. We chose to work on the concept for The Last Signal, a top down shooter where the player has to navigate a spaceship while avoiding/fighting aliens in order to send a signal back to Earth. I am the lead programmer for the team, which means that I am responsible for the code of the game and oversee that it is fully functional, without any bugs, when we reach the release date of the game. The programmers of the group(two, me and one other) have started work on a prototype that is to be used to test various features of the game. So far my fellow programmer and I have created code for the players avatar to be able to move around in the prototype using the A and D keys to rotate, and pressing both to move forward. This is to simulate the two thrusters in the avatars spacesuit that is used to navigate. The controls and movement are clunkt, but this is not a bad thing since navigating in space without gravity is not an easy task to accomplish. The player can also fire a projectile using the enter key. We have also added a few enemies to the prototype with a placeholder image for the sprite. The enemies have functionallity to multiply themselves to a certain extent. So far the only movement options they have are that they rotate to face the player and can shoot projectiles if the player is within range. The projectiles that the player can fire and the enemies fire are using the same placeholder image as the enemies.  |
