Make progress
This commit is contained in:
32
todo.md
32
todo.md
@@ -6,16 +6,16 @@ Basically all admin commands.
|
||||
* ~~setowner~~
|
||||
* ~~dispose~~
|
||||
* ~~reset~~
|
||||
* swap
|
||||
* ~~swap~~
|
||||
* New admin commands that I can't think of right now.
|
||||
|
||||
Also
|
||||
* ~~setbiome~~
|
||||
* random
|
||||
|
||||
Modify home command:
|
||||
~~Modify home command:~~
|
||||
* ~~Make `:` not be required if prior component cannot be parsed to an int~~
|
||||
* Listen for command events that use plotme-style argument, and transform the command
|
||||
* ~~Listen for command events that use plotme-style argument, and transform the command~~
|
||||
|
||||
~~Add permissions to commands (replace or fix `IContextFilter` from command lib
|
||||
to allow inheriting permissions properly).~~
|
||||
@@ -23,32 +23,34 @@ to allow inheriting permissions properly).~~
|
||||
Parcel Options
|
||||
-
|
||||
|
||||
Parcel options apply to any player with `DEFAULT` added status.
|
||||
Parcel options apply to any player with `DEFAULT` added status.
|
||||
They affect what their permissions might be within the parcel.
|
||||
|
||||
Apart from `/p option inputs`, `/p option inventory`, the following might be considered.
|
||||
|
||||
Move existing options to "interact" namespace (`/p o interact`)
|
||||
~~Move existing options to "interact" namespace (`/p o interact`)
|
||||
Add classes for different things you can interact with~~
|
||||
|
||||
Then,
|
||||
* Split `/p option interact inputs` into a list of interactible block types.
|
||||
The list could include container blocks, merging the existing inventory option.
|
||||
* Players cannot launch projectiles in locations where they can't build.
|
||||
~~Then,~~
|
||||
~~* Split `/p option interact inputs` into a list of interactible block types.~~
|
||||
~~The list could include container blocks, merging the existing inventory option.~~
|
||||
* Players cannot launch projectiles in locations where they can't build.~~
|
||||
This could become optional.
|
||||
* Option to control spreading and/or forming of blocks such as grass and ice within the parcel.
|
||||
|
||||
* Option to control spreading and/or forming of blocks such as grass and ice within the parcel.~~
|
||||
|
||||
Block Management
|
||||
-
|
||||
~~Update the parcel corner with owner info when a player flies into the parcel (after migrations).
|
||||
Parcels has a player head in that corner in addition to the sign that PlotMe uses.~~
|
||||
|
||||
Commands that modify parcel blocks must be kept track of to prevent multiple
|
||||
~~Commands that modify parcel blocks must be kept track of to prevent multiple
|
||||
from running simultaneously in the same parcel. `hasBlockVisitors` field must be updated.
|
||||
In general, spamming the commands must be caught at all cost to avoid lots of lag.
|
||||
In general, spamming the commands must be caught at all cost to avoid lots of lag.~~
|
||||
|
||||
Swap - schematic is in place, but proper placement order must be enforced to make sure that attachable
|
||||
~~Swap - schematic is in place, but proper placement order must be enforced to make sure that attachable
|
||||
blocks are placed properly. Alternatively, if a block change method can be found that doesn't
|
||||
cause block updates, that would be preferred subject to having good performance.
|
||||
cause block updates, that would be preferred subject to having good performance.~~
|
||||
|
||||
~~Change `RegionTraversal` to allow traversing different parts of a region in a different order.
|
||||
This could apply to clearing of plots, for example. It would be better if the bottom 64 (floor height)
|
||||
@@ -79,6 +81,6 @@ Implement a container that doesn't require loading all parcel data on startup (C
|
||||
|
||||
~~Update player profiles in the database on join to account for name changes.~~
|
||||
|
||||
Store player status on parcel (allowed, default banned) as a number to allow for future additions to this set of possibilities
|
||||
~~Store player status on parcel (allowed, default banned) as a number to allow for future additions to this set of possibilities~~
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user