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.

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.

Provide default states for input and output.

Allow MIDI input to be filtered through MIDI channels.

Use higher bits of first message byte to get notes from all channels.

Restrict Yes/No actions in same 2-octave span.

The game now uses MIDI support for alternative input methods.

Put I/O values to their respective structs.

Isolate input items into their own directory.

Ensure joystick direction enum names are consistent.

Ensure each initialization method is in its own source.

Ensure correct arguments are passed.

Determine config path only once.

Add geometry methods for point, vector, and rectangle.

Ensure one type of test can only be handled at a time.

Implement tests for joystick axis, hat, and button events.

Add third-party mocks, specify mock files.

/? Do we need first-party mocks in their own files, or can we provide a
mock flag in the implementation files already?

Make device handling opt-in.

Use types from header file.

Use call count type to contextualize call counts.