Skip to main content
warningServer ErrorsAffects: Paper servers

How to Fix Paper Configuration Errors

Paper stops or warns when config/paper-global.yml is newer than the build, has a YAML error or can't be saved. How to read the message and fix the file.

Quick Fix

Back up the config folder, then fix the YAML at the line and column in the error, or start the Paper build that wrote the files.

Error Message

Loading a newer configuration than is supported

How to Fix

1

Start the Paper build that created the files, or back up config/paper-global.yml and config/paper-world-defaults.yml, delete them and let your build write new ones.

2

Fix YAML errors at the line and column in the message, and replace tabs with spaces.

3

Leave the _version line at the top of each file alone.

4

Put changes for one world in paper-world.yml inside that world's folder, and settings for every world in config/paper-world-defaults.yml.

5

Make sure the server can write to the config folder so Paper can save new settings.

6

Restart after editing. /paper reload exists, but a reload that fails stops with Could not reload paper configuration files.

Common Causes

  • The config files were written by a newer Paper build than the one you start, for example after going back to an older jar. Paper compares the _version number in the file with the highest version it supports and logs Loading a newer configuration than is supported.
  • A YAML syntax error in paper-global.yml, paper-world-defaults.yml or a world's paper-world.yml, such as a tab used for indentation or a missing colon.
  • The _version line was removed. Paper warns The global config file didn't have a version set, assuming latest, and then skips the upgrade steps an older file would need.
  • Paper is converting an old paper.yml. It moves the file to config/legacy-backup/paper.yml.old, leaves a paper.yml-README.txt, and stops with Could not convert 'paper.yml' to the new configuration format if that fails.
  • Paper can't write the file, for example because it is read-only. It warns Could not save and keeps the missing settings at their defaults in memory.

Diagnostic Steps

  1. Back up the config folder.
  2. Read the first Paper error in latest.log.
  3. Fix the YAML, or use files that match your Paper build.
  4. Restart the server.

FAQ

Where are Paper configs located?

config/paper-global.yml for server-wide settings, config/paper-world-defaults.yml for defaults that apply to every world, and paper-world.yml inside a world's folder for that world only.

Can I delete a Paper config file?

Yes, after backing it up. Paper writes a new file with default values on the next start, so any changes you made have to be set again.

Why does Paper say the configuration is newer than supported?

The file was written by a newer Paper build. Start that build again, or back up and delete the file so the build you are running can write its own.

Related Errors

Need More Help?