This repository has been archived by the owner on Dec 11, 2021. It is now read-only.
Go back to YAML for worlds configuration #35
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Evan Maddock <maddock.evan@vivaldi.net>
Signed-off-by: Evan Maddock <maddock.evan@vivaldi.net>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After a lot of thought and some user feedback, I feel it would be better to keep the existing YAML structure for the worlds configuration files. Now that server administrators have the ability to modify their group setups using commands, it should be fine to stick with YAML and still have less configuration issues.
Given that this is still in Beta with plenty of warnings, no automatic conversion from Json back to Yaml will be included.