A prototype I developed to learn how to parse JSON files to define custom player input keys and player properties. This also allowed (although now primitive) for persistent storage of state.

This was my first time also working with a Finite-State-Machine (FSM) to handle player state and animations, the idea of FSM was quickly integrated into all my projects soon after.

The original game idea was about having a “red” form for platforming sections and a “purple” form for combat, the player was able to switch between them at the press of the Q button. Other forms were also planned but never implemented, like most of the game idea.

When I found out that I really enjoyed developing data-driven systems, my first thought was “how do Tower defense games utilize the concept in their game loops?”.

So I sought out to develop my own wave manager, enemies with path finding, turrets with targeting and predictive logic using a lot of applied mathematics (not the available tools in Construct 3) AND a player inventory to store what turrets were available for placing.

This developed my initial skills in data-driven managers that could process any combination of inputs and output the expected behavior. UI is adaptive to the turret placing range using Pythagoras.

The original game idea was for the game to get progressively difficult the more waves the player beats, turrets could malfunction and would need to be repaired. This was all an effort to make TDG more interactive.