Production Diary #2 - Construct Development

30/01/2019

We have began to turn our ideas into a demo for our final game, this will act as our "Version 1" which will be a way of discussing what is good about the game but more importantly what do we need to do to make it better and how are we going to add to the game to turn it into a fully fledged educational game for year 6 children.

So far the game has a work in progress menu and a cut down version of level 2 which will act as the "decision level" for the demo. This level will determine what you see next and how the game will progress. It allows us to show off the fact that choices make differences and so you get to see the main feature of the game.

I've created sprites in Photoshop and then imported them into Construct as usable objects. We decided that the buttons would not work with the fading mechanic we wanted to have because they have a special property that keeps them on top of everything else. Because of this we decided to swap out the button objects for button styled sprites we created in Photoshop.

In conclusion, this development has allowed us to get closer to a Version 1 of our game, a demo version for others to playtest which will give us feedback on what needs to be changed immediately. I have learnt that button objects are considered HTML within Construct and that HTML objects always float to the top of the layout and so cannot be hidden with fade behaviors.