Fenhl

This seems like the sort of thing we should allow mods to implement.

We will need to support Anvil for vanilla compatibility. Any other storage can be added later, possibly through the mod API. I don't understand your second comment, sorry.

I'm not currently working on or tracking anything on this list.

Here's a different approach: Each client connection is managed by a thread, which handles packet encoding/decoding (this type of io should be async), and we use timers to push scheduled...

Currently? Completely absent, as far as I'm aware. However, we could use native threads for now and switch to green threads when they become usable.

@RichardlL I maintain that we should use one thread per connection, as outlined [above](https://github.com/PistonDevelopers/hematite_server/issues/26#issuecomment-76886689). That would make this unnecessary, right?

Is there enough server-specific code to warrant the Common/Server split? The way the project is set up right now, the server lib would be a dependency of the client, which...

@toqueteos whatever mods you can apply to the standalone server should also be applicable to the embedded server used in singleplayer, no?

@indiv0 How so?

@indiv0 no, I'm not ruling out a separate client mod API. (However, given the potential complexity I'm not sure if any modding API should be a project goal.)