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

Convert server txt files to json #405

Merged
merged 2 commits into from
Oct 15, 2020
Merged

Convert server txt files to json #405

merged 2 commits into from
Oct 15, 2020

Conversation

renderorange
Copy link
Contributor

@renderorange renderorange commented Sep 27, 2020

This pull request changes the default server files from txt to json.
To support that change, additionally update the wl, bl, and op
commands to no longer edit their corresponding server files but
rely on passthrough commands to the minecraft server.

Operationally, the only difference the user will see is when running
the commands when the server is not running. Rather than edit
the txt file, msm will return "Server servername is not running."

Fixes issue #404

This commit changes the default server files from txt to json.

The only exception is ops.txt which is still populated with users
from DEFAULT_OPS_LIST on server creation.  Until msm is updated to
correctly populate ops.json on startup, msm relies on minecraft
server's mechanism to convert ops.txt.

Fixes issue #404
This commit updates the wl, bl, and op commands to no longer edit
their corresponding server files.  msm still edits config settings
in files, but relies on minecraft server to manage it's own files,
passing the commands to the running server for changes.

Minecraft server moved to json in version 1.7.2 which made
directly editing txt files no longer work.

This change follows the pattern of the other passthrough commands
that if the server isn't running, returns error_exit informing the
user the server is not running.

Fixes issue #404
@endofcake endofcake merged commit 901f02b into msmhq:master Oct 15, 2020
@endofcake
Copy link
Contributor

I merged this, as it looks reasonable. I'm not sure what's the procedure to release new versions anymore, as I don't have admin rights, and I think the CI integration has been broken for some time.

@renderorange renderorange deleted the convert-server-txt-files-to-json branch October 15, 2020 13:11
@renderorange
Copy link
Contributor Author

renderorange commented Oct 15, 2020

You have to create a new tag then create a new release for that tag. Marcus has a gitbump script that makes incrementing the tag easy, but you could also increment the tag number by hand.

You also have to update the change log with all of the changes since the last version.

@endofcake
Copy link
Contributor

Well, this will need fixing a build too, and I don't have permissions for that. A bit hard to maintain the project when I can't even create a new release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants