Add some missing parts.

Add documentation for sprites and animation management.

Demonstrate on-the-fly flip for sprites.

Some contents for deliberation.

TODO comments for implementation.

Make distinctions between internal and external (downloaded from
third-party servers).

Make use of sprite loading to streamline the sprite management process.

The sprites are now loaded using a utility function in IZ_video.

The magazines for each weapon except the rifles have been drawn.

Add custom enums for making sense of returned values from config and
game app code.

Ensure every config-backed subsystem can serialize/deserialize config in
a single consistent manner.

Add templates for config item types.

Also updated server's config to use the global config module.

Remove symlinks and make codebase use common modules instead.

Rename files in order to prepare for extraction for publishing
subsystems independently.

Unify config loading in net and video subsystems.

Make sure to have help messages for both the game and the server.

Make the member name generic to accommodate other potential
implementations beyond Websockets.

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

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.