Code

Didac Romero

Input: Gamepads (controllers) Input and vibration

As one of the code leads of CheckTheDog I have been responsible of building flexible easy to use functions to interact with some back end features I coded. This allowed other programmers to easily interact with the system I created to gather and manipulate all the data and haptic features (vibration) of the controllers.

Input: Game controllers button customization

Since I've been in charge of everything related to gamepads in our input module, I developed the buttons and triggers customization features, as well as their use in UI in the Options Screen.

Gameplay: Storm

The ruthless storm was assigned to my tasklist, and since it is something that needs a lot of balancing I built it as customizable as possible. The amount of times that the storm moves, the time it waits until it starts moving again, and the damage it causes to the players are amongst the variables that can be customized through an xml document.

Gameplay: Item manager

I worked on the item manager that deploys pseudo-random items in spawners located aroud the map. Game designers can easily manipulate the position and number of spawn points by placing them as they want in the map in Tiled, with the item manager managing all the data so designers don't need to worry about it and can freely place them.

Sprite in-game re escalation feature

Some sprites wouldn't be in perfect sync in terms of size or proportions relating to other elements on the screen, so I worked on a simple system to easily resize sprites in game to fit any needs.

UI: UI compatibility with gamepads

Since our game is fully played with gamepads I have been in charge of making the mouse based UI compatible with the gamepads. I also worked on the markers (feathers and arrows in customization screens) which helps the user quickly visualize which button he/she is interacting with.

Discarded gameplay: Bush based fog of war implementation

I worked on a fog of war bush based system, based on games like League of legends or Brawl Stars. It was based on a personal research I did for this same subject and it posed a challenge to adapt the implementation to 4 viewports and the complex data generation algorithm needed to efficiently manage visibility inside and outside the bushes. Due to a combination of lack of time and the fact that it didn't seem to work with the gameplay of the game, the feature was discarded midway production.

Twitter Community manager

I have also been in charge of udpating our Twitter account with the progress of the team and the different strategies to achieve visibility and engagement in this social network.