Server structure

This is not a final state, but a merely a proposal.

widely accessed data

• chunks
• socket ids to send packets to a client from any process
• player list

processes

• one process enough for several points?

per client:

• receive packets
• send packets (needed? is gen_tcp:send/2 an atomic operation?)

per map area:

• entity simulation -> players, animals, mobs, pickups
  • split up because of different sight ranges?
• send chunks to clients when necessary