Update Regen (research required)

This commit is contained in:
iiegit 2016-11-09 13:19:54 -05:00 committed by GitHub
parent 43bf947f7f
commit f4af1d1260

View file

@ -9,90 +9,65 @@ Decide which LAYER's version of the chunk to load from, and save to.
2) LAYERS: 2) LAYERS:
SEED: SEED:
the unmodified, from-seed version of each chunk the unmodified, from-seed version of each chunk
stored and NEVER CHANGED. stored and NEVER CHANGED.
MODIFIED LAYER: MODIFIED LAYER:
multiple modified versions of the world multiple modified versions of the world
these can be associated with regions these can be associated with regions
WILDERNESS BUILD LAYER (default):
DEFAULT LAYERS:
WILDERNESS BUILD LAYER:
temporary changes made to the wilderness are stored here. temporary changes made to the wilderness are stored here.
these chunks are periodically overwritten from SEED these chunks are periodically overwritten from SEED
this layer is the default layer built into the plugin
OUR LAYERS: "SERVER BUILD" LAYER:
"SERVER BUILD" LAYER
this layer contains Spawn, the dungeon-portal chunks, this layer contains Spawn, the dungeon-portal chunks,
anything that is "part of the server" anything that is "part of the server"
TOWN LAYER: TOWN LAYER:
this is the layer containing the stable, "official" peacetime contents of towns. this is the layer containing the stable, "official" peacetime contents of towns.
permanent changes, made by residents, are saved here. permanent changes, made by residents, are saved here.
OTHER: OTHER:
SOFT CLAIMS LAYERS: SOFT CLAIMS LAYERS:
every soft claim generates its own temporary layer every soft claim generates its own temporary layer
TEMPORARY MOVECRAFT PARKING: TEMPORARY MOVECRAFT PARKING:
want to park your craft without it being regenned to wilderness? want to park your craft without it being regenned to wilderness?
WILDERNESS EVENT REGIONS: WILDERNESS EVENT REGIONS:
used for longer events taking place in the wilderness used for longer events taking place in the wilderness
maybe used for pitched battles? maybe used for pitched battles?
3) LOGIC 3) LOGIC
REGION MANAGER: REGION MANAGER:
region manager .yml declares which regions are working off which layers. region manager .yml declares which regions are working off which layers.
also declares any automated chunk regeneration (and which layer to regenerate from) also declares any automated chunk regeneration (and which layer to regenerate from)
COMMAND MANAGER: COMMAND MANAGER:
create commands for complex actions (such as toggling war) that have multiple steps. create commands for complex actions (such as toggling war) that have multiple steps.
possible steps: create or delete layers, or, modify settings in the region manager possible steps: create or delete layers, or, modify settings in the region manager
COMMAND SCHEDULER: COMMAND SCHEDULER:
put a command on a clock put a command on a clock
4) HOW WE WOULD USE THIS PLUGIN: 4) HOW WE WOULD USE THIS PLUGIN:
WAR: WAR:
During war, affected regions are placed in SANDBOX MODE. During war, affected regions are placed in SANDBOX MODE.
We create a temporary layer; war chunks are saved to, and loaded from, this temporary layer. We create a temporary layer; war chunks are saved to, and loaded from, this temporary layer.
When war ends, the temporary layer is discarded. Return to using the TOWN LAYER. When war ends, the temporary layer is discarded. Return to using the TOWN LAYER.
WILDERNESS: WILDERNESS:
Changes made to the widerness are stored in the WILDERNESS BUILD LAYER. Changes made to the widerness are stored in the WILDERNESS BUILD LAYER.
When a chunk has not been modified for a while, it is reset from SEED. When a chunk has not been modified for a while, it is reset from SEED.