How bluemap-minecraft/bluemap works
Project type and purpose
• BlueMap is a multi-module Java/Kotlin application for reading Minecraft world files, rendering 2D/3D map data, and serving a browser-based frontend.
• It ships as (a) a standalone CLI tool, (b) plugins/mods for various Minecraft servers (Spigot/Paper, Forge, Fabric, Sponge), and (c) an embedded HTTP server + webapp for interactive map viewing.
File structure
• Top-level Gradle multi-project (settings.gradle.kts) with subprojects:
• core – the map-generation engine (world parsing, tile & model rendering, storage).
• common – shared services (config management, command framework, HTTP server, addon/plugin API).
• api – interface definitions for external extensions.
• implementations – per-server/serverless deliverables:
· cli – standalone command-line invocation
· fabric, forge, neoforge, paper, spigot, sponge – server mods/plugins forwarding events to BlueMap
• common/webapp – Vue.js + raw JS static frontend (Map Viewer).
• resourceExtensions – default Minecraft assets & JSON resources (blockstates, models, textures).
• buildSrc contains custom Gradle logic (publishing, versioning, copying files).
• Configuration files: gradle.properties, Dockerfile, CI workflows, sample .conf under common/src/main/resources.
README for additional insights
• BlueMap reads world files asynchronously, renders 3D geometry, serves via webapp.
• It is extensible: plugin API, addons.
• Features include low-res & high-res rendering, mask configurability, multiple storage backends (file, SQL).