Deity: Become One

Pros

Refactoring the code down so it made it easier to understand and read, when someone else was looking at it.
Reading/writing to dat files worked well when loading and saving the levels. It was broken down into 4 parts. One dat file stored the data on the boss, another the obejcts such as blocks and lesser enemies, another the player data and the last one stored the settings for the levels.
The mixture of inheritence and composition based progarmming also worked well with our lecturer commenting that we had done a "superb job".
The astectics were also very good as it gave our game a very unique style and people could instantly recognise our game.

The level builder wasn't as good as it could of been code wise and also when using it.
The code for the level builder was a bit messy and could of been cleared up if I had made a button or an UI class to help with all the button presses and unique code.
The design was a bit confusing so as some people were saying they didn't know what to press once they had made their level and that they didnt seen the side bar as it was hidden away too much.
The story was also a bit lacking and there was no real motivation to play in terms of character that the user could relate to or become interested in.

Make the enemy designs more unique so they are clearer and easier to distinguish.
Added in a real story to make the user want to play the game more.
Compress the audio so it doesn't take ages to load up rigth at the start.

I learned about component based programming and how useful it is. The fact that you can just attach a component to an object and say, ok now behave like this and then attach another one and the object can act entirely different.
It taught me component based programming, as well as consolidating my understanding of how classes and objects should interact in a game.
Also I learned how important constant communication in a group project is, as sometimes we didn't and then we would end up working on the same thing and end up clashing.