You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.The text was updated successfully, but these errors were encountered: