Paper ParsingException "Unknown error occurred while loading"
A Paper ParsingException with Unknown error occurred while loading means one of Paper's own YAML files could not be read at all, and Paper stops instead of guessing. This is how it looked on a Paper 26.3 server:
Paper 26.3, in the console
[Server thread/ERROR]: Encountered an unexpected exception
org.spongepowered.configurate.loader.ParsingException: []: Unknown error occurred while loading
at org.spongepowered.configurate.loader.AbstractConfigurationLoader.load(AbstractConfigurationLoader.java:171) ~[configurate-core-4.2.0.jar:?]
...
at io.papermc.paper.configuration.Configurations.initializeWorldDefaultsConfiguration(Configurations.java:168) ~[paper-26.3.jar:26.3-194-3988767]
at net.minecraft.server.dedicated.DedicatedServer.initServer(DedicatedServer.java:239) ~[paper-26.3.jar:26.3-194-3988767]
...
Caused by: mapping values are not allowed here
in 'reader', line 277, column 31:
refresh-max: 2d refresh-min: 12h
^The first line says little. [] is the path inside the file where loading failed, and an empty path means the file as a whole. The useful parts are further down: the method name tells you which file, and the Caused by: line tells you what is wrong in it.
| Method in the stack | File it was loading |
|---|---|
initializeWorldDefaultsConfiguration | config/paper-world-defaults.yml, the default settings for every world |
initializeGlobalConfiguration | config/paper-global.yml, the settings for the server as a whole |
Both logs behind this guide named initializeWorldDefaultsConfiguration, so the broken file was paper-world-defaults.yml.
Why a Paper config stops the server and a plugin config does not
When a plugin's config.yml has the same kind of typing error, Paper still starts and only that plugin fails, as described in plugins that will not load. Paper's own files are read in DedicatedServer.initServer, while the server is still starting up. If that fails there is no fallback, so no world loads and nobody can join. For other reasons a start can fail, see Minecraft server not starting.
"mapping values are not allowed here" in paper-world-defaults.yml
mapping values are not allowed here in paper-world-defaults.yml means YAML found a colon followed by a space in a place where no new setting can start. Paper reads YAML with SnakeYAML, and these messages come from it.
In the log above, line 277 of the file reads refresh-max: 2d refresh-min: 12h. Two settings ended up on one line. YAML reads 2d refresh-min as the value of refresh-max, then meets the colon after refresh-min and stops, because a value cannot be followed by another key on the same line.
| Part of the message | What it tells you |
|---|---|
in 'reader' | SnakeYAML's name for the text it was reading. It does not name the file; the stack above does. |
line 277 | The line in the file, counted from 1 at the top. |
column 31 | The character on that line, counted from 1 and including the spaces at the start of the line. |
The text and the ^ under it | A copy of that line with a marker under the spot where reading stopped. Here that is the colon after refresh-min. |
The copied line in the console may not show the spaces at the start, so find the spot through the line number and the file itself, not the copy. When we fed the same line with two spaces in front to SnakeYAML ourselves, it reported column 30, on that same colon. The file on that server had one space more in front of it.
The fix is to put each setting on its own line, at the same depth as its neighbours. Both settings sit under lootables. Paper's defaults are refresh-min: 12h and refresh-max: 2d, each written as a number with a single unit: d, h, m or s.
The same message appears when a value itself contains a colon and a space, such as key: hello: world, and when a line is indented one space deeper than the setting above it. A value with a colon in it is fine once you put it in double quotes.
"could not find expected ':'" and other YAML errors in a Paper config
could not find expected ':' means a line between settings has text but no colon, so YAML cannot tell which part is the name and which is the value. It comes in two halves: while scanning a simple key with the line where that text starts, then could not find expected ':' with the line where SnakeYAML gave up, which is often the next one. The mistake is on the first of the two lines.
These are the SnakeYAML messages you can meet in a Paper settings file, each tried on a small test file of our own. All of them come with a line and column in the same format.
| Message after Caused by | What is wrong on that line | Fix |
|---|---|---|
mapping values are not allowed here | Two settings on one line, a value with : in it, or a line indented deeper than its neighbours | One setting per line, quotes around the value, or the same indent as the line above |
while scanning a simple key ... could not find expected ':' | A setting name without its colon, or a stray word on its own line | Add the colon and a space, or delete the stray text |
found character '\t(TAB)' that cannot start any token | A tab at the start of the line | Replace the tab with spaces |
while scanning a quoted scalar ... found unexpected end of stream | A value opened with a quote that is never closed | Add the closing quote on the same line |
Indentation is what tells YAML which section a setting belongs to. In Paper's files each level is two spaces deeper than the one above. A block copied from a web page or a chat can bring tabs or a different indent with it, so check the lines you pasted last.
Paper config NumberFormatException: For input string "default"
NumberFormatException: For input string: "default" in a Paper config means the file is valid YAML, but a setting holds the word default where this Paper version only accepts a number. This time the message is a SerializationException, and it names the setting as a path in square brackets. On a Paper 1.20.1 server it looked like this:
Paper 1.20.1, in the console
at io.papermc.paper.configuration.Configurations.initializeWorldDefaultsConfiguration(Configurations.java:154)
...
Suppressed: org.spongepowered.configurate.serialize.SerializationException: [entities, behavior, zombie-villager-infection-chance] of type java.lang.Double: java.lang.NumberFormatException: For input string: "default"
...
Suppressed: org.spongepowered.configurate.serialize.SerializationException: [misc, max-leash-distance] of type java.lang.Float: java.lang.NumberFormatException: For input string: "default"Read the path in brackets from left to right: [entities, behavior, zombie-villager-infection-chance] is the setting zombie-villager-infection-chance under behavior under entities. of type java.lang.Double and java.lang.Float say Paper wanted a number there.
In current Paper, default is the normal value for both settings. The Paper documentation lists default as the default of each, and for the infection chance it means the game's own behaviour based on difficulty. Older Paper versions did not know that word for these settings. In Paper's source code for 1.20.4 and 1.20.6, the infection chance already accepts default, but max-leash-distance is still a plain number with 10 as its default. It takes default in the code for 1.21.1. The 1.20.1 server above refused default for both.
So a file holding default in those places was written by a newer Paper, or copied from a server that runs one. The cleanest fix is to let this Paper version write its own file, as shown in the next section, and copy only your own changes back. Typing a number by hand also works: for the infection chance, 0.0 means villagers always die when a zombie kills them and 100.0 means they always turn into zombie villagers.
How to fix a broken Paper config file on Lodehost
A broken Paper config file is fixed in one of two ways: correct the line the error names, or rename the file so Paper writes a new one on the next start. Paper checks whether paper-global.yml and paper-world-defaults.yml exist when it starts, and when one is missing it creates it with the default settings. On Lodehost:
Note the file, line and column
Open the Console tab and find the
Caused by:line, or theSerializationExceptionwith its path in brackets. Use the method name in the stack to tell which file it is. The crash report guide shows where these lines sit in a long log.Stop the server and make a backup
Leave the server stopped while you work on the file, and make a backup on the Backups tab first, so the current state can be put back with Restore.
Fix the line on the Files tab
Open the
configfolder on the Files tab and open the file to edit it. Go to the line number from the error, compare it with the lines around it and fix it with the table above: one setting per line, spaces instead of tabs, a colon after every name. For adefaultthat your version refuses, put a number in its place.Start and read the console again
SnakeYAML stops at the first error it meets, so a second mistake further down only shows up on the next start. Repeat until the server gets past loading its config.
Or rename the file and let Paper write a new one
If the file is beyond saving, rename it, for example to
paper-world-defaults.yml.broken, with the server stopped. On the next start Paper creates a freshpaper-world-defaults.ymlwith the defaults of the version you run.Copy your own settings back
Open the old file next to the new one and copy over only the values you had changed, one at a time and at the same depth as in the new file. Start the server after each batch so an error points at the last thing you copied.
A fresh file resets every setting in it
The new file holds Paper's defaults, so changes you made in that file, for performance or anti-xray for example, are gone until you copy them back. Changes you made in a world's own paper-world.yml stay, because Paper keeps per-world overrides in separate files. Do not copy the whole old file back in one go: if it came from a newer Paper, it brings the same error with it. For the settings people change most for performance, see Paper config settings for lag.
Written and checked by the Lodehost team, last reviewed on 16 November 2026.






