Перейти к содержимому

squaremap 1.3.13.3 для Minecraft 26.1.2 (Fabric)

Релиз9 октября 2026Minecraft 26.1.2Fabric79 скачиваний на Modrinth
Это не последняя версия. Последняя для 26.1.2 · Fabric — 1.3.13.5Открыть 1.3.13.5 →

Файлы · 1

squaremap-fabric-mc26.1.2-1.3.13.3.jarОсновной8,59 МБСкачать
Основной · 8,59 МБ
SHA-1957e7c811060625e3233510031fd23b63bca84d2SHA-5128af58ad181c084ec30cd511a15d15a596889d94138fb6633dc31c843abd2c1d05dfa8d1341842da4dac0bd46541a5cf9e9f89e826b84c47a30d4c57f65091c14
Скачать

Что изменилось

Changelog

Performance

Full renders are much faster. In our benchmark with default settings, a full render on Paper took 14.03 s instead of 38.59 s, a 2.75× speedup, using half as many render workers and producing identical output (Ryzen 9 5950X, 288,369 chunks, Minecraft 26.3). (#601, #610)

Full render: 38.59 s → 14.03 s with default settings

  • Rewrote the rendering pipeline: renders work through a bounded number of regions at a time, scanning runs on a separate CPU worker pool, chunk and neighbour loads are planned ahead and shared, and region images are saved by multiple writers (#610)
  • Read unloaded chunks directly from region files off the main thread on Paper, and on Fabric and NeoForge with the Moonrise mod installed (recommended) (#601)
  • Skip biome blending when every position in the blend window is the same biome
Breakdown: renderer rewrite vs. direct snapshot loading

On its own, the renderer rewrite is 1.21× faster without direct snapshot loading and 1.48× faster with it.

Full render times with and without direct snapshots

Changed
  • Render settings are now set per render mode under map.render.<full|radius|background>, and image saving is configured under map.image-saving. Existing configs are migrated automatically (config version 3)
  • Default render worker counts are lower on machines with more than 8 threads. Configs using the old automatic default (-1) migrate to default and get the new counts
  • The default max-chunks-per-interval for background renders is raised from 1024 to 2048. Configs still set to 1024 are migrated to 2048; other values are kept
  • Radius renders now resume after a restart, like full renders; resumed renders skip chunks that are no longer visible
  • Visibility limits, the world border and render settings are captured when a render starts
  • Queued image saves are always completed at shutdown instead of being dropped after 5 seconds
  • Region scanning log messages now name the world, and image read/save errors name the file; the could-not-*-region locale keys are now could-not-*-image
  • Removed squaremap-client support
  • Mark Moonrise versions older than 1.0.1 as incompatible on Fabric and NeoForge (Moonrise is still optional)
  • Update dependencies
Fixed
  • Fix world configs retaining worlds unloaded at runtime #600
  • Fix partially upgraded terrain being rendered for retrogen chunks (#601)
  • Fix terrain shading next to fluids (#604)
  • Fix inconsistent shading across chunk and region boundaries in all render types
  • Fix the first run limiting rendering to the world border even though the generated config showed the limit as disabled
  • Fix full renders failing for dimensions that have never saved a chunk
  • Fix /squaremap resetmap leaving tiles from in-progress renders and queued image saves in the reset map. It now refuses to run while a full or radius render is in progress
  • Fix markers.json and other web files not being rewritten after a map reset when using an external web server
  • Fix unreadable render progress being warned about on every startup
  • Fix background renders losing claimed chunks in some cases, such as when stopped while planning
  • Fix progress logging: the ETA no longer wraps after 24 hours, a final line is logged when a render ends, and re-enabling logging mid-render works
  • Sponge: fix commands failing to register

Зависимости этой версии

Fabric APIобязательная · 0.155.3+26.1.2 для 26.1.2Скачать для 26.1.2 · Fabric
Moonriseнеобязательная · 1.0.2+ea9fc28Скачать для 26.1.2 · Fabric

Сайт использует cookie: необходимые — для входа и темы, а также счётчики посещений Яндекс Метрика и LiveInternet — по ним мы видим, как пользуются сайтом. Рекламных cookie у нас нет. Подробнее