-
Notifications
You must be signed in to change notification settings - Fork 3
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
haze test
can overwrite an already existing world by default
#1
Comments
I sort of had the suspicion this could happen, but never managed to get it to actually happen. I've thought about this for a little bit and I think This is definitely a design oversight I made, so thank you for bringing it up to my attention! |
haze test
can overwrite an already existing world
Overwriting worlds is useful. With that feature you can use haze for reloading the game to a specific state. This way you can be very destructive when you work on your map. It helps when you're testing things that break blocks (for example custom explosive weapon). |
Yeah, that's actually a great use case that I've never thought about until now! Making overwriting disabled by default for |
haze test
can overwrite an already existing worldhaze test
can overwrite an already existing world by default
Fixed with #2 |
I don't have exact reproduction steps. I was basically trying to do everything to break my world using haze and I think that the problem may depend Minecraft saving the game at the same time as haze copies files.
Haze is not safe for careless users. If you
haze test
while having the world open, you can easily break your world. In my case, the world could still be opened but the chunks were broken. The best solution for that problem would probably be testing whether the world is being used and preventing haze from doing any kind of operation on the world files.The text was updated successfully, but these errors were encountered: