02-09-2016, 05:26 PM
(This post was last modified: 04-25-2016, 03:24 AM by LogicParrot.)
April 20, 2016 edit:
As of April 20 (#3150), this error has been removed from Cuberite. If you downloaded Cuberite prior to April 20 and are getting that error, then updating Cuberite is the easiest solution.
April 14, 2016 edit:
If you downloaded Cuberite between the 13th and the 14th of April, please re-download Cuberite. Those builds create this error as a a false alarm. This has been fixed. See #3141 for more info.
You are probably here because your server is refusing to start and is directing you to this thread. I will explain this error in detail below.
What is this error?
Starting from February 9, 2016, the server became strict about world linkage configuration. If your nether and/or end portals lead to invalid worlds, the server will now refuse to start. Previously, the server would let you get away with this and would create the invalid world on the fly. See #2810 for technical info.
What is an invalid world?
An invalid world is a world name not mentioned in settings.ini, but mentioned in a world.ini. For instance, if you configured your overworld (typically called "world") nether portal to lead to world_nether, but your settings.ini has no world called world_nether, then world_nether is an invalid world, and the server will refuse to start until you fix your overworld configuration.
But I didn't touch the default configuration!
Even default configurations created by servers downloaded prior to February 9, 2016 can have invalid worlds.
What do OverWorldName, NetherWorldName, EndWorldName do?
They determine where each world's portals lead to. For instance, if myAwesomeWorld/world.ini has this setting: NetherWorldName=world2, then stepping through a nether portal in myAwesomeWorld leads to world2. If you don't have a world called world2 in settings.ini, the server will refuse to start.
What do I need to do?
If you don't care about preserving the world that the server is complaining about, just delete its folder and restart the server. If you do care about keeping that world, read on.
How do I fix this without removing the world?
In one of your world.ini files there is an invalid world in one of the following configuration lines: OverWorldName, NetherWorldName, EndWorldName. You need to make sure these settings are either set to existing worlds, or set to blank. A blank line means that particular world's nether/end portals will be disabled.
Guide me through this
Follow the steps below:
Why can't the server automatically fix this?
The server already autofixes this properly for most people who have default configs, but unfortunately the autofix doesn't cover everyone. The autofix does not cover:
Still need help? Feel free to post any questions below.
As of April 20 (#3150), this error has been removed from Cuberite. If you downloaded Cuberite prior to April 20 and are getting that error, then updating Cuberite is the easiest solution.
April 14, 2016 edit:
If you downloaded Cuberite between the 13th and the 14th of April, please re-download Cuberite. Those builds create this error as a a false alarm. This has been fixed. See #3141 for more info.
You are probably here because your server is refusing to start and is directing you to this thread. I will explain this error in detail below.
What is this error?
Starting from February 9, 2016, the server became strict about world linkage configuration. If your nether and/or end portals lead to invalid worlds, the server will now refuse to start. Previously, the server would let you get away with this and would create the invalid world on the fly. See #2810 for technical info.
What is an invalid world?
An invalid world is a world name not mentioned in settings.ini, but mentioned in a world.ini. For instance, if you configured your overworld (typically called "world") nether portal to lead to world_nether, but your settings.ini has no world called world_nether, then world_nether is an invalid world, and the server will refuse to start until you fix your overworld configuration.
But I didn't touch the default configuration!
Even default configurations created by servers downloaded prior to February 9, 2016 can have invalid worlds.
What do OverWorldName, NetherWorldName, EndWorldName do?
They determine where each world's portals lead to. For instance, if myAwesomeWorld/world.ini has this setting: NetherWorldName=world2, then stepping through a nether portal in myAwesomeWorld leads to world2. If you don't have a world called world2 in settings.ini, the server will refuse to start.
What do I need to do?
If you don't care about preserving the world that the server is complaining about, just delete its folder and restart the server. If you do care about keeping that world, read on.
How do I fix this without removing the world?
In one of your world.ini files there is an invalid world in one of the following configuration lines: OverWorldName, NetherWorldName, EndWorldName. You need to make sure these settings are either set to existing worlds, or set to blank. A blank line means that particular world's nether/end portals will be disabled.
Guide me through this
Follow the steps below:
- Open settings.ini, make sure the worlds listed there are the worlds you want enabled.
- Open <Problematic World's name>/world.ini. Make sure this is the world that the server is complaining about.
- If your problematic world is a nether or an end world, there should be a configuration line called OverWorldName. Edit that value, and put either a valid world or a blank line instead. The value must be a world listed in settings.ini.
- If it's an overworld, there should be a configuration line called NetherWorldName, and a configuration line called EndWorldName. As before, set both of them to either existing worlds, or to blank.
- Note: Some worlds created prior to February 9, 2016 are called x_nether or x_end but are in fact overworlds! If you have such a world, consider removing it or renaming it.
Why can't the server automatically fix this?
The server already autofixes this properly for most people who have default configs, but unfortunately the autofix doesn't cover everyone. The autofix does not cover:
- People with non-default worlds or non-default world linkages.
- People with default configs who downloaded a server between Jan 12, 2016 and Feb 8, 2016, and had a default settings.ini created prior to Jan 12, 2016. Note that this means that completely fresh installs during that time got the proper autofix.
- People with default configs who downloaded a server between Jan 12, 2016 and Feb 8, 2016 and regenerated a world_nether or world_end by removing its folder.
- Some edge cases which I have not considered are probably not covered as well.
Still need help? Feel free to post any questions below.
