Publish a squaremap world map with a separate web port

squaremap provides a top-down Minecraft map in a browser. Its web port, public link and rendering settings have different purposes. Setting a public URL does not open a listener or make an unallocated port usable.

Check the release and preserve existing data

Choose the release for your exact server platform and Minecraft version through the project's download links. A Paper plugin and a Fabric or NeoForge mod are different artifacts. Check that release's Java requirement and dependencies rather than using the build prerequisites for developers as a player installation checklist.

Stop the server normally and create a completed backup. Preserve squaremap's configuration and generated web files when updating, particularly if you have customised markers or extensions. Keep a recovery copy outside the server. See game backups and plugin installation.

Configure web access

1. Install the matching file and start once. Confirm that squaremap enables before editing its generated configuration.
2. Stop again and open its config.yml. Find settings.internal-webserver, preserving the generated YAML indentation.
3. Use the internal web server for an ordinary installation. Set its port to a separate TCP allocation assigned to this game server. Ask support if you do not have one.
4. Review the generated binding setting with support if the listener is not reachable. Do not bind to another customer's address or to an arbitrary private management address.
5. Set settings.web-address to the intended player-facing map URL. It describes a link; it does not create DNS, enable HTTPS or change the actual listener port.

Start and read the first startup messages. Open the assigned map endpoint from outside the server network. If you require HTTPS on a domain, arrange the web-proxy side separately instead of assuming that changing the URL enables encryption.

Check world identity before requesting a render

Use the installed command help to identify the world argument squaremap expects. Current upstream documentation distinguishes dimension identifiers from legacy Bukkit world names. Copy the identifier reported for the running world rather than guessing from level-name or a folder path.

Start with a small radius render using the documented /map radiusrender syntax for that build. A player can use their current location where the command supports it; Console needs the relevant explicit arguments. Watch render progress, CPU load and disk usage before expanding the test.

A map render is not a terrain-backup operation. Avoid resetmap during diagnosis: upstream documents it as deleting that world's generated tiles without undo. Cancelling or pausing a task and preserving its files is safer than repeatedly resetting the map.

Review visibility and troubleshoot

Decide which worlds and player markers should be public. Inspect visibility limits before a large render; changing a limit does not necessarily remove tiles already generated outside it. Test the map using an ordinary browser session rather than only an administrator account.

If the web page loads but a world is blank, inspect the render target and progress. If it times out entirely, inspect the port and listener instead. Send support the version, server ID and exact error. Further reading: default configuration and commands and permissions.

Looking for another plugin? Browse the Minecraft plugin guide directory.