Smarter Database Writer for player info

[trasa]

have a writer thread that puts db updates separate from game thread; more aggressive memory caching of objects for reads.

Currently player state is saved when they send a message and that message was acted upon. But what happens if the player alters another player's state?

Also need a much smarter way to handle DB writes than on each message as that is going to fall apart with a small number of players.