ChromaGaming/TBMC-Blueprint
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Update Per-World.md

Browse source
This commit is contained in:
iiegit 2016-11-09 16:16:30 -05:00 committed by GitHub
parent 8d1ca7a83c
commit ad430cde0f
1 changed files with 20 additions and 21 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
Plugins/World/Per-World.md
View file

@ -2,14 +2,12 @@ the basic functionality is done
it can store and retrieve inventories, playerdata, and player locations it can store and retrieve inventories, playerdata, and player locations
THINGS I WILL ADD: ####THINGS I WILL ADD:
================== --
"object-based" configuration:
"OBJECT-BASED" CONFIGURATION
LOCATIONS: LOCATIONS:
world-specific, or world-specific, or
categorical (ie "spawn" - every world has one) categorical (ie "spawn" - every world has one)
@ -21,6 +19,7 @@ THINGS I WILL ADD:
including "none" - ie, cancel the teleport if the target world has no coords set including "none" - ie, cancel the teleport if the target world has no coords set
for that category for that category
--
EXCURSIONS: EXCURSIONS:
an excursion is an ongoing "visit" to a world. an excursion is an ongoing "visit" to a world.
each player can have multiple stored excursions per world each player can have multiple stored excursions per world
@ -32,6 +31,7 @@ THINGS I WILL ADD:
excursion tracking: some excursions might terminate if the player dies, respawning them elsewhere, excursion tracking: some excursions might terminate if the player dies, respawning them elsewhere,
or, perform some other action in response to an event occuring within the excursion or, perform some other action in response to an event occuring within the excursion
--
STORYLINES: STORYLINES:
a player can have multiple storylines, each one a separate path through the server, almost like multiple a player can have multiple storylines, each one a separate path through the server, almost like multiple
accounts per player. There could be, for example, a utility admin storyline, a path completely separate accounts per player. There could be, for example, a utility admin storyline, a path completely separate
@ -41,8 +41,7 @@ THINGS I WILL ADD:
those worlds when entered might default you to a different storyline, or deny your entry entirely those worlds when entered might default you to a different storyline, or deny your entry entirely
until you switch to an allowed storyline for that world. until you switch to an allowed storyline for that world.
--
PLAYER TRACKING: PLAYER TRACKING:
certain player data points must be tracked and stored, such as last known location, last death, number of deaths, etc. certain player data points must be tracked and stored, such as last known location, last death, number of deaths, etc.
These are all stored in the following way: These are all stored in the following way: