Closed dreadnaut closed 10 months ago
Hmm. The idea here was that errors are only ignored for the first stage of processing (as errors can easily occur when minedmap is running while Minecraft is saving), and in later stages no errors should ever happen as long as you got a complete run at least once (as the old processed data would be preserved in that case).
I did not think of persistent invalid files, but I agree it's better to have the run succeed with holes in such cases than to break altogether. I will work on a fix soon.
I have prepared a fix in #33. Will run a few more tests and likely make a fix release soon.
Thank you!
Hello @neocturne, first of all congratulations on the Rust release! It might actually push me to learn some Rust 😀
I have noticed that the new version is more strict about errors, and if a problematic region means that a tile can't be rendered, the whole process fail — leaving no map at all. The C version would skip the tile, leaving a hole on the map, but the process would complete.
Like the "processing" phase, tile rendering could continue even if a tile is missing, leaving a hole in the map.
https://github.com/neocturne/MinedMap/blob/ceb71f035caa5214e19dda49c63b6ea4b36c200b/src/core/tile_renderer.rs#L327-L330
The problematic regions have size
0
. I don't know I common this is, but it happens sometimes on my server 🤔