alexmdodge / grid-grind Goto Github PK

There is still a fine line between the game being incredibly easy and incredibly difficult. Still need to play around with some different settings in the level configuration to ensure that everything if working. This may change when higher level chains are implemented.

Need to both tweak the difficulty settings, and also add a selectable difficulty setting.

Originally the game components were going to exist primarily in the game canvas container, but with how easy it is to references databases and modify external elements I would like to only place the bare minimum game logic in the framework. The external components would be,

• Start screen with background animations, user name choice, avatar selection, highscores
• An update of the current menu's so they are mobile friendly and will appear when selected from a small button
• There should also be a tutorial section with animated gifs and other helpful suggestions

Write the test suite for the colorTree class. Note that this data structure was used from another repository, so game specific test cases will be used.

Build out a simple backend using Node for storing highscores

Introduction

The start menu UI should have a start button, a high scores button, and the logo! If you're interested in spicing it up, there could be animated objects in the background moving or fading in and out

Implementation

This project implements the Phaser framework and is written using ES5! If there are any issues with installation let me know! The buttons and the logo should be added as sprites. To create the menu the game objects should have the visibility false beforehand then switched upon starting.

Before I start to advertise the project to external developers I really would like to get a good test environment configured and setup with separation of concerns to ensure that. Need to pick a testing framework and get a number of tests up and running with code coverage badges.

This will ensure a solid future environment with higher quality code.

Finish the test cases for the level configuration class

The first step to supporting ES 2015 is to get the Babel transpiler working through my gulp build files.

Setup the Mocha testing suite to transpile ES 2015 code.

Update all of the current build version and move the build tools to Webpack. Also add things like templating integration and other components.

Some issues with the current game state,

• The points do not reset from level to level for the counter
• The tiles change randomly and will pick up colour tiles that were in a previous array which will then collect colour not adjacent to one another.
• On game over, level and moves left do not reset properly

Determine how to write some test cases for the game file. This will more likely be use case driven tests, as the game is very much intertwined as this point. Perhaps with such high coupling between functions it would be best to consider the orthogonality of the software.

This will relate to #3 as I have yet been able to determine the cause of this bug.

CirceCI only supports XML style JUnit tests. The current mocha setup only uses the spec reporter, so will need to install and configure the Mocha CircleCI Reporter.

Integrate templating framework in the build to deal with smaller components from the tutorial screen. Look into templating through Webpack.

I've been putting off switching all of my code for the project to ES 2015+. This really should have been the first thing I did but I'm happy I learned the project the way I did.

Separate logic into separate classes more effectively,

• Block setup
• Animations
• Menus

Create a build step for deployment where assets are bundled and prepared.

Currently the game does not indicate when a player has entered the next level. It also does not show when the game has started or ended.

Currently passed level three points are not properly counted toward the level total. They seem to be double, but this behaviour needs to be investigated further.

Get ESLint setup using the AirBnB linting guidelines to ensure higher quality code.