Skip to content
BlogStart for free

Deployments

Inspect and edit server files

Open Files in the deployment dashboard to browse permitted runtime paths and edit supported configuration files during a test session.

Project files Deployment files
Source and resources used to create an artifact. Files present in a deployment’s server environment.
Edited before a build. Often edited after startup for runtime configuration.
Included in the next artifact when applicable. Do not automatically update project source or a downloaded artifact.
Persist with the project. Belong to a temporary session.

If a server-side configuration change should become the default for future builds, apply the equivalent change in the project and rebuild. A live-server edit stays in that test session.

  1. Open the deployment and select Files.
  2. Wait for the file tree to load.
  3. Expand an allowed directory or search for a file name.
  4. Select the file and wait for its content.
  5. Check the path before editing.

Relevant paths can include config, plugins, world, and selected root configuration/identity files such as server.properties, whitelist, operator, and ban lists. The tree does not expose unrestricted host-machine access.

Use Find in file or Ctrl + F in the file editor to locate a setting. File-tree search and content search serve different purposes.

  1. Confirm owner/editor access and the session’s running state.
  2. Open the intended configuration file.
  3. Copy its original value or download a copy if you need to retain it.
  4. Change the relevant setting while preserving the file’s syntax.
  5. Save and wait for confirmation.
  6. Reload through a documented feature command or restart when the setting requires it.
  7. Verify the behavior and check the console for errors.

You can edit eligible files up to 512 KiB. Binary files are read-only, and path/type restrictions apply. A visible file is not necessarily editable.

For YAML, preserve indentation. For JSON, preserve valid braces, quotes, and commas. For properties files, preserve the expected key/value syntax. If uncertain, ask Buildryn to explain the setting before changing it.

Use the dashboard’s player and whitelist actions for normal operator/ban/whitelist changes. Editing identity JSON manually can make it harder to ensure the server’s live state and the stored file agree.

Use the file editor for settings without a dedicated dashboard action, or to inspect generated configuration.

Open the desired file and use Download active file when available. Check the downloaded name and content. The download contains the selected file. To keep other runtime files, download them before the session ends.

Before the session ends, retain configuration changes and evidence that you need. Temporary-session cleanup means you should not rely on later access to every runtime file.

For a plugin message setting:

  1. Locate the plugin’s configuration under its runtime directory.
  2. Change one message and save.
  3. Use the plugin’s supported reload command or restart.
  4. Trigger the feature and confirm the new message.
  5. If the change is desirable, update the project’s default configuration and rebuild.

Check the file type, size, permitted path, your role, and whether the server is still active. Read the displayed error before retrying. If a restart or configuration reload fails, inspect console output and restore the original valid content when appropriate.

Not an official Minecraft product. Not approved by or associated with Mojang or Microsoft.