{{ articleTitle }}
{{ articleLede }}
{{ b.text }}
{{ b.text }}- {{ item.text }}
- {{ item.text }}
{{ heroYue }}
A from-scratch TypeScript port of BlueMap, the Minecraft world renderer and 3D web map.
Render from a desktop application, or from a GitHub Actions run with nothing installed at all, and browse it in an interface rebuilt from the ground up in Material Design 3.
This build of the site did not find a published release with a verified installer attached, so it offers no download. Nothing here guesses a URL.
Windows only, and permanently unsigned by choice — SmartScreen will warn. Rendering needs Java, which the app fetches into its own folder.
The server wizard offers read-only checks for a saved SSH host, proposed memory and port. SSH trust, Linux services, folder, Java and resource observations do not install or start a server; Next and Create stay disabled. Controlled Linux SSH and native Electron wizard checks pass; Windows and deployment-host acceptance remain pending. The delivery inventory tracks 107 requirements, with 505 surface requirements still pending as of 2026-10-15. Read “Read-only SSH-process readiness” and “Maintained viewer build ordering” in the documentation for the workflow and build limits.
SSH 程序新增唯讀準備檢查,可以揀已儲存主機、記憶體同連接埠。SSH 信任、Linux 服務、資料夾、Java 同資源檢查唔會安裝或者開服,下一步同建立仍停用。Linux SSH 同原生 Electron 精靈受控檢查通過,Windows 同部署主機驗收待完成。截至 2026-10-15,清單有 107 項要求,505 項介面要求仍待完成;要求數量唔代表完成數量。文件內嘅「Read-only SSH-process readiness」同「Maintained viewer build ordering」載有流程同建置限制。
A world you render locally is rendered by upstream BlueMap's own Java engine, built from the vendored source and driven by the application as a child process. The TypeScript mesher this project exists to write passed its byte-comparison parity gate on 2026-08-04 and still does not render anything in the product. Every render records which engine produced it.
A port of a renderer is not one file, and none of these numbers are marketing. Each one is countable from the repository, and the line beneath it says where.
Every row is built, unit tested and reachable by clicking. Each links the article that states its behaviour, configuration, failure modes and verification.
Everything above assumes some BlueMap vocabulary already. This does not.
Laid out side by side so nobody has to infer which is which.
Built from the vendored source and driven by the app as a child process, so a world can be rendered now rather than after the port finishes.
961 of 961 hires tiles equal byte for byte, all 24 lowres tiles equal pixel for pixel, on 2026-08-04. Switching over is a separate change with its own verification.
Captures taken by the project's own harness in continuous integration, not mockups.
Finite walkthrough animations with static reduced-motion fallbacks. They are explanatory media, not deployment proof.
An article for every feature, covering behaviour, configuration, failure modes, security considerations and verification. {{ articleTotal }} articles, straight from the repository's own docs/ folder.
{{ cat.lede }}
{{ articleLede }}
{{ b.text }}
{{ b.text }}Captures of the real running application, taken by the project's harness in continuous integration. Nothing here is a mockup or a redraw.
{{ shotsSummary }}
{{ g.description }}
{{ s.state }} {{ s.commit }}
Every setting is declared once, searchable, exportable and resettable. Six groups; open one to get a focused page rather than a wall of controls.
{{ groupDesc }}
Every entry is one commit, carrying the full SHA so the claim can be checked. Entries are grouped by the area of the repository they changed — never inferred as feature or fix.
History only — this surface never interrupts. Toasts appear at the corner of the running application; what they said is kept here.
The site ships every article it links, so a missing page means the address was typed, guessed or came from an older deployment. Nothing was fetched from anywhere else to find it.