Include tools for testing various parts of the app

Put shell sounds to their own directory.

Rename audio to corresponding audio event.

Provide latest versions of the files.

Provide the facility for the player to retry a failed connection a
certain number of times.

Assets for weapons.

This file is unnecessary.

Use appropriate identifier for function that runs network thread.

Put input and video subsystems into their own directories.

Split the network events to the net directory to keep the app code
implementation clean.

Ensure no side effect persists when errors have been triggered.

Database will be used for authentication.

Update documentation.

Implement the sending of input events to the websocket server.

Use common method for creating messages in client and server.

Update identifiers to be consistent.

Add subdirectories for grouping net-related functions.

Make server optionally have a mountpoint for putting assets.

Point symlinks to relative paths.

Copy implementation from lws.

Connect client to server, save connection details.

Ensure app pointer is present in callbacks.

With the help of the test client app, the real client is able to receive
messages which are transmitted through the server.

Ensure the same reference of the server is terminated in the server,
while the client should check the context when connecting/disconnecting.

Attempt to connect client to server.

Ensure mounts are configurable.

Isolate network logic to each subsystem.

Split callback logic into several functions.

Update initialization method.

Use ring example.

Use minimal server echo example instead.

The client app is able to connect to the server, however no further
communication is happening. Must've been the callbacks?

Also the client app enters into an infinite loop when lws_service() is
called inside the game loop.

Set log level to 0 for SDL to handle logging.

Add libwebsockets client to game executable.

Protocol retrieved from lws git repo for samples.

Websockets server is for game networking.

Only check if events should break the game loop instead of having a
separate member for game loop checking.

Delegate the event handling solely in input state.

Add tests for initialization and teardown for all input methods.

Specify describe block for each player tests.

Allow current item pointer to have custom type.

Change the pool list initializations.

Add memory and data-related implementations for handling game data.

Use consistent integer types for mocks.

Properly mock video function dependencies.

Correctly dereference pointers.

Update input tests.

Declare memory before processing.

Declare variables early on.

Use short names for int types.