Update Per-World.md
This commit is contained in:
parent
b818bd53f4
commit
15a6e85a6b
1 changed files with 63 additions and 63 deletions
|
@ -2,10 +2,10 @@ 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:
|
locations, excursions, storylines, player tracking
|
||||||
|
|
||||||
LOCATIONS:
|
LOCATIONS
|
||||||
|
|
||||||
world-specific, or
|
world-specific, or
|
||||||
categorical (ie "spawn" - every world has one)
|
categorical (ie "spawn" - every world has one)
|
||||||
|
@ -18,8 +18,8 @@ LOCATIONS:
|
||||||
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
|
||||||
every excursion has its own inventory and/or data
|
every excursion has its own inventory and/or data
|
||||||
|
@ -30,8 +30,8 @@ every excursion has its own inventory and/or data
|
||||||
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
|
||||||
from the admin's journey as a player
|
from the admin's journey as a player
|
||||||
|
@ -40,8 +40,8 @@ from the admin's journey as a player
|
||||||
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:
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue