Only start WorldSaving in server-mode.
Signed-off-by: Chris Sanders <zidane@outlook.com>
WorldSaving/World unloads now in server-mode.
Signed-off-by: Chris Sanders <zidane@outlook.com>
Throw exception in client-mode when chunks save.

This will show us where the extent of saving is (and harden it further to
server-mode).
Signed-off-by: Chris Sanders <zidane@outlook.com>
Lock down WorldSavingThread to server mode.
Signed-off-by: Chris Sanders <zidane@outlook.com>
Only create world files in server mode
Signed-off-by: Chris Sanders <zidane@outlook.com>
Remove these from being final
Signed-off-by: Chris Sanders <zidane@outlook.com>
Set these final once again
Signed-off-by: Chris Sanders <zidane@outlook.com>
Partial fix for region files - RegionGenerator.java still not done
Change how the client handles the world and player

- Server sends a worldChanged to the Client
- Client constructs new SpoutClientWorld, deserializes datatable
- Server sends AddEntityMessage
- Client adds new entity to its' world, creates a new SpoutClientPlayer if
  the player joining the world is the client player. There is only one
  entity that has the -1 ID and that is the client player
- Override a few methods in SpoutClientWorld, throw
  UnsupportedOperationExceptions to let us see what the client is trying
  to do when it shouldn't.
Signed-off-by: Chris Sanders <zidane@outlook.com>