Skip to content
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

World is now void #15

Open
Lich4r opened this issue May 28, 2016 · 5 comments
Open

World is now void #15

Lich4r opened this issue May 28, 2016 · 5 comments

Comments

@Lich4r
Copy link

Lich4r commented May 28, 2016

HI,

I reseted my world and now it's full of void, there is nothing in it. I used world borders and the fill command to generate all chunks before saving the world in templates/worldname. Whatever I do (tp in the world or reset it) it's full of void.

Did I just loose a world ? What happened ?

Thanks

@cybertiger
Copy link
Owner

Working on it, likely a bug, thanks for reporting.

The world is still there, InstantReset never writes to it.

Will probably be Wednesday or later before I can get to it (real life commitments).

@Lich4r
Copy link
Author

Lich4r commented May 30, 2016

As I said on spigot, it's not the reset that makes this. Even if I don't reset the world it's void as soon as the server was started with instantreset set up for this world.

However this may be linked to multiverse cause once it's void I i do :
mv remove worldname
mv import worldname normal

I get the world back ;)

Maybe how instantreset and multiverse handle the normal/end/nether worlds type ?

@cybertiger
Copy link
Owner

It's actually a bukkit thing.

Different world types store the region file in different locations.

So if you try to load a world with the wrong world type, you get a newly generated world with the same seed.

InstantReset always uses a void generator though (since the idea is your world is already generated, and you don't want your server generating new chunks since it causes lag) so you get void.

@Lich4r
Copy link
Author

Lich4r commented May 30, 2016

Oh I see.

Can't wait for your update then ;-)

Thanks

@ArVdC
Copy link

ArVdC commented Jun 27, 2016

Hi,
I've reported a very similar issue for Instances : cybertiger/Bukkit-Instances#75
I just tried the @FromBabylon 's trick :
mv remove worldname
mv import worldname normal
but nothing works, my world remains empty.
The chunks in the original world are already loaded and I only work with normal worlds , so I have no more ideas to solve this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants