Geo + Player Data #4
Description
Should have a system of defining Data API data that is stored external to the game.
Entity/PlayerData with various 'Scopes'
Geographical Data (region bounded?) with various 'Scopes'
Player Data differs to entity data in that it is retrievable whilst the player is offline for a given scope.
Possible Scopes/Contexts/Contextual?
Network, Server, Save, Universe, World, Region, Chunk
Network would be shared between servers.
Server Scope is shared between levels.
Save Scope is per level.
Universe is a meta-grouping of several dimensions.
World is a Scope based on a specific dimension instance
Region (Match the native Minecraft Region)
Chunk (Would save as regions for performance, but can be fetched by Chunk)
Player/Entity data can be scoped by Network, Server, Save, Universe, World. Region or Chunk is supported, but should be implemented manually.
Geo data can be scoped at any level down to blocks. Care should be taken about performance and 2 abstract implementations should exist, sparse and dense.