Thursday, 28 April 2016

Year 3: Final evaluation (21/09/2015 - 29/04/2016)

Final evaluation (21/09/2015 - 29/04/2016)

What I have been asked to do:
For this year I was asked to choose a subject of games design to specialist them and create a full year long project. the specialist I chose  was the interactive specialist as creating code and gameplay mechanics is what I hope to do in the future as the job.

The idea I had for my project this year was to create a tower defense/real-time strategy game that would employ many different game mechanics and would work as a sort of showpiece of what I could do with a game engine.

The idea of this game was that it would be a wave-based tower defence game in which the player has to survive as long as possible this is an idea I've been developing parallel to my work in the current years but now I'm beginning to implement them together.

Good points:
When  creating this project the role of points I did enjoy most of the coding within blueprint was thoroughly enjoyable and I found it interesting and enjoyable to code multiple systems and learn how to code new features that I had no idea how to do before

Another part of the development cycle I really liked was the playtesting session as it was really interesting to see other people's take on the game and also to hear their ideas which sometimes reveal information about the game I had completely overlooked an hour and have allowed me to implement new features to the game that I would not for of previously

Bad points:
upon reaching the end of this project walking back I can see many areas where I can improve and many bad points of the projects that stick out to me. One of the main point is I feel that the idea of this game overall is not good enough to be a full game on a turn feel that its concept is just not quite there and if I was to choose my project began I would definitely not recreate this game would probably try use another idea.

Another bad points and I found with my project was my responsibility and that was I was not able to conduct as much play testing sessions as I would have liked. and if I was to redo the project again I would definitely have given myself a deadline to finish the main game and have a longer period to play as it can reveal so much negativity about your game but you can improve a felt that with more time it would have made my game many times over more impressive and better for the player.

My thoughts on the year:
overall my thoughts on the year  where that it was very interesting and enlightening and has really given me a clear path to aim for when I leave university. This path will be along the coding side of gaming as I feel there is more suits what I  like to do and it's also in like me to the real realities of working on a project for a year.  working on a game for a year really offers insights into problems that can arise over time if the core concept is not stable not to say that the concept of my game was totally unstable fourths I think if I was to read you this project again I would definitely of spent more time breaking down the idea of a game before committing to. 

Year 3: Week 28 Summary (25/04/2016 - 29/04/2016)

Summary (25/04/2016 - 29/04/2016)

Events This week:
a final group session on Thursday

Learning agreement schedule of work:
.Implemented more features into the game .Begin to finalise game mechanics and features

Progress on different projects:
I have finalized the game and have implemented the last of the artwork needed the game is now fully complete though I am very disappointed that I only managed to get a limited amount play testing feedback to the game I felt that with more time it would have vastly improved the gameplay performance and made the game a lot more enjoyable for people.

Year 3: Week 27 Summary (18/04/2016 - 22/04/2016)

Summary (18/04/2016 - 22/04/2016)

Events This week:
a group session on Thursday where I managed to ask some of my fellow course mates to conduct play sessions with me.

Learning agreement schedule of work:
.Implemented more features into the game .Begin to finalise game mechanics and features

Progress on different projects:
I managed  to ask fellow classmates if they would buy my game and give feedback  to it. The information was stored in a survey by asking to complete and some of them gave some really good ideas into new metallic strip about the game as well as sort of changes that could make the game are these were such things as title up the UI interface as well as implemented to tour real which has been fully integrated now and as well as add some small mechanics to different the source systems within the game.

Year 3: Week 26 Summary (11/04/2016 - 15/04/2016)

Summary (11/04/2016 - 15/04/2016)

Events This week:
A group teaching session on Thursday

Learning agreement schedule of work:
.Implements more mechanics into the evolution game project

Progress on different projects:
This week I managed to conduct a small playtesting group of close friends to play my game they offered some surprisingly useful imports of small mechanics to change which I did implement in the game. As well as cleaning up blueprint scripts and making a more efficient and as well as general repairs and fixes throughout the game

Year 3: Week 25 Summary (04/04/2016 - 08/04/2016)

Summary (04/04/2016 - 08/04/2016)

Events This week:
group session on Thursday

Learning agreement schedule of work:
.Implemented more features into the game .Begin to finalise game mechanics and features

Progress on different projects:
Though it has taken a long time the game is now fully ready for playtesting to begin with they can be our lot longer than I thought it would an  has really caught in to my playtesting time that I was hoping to get meaning that I will have less time to implement these changes in less time to improve my game which to be honest is made me a bit disappointed.

Year 3: Week 24 Summary (14/03/2016 - 18/03/2016)

Summary (14/03/2016 - 18/03/2016)

Events This week:
.A group session on Thursday

Learning agreement schedule of work:
.Implemented more features into the game .Begin to finalize game mechanics and features

Progress on different projects:
Most of the features of the saving system have been implemented within the game only a few UI and cosmetic features still need to be implemented to have this feature complete which means playtesting can begin once the system is fully integrated.

Year 3: Week 23 Summary (07/03/2016 - 11/03/2016)

Summary (07/03/2016 - 11/03/2016)

Events This week:
A group session on Thursday

Learning agreement schedule of work:
.Implements more mechanics into the evolution game project

Progress on different projects:
the mega mutations of them fully completed and work has started on the sealing system like game this is the ability of the players to save their towers within the game. This presents quite a challenge me as I have never dealt with saving systems within a game but after doing some research into the mire it seems that it is not so daunting task and may be completed within this month.