What I did / Steps to reproduce

I upgraded an existing BlueMap installation from 3.5 to 3.6 by replacing the BlueMap jar and deleting bluemap/web/index.html. I upgraded PaperMC from 1.19.2-271 to 1.19.2-287 at the same time in case that's relevant.

Expected result

I expected the map to stay effectively unchanged.

Actual result

I get glitchy textures in the area of high LoD:

The map is available here.

Context

BlueMap Version: BlueMap-3.6-spigot
BlueMapOfflinePlayerMarkers version: 2.0.1
Platform: paper-1.19.2-287 on Linux

[2022-11-25 06:55:49] [Server thread/INFO]: Loading BlueMap v3.6
[2022-11-25 06:55:49] [Server thread/INFO]: Loading BlueMapOfflinePlayerMarkers v2.0.1
[2022-11-25 06:55:53] [Server thread/INFO]: Enabling BlueMap v3.6
[2022-11-25 06:55:54] [Server thread/INFO]: Enabling BlueMapOfflinePlayerMarkers v2.0.1
[2022-11-25 06:55:55] [Craft Scheduler Thread - 3 - BlueMap/INFO]: Loading...
[2022-11-25 06:55:56] [Craft Scheduler Thread - 3 - BlueMap/INFO]: Loading resources...
[2022-11-25 06:55:57] [Craft Scheduler Thread - 3 - BlueMap/INFO]: Loading textures...
[2022-11-25 06:56:00] [Craft Scheduler Thread - 3 - BlueMap/INFO]: Baking resources...
[2022-11-25 06:56:00] [Craft Scheduler Thread - 3 - BlueMap/INFO]: Resources loaded.
[2022-11-25 06:56:00] [Craft Scheduler Thread - 3 - BlueMap/INFO]: Initializing Storage: 'file' (Type: FILE)
[2022-11-25 06:56:01] [Craft Scheduler Thread - 3 - BlueMap/INFO]: API Ready! BlueMap Offline Player Markers plugin enabled!
[2022-11-25 06:56:01] [Craft Scheduler Thread - 3 - BlueMap/INFO]: Loaded!
[2022-11-25 06:56:01] [Craft Scheduler Thread - 3 - BlueMapOfflinePlayerMarkers/INFO]: Marker for [...] added

The way you fix this will be purging the entire map and letting it regenerate. The best way would be to:

• freeze the maps
• purge the maps
• reload bluemap
• unfreeze the maps

This way you have a clean texture-gallery again ...

The reason this happened is likely not the update from 3.5. to 3.6 but some failed texture-gallery loading/saving which resulted in lost texture-data. This probably just somehow occurred at the same time you updated.

TODO for this issue:

• I will investigate why this can occur sometimes and try to handle it better so the textures won't be lost so easily.
• Also the purging needs to be improved so the texture-gallery is properly reset as well when purging a map (even without the 4-step way i described above).

I can confirm having the same issue on the new fabric release as well.

• freeze the maps
• purge the maps
• reload bluemap
• unfreeze the maps

Thanks, that helped. For anyone else doing this, you'll need to wait for the purge to finish before reloading.

Related commit: 0fc1424

Related commit: 1368f86

This should be much better handled now with those two commits, closing this :)