So simply put, my first steps into Construct 2, " a leading free HTML5 game engine" as it says on its web page was a rather pleasant experience. Initially I just followed a tutorial on building a platformed style video game and after a few minutes I found my self rather engrossed with the entire methodology behind how Construct 2 works and handles certain things. The intuitive nature behind creating a player controlled assets felt rather streamlined and easy since the steps could be counted easily on one hand. Add some finessing with animated sprites, a few more assets for obstacles and the like and I had a fledgeling game in no time.
If i had to shower some lime light on any one key feature, it would be my experience with I came to know as the event sheet. Every part of Construct 2 it would seem is run by events that tie into actions. These Events and Actions drive the majority of the game you are planning on creating. A simple example is lets say you wish an animation to play when a certain key is struck, such as the left or right arrow keys. The action of pressing the key is what is considered as the "event" and so you define the "action" that will be taken, the desired animation played as a response to the pressing of the key. Although the concept of Events and Actions is easy to understand, the action implementation of it can quickly become rather complex rather quickly. This requires a mentality that can think on a per action/reaction style, which I guess for some would be quite tiresome. However, mechanically speaking Construct for me is a rather impressive little engine; I'm looking forward to delving deeper into the program.
If i had to shower some lime light on any one key feature, it would be my experience with I came to know as the event sheet. Every part of Construct 2 it would seem is run by events that tie into actions. These Events and Actions drive the majority of the game you are planning on creating. A simple example is lets say you wish an animation to play when a certain key is struck, such as the left or right arrow keys. The action of pressing the key is what is considered as the "event" and so you define the "action" that will be taken, the desired animation played as a response to the pressing of the key. Although the concept of Events and Actions is easy to understand, the action implementation of it can quickly become rather complex rather quickly. This requires a mentality that can think on a per action/reaction style, which I guess for some would be quite tiresome. However, mechanically speaking Construct for me is a rather impressive little engine; I'm looking forward to delving deeper into the program.