Repository navigation
Map Revealer 1.2.1 fixes server stalls and unclear blank-map behavior when rendering large, high-scale walls.
- Removes synchronous generated-chunk checks that blocked Paper's server thread during terrain lookups. Terrain lookups use asynchronous loading, while snapshots obey the per-tick capture budget.
- Publishes terrain progressively and renders maps nearest the selected frame first. Wall refreshes report progress every ten seconds and identify missing chunks and maps with no generated terrain.
- Avoids terrain scans and unnecessary async processing for absent chunks, including Nether depth slices.
- Nether walls and held maps retain their required lock state so vanilla updates cannot overwrite the below-roof rendering.
- End islands remain visible and End void stays transparent.
About a 10×10 scale-4 wall: It covers 20,480×20,480 blocks, or up to 1,638,400 chunks. The default rendering.generate-missing-chunks: false displays existing terrain only. Ungenerated areas stay transparent until you explore/pregenerate them and refresh the wall; waiting alone cannot reveal terrain that does not exist. Use scale 0 or 1 for a local wall. New generation remains explicitly opt-in.
Configuration: rendering.lookup-chunks-per-tick defaults to 256. rendering.capture-chunks-per-tick remains 16. Existing configurations use these defaults when the new setting is absent.
Validation: Maven clean verify and terrain/buffer regression tests; live 10×10 scale-4 Overworld wall, scale-4 End/Nether walls, held maps in all three dimensions, saved/client pixel buffers, and server restart persistence on Paper 26.2.