Fill out data for Ordinator.

The weapon sprites are now exported to SVG.

There is a new weapon called Ordinator which fires 20 rounds of .45 ACP.

The bullets have been improved. Also, file structure for weapons is
being drafted.

Ensure no transforms are done with the sprite components.

The magazine for Paragon is now drawn. Also the weapons showcase is
added for showing all the available geometry of all the weapons.

Ensure magazine is completely drawn.

Fix sprite grouping, add more neutral codenames to weapons.

Use measurements from CIP.

Use construction sheet for 9mm.

Draw the rifle bullets according to dimension charts.

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

Add remarks for M9.

Small changes to weapons sprites.

We'll just use the flipped versions for ease of development.

Include weapon sprites, however the flipped versions need re-tracing
details.

Specify final list of weapons in the game. Add additional details for
information on sprites.

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

Organize audio. The sfx are also rearranged.

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.

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.