Need to know who is allied in any given game

Allow user to supply email address (and any other relevant fields) when being created
Also, need way to update password/modify user

Support for original game clients (in additional to CnCNet)
https://github.com/mafintosh/udp-request

Currently a new entry is created in auth collection per player - duplicating username/password. Ideally, one entry per username/password combo with an array of nicks.

Proposed Auth Object

{
  "id": "ObjectId",
  "username": "String",
  "password": "String",
  "email": "String",
  "nicks": [
    "ObjectId"
  ]
}

Also need to logic to determine that the player passed in Packet or various endpoints, matches the auth username that was passed

http://ladder.cncnet.org/api/ladder/ts?limit=5

this doesn't seem to be working anymore despite tests?
tests/functional/ladder.spec.js#L496-L503

The client will request a list of authenticated users.
It will then match the response to it's internal list of ChannelUsers and mark the users that are authenticated.

Need to support more than 1v1

The API should allow consumers to POST to /ladder/:game/game to reserve a gameId in which stats can be posted to at a later time. Ideally, this should be called only once by the "Host" when they start any game.

The "Host" client can then communicate the "gameId" (from response) to all players within the game.

Example Request

POST /ladder/yr/game HTTP 1.1
Authorization: Basic <hash>

{
  "players": [{
      "nam": "Wingle"
  }],
  "settings": {
    "sped": 0,
    "scen": "Some Map",
    "unit": 1,
    "aipl": 0,
    "crat": 1,
    "base": 1,
    "supr": 0,
    "shrt": 0,
    "cred": 10000,
    "trny": 1
  }
}

Example Successful Response

Request Method: POST
Status Code: 201 Created

{
  "gameId": 1,
  "url": "/ladder/yr/game/1"
}

Need to determine if a packet field exists for clan matches

Save user passwords as hashed passwords.

As it stands, clients must maintain user credentials for auth required endpoints.
Should instead issue a JWT at auth-time and rely on Authorization: Bearer <jwt> scheme

go lose some weight fatty

Create hof (array) property in player object, so it can be easily displayed in the UI

player {
  name: "(string)",
  hof: [
    '(string)', // November 2016
    '(string)' // December 2016
  ]
}

FFG vs Ranked games

• Clients need to send trny flag

Node has native Promise support. Need to move away from the q library dependency

In reference to 26af006, need to update all members of a given clan upon destroy