Needs type, text, recipient id, possibly some custom fields for type-specific strings, a boolean for mark as read, etc

Actually check for existing names/emails, put stuff in the table, etc

Create the game board and display the pieces on the board

-Should be serializable with gson. Either set it up for direct serialization or register a method for it somehow.
-Might need to have subclasses for invite, message, match result.

Forfeit, 50 moves, Checkmate, King Circle, etc

Create a client-side class used to display errors

Allow users to create games.
Allow users to view their history
Allow users to move in games they are in
Allow users to forfeit.
Allow users to unregister.

Bounces, clockwise movement, etc for all pieces. Done in #60.

Invites now go to notifications table

-Client request should extend AuthenticatedRequest and include notification id and what they want to do to it. -Alternatively, set up separate apis for mark as read and delete.

End the game when both players have made 50 moves in a row without captures

User gets notified of new game invitations.
User gets notified that it is their turn.
User gets notified of final game results (win, lose, forfeit)

This is a client side task
should have username, password, email fields, and be able to send requests to server

End the game when either player performs a successful King Circle, clockwise from their starting line to their opponent's

Also includes sending invites. Done in #64.

something along the lines of:
Path: /api/register
request data:
{ username: "", email: "", password: ""}
response data:
{result: bool}

Users should be able to forfeit when it's not their turn,. but not when the game is already over

-should take a list of notification objects
-should have a way to mark notifications as read/deleted that sends something to the server. Check #50. If it's been done already, follow them. Otherwise, make your own format that seems reasonable. Remember to include the authentication token with every request.

Either display homepage after successful registration or display error sent back from server

Check against the database, generate and return token if successful

Either go to homepage with successful login or display error message

Done in #64

this class should include: email, nickname, password, unique ID
it should be used to store this data after retrieving it from the database

table should have fields for password hash, username, email, unique id

-Create a subclass of AuthenticatedRequest server-side. Probably doesn't need anything else for now.
-Register a handler for post to api/notifications that gets the account id and uses it to search the notifications table as a foreign key, then returns a list of notifications (or an authentication error if that failed)
-We might need to add an account id variable to the authentication tokens. Alternatively, need an easy way to get accounts by username instead of id. Either way will take a bit of work, adding id to tokens is probably more work but also more secure.

Make buttons more intuitive

Also includes creating corresponding DB table

this class should manage connections to the database and send sql queries

Teach it the rules.
Track moves.
Interface with Move objects
Store and send the board data.

This is a client side task
should have username and password field
should send login request to server
should display the result of attempted login