Multiverse suddenly broke
Awesomeguys900 opened this issue ยท 8 comments
Information
-
Full output of
/mv version -p
: https://paste.gg/p/anonymous/58733f42550d4091a5cfc55a2642e793 -
Server log: https://gist.github.com/Awesomeguys900/35951276328669c4138a820401b49f18
Help request
Problem
My Multiverse randomly crashed and doesnt load, when I do a command it says interval server errorWhat I have tried
Updating versionsScreenshots
PaperMC/Paper#5331 This is an issue with paper and having faulty logic for world name validation.
Update paper at: https://papermc.io/downloads
I will leave this issue open for awhile so ppl know to update papermc. This is NOT a bug with mutliverse.
Problem persist on paper-545 of march 10...
- Ensure you actually, updated, sometime server host does weird things
- Your world names must be English characters and cannot have space or other special characters
If you have checked both and the issue still persists, open an with paper.
Unfortunately, I am sure it's updated. The server is running on a private server at home. No hosting involved.
Problem I am facing; the first world had all playerdata and has spaces in the world-name. If I change it - and edit config files accordingly - players lose all stats and so on...
Why wasn't this an issue before all this...?
@Dnaleor77 In 1.15, there was a change that disallow loading of worlds with spaces, but for some reason they didn't do this check for the default world and now its finally implemented. So if your default level-name
world had space, it will be an issue. You will have to adjust accordingly and contact paper if the world continues to not load properly.
Also note that the playerdata
lose is probably the expected result of a level-name
, nothing mv can control about that.
It works now, thank you. It was the default world with the spaces in them like @benwoo1110 suggested. Renaming the world directory and names in the config-files did the job.
'
@benwoo1110 thank you for clarifying! the playerdata loss was simply because I renamed everything, except the world-name in the server.properties, which caused the server to actually generate a new world with spaces in the name