Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Save waystone locations #49

Open
AtriusX opened this issue Jan 1, 2022 · 0 comments
Open

Save waystone locations #49

AtriusX opened this issue Jan 1, 2022 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@AtriusX
Copy link
Owner

AtriusX commented Jan 1, 2022

Currently, the plugin tries to be as hands-off as possible with waystone locations as possible. However in the future it will likely be important that we have access to all waystones currently active on a server all at once (such as in the case of #47).

The implementation of this could mirror the same simple JSON files we have already, however it may also become necessary at some point to consider the possibility of database support. In order for a smooth transition to occur, it might make the most sense for this feature to be included in a patch update (1.1.1 perhaps) so that servers will have a bit of time to adjust and track existing waystones.

Attention will also need to be given to determine the factors for when a waystone should be created or destroyed. It should also be discussed if we should migrate away from the existing warpnames.json file used for name storage. If we implement location storage for all waystones, then it might make more sense to simply merge the names file with the new one to avoid excess file creation.

@AtriusX AtriusX added the enhancement New feature or request label Jan 1, 2022
@AtriusX AtriusX self-assigned this Jan 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant