-
Notifications
You must be signed in to change notification settings - Fork 2
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
Comments
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). |
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 : I get the world back ;) Maybe how instantreset and multiverse handle the normal/end/nether worlds type ? |
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. |
Oh I see. Can't wait for your update then ;-) Thanks |
Hi, |
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
The text was updated successfully, but these errors were encountered: