Multiplayer.

Multiplayer was the main focus of this game.

I had figured out how to post and request data from a database, and wanted to try creating a multiplay game with it.
From the beginning I knew that you should actually use sockets for multiplayer, but I wanted to try it anyway (although I do want to learn about sockets aswell).

I learnt a great deal about requesting and posting via this project, aswell as the time it takes to make a request,
which was the reason I went on to multithreading to speed the game up.
And if the request is to be processed, an API of some sorts is also needed, so I created a small API to process the request the game makes.

Server (substitute).

I did not create an actual server that would keep track of the game, so the game does that itself (as a substitute server).
It looks at what data (players and collectibles) it currently knows about, and compares that to what it receives from the database.
And based on that, it checks every collectible and player for where it should move, if it should still exists, what score it is, etc.

It also posts the changes that were made on it's own players game to the database, handles players quitting, and collectibles being picked up (although some of these are still work in progress).