New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: [Multiverse-Core] The world 'Spawn' could NOT be loaded because it contains errors and is probably corrupt! #2816
Comments
Full logs will help. There is probably more to that error than you have copied. |
This is as much as I can scroll to after a restart is is this enough? |
Here are some steps to give us full logs Your logs can be found in After you open that file you will see lots of text, copy and paste that with CTRL+C and CTRL+V it in https://mclo.gs/ , just click save and send the link to the page it sends you to. |
I am having this issue at the moment as well. https://paste.gg/ed436cd3884f47cda53344c80c94e3a9 /logs/latest.log
|
I suspect something outside of MV's control has happened here and there may be some credibility to the world errors. The stacktrace originates from Bukkit and the environment exception (and warning) isn't something reported by MV. As this seems to be world data related (and not region data), you may be able to delete certain dat files to get the world to load (e.g., Either way, I highly doubt this is a Multiverse issue, unless someone else can prove otherwise. Multiverse doesn't really have much involvement in the actual loading process of a world, like parsing the environment. Loading a world through Bukkit world management is a fairly hands-off process and even feeding it bad data from our end (e.g., wrong environment) just results in it loading the options from the level data and not from our parameters. |
I'm encountering this bug as well, its extremely frustrating that MV refuses to load a world even though its entirely compatible. I'm trying to load a world called https://paste.gg/p/anonymous/610a6a71301f4d86a9e502ae3aaa238c I've used the region fixer, loaded it on singleplayer on the same version, but to no luck. Wtf is happening? Tested on multiverse versions 4.3.2 and 4.3.9 |
Hello! I have the same issue! With a 1.20-compatible world and Multiverse Plugins version 4.3.12 (I used "Minecraft Region Fixer" as mentioned in the error message below. But the issue persists!) Thank you! |
Paste your Logs into https://mclo.gs/ then paste the link here. |
/mv version -p
outputVersion info dumped here: Error posting to service
Server logs
Error in logs - [02:32:29] [Server thread/ERROR]: [Multiverse-Core] The world 'amongus' could NOT be loaded because it contains errors and is probably corrupt! [02:32:29] [Server thread/ERROR]: [Multiverse-Core] Try using Minecraft Region Fixer to repair your world! 'amongus' [02:32:29] [Server thread/ERROR]: [Multiverse-Core] https://github.com/Fenixin/Minecraft-Region-Fixer [02:32:29] [Server thread/ERROR]: [Multiverse-Core] Failed to Create/Load the world 'amongus'
Server Version
Bug Description
I just got the plugin and did /mv hub normal create -t flat 3 times and all three times it said failed
I can delete the worlds
they are unloaded
and i dont know what to do
Steps to reproduce
idk
/mv delete
Agreements
The text was updated successfully, but these errors were encountered: