[Bug]: Failed to autoload world survival_the_end: Failure{reason=WORLD_FOLDER_INVALID}

[james090500]

/mv dumps output

https://pastes.dev/vBm2tAhyL5

Server logs

https://mclo.gs/zN6VHE7

Server Version

This server is running Paper version 26.1.2-52-main@174eab0 (2026-04-29T08:10:12Z) (Implementing API version 26.1.2.build.52-beta)
You are 1 version(s) behind
Download the new version at: https://papermc.io/downloads/paper
Previous version: 1.21.11-127-bd74bf6 (MC: 1.21.11)

Bug Description

Our end folder doesn't auto load. It complains of an error

[02:11:44] [Server thread/ERROR]: [Multiverse-Core] Failed to autoload world survival_the_end: Failure{reason=WORLD_FOLDER_INVALID}

However when we use /mv load survival_the_end --skip-folder-check the world loads fine

Steps to reproduce

1. Set allow-end to false in bukkit.yml
2. Run /mv create world_the_end the_end
3. Restart the server

Agreements

• I have searched for and ensured there isn't already an open or resolved issue(s) regarding this.
• I was able to reproduce my issue on a freshly setup and up-to-date server with the latest version of Multiverse plugins with no other plugins and with no kinds of other server or client mods.

[james090500]

The level-name is survival.

The old names were survival, survival_nether and survival_the_end. After the upgrade to 26.1.2, the world migrated successfully into correct dimension folders. survival and survival_nether load fine, but survival_the_end doesn't load unless we do /mv load survival_the_end --skip-folder-check

[benwoo1110]

Folder checking will improve to account for the new namespace dimension structure of 26.1 in v5.7. As a workaround for now, you should let the server load the end world during startup by setting allow-end to true in bukkit.yml config file. If you already want to end the world to load, I don't see a reason to disable allow-end in the first place. To disable usage of end portals, you can do that with the Multiverse-NetherPortals plugin.