Skip to main content
Version: 1.0

Updating & downgrading

Updating​

  1. Read the changelog for anything marked breaking.
  2. Back up plugins/ProjectOne/ and your world if the release changes stored data.
  3. Stop the server.
  4. Replace the jar. Leave config.yml in place — new keys are added with their defaults on start.
  5. Start the server and check the console for migration messages.
Config keys are added, never removed

New keys appear with defaults; keys you removed are re-added. Renamed or removed keys are listed in the changelog, so read it rather than diffing the file.

Downgrading​

Downgrading is only safe when the newer version did not migrate stored data. If it did, restore your backup instead — an older build will not understand the newer schema and may refuse to start or, worse, misread it.

State that explicitly per release. "Can I go back?" is a question people ask at the worst possible moment.

Reading docs for the version you run​

The version dropdown in the navbar switches these docs between releases. If you are on an older build, switch to it — the current page may document behaviour your jar does not have.