Welcome to Flighty Mk. 2. Although the original version was great, we've added countless improvements to optimise performance of the game, new features including online multiplayer and a parallax effect powered by the position of your face (using face tracking) and a whole extra bit of colours. Take a look below and download Flighty Mk. 2 to try it.
For this assessment, we figured that the 8 bit graphics we were provided with in the previous game just didn't quite cut it. So, during our many 'idea and design' sessions, after pouring over a whiteboard for hours and hours, we came up with the innovative solution of adding 1 extra bit of colour - so we now have 9-bit colour!
- Single player unlock system
- Multiplayer is consistently played on the left
- Face-tracking parallax
- Buyable items to make your opponent's game harder
- All Java code
- Uses LWJGL - super light-weight, very commonly used because it's so simple and well documented.
- Cross platform - one Jar for all platforms. Just don't try to run from a Windows networked drive! (Will only affect players on corporate networks, and chances are they shouldn't be playing games anyway. If you are one of these users, and want to hide from your boss whilst playing this game, we recommend storing it in "C:\temp".).
- Complete Traceability
- Original code was very stable, but poorly structured - initially, we had to refactor massive 1000 line classes and 800 line methods. Now the structure is super clear and easy to maintain.
- Super well structured networked multiplayer - we constructed a server from scratch in Haskell to pass byte-strings, where of these is defined as a message type, and a client in Java, also containing these pre-configured byte-strings. Simply call a one line method to send any parameter or object to the other player or the server
- Fully Documented, so you have endless comments to trawl through before you find actual code.
Our code is really easy to understand - it's self documenting. But just in case you're struggling, we've added tonnes of comments and documentation.
Drop us an email - Sam Heather (firstname.lastname@example.org) or Paul Gibson (email@example.com) - we're happy to answer them!