Dynmap: Overview of the 3D Online Map Plugin for Minecraft

In multiplayer Minecraft, coordinating between players, finding free areas for building, and tracking activity across large territories often present challenges. Basic tools offer only local paper maps that do not cover the entire world and do not update in real time. The Dynmap utility solves this problem by creating an interactive map of the game world accessible through a regular web browser. It operates on the principle of geographic information services like Google Maps, displaying detailed terrain, player locations, claimed region borders, and in-game chat messages.

Rendering Engine Operation and Tile Saving

At the core of Dynmap's functionality lies its custom rendering pipeline, which converts three-dimensional Minecraft chunk data into a set of two-dimensional graphic files (tiles).

Rendering Types and Projections

The plugin supports three main world display options:

• Flat view: A classic 2D map with a top-down view. It consumes the least disk space and CPU resources during generation.

• Isometric 3D view (Surface): A volumetric three-dimensional projection at an angle, allowing you to evaluate landscape elevation changes, building architecture, and water depth.

• Cave view: Renders underground cavities and mines, showing the structure of caves below surface level.

File Saving and Disk Load

All generated map tiles are saved as standard PNG or JPG images in the plugins/dynmap/web/tiles/ folder. With every block change by players (building, destruction, explosions), Dynmap triggers an incremental update process — only the tiles directly within the updated chunk area are redrawn.

The server's disk subsystem experiences significant load (I/O operations) during the initial world rendering. At high resolutions, the tile folder for a large map can reach tens or even hundreds of gigabytes, which requires fast SSD storage and setting a WorldBorder.

alt: [Dynmap web map interface in a browser showing a 3D isometric view of the spawn]

Web Server Infrastructure: Jetty vs Nginx

Dynmap offers two deployment schemes for the web interface, depending on the server scale and expected load.

Built-in Jetty Web Server

By default, after installation, the plugin automatically launches an integrated Jetty web server on port 8123. This option requires no additional configuration: the administrator simply needs to open port 8123 on the hosting provider, after which the map becomes accessible at http://Server_IP:8123/.

Integration with an External Server (Nginx or Apache)

For public servers with high player counts, the built-in Jetty creates additional overhead for the Java game process, as every web user consumes traffic directly through the game server. For optimization, it is recommended to configure tile delivery through an independent Nginx or Apache web server.

In this setup, Nginx is configured to work directly with the web/tiles/ folder, bypassing the Minecraft game engine. This has several key advantages:

• Game Thread Protection: Browser requests are handled by a separate web server, eliminating micro-stutters (TPS drops) in the game.

• HTTPS Encryption: The ability to easily configure free Let's Encrypt SSL certificates for a secure connection.

• Offline Availability: The web map of the terrain remains accessible for viewing even when the Minecraft game server is restarting or turned off.

Configuration Settings and Rendering Management

The plugin's main parameters are edited in the plugins/dynmap/configuration.txt file.

General Rendering and Saving Settings

Web Infrastructure and File Paths

Configuring Web Interface Components (Web Chat, Markers, Players)

Optimization and CPU Performance Limits (TPS/MSPT)

Optimization Parameters in configuration.txt

To preserve server performance, pay attention to the following configuration file variables:

• deftemplatesuffix — rendering quality suffix. Values like vlowres (very low quality) or lowres (low) allow for significantly faster map generation and reduce file sizes by 4-8 times compared to the standard hires.

• tilespath — allows redirecting map saves to a different server hard drive, protecting the primary storage from overflow.

• webserver-port — port for connecting to the map (instead of the standard 8123).

Render Management Commands

Map generation is controlled through the server console by a level 4 operator:

• /dynmap fullrender <world> — starts full rendering of the specified world. It is recommended to run this only after full chunk pre-generation and during periods of low online activity.

• /dynmap radiusrender <radius> — updates the map only within a certain radius around the player, which is convenient after building large cities.

• /dynmap cancelrender — stops current rendering processes in case of CPU overload.

• /dynmap pause all — temporarily pauses all map calculations, freeing up resources to stabilize TPS.

Conclusion

The Dynmap plugin is a powerful tool for world visualization and improving player interaction on large Minecraft servers. Thanks to isometric 3D rendering and web interface integration, it transforms the map into a full-fledged information portal for the project.

Compared to alternatives like BlueMap (which uses heavy WebGL for full 3D viewing) or Squaremap (which offers an exclusively fast 2D map without volumetric models), Dynmap provides an optimal balance of functionality. However, high disk space requirements and constant I/O load demand careful attention from administrators regarding world limits and the correct choice of resolution. The plugin is an excellent choice for large survival servers, anarchy, or RP worlds.