Stop accessing mongo from the client

[PeterGerrard]

There are bits of code in the client like:

Games.update(gameID, {$set: {state: 'nightTime', deaths: [], injuries: []}});

For a prototype this is fine, but longer term it would be preferable to have a cleaner api where onlt the server can access mongo. There are two main reasons:

• All the state modification code lives in one place making it easier to reason about
• Allows you to put checks in ensuring there isn't a vote on before starting nighttime. Currently this relies on the sleep button not being present on the ui.

[timadye]

My current model is to allow Player-specific changes in the client, but global changes should be done by the server.
You found a case that breaks that rule, which I should probably fix.
More generally, I didn't find a clean protocol to allow the server to roll back an action that the client wanted to do but wasn't allowed. That would be necessary if the client has moved on to another screen. So it's easier to put the check in the client, even though that's not ideal.